Previous Topic: Policy DescriptionNext Topic: Attributes Highlighted as Changed on Workflow Approval Screens

Approval Policies and Multivalued Attributes

If a rule was set up for a multivalued attribute, there was no way to say that this rule should apply only on newly added or removed values for the multivalued attribute. By looking at the Policy Evaluation Type for a rule based on a multivalued attribute, this is now achieved. If the rule evaluation type is Onchange then this rule can only be applied to the new added or removed values of the multivalued attribute and not on all values of the multivalued attribute.

If the rule must be based on all values of the multivalued attribute irrespective of whether they were newly added or removed, the evaluation type for that rule must be Always.

Changes made to multivalued attributes are highlighted on the profile screen with an undo icon. If a rule evaluated to true because a new value was added or removed to a multivalued attribute, the approver approving this change sees ALL values contained in the multivalued attribute. Clicking the undo icon reverts the value for that attribute back to its original value. If an approver wants to see the removed values, clicking the Undo icon shows the original set of values.

Clicking the redo icon shows the new set of values letting the approver differentiate which were the removed values and which were the added ones. Clicking the approve button approves all the changes to this multivalued attribute. Clicking the reject button rejects all changes to this multivalued attribute. All subsequent rules pertaining to this multivalued attribute are not evaluated unless there is a new delta of values for this multivalued attribute.

Note: For rules based on multivalued attributes, the values contained in the multivalued attribute are the actual values and not the display values. For example, the display value for the state MA is Massachusetts. When creating an approval policy that is based on the state attribute, the rule should look like state=MA.

Consider the following example policies, all for ModifyUserEvent in the Modify User admin task:





User where (State = MA)



User where (state = DC)


Policy1 is evaluated every time an administrator invokes the ModifyUser task to change the state attribute and evaluates to true if the value MA is either added or removed from the state attribute.

Policy 2 is evaluated every time the administrator invokes the Modify User task for a user whose state contains the value DC.