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

Icon

Approve Transaction

Add the Approve Transaction action to ask someone for approval to deliver or return the service, for example the manager of the subscriber to the service.

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 action. Specify actors manually or use the drop down field to specify them indirectly.

Dynamic actors

You can use attributes and 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.

  • In the Determine actor based on field, specify the attribute and/or function that resolve in one or more actor(s). Specify a separator for multiple actors.
  • In the Look up actor with person identifier field, specify the person identifier that identifies the actor based on input from the previous field.
  • In the Action behavior field, specify what should happen to the action.
    • Select Assign to one person on the list to assign someone on the list.
      • 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 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 approves.
    • Select Require approval from all people on the list to assign everyone on the list.
    • Select Require approval from the majority on the list to assign everyone in the list.
    • Select Require approval from a custom number of people on the list to assign everyone in the list.
      The following additional fields appear:
      • Value: Specify how many people have to approve.
      • Type: Specify if the Value you entered is a Number (larger than 0) or a Percentage (1-100). For both types the Value must be a whole number.

Smart rules

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

  • Select Assign to one person on the list to assign someone on the list.
    • 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 was 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 approves.
  • Select Require approval from all people on the list to assign everyone on the list.
  • Select Require approval from the majority on the list to assign everyone in the list.
  • Select Require approval from a custom number of people on the list to assign everyone in the list.
    The following additional fields appear:
    • Value: Specify how many people have to approve.
    • Type: Specify if the Value you entered is a Number (larger than 0) or a Percentage (1-100). For both types the Value must be a whole number.

Message

Specify a message.

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

Reason for Approval,
Reason for Rejection,
Reason for Exception

Allow Web Portal users to provide a reason to approve, reject, or provide an exception. Each of these can be set to one of the following values:

  • Disabled – no popup appears to the user in the Web Portal and the action is progressed
  • Optional – a popup appears to the user in the Web Portal and the action is progressed whether or not the user enters a reason
  • Mandatory – a popup appears to the user in the Web Portal and the action is progressed only after the user enters a reason

When upgrading from v10 or earlier, these fields are set to Disabled. When upgrading from v10.1 or later, each of these fields is set to match the value set in the single Reason field available in those earlier versions.

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 if notifications are sent to multiple actors as the result of a smart rule: it prevents unnecessary e-mail notifications. For example, if you configured a service with an Approve Transaction 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.

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 configured at Setup > Behavior.
  • Select Status only to show the status of the service.
  • Select Workflow step 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.
  • This action adds two exceptions to the workflow: one that specifies what happens when the request is rejected and one that specifies what happens when the action expires.
  • This action can be translated. The RESX file of the service that uses the action, contains the translatable fields.
See also