|
|
|
The fulfillment-related rules are all associated with the Request/Subscription Item Change event. This event is launched when a subscription detail item changes. What this means is that this event is launched when the status of a service option element changes. Since fulfillment is done at the service option level and a service option may consist of multiple service option elements, the event is launched for each service option element in the service.
The rule condition is used to ensure that the rule actions are only performed at the appropriate time. In the case of fulfillment, we want the fulfillment action to occur only for the first service option element in the first row for the first service option group in the request. This means the rule is launched only once for each service option regardless of the number of service option elements in the service option.
In addition, the fulfillment process takes different paths based on the category and status of the first service option element in the service option. The categories of interest are Software (0), Hardware (1), None (-1) and all other categories. The list of categories and their associated numeric values are defined in the following line:
USM_HOME\view\webapps\usm\locale\icusen\billing\category.xml
The list of statuses and their associated numeric values are defined in the following line:
USM_HOME\view\webapps\usm\locale\icusen\request\requestshared.xml
| Copyright © 2013 CA. All rights reserved. |
|