Final action (workflows)
Final actions can be defined here. These are executed after the workflow job has reached any end state and before it is terminated.
In the following cases the final action is not executed (because the workflow job gets terminated but no end state has been reached).
If a workflow job was manually terminated in the Control Center.
If a workflow job was terminated due to the use of the stop workflow () function or the REST call kill.
If a workflow job was terminated due to a waiting time reached in a state. Here, however, (local) final actions valid for this state can be defined.
Settings
(1) Final action after workflow finished: If this checkbox is set and the workflow job has reached an end state, final actions (4) can be executed.
(2) Documentation URL: Here you can specify any URL that contains documentation of these actions, which can be called via the icon on the right. You can also insert system constants into the URL there.
(3) Set conditions: Only if there are no conditions or if the conditions are fulfilled, the actions (4) are executed . If the conditions are not fulfilled, no actions will be executed, but the workflow job will still be terminated. Note: Either the calculated value or a fixed value can be used as the result of each individual function.
(4) Actions: Actions to be executed (profiles, other workflows , ASM entries, ETL/ELT pipelines, Content Inspectors) if the check in (3) is successful. If you use profiles, you have to distinguish between cron profiles ( time-driven ) and non-cron profiles ( event-driven ). For cron profiles, always set option Start cron profile via the context menu . This marks that the profile is only triggered and fetches its own data. Non-cron profiles get their input data from the workflow variable VAR_SYS_WF_DATA or VAR_SYS_WF_FILE (see details there). If the variables do not supply any data, the profile generates an error.
Each action by itself can be executed only once, but any number of actions can be selected, i.e. a profile MyProfile can be selected only once, but further profiles can be added. The same applies to the other action types.
If more than one action is specified, the behaviour of the action chain can be defined if one of these actions fails. If an action fails and Ignore error is set, the action chain simply continues. If an action fails and Stop on error is set, the action chain terminates.