1 ACCEPTED ANSWER
Hi Gilberto,
I am just curious why this must be a script? There may be some reasons NOT to do it this way, but you can use recursive native workflow to delay for five (or more) seconds. This is wont be exactly five seconds, but depending upon how important pausing for exactly five seconds is and you have a bit of wiggle room - as in 5.1-6 seconds wont mess up the processes - this seems to work for me in version 15. not sure when the expression function ceil became available though so your results may vary:
- using the action Set Property to Expression create propWaitUntil property and set it equal to ceil(now()*24*60*60)+5. This sets the current date time in seconds (24 hours a day, 60 minutes an hour, 60 seconds per minute) to five seconds in the future.
- using the action Set Property to Expression create propNow property and set it equal to ceil(now()*24*60*60). This captures the current date time in seconds.
- using the rule Compare Property Value set PropWaitUntil is < propNow indicating that the time I had set to wait for in the future (that is + 5 seconds) is less than the time (in seconds) now, so the wait has been completed
- Under True branch (wait is over)
- I added a message box stating that five seconds are up
- Under True branch (wait is over)
- BREAK - I added a break after the message box, but you would not want it because it prevents what ever comes after the Task List from being evaluated. I would avoid putting steps unrelated to waiting five seconds in this task list. That way you could just copy/paste this Task List next time you want a five second rest and not worry that you have other actions/rules that are NOT strictly involved with waiting five seconds
- In the false branch
- drag and drop or copy/paste the same action that created propNow
- Copy and paste the Rule created above into the False branch
the whole thing looks like this - note that you can keep expanding false branch of the rule forever and will keep getting the repeat. versions ago if you shift + right arrow, the configuration client (where workflow used to be configured) would crash as the branches kept expanding. that does not happens in Studio (*phew*). I only expanded three false branches, but you get the idea
so I am very interested in hearing why i should not do this 😉 I get it may take up more processing power than a script, but how much more and how big of an issue is that?
thanks all - I am looking forward to the comments !
