How to Add a 3-Second Delay Before Displaying Data in a Repeating Group After Button Click?

jenil.kukadiya · 2024-10-14T09:31:17.326Z

Hi everyone, I want to display the data in a repeating group 3 seconds after clicking the ‘Generate’ button. How can I set a time delay so the data appears in the repeating group after 3 seconds? Any suggestions on how to achieve this?

jenil.kukadiya · 2024-10-14T09:43:28.205Z

@adamhholmes @boston85719 have you any idea?

JDeltree · 2024-10-14T10:25:18.711Z

If I understand your request, you can use the “Add a pause before next action” and set it to 3 seconds.

jenil.kukadiya · 2024-10-14T10:31:22.760Z

image1909×948 34.2 KB

image1508×943 41.9 KB

I have a form where users can enter a start date and end date. When they click the Generate 1 button, a workflow is triggered to fetch employee data, including Employee Email, Working Days, and Total Minutes.

I want to introduce a 3-second delay after the user clicks Generate 1 or Generate 2, before displaying the data in a repeating group. How can I set up this delay in the workflow?

Here’s what I’ve set up so far:

The user inputs start and end dates.
The workflow is triggered by clicking Generate 1.
I want the repeating group to show the fetched data after a 3-second delay.

Any guidance would be appreciated!

jenil.kukadiya · 2024-10-14T10:31:35.039Z

@JDeltree

JDeltree · 2024-10-14T10:43:24.389Z

Curious, why do you want a 3 second delay?

From the screenshots, I can see that the list is generated via a backend workflow which means you cannot quite estimate how long it would take yes? If your goal is mostly UX driven, then I’d suggest creating a custom event. Something along the lines of:

When button is clicked > [step 1] Add a pause before next actions (3 seconds) > [Step 2] Show Repeating Group

Perhaps if I know why you require the delay, I can profer an alternate solution.

jenil.kukadiya · 2024-10-14T10:48:49.135Z

Hi @JDeltree

I have a form where users input a start date and end date. When they click the Generate 1 button, a backend workflow is triggered to fetch and store employee data (Employee Email, Working Days, and Total Minutes) in the database.

The backend workflow may take around 5 seconds to complete as it creates entries for all employees in the database. I want the repeating group to display the data only after the backend workflow finishes. How can I ensure the repeating group waits for the workflow to complete before showing the employee data?

Here’s the process so far:

User enters the start and end dates.
Clicking Generate 1 triggers the backend workflow to create employee entries.
I want to delay showing the data in the repeating group until after the backend workflow is fully completed and all entries are created in the database.

Is there a reliable way to detect when the backend workflow finishes so that the data can be shown without relying on a set delay?

adamhholmes · 2024-10-14T10:55:27.212Z

Just schedule a Custom Event to run 3 seconds after the button is clicked.

That custom event can either ‘show’ the RG, or ‘Display’ the relevant data in it (or whatever you want).

JDeltree · 2024-10-14T10:57:23.886Z

You can return data from the API workflow if scheduling a custom event will not suffice. See - Loader in front-end while backend workflow is ongoing

adamhholmes · 2024-10-14T11:02:55.933Z

Yeah… if you need to wait until the backend WF has actually finished (and not just some arbitrary amount of time), then you’ll need to establish when that is the case.

One simple way is to set some value in the Database in the backend WF itself, and then use that as a trigger on the page.

The other way is to User the API connector (or even the App connector) which will allow to to get a response from the backend WF.

jenil.kukadiya · 2024-10-15T10:36:39.724Z

image1919×879 33 KB

image1565×895 34.2 KB

image1265×859 32.2 KB

image1228×948 35.6 KB

I’m working with an external API that only returns 100 employees at a time. Our company currently has 115 employees, so I need to call the API twice—once with start index = 0 and then again with start index = 100.

In my current setup, I have two separate workflows that are almost identical, except for the start index parameter. Both workflows trigger the same backend workflow to handle the API response and store the data.

Is there a way to merge these two workflows into a single button click (i.e., one workflow) that calls the API twice with different start index values and processes the results accordingly?

I would like to avoid creating redundant workflows for this.

Thanks in advance for your suggestions!

jenil.kukadiya · 2024-10-15T10:36:50.160Z

@adamhholmes @JDeltree

jenil.kukadiya · 2024-10-15T12:08:59.180Z

@boston85719 @adamhholmes @JDeltree can you help me to resolve this issue?

kirsnvartem · 2024-10-15T15:08:03.547Z

Hi @jenil.kukadiya,

Have you tried organizing all the logic into a single workflow? You can start by triggering the 1-100 call, and in the second step, trigger the 101-115 call. Afterward, you can combine the two responses (lists) and continue with your logic aka Result of step 1 + Result of step 2. This way, you don’t need to repeat the process twice.

PS: If you have access to the company’s API or can reach out to the developers, ideally, you could just fetch all 115 items in one go instead of 100. I don’t see any issues arising with this small number.

Hope this helps! Let me know if you need more assistance.

Best,
Artem

jenil.kukadiya · 2024-10-16T05:10:29.037Z

Hi @kirsnvartem

image1383×788 32.1 KB

Here i cann’t able to add both of this results(result1 and result2) data. Can you tell me how can i add this? And i am using the external api which gives only 100 employees data at a time so i don’t have a rights to changes in api’s responses.

jenil.kukadiya · 2024-10-16T05:12:25.618Z

Hi @adamhholmes ,
I didn’t get the simple way you have mentitioned.Like using set some value in the Database in backend workflow can you tell me with proper examples where should i change?

system · 2024-12-23T09:31:21.926Z

This topic was automatically closed after 70 days. New replies are no longer allowed.