We have implemented a process where in two user steps (the second of which is an

vasileiosp over 8 years ago

We have implemented a process where in two user steps (the second of which is an optional step, which is not always executed) the user selects a specific Date & Time (sets a variable) for a Timer (in another point of the flow) to be triggered. This Timer starts the execution of a 1-2 nodes that will later converge to the main flow. In the 2nd of these steps, the user may select a different Date & Time for the execution of the timer (i.e. the 2nd user can override the selected Date & Time by the 1st user).

The issue is that, when the 2nd user overrides the Time & Date we cannot find a way to deactivate the timer activated by the 1st user and to activate it again and set the Date & Time selected by the 2nd user. In fact, when the timer is activated once (through a connection in the flow, directly after the 1st user step), and the variable that controls the timer changes later on, the timer is not reset. If however, the timer is re-activated (through...

Discussion posts and replies are publicly visible

0 vasileiosp over 8 years ago

... a 2nd connection in the flow), then we have two instances activated, which is not the desired outcome...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Shyam Bommakanti
Certified Lead Developer
over 8 years ago

The behavior is as expected. To achieve what you want, if it's possible, use subprocess for the timer. And have a rule event to terminate if the timer changes and initiate a new subprocess with new date/time.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel