Add the Jump action to redirect the workflow to another action and continue from there, instead of from the current location. This makes services more powerful and flexible, because specific parts of a service workflow can now be repeated or skipped. It also makes workflows failsafe, because you can now configure services that keep trying to provide an outcome until a condition is met.
For example, you can use the Jump action in services that:
- Create a Windows user account. Instead of failing the transaction if the account cannot be created because it already exists, the service can now try again by e.g. applying a number to the end of the account.
- Allow users to postpone a Run Book for a specific number of times.
You can implement the above examples by combining the Jump action with a Compare Attributes action and the function @[EVAL(<expression>)]. See:
Configuration
|
Item |
Explanation and Tips |
|---|---|
|
Action Name |
Optionally specify a friendly name for the action. This name must be unique in the workflow. |
|
Jump to |
Select the action to which the workflow is redirected, by clicking the Jump label ( |
) to the right of the action. You cannot refer to another - This action adds:
- a notification that shows to which action the workflow is redirected.
- an exception that specifies what happens when the action fails to redirect to the specified action.
- Jump actions are validated when you save the workflow. This ensures the workflow does not fail due to an invalid redirection.
- Misconfiguration of Jump actions in your workflow may lead to infinite loops when the workflow is executed.
- Each executed workflow action caused by Jump actions are shown at Transactions, with the number of times it is executed as a result of a Jump action. This makes it is easy to see what happened (e.g. for troubleshooting purposes).
- The status that is shown (pending, failed, success) is a representation of the latest status of an action.
- At Transactions, use the timeline view to navigate to a specific moment in time. The execution of the workflow does NOT result in multiple action instances. Instead, at each Jump action, the relevant part of the workflow is copied and inserted into the overall workflow.