|
|
|
The fulfillment-related rules are associated with the Request/Subscription Item Change event. This event is launched when any service option element in any service in a request changes.
Because fulfillment is accomplished at the service level, you must assign a rule to perform one or more actions the status changes for every service in a request. You specify the conditions in the rule to help ensure that the rule actions are performed only for the first service option element in the first row of the first service option group in each service in the request. Thus, the rule launches only once for each service, regardless of the number of service options and service option elements in the service.
Use the rule condition to help ensure that the rule actions are performed only at the appropriate time. For fulfillment, you 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 are Software (0), Hardware (1), None (-1) and any custom categories that you define.
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. |
|