This is not the latest version of Identity Director documentation.
View available documentation.

Icon

Perform Tasks

Add the Perform Tasks action to ask someone to perform a list of tasks when the service is requested. For example, this can be the ordering of a new mail server, a laptop or a mobile phone.

Configuration

Field

Explanation and Tips

Action Name

Optionally specify a friendly name for the action. This name must be unique in the workflow.

Actor

Specify who should perform the tasks. Specify actors manually or use the drop down field to specify them indirectly.

Dynamic actors

You can use placeholders and/or functions to dynamically determine the actor(s) to which the action applies. When the action is executed, these resolve into a specific value. For example, this allows you to determine the actor by a previous action or by user input.

  • Use the Determine actor based on field to specify the placeholder and/or function that resolve in one or more actor(s). Specify a separator for multiple actors.
  • Use the Look up actor with person identifier field to specify the person identifier that identifies the actor based on input from the previous field.
  • Use the Action behavior field to specify what should happen to the action.
    • Select Assign to one person on the list to assign someone on the list. However, this may cause a delay in the workflow, for example if this person is away from the office and not able to respond.
      • If there is no preceding action with the same dynamic actor rule, a random actor is assigned.
      • If there is a preceding action with the same dynamic actor rule and one actor was assigned, this actor is assigned.
      • If there is a preceding action with the same dynamic actor rule and multiple actors were assigned, the actor who completed the preceding action most recently is assigned.
    • Select Assign to all people, proceed with first response to assign everyone on the list. The normal workflow continues as soon as someone responds.
    • Select Require all people on the list to complete the tasks to assign everyone on the list. The workflow continues when everyone has completed ALL tasks.

Smart rules

If you select a smart rule of type List of people or People related to subscriber, also specify its behavior:

  • Select Assign to one person on the list to assign someone on the list. However, this may cause a delay in the workflow, for example if this person is away from the office and not able to respond.
    • If there is no preceding action with the same smart rule, a random actor is assigned.
    • If there is a preceding action with the same smart rule and one actor is assigned, this actor is assigned.
    • If there is a preceding action with the same smart rule and multiple actors were assigned, the actor who completed the action most recently is assigned.
  • Select Assign to all people, proceed with first response to assign everyone on the list. The normal workflow continues as soon as someone responds.
  • Select Require all people on the list to complete the tasks to assign everyone on the list. The workflow continues when everyone has completed ALL tasks.

Message

Specify a message.

  • The markup editor supports styling functionality like headings, colors and numbered lists, but also hyperlinks and drag-and-drop.

Send e-mail notification

Enable e-mail notification for this specific action. This sends an e-mail to the user that a message has been delivered in the Web Portal, if you enabled E-mail Integration (at Setup > E-mail Integration).

  • This option is selected by default and in upgraded environments.
  • Clear the option to disable e-mail notification. This is useful in actions that send notifications to multiple actors as the result of a smart rule: it prevents unnecessary e-mail notifications. For example, if you configured a service with a Perform Tasks action that is sent to all actors on a smart rule list, and the workflow should proceed with the first response, you probably do not want to send this notification by e-mail. You can prevent this by disabling e-mail notification for this specific action.

Allow user to cancel this action

Allow the subscriber to cancel the action from the Status Details window in the Web Portal. Auto provisioning is not affected by this option. The Cancel option is only displayed:

  • if the service was requested by the subscriber;
  • when this action is Pending.
If the user cancels the action, the transaction will follow the exception path that was configured for this action.

Email reminder

Starting with Identity Director 2021.2, you can optionally notify the person that needs to approve or confirm the action, according to the time interval you input.

  • You can set the time interval to a number of hours, days, weeks, or months.

  • The system keeps sending notifications until the action is approved, canceled, or when it expires.

Expiration

Specify when the action expires. If the action has not been performed in time, it fails.

  • You can use placeholders to make the expiration time for the action dynamic.
    • When the action is executed, the placeholder needs to resolve into an integer (e.g. "9"). Invalid input (e.g. "Nine") causes the action to ignore the expiration time. The transaction continues immediately.

Workflow Detail

Specify the level of detail that is shown when people track the service status. Depending on your configuration of this field, the Label field specifies the status information.

  • Select Default to show the behavior that you configured at Setup > Behavior.
  • Select Status only to show the status of the service.
  • Select Workflow action to show the status of the action.
  • Select Full details to show the status of the action and its actor.
  • Select Use custom label to configure a custom text.

Tasks tab

View the list of tasks that are to be completed by the actor. This list is shown with check boxes in the Web Portal.

  • This action adds an exception to the workflow that specifies what happens when a user cancels the action or if it expires.
  • This action can be translated. The RESX file of the service that uses the action, contains the translatable fields.
See also