Siebel Order Management Guide Addendum for Communications > Workflows for Employee Asset-Based Ordering > Workflows to Process an Order >

SWIOrderUpsertSubProcess Workflow

This workflow triggers the auto-asset functionality for root line items only, and updates the line items for event products. This workflow is called by the SWIOrderUpsert workflow.

Figure 109 illustrates the SWIOrderUpsertSubProcess workflow.

Figure 109. SWIOrderUpsertSubProcess Workflow

Workflow Description. This workflow performs the following actions:

1. RunOnWorkflowProcMgr? This step checks whether the RunOnWorkflowProcMgr process property is set to Y. If this process property is set to Y, then this step converts the Siebel message from a string to a hierarchy, as this workflow would have been called through the Server Request business service.
2. Convert From XML. This step converts the Siebel message from a string to a hierarchy.
3. Trim Subscription Items. This step removes all the products from the Siebel message in which Billing Type is not equal to Subscription.
4. Subscription Items Exists? This step returns TRUE if any products of Type equal to Subscription are returned by Step 3.
5. Trim Header (Subscription). This step uses the CMU External Integration Service business service to trim the order header and send only the details of the order line items as a Siebel message.
6. Retrieve Next Object (Subscription). If the Item Present flag is set to True, then this step calls the Retrieve Next object From List method multiple times with the same input argument. Each time it calls this method, the workflow returns the next root component. Also, the workflow uses it in conjunction with Update Multi Object List to form a loop control.
7. Update Multi Object (Subscription). This step returns the resulting integration object and cycles through each object one by one, in combination with Step 6.
8. Get Field Value (Subscription). This step takes Fieldnames, HierarchyNode, SiebelMessage, and MaxFields as input, and gives Fieldvalues as output.
9. Update SubComponent. If the Cascade Down flag is set to True and the Billing Type is Subscription, then this step updates the Status, Milestone, Completed Date, Change Cost, Status Context, and Expected Delivery Date of the child line items with the Status of the parent line item, which includes the Billing Type of Subscription. If the Fulfillment Status Code is Completed or Canceled, then only those values are copied to Status field of the line items of both the parent and child.
10. Is Object Exist. This step checks whether the Remaining Objects process property is set to True or False. If line items exist, then the workflow loops through each line item.
11. Is Trigger Auto-Asset. This step checks whether Status is Complete, the Auto-Asset flag is set to True, the Line Item Id is Root Line Item Id, or the Billing type is Subscription.
12. Trim Root Items. This step removes all products from the Siebel message except the root line item.
13. Root Items Exists? This step returns TRUE if any Root Line Items exist.
14. Trim Header (Auto-Asset). This step uses the CMU External Integration Service business service to trim the order header and send only the details of the order line items as a Siebel message.
15. Retrieve Next Object (Auto-Asset). If the Item Present flag is set to True, then this step calls the Retrieve Next object From List method multiple times with the same input argument. Each time it calls this method, the workflow returns the next root component. Also, the workflow uses it in conjunction with Update Multi Object List to form a loop control.
16. Update Multi Object (Auto-Asset). This step returns the resulting integration object and cycles through each object one by one, in combination with Step 15.
17. Get Field Value (Auto-Asset). This step takes Fieldnames, HierarchyNode, SiebelMessage, and MaxFields as input, and gives Fieldvalues as output.
18. Trigger Auto Asset. This step calls the SIS OM Apply Completed Service Order Line Item to Service Profile workflow. This workflow triggers an auto asset process for each line item.

    For more information about the SIS OM Apply Completed Service Order Line Item to Service Profile workflow, see the chapter on workflows for employee asset-based ordering in Siebel Order Management Guide.

19. Items Exists? This step returns TRUE if more Root Line Items are present that must be provided with an auto asset.

Table 94 shows the steps in this workflow that call business service methods.