Siebel Pricing Administration Guide > Creating Product Offers > Workflow Reference for Product Offers >

RAF Apply Multiple Offer To Create Order Web Service Workflow

RAF Apply Multiple Offer To Create Order Workflow, shown in Figure 35, takes the account and a list of offer IDs to generate an order for a residential customer. The order can be generated in-memory or saved to the database based on the SaveInstance input argument.

This workflow is called by the ApplyMultipleOffersforOrder method of Apply Multiple Product Offers Web service. Optionally, this workflow accepts the order structure as an input argument and applies offer actions to this order structure instead of creating a new order. For existing customers, the workflow takes the Asset Id as an input argument and offers' are applied to the customer's asset.

NOTE:  For more information about the Web service that calls this workflow, see Siebel CRM Web Services Reference.

Figure 35. RAF Apply Multiple Offer To Create Order Workflow

Workflow Description. This workflow performs the following actions:

1. Has Asset Id? This decision step checks whether the input of the Web service operation ApplyMultipleOfferToCreateOrder contains AssetId. If so, it routes the flow to the step Query Asset With Asset Id. Otherwise, it routes the flow to the step Query Asset for Account Only.
2. Query Asset With Asset Id. This step calls Query method of the business service EAI Siebel Adapter, using the Account Id and Asset Id to retrieve the asset Information for the specified account and asset.
3. Query Asset for Account Only. This step calls the Query method of business service EAI Siebel Adapter, using the Account Id to retrieve the Account details from Integration object ISS Account Instance. This step is called when Asset Id is not part of the input message of the Web service.
4. IO Transformation. This step calls the method IntObjHierToPSHier of the business service EAI Integration Object to XML Hierarchy Converter to transform the queried message from the previous step from Integration Object format to Property Set Format.
5. Get Context. This step calls the GetRowSetData method of the Context Service business service. It uses the Variable Map Default Product Offer Recommendation Variable Map - Context to get the account header information.
6. Get Rowset. This step calls the GetRowSetData method of the Context Service business service. It uses the Variable Map Default Product Offer Recommendation Variable Map - Row Set to get the asset information for the account.
7. Residential Account? This decision step checks whether the account in the input of the Web service is of the type Residential. If so, it routes the flow to the step Create SearchSpec. Otherwise, it routes the flow to the Stop step to set the error message.
8. Stop. This stop step sets an error message as part of output message of the Web service operation ApplyMultipleOfferToCreateOrder, if the account is not a residential account. It aborts further processing and exits the workflow.
9. Create SearchSpec. This step calls the CreateSearchSpec method of the RAF Product Offers Service business service, which traverses the list of offers from the input message of the web service and prepares a search expression with the offer IDs.
10. RAF Create Document Workflow. This step calls the subprocess RAF Create Document Workflow to process the actions for all the offers provided in the input message. If the order is generated in-memory, the subprocess returns the Order structure. If the order is saved to the database, the subprocess returns the Order ID.
11. Process In Memory? This step checks if the order processing is done in memory. If so, it returns the order structure as the output argument of the web service. Otherwise, it routes the flow to Active Doc Id.
12. Active Doc Id? This step verifies whether the offer is successfully applied by creating an order with a non-null value for the DocId. If DocId (Order Id) is NULL, it routes the flow to the step Query Empty Order. Otherwise, it routes the flow to the step Query Order.
13. Query Empty Order. This step calls the Query method of the EAI Siebel Adapter business service, querying an invalid order to populate the empty value for the order message as part of response message the Web service call.
14. Query Order. This step calls the Query method of the EAI Siebel Adapter business service to retrieve the order in SIS OM Order integration object format. It takes the DocId (Order ID) as input and returns the full order structure as the output that would be part of the response message to the Web service call.