Integrating with CA Workflow › CA Workflow-Driven Fulfillment › Complex Fulfillment Rules and Actions › Received Cancelled Rules

Received Cancelled Rules

The Received Cancelled rules have been renamed, as follows:

• When Category is Hardware and Status is Received or Order Canceled (formerly WFHWReceivedCancelled)
• When Category is Software and Status is Received or Order Canceled (formerly WFSWReceivedCancelled)
• When Category is neither Hardware nor Software and Status is Received or Order Canceled (formerly WFOtherReceivedCancelled)

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 Received or Order Canceled

formerly WFHWReceivedCancelled. This rule is launched when a request item status changes and these conditions are satisfied:

• old status <> 1007 - The old status is not Received (1007)
• old status = 1008 - The new status is not Order Cancelled (1008)
• 1007 <= new status <= 1008 - The new status is Received (1007) or Order Cancelled (1008)
• 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’s status is changed to Received or Order Cancelled.

When Category is Software and Status is Received or Order Canceled

formerly WFSWReceivedCancelled. This rule is launched when a request item status changes and these conditions are satisfied:

• old status <> 1007 - The old status is not Received (1007)
• old status = 1008 - The new status is not Order Cancelled (1008)
• 1007 <= new status <= 1008 - The new status is Received (1007) or Order Cancelled (1008)
• 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 software item’s status is changed to Received or Order Cancelled.

When Category is neither Hardware nor Software and Status is Received or Order Canceled

formerly WFOtherReceivedCancelled. This rule is launched when a request item status changes and these conditions are satisfied:

• old status <> 1007 - The old status is not Received (1007)
• old status = 1008 - The new status is not Order Cancelled (1008)
• 1007 <= new status <= 1008 - The new status is Received (1007) or Order Cancelled (1008)
• category > 1 – The service option element category is not None (-1), Software (0) or 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 item’s status is changed to Received or Order Cancelled and the item’s category is not hardware or software.

The action associated with these rules is named Launch USM_CheckAvailability Workflow (formerly Workflow Check Availability, Workflow Hardware Check Availability Received, 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.