Example Jump action: Create a Windows user account

Add a Jump action to redirect the workflow to another action and continue from there, instead of from the current location. 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.

Configuration

In this scenario, the Jump action is used in a service that creates a Windows user account. If this fails, the service retries three times.

  1. In Ivanti Automation, configure a Run Book Onboarding that can create Windows user accounts.
  2. In the Ivanti Identity Director Management Portal, configure a service Create Windows user account.
  3. On the Attributes tab, configure a text service attribute Counter with initial value 1.
  4. On the Workflow tab, add a Compare Attributes action.
  5. In the True path of the Compare Attributes action, add a Send Message action that informs the user that the attempt to create a Windows user account failed after three times.
  6. Add an End Workflow action that sets the status of the transaction to Failed.
  7. In the False path of the Compare Attributes action, add a Set Service Attribute action.
  8. In the False path of the Compare Attributes action, delete the first End Workflow action. This is NOT the End Workflow action that was added as part of the exception path of the Set Service Attribute action. The workflow now continues after the Service Attribute action.
  9. After the Compare Attributes action, add an Invoke Run Book action that invokes the Run Book Onboarding.
  10. Consider adding additional service attributes and a Provide Information action to the workflow, to ensure the Run Book is executed with the correct information.
  11. In the exception path of the Invoke Run Book action, add a Jump action that redirects the workflow to the Compare Attributes action that you configured in step 4.
  12. Save the service.

Service Request

In this scenario, when the service is requested:

  1. The service placeholder #Service[Counter] in the Compare Attributes action is compared if it equals "3". Because this is the first attempt to create a Windows user account, the value is 1.
  2. The workflow continues with the Set Service Attribute action, who sets the value to 2.
  3. Next, it executes the Invoke Run Book action and tries to create a Windows user account. Let's assume that the action fails (e.g. because the Windows user account already exists).
  4. The workflow continues in the exception path of the Invoke Run Book action and executes the Jump action.
  5. The Jump action redirects the workflow to the Compare Attributes action in step 1.
  6. Here, the value of service placeholder #Service[Counter] is compared again, etc.

The workflow continues until either the Invoke Run Book action is successful or the value of service attribute Counter equals 3.


Was this article useful?    

The topic was:

Inaccurate

Incomplete

Not what I expected

Other