Hi All,
I have a requirement where first interface/section( with inprogress spinner gif) needs to be displayed for 5 seconds and then Second one.
I tried with refresh variable but we have minimum refresh interval of 30 seconds only.
Do we have any alternative way to do?
My Solution with 30 seconds interval ,
a!localVariables( local!currentTime: now(), local!waitingTime: a!refreshVariable( value: local!currentTime + intervalds(0, 0, 5), refreshInterval: 0.5 ), { if( local!waitingTime >= now(), a!sectionLayout(label: "First", contents: {}), a!sectionLayout(label: "Second", contents: {}),) })
Discussion posts and replies are publicly visible
Sorry, 30 seconds is the limit and there is no other way of doing it.
@Stefan Helzle Thanks for quick reply.
Can we delay displaying an interface to user? I tried to add timer event before User Input Task in PM but it's breaking activity chaining and user is redirected to start form after time event execution.
The way you mentioned will also not work as you found out.
Can you elaborate on what you want to achieve in a broader sense?
@Stefan Helzle
As you can see in above snapshot I am sending 1 file to XYZ system and then i am checking file transferred or not . If file transferred successfully then i get response in 2-3 seconds. If response is not received within 5 seconds that means it's failed to transfer.
Now the requirement is to keep user busy for 5 seconds so that i would get file transfer status.
On 'Wait Message' UIT , I have I have displayed a message that 'Transfer is in progress' but also i have provided button names as 'Next'. But user can click that button within millseconds and then flow will go into wrong path.
My normal solution to this is to offer the user the "wait message" interface accompanied by a button that says "check again", which they can spam-click if they like, since all it does is submit the form, exit to the process, and loop back to the same form again, until the background action is completed in which case they get a success message on that form and a different button to click.
I support Mikes approach.
[clicks nonexistent "like" button]
Make Sense.
Thanks Stefan Helzle Mike Schmitt