| The state of a form record can be changed using something like a state endpoint. This event occurs once after the form record has remained in a particular state for a certain amount of time following a state change. If the state is changed again before the time to scheduled execution expires, the scheduled event is deleted and no longer occurs. If a state endpoint is passed through, where the target state is the same as the current state of the process, this is considered a state change and a new event is scheduled and the old one is deleted. CONTENTS
|
Parameters
State and delay
- Duration in state until event fires
- Indication of the delay time in days, hours and minutes.
- After change to state
- The event occurs after a state change to one of the selected states. If no status is selected, the event occurs after every state change.
System variables
Events of type After state change provide system variables which can be used in subsequent actions.
Default variables
- [%$TRIGGER%]
- Can be used in the new workflow to access the data provided by the current event. This data will be returned as JSON. The individual values of the event can be accessed via JsonPath (see [%$TRIGGER.<JSON_PATH>%]).
- [%$TRIGGER.<JSON_PATH>%]
- Depending on the type of event, different information is provided via the event variables. Specific information of the event can be accessed via JsonPath. Which information the different event types provide can be seen via the infobox at the event.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article
