Using Policies to Manage Requests › How to Create a Condition › Conditions Based on the Attributes of Requests

Conditions Based on the Attributes of Requests

You can specify conditions based on the following attributes of the request affected by the policy:

The following attributes may require explanation:

estimatedCost

Specifies the total estimated cost of all services (including all service options) in the request. The Catalog system calculates this cost when the request is submitted.

To find the cost of an entire request, select Home, Requests and view the details for the request of interest.

priority

Specifies the priority of the request as a number, using one of the following values:

1 = high

2 = medium_high

3 = medium

4 = medium_low

5 = low

status

Specifies the numeric value of the status of the request.

To use request status as a condition for approval, specify this attribute in your condition, using the approval range, by default, less than 800. For example, the following condition is met when the service is named "Procure Laptop" and the request status is approved:

$(_.service.name=='Procure Laptop' && _.request.status < 800)

To use request status as a condition for fulfillment, specify this attribute in your condition, using the fulfillment range, by default, greater than or equal to 999. For example, the following condition is met when the service is named "Procure Laptop" and the request status is fulfilled:

$(_.service.name=='Procure Laptop' && _.request.status >= 999)

If your organization is not using custom statuses, you can specify the default status values.

If your organization is using custom statuses, to find all actual status values (both default and custom), open the file named requestshared.xml and record the values that you want to use in your conditions.

See also the other examples later in this topic.

Note: This file can be different based on the language of the operating system and is located in a different folder for each localized version of CA Service Catalog. For example, for English (icusen), the requestshared.xml file is located in the %USM_HOME%\view\webapps\usm\locale\icusen\request folder. For more details about this file, see the Implementation Guide.

other attributes

You can view most of the other attributes when you view the request list pages. Otherwise, open a request to view its additional details.

Examples

• To assign a pending action when the estimatedCost of the request equals 100 monetary units (by default, dollars), use this condition:

  $(_.request.estimatedCost == 100)

• To assign a pending action when the priority of the request equals 1, meaning high priority, use this condition:

  $(_.request.priority==1)

• To assign a pending action when a request item has not been approved (status 800) and the requested for user has a manager, use this condition:

  $(anySoWith('status', lt, 800) &&_.request.requestedForUser.manager != '')

• To assign a pending action when a request item has been approved or when the requested for user does not have a manager, use this condition:

  $(anySoWith('status', gteq, 800) || _.request.requestedForUser.manager == '')

  The assignee list for this example could specify the default user (spadmin) or another suitable user.

• To assign a pending action when the request status is greater than 200 (submitted) and the assignee's business unit is ca.com, use this condition:

  $(_.request.status>200 && _.request.bu.id=='ca.com')