Approve Transaction

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

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.
    Behavior of the workflow

    • The normal workflow continues when EVERYONE approves.
    • If someone denies, the workflow continues with the rejection path.
    • If the action expires or is canceled, the workflow continues with the exception path.
  • Select Require approval from the majority on the list to assign everyone in the list.
    Behavior of the workflow

    • The normal workflow continues when the majority (for example 6 out of 10) approves. This also happens if not everyone has responded yet, but there is already a majority who approved: The people who did not respond will be skipped.
    • If the majority denies, the workflow continues with the rejection path. This also happens if the number of people who approved and who denied is the same.
    • If the action expires or is canceled, the workflow continues with the exception path. This also happens if the number of people who canceled the action is larger than the number of people who denied.
  • 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.
    Behavior of the workflow

    • The normal workflow continues when the Number or Percentage is reached or exceeded.
    • The number of people based on a Percentage is always rounded up.
      Example:
      10% of 11 people = 1.1 people, which Identity Director rounds up to 2.
      In this scenario, the transaction needs approval of 2 people.
    • If the number of rejections or cancellations of approval makes it impossible to reach the required number of approvals, the workflow continues with the rejection path.
      Example:
      From a list of 3 people, 2 approvals are required.
      If 2 people reject or cancel, it is not possible to reach the required number of approvals.
    • If the Number of required approvals is higher than the number of people on the list, the workflow continues with the exception path.
      Example:
      The Number of required approvals is 5.
      During the transaction, the smart rule resolves to 4 people.
      Even if all 4 people on the list approve the transaction, the required number of 5 approvals cannot be reached.

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.
  Behavior of the workflow

  • The normal workflow continues when EVERYONE approves.
  • If someone denies, the workflow continues with the rejection path.
  • If the action expires or is canceled, the workflow continues with the exception path.
• Select Require approval from the majority on the list to assign everyone in the list.
  Behavior of the workflow

  • The normal workflow continues when the majority (for example 6 out of 10) approves. This also happens if not everyone has responded yet, but there is already a majority who approved: The people who did not respond will be skipped.
  • If the majority denies, the workflow continues with the rejection path. This also happens if the number of people who approved and who denied is the same.
  • If the action expires or is canceled, the workflow continues with the exception path. This also happens if the number of people who canceled the action is larger than the number of people who denied.
• 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.
  Behavior of the workflow

  • The normal workflow continues when the Number or Percentage is reached or exceeded.
  • The number of people based on a Percentage is always rounded up.
    Example:
    10% of 11 people = 1.1 people, which Identity Director rounds up to 2.
    In this scenario, the transaction needs approval of 2 people.
  • If the number of rejections or cancellations of approval makes it impossible to reach the required number of approvals, the workflow continues with the rejection path.
    Example:
    From a list of 3 people, 2 approvals are required.
    If 2 people reject or cancel, it is not possible to reach the required number of approvals.
  • If the Number of required approvals is higher than the number of people on the list, the workflow continues with the exception path.
    Example:
    The Number of required approvals is 5.
    During the transaction, the smart rule resolves to 4 people.
    Even if all 4 people on the list approve the transaction, the required number of 5 approvals cannot be reached.

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.

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 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.