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

Conditions Based on the Attributes of Service Options

Conditions based on service options can apply to either global or attached policies.

Formats

Use the following format for conditions with a match function:

$(anySoWith('attribute',operator,'value'))

Use the following format (without spaces) for conditions without a match function:

• For global policies, you specify conditions that begin with the service option group to which the service option belongs. Use the following format:

  $(_.sog['sogname'].serviceoption[rownumber] operator 'value' )

  Use the product UI to find the row number of a service option. Row numbers apply to global policies only.

• For attached policies, you specify conditions without the service option group name and row number. Use the following format:

  $(_.serviceoption operator 'value' )

  Note: Attached policies let you specify a policy that you can share among multiple service options efficiently, using a simple condition. However, when you specify a global policy for a service option, you must find its row number and use that number in the condition.

For all formats, enclose string values in single quotation marks, and enter numeric values without quotation marks.

Use the following attributes to specify conditions based on service options:

For service options and service option elements, you can specify conditions that use match functions.

The following attributes may require explanation:

category, category class, and category subclass

Specifies the values for category, category class, and category subclass from the category.xml file.

View this file and record the values that you want to use in your conditions. This file is located in a different folder for each localized version of CA Service Catalog. For example, for English (icusen), the category.xml file is located in the USM_HOME\view\webapps\usm\locale\icusen\billing folder.

Note: This file may be different, based on the language of the operating system. For details about this file, see the Implementation Guide.

estimatedCost

Specifies the estimated cost of a service option in a service in a request. The Catalog system calculates this cost when the request is submitted.

Note: To find the cost of the service option, click Home, Requests and, if applicable, use the My Requests drop-down list to display requests. Find the request that contains the service option and view the details.

external_id and keywords

Specifies the values for the attributes named external_id and keywords.

Service builders specify these values when defining the service options of a service option group. Service builders typically use these attributes to add meta information about services, especially for categorizing services.

You can find the values of these attributes and record them for use in this condition.

status

Specifies the request status of the service option.

track_as_asset

Specifies a numeric value indicating whether to track this service option as an asset in CA APM, as follows:

0 - No

1 - Yes

Note: This attribute is relevant only when CA Service Catalog is integrated with CA APM.

You can verify whether a service option uses this attribute, as follows: View the value of the Track as an Asset field on the Service Option Element Options window--Options tab.

You identify service options in conditions by their row number in the service option group. On the CA Service Catalog GUI, you can find this row number by selecting Catalog, Service Offerings, Option Groups. Click the service option group on left pane, and click the Definition tab on right pane.

When you do so, each service option in the group appears in a table; each row contains one service option. In the condition, specify the row number of the service option of interest. For example, suppose row 2 contains a service option named Windows server. In that case, specify the following conditions to include this service option.

For a global policy: $(_.sog['sogname'].serviceoption[2]

For an attached policy: $(_.serviceoption

Examples

Consider the following examples.

• You can specify the assignee when the name of the service option group is Procure Laptop and the category of the first service option is 1. To do so, use this condition:

  For a global policy: $(_.sog[‘Procure Laptop’].serviceoption[1].category==1)

  This policy applies to the service option in row 1 of the service option group.

  For an attached policy: $(_.serviceoption.category==1)

  This condition specifies that the pending action is assigned to the approver or fulfiller when the service option group is named Procure Laptop and the first service option in it belongs to Category 1. By default, Category 1 signifies hardware.

• You can specify the assignee when both of the following are true:
  • The name of the service option group is New Hire Onboarding.
  • The estimated cost of the third service option is 30 monetary units. A sample unit is Euros.

  To do so, use this condition:

  For a global policy: $(_.sog['New Hire Onboarding'].serviceoption[3].estimatedCost==30.0)

  This policy applies to the service option in row 3 of the service option group.

  For an attached policy: $(_.serviceoption.estimatedCost==30.0)

• You can specify the assignee when both of the following are true:
  • The name of the service option group is Handheld Devices.
  • The estimated cost of the service option in the third row of the group is 300 monetary units.

  To do so, use this condition:

  For a global policy: $(_.sog[‘Handheld Devices’].serviceoption[3].estimatedCost==300)

  This policy applies to the service option in row 3 of the service option group.

  For an attached policy: $(_.serviceoption.estimatedCost==300)

Examples with the Match Function

Consider the following examples:

• You can specify the assignee when the service option group includes a service option (in any row) with a category class greater than 10. To do so, use this condition:

  $(anySoWith('category_subclass',gt,10))

  This condition specifies that the pending action is assigned to the approver or fulfiller when any service option belongs to a category class greater than 10. By default, a category class greater than 10 signifies that the request is not related to any IT category, such as hardware or software.

• To specify the assignee when any service option in the request includes a category subclass greater than 10, use this condition:

  anySoWith('category_subclass',gt,10)

• To specify the assignee when the external_id (a string) of any service option ends with the string "MB," use this condition:

  $(anySoWith('external_id',endsWith,'MB'))

• You can specify the assignee when the category of any service option in the request is greater than 10 but less than 30. To do so, use this condition:

  $(anySoWith('category',gt,10) && anySoWith('category',lt,30))

• You can specify the assignee when both of the following are true:
  • The value of the external_id attribute of any service option in the request begins with the case-sensitive word "Memory"
  • The request contains a service option group named Procure Server and the category attribute of its first service option (row 1) has a value of 1, signifying hardware

  To do so, use this condition:

  $(anySoWith('external_id',startsWith,'Memory') && _.sog['Procure Server'].serviceoption[1].category==1)

• To specify the assignee when any service option in the request is tracked as an asset in CA APM, use this condition:

  $(anySoWith('track_as_asset',eq,1))

  Note: This attribute is relevant only when CA Service Catalog is integrated with CA APM.