A custom event does not occur automatically, but must be triggered manually by a user. This can be done, for example, via the inbox or by means of an action of the type "Trigger user-defined event". Furthermore, it can be defined which user groups can trigger this event in the inbox and which status the form record must have for this. CONTENTS |
Parameters
Restrictions
- Only allow for states
- This restriction concerns the execution of events in the inbox. If no status is selected, the event will be executed in any status.
- Allow only for user groups
- This restriction concerns the execution of events in the inbox. If no user group is selected, all user groups are allowed to execute the event.
System variables
Events of type Custom event 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