Skip to content

Verify Request Activity

Nilesh Ghodekar edited this page Oct 28, 2016 · 9 revisions

Overview

The Verify Request activity is an Authorization phase activity used to perform validation of the current request and reject the current request if it does not meet the validation criteria.

Activity UI

Verify Request - Activity UI

Activity Display Name

Optional. Name of the activity to be displayed on the MIM / FIM workflow designer.

Advanced Features

Activity Execution Condition

Optional. The condition which must be satisfied for execution of this activity's core task (i.e. validate the current request). This can be any WAL function expression resolving to a boolean value. See Activity Execution Condition wiki for more information.

Verify the Resource as Unique

Optional. If this setting is selected, the activity can be configured to perform a uniqueness validation for the target resource of the current request.

Conflicting Resource Search Filter

Required when "Verify the Resource as Unique" setting is selected. Specify the XPath search filter that will return a conflicting resource. e.g. /Person[EmployeeID = '[//Delta/EmployeeID]'].

Conflict Denial Message

Required when "Verify the Resource as Unique" setting is selected. Specify the request denial message to be returned to the submitter when a conflicting resource is found. e.g. The employee ID [//Delta/EmployeeID] is already assigned to some other user.

Verify the Request as Unique

Optional. If this setting is selected, the activity can be configured to perform a uniqueness validation for the current request against other authorizing requests.

Advanced Request Search Filter

Optional when "Verify the Request as Unique" setting is selected. Specify the XPath search filter that will return requests that should be evaluated as potential conflicts. If the search filter is not specified, the activity will evaluate all requests with a status of "Authorizing" and a matching target resource type and operation.

Match Condition Identifying a Conflicting Request

Required when "Verify the Request as Unique" setting is selected. Specify the boolean condition that identifies an evaluated request as a conflict. e.g. And(Eq([//Delta/AccountName], [//ComparedRequest/Delta/AccountName]), Eq([//Delta/Domain], [//ComparedRequest/Delta/Domain]))

Conflicting Request Denial Message

Required when "Verify the Request as Unique" setting is selected. Specify the request denial message to be returned to the submitter when a conflicting request is found. e.g. Another request to create user with employee ID [//Delta/EmployeeID] is already being processed and awaiting approval.

Required Request Conditions

Required. Specify the conditions which must be satisfied for the request to be considered valid. Each condition can be any WAL function expression resolving to a boolean value. If any condition does not evaluate to true, the request will be denied with the associated error message.

Implementation Guidance

Use Verify Request activity to do request validations only when the capabilities of RCDC controls fall short to do the required request validation at the UI Form level.

If the request will lead to triggering a workflow for programmatic creation of resources using Create Resource activity, use a Verify Request activity to validate that the resulting resource will not result in a duplicate. While the Create Resource activity can detect conflicts, it cannot fail the request during the authorization phase with a configurable error and alert the user to the error like Verify Request activity can.

Examples

The following Verify Request activity ensures that when a user's account status is updated a reason is provided by updating the description field:

Activity Display Name Ensure Account Status Update Reason is Provided
Conditions
Required Condition for the Request Denial Message if the Condition is not Satisfied
IsPresent([//Delta/Description]) "A reason (description) must be provided when updating the account status."
Clone this wiki locally