Configure smart rules for a list of people

In the Management Portal at Data Model > Smart Rules, configure sets of criteria that you can use in services to dynamically determine to whom workflow actions apply during a service transaction. Smart rules for a list of people apply an action to a random actor on a list of people.

Configuration

Field

Explanation and Tips

Criteria

In the Criteria area, configure the list of people.

  • You can base the list on people and organizational context.
    • If you specify multiple organizational context items, the rule is applied to people who are classified in ALL items. Click Insert OR to specify that people only need to be classified in ONE item.
    • If you specify multiple persons, an OR criterion is added; a person can never be another person as well (i.e. Amanda Cavendish can't also be Dan Harris).
  • Click NOT to exclude specific persons and/or organizational context.
  • Click the arrows to create groups of criteria.

Diagnostics tab

View who matches the rule.

Smart Rule Behavior

For certain actions, you can further specify whose response(s) from the group of people are required to continue the workflow. This allows Ivanti Identity Director to handle actions more efficiently. For example, when you use this smart rule type in an Approve Transaction action, you can enforce unanimous approval from the group before the workflow is allowed to continue. In a Provide Information action, you can use smart rules to obtain information more efficiently by requesting it from the group and continue with the transaction as soon as a group member has provided it.

Workflow action

Explanation and Tips

Approve Transaction

  • Select Assign to one person on the list to assign a person from the list.
    • If there isn't a 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, the same actor is assigned.
    • If there is a preceding action with the same smart 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 all people on the list. The workflow continues as soon as someone approves.
  • Select Require approval from all people on the list to assign all people on the list. The 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 all people on the list. The workflow continues when the majority (e.g. 6 out of 10) approve. This also happens if a majority is reached before everyone has responded: Those who did not respond are 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 majority canceled the action.

Perform Tasks

  • Assign to one person on the list
  • Assign to all people, proceed with first response
  • Select Require all people on the list to complete the tasks to assign all people. The workflow continues when EVERYONE completes ALL tasks.

Provide Information

  • Assign to one person on the list
  • Assign to all people, proceed with first response
  • Select Require response from all people on the list to assign all people. The workflow continues when EVERYONE provides information. If the action expires or is canceled, the workflow continues with the exception path.

Send Message

  • Send to one person on the list
  • Send to all people on the list
See also

Was this article useful?    

The topic was:

Inaccurate

Incomplete

Not what I expected

Other