When you schedule a workflow in the client UI, you can provide values to some (or all) of workflow input parameters, so when the schedule is triggered and the workflow is executed, these provided parameters will be passed as actual parameters to the execution.
When you schedule a workflow programmatically, the keys of this properties parameter are the names of the workflow's input parameters, and the its values are the corresponding values for the input parameters.
Hi Ilian Iliev,
Thanks & Regards,
vRO provides a function System.sleep(milliseconds) that allows your code to wait a given number of milliseconds. Using this function, you can kind of simulate the behavior of setInterval and setTimeout by explicitly waiting when necessary.