Integrating with CA Workflow › CA Workflow-Driven Fulfillment › Complex Fulfillment Rules and Actions › Check Availability Rules

Check Availability Rules

The CheckAvailability rules have been renamed, as follows:

• When Category is Hardware and Status is Pending Fulfillment (formerly WFHWCheckAvailability)
• When Category is Software and Status is Pending Fulfillment (formerly WFSWCheckAvailability)
• When Category is neither Hardware nor Software and Status is Pending Fulfillment (formerly WFOtherCheckAvailability)

The former names are retained here for compatibility, in case you have not yet started using the new rules.

When Category is Hardware and Status is Pending Fulfillment

(formerly WFHWCheckAvailability) The When Category is Hardware and Status is Pending Fulfillment rule is launched when a request item status changes and these conditions are satisfied:

• 800 <= old status < = 999 - The old status is in the approved range
• new status = 1000 - The new status is pending fulfillment (1000)
• category = 1 - The service option element category is Hardware (1)
• rate_item_col = 0 - This service option element is the first service option element in its row of service option elements

This rule condition ensures that the rule is used only when a requested hardware item first enters the fulfillment phase.

When Category is Software and Status is Pending Fulfillment Rule

(formerly WFSWCheckAvailability) This rule is launched when a request item status changes and these conditions are satisfied:

• 800 <= old status < = 999 - The old status is in the approved range
• new status = 1000 - The new status is pending fulfillment (1000)
• category = 0 - The service option element category is Software (0)
• rate_item_col = 0 - This service option element is the first service option element in its row of service option elements

This rule condition ensures that the rule is used only when a requested hardware item first enters the fulfillment phase.

When Category is neither Hardware nor Software and Status is Pending Fulfillment Rule

(formerly WFOtherCheckAvailability) This rule is launched when a request item status changes and these conditions are satisfied:

• 800 <= old status < = 999 - The old status is in the approved range
• new status = 1000 - The new status is pending fulfillment (1000)
• category > 1 - The service option element category is not Hardware (1) or Software (0) or None (-1)
• rate_item_col = 0 - This service option element is the first service option element in its row of service option elements

This rule condition ensures that the rule is used only when a requested non-hardware or software item first enters the fulfillment phase.

The action associated with these rules is named Launch USM_CheckAvailability Workflow (formerly Workflow Check Availability, Workflow Software Check Availability, and Workflow Other Check Availability). The Launch USM_CheckAvailability Workflow action uses the following values:

• Type – Workflow
• Process Definition – USM_CheckAvailability
• Process Parameters –

  RequestedForUserID = $req_for_user_id$
  RequestDesc = $request_name$
  BusinessUnit = $domain$
  RequestItemName = $rate_item_name$
  RequestItemID = $id$
  FulfillmentUser1 = spadmin
  FulfillmentUser2 =
  FulfillmentUser3 =
  FulfillmentUserList = spadmin
  RequestID = $request_id$

This action launches the USM_CheckAvailability Workflow process definition, passing the information necessary to assign a check availability task to the appropriate fulfillment user(s) (up to three).

Note: By default, the fulfillment user who is assigned the check availability task is spadmin, the default Service Delivery Administrator. If more than one fulfillment user is specified, all users must be indicated in the FulfillmentUserList field, separated by semi-colons. Also be aware that additional logic as to who the correct fulfillment user is can be added to the USM_CheckAvailability process definition. Additional rules can also be created that assign this fulfillment task to different users based on other rule filters.

Example

If your business processes specify that Laptops are fulfilled by one user and Desktops by another, you can add a filter based on the category_class field or other relevant field and pass different user IDs in the FulfillmentUser1 and FulfillmentUserList fields.

Or if your business processes specify that all requests are fulfilled based on the requesting user’s city, then logic can be added to the CA Workflow process definition to appropriately assign the fulfillment user.