Configure smart rules for people related to the subscriber

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 people related to the subscriber apply an action to the first person they can find who is related to the subscriber.

Configuration

Field

Explanation and Tips

Properties tab

  • In the Look up related people in field, specify the organizational context in which people related to the subscriber are classified.
  • Select at least one relationship type.
    • Select Direct relationship to include people who are classified in the same organizational context as the subscriber.
    • Select Hierarchical relationship to include people who are classified in a parent organizational context of the one in which the subscriber is classified.
    • Select Direct relationship AND Hierarchical relationship to search for related people with a direct relationship, or if no match is found, related people higher in the hierarchy.
  • Optionally, select Additional criteria to apply additional, restrictive criteria. You can configure these criteria on the Additional criteria tab.

Additional Criteria tab

  • When you specify organizational context, you can choose to include subitems. Organizational context that includes subitems appear with \* in the list.
  • If you specify multiple organizational context items, people must be classified in ALL items before the rule applies. Click Insert OR to specify that people only need to be classified in ONE organizational context item. You can also use OR to create groups of organizational context items.
  • Click NOT to exclude specific organizational context.
  • Click the arrows to create groups of criteria.

Diagnostics tab

View who matches the rule.

Example 1

Consider the following situation:

Subscriber

John Smith

Smart Rule

Classifications:

  • Locations\London\Sales

Classifications:

  • Locations\New York\Sales

Look up related people in: Locations\*

  • [x] Direct relationship
  • [0] Hierarchical relationship
  • [0] Additional criteria

In this situation, the smart rule does not yield John Smith: John is not classified in the same organizational context as the subscriber; there is no direct relationship.

Example 2

Consider the following situation:

Subscriber

Amanda Cavendish

Smart Rule

Classifications:

  • Locations\New York\Sales

OR

  • Locations\London\Sales

Classifications:

  • Roles\Employee
  • Locations\New York\Sales

OR

  • Roles\Manager
  • Locations\London

Look up related people in: Locations\*

  • [x] Direct relationship
  • [x] Hierarchical relationship
  • [x] Additional criteria

Additional criteria:

  • Roles\Manager

In this situation, the smart rule yields Amanda Cavendish:

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. When you use it in a Provide Information action, you can obtain information more efficiently by requesting it from the group and continue with the workflow 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) approves. 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