Bookshelf v7.8: Configuring Asset-Based Ordering

Configuring Asset-Based Ordering

Upgrades: Releases 7.0.x, 7.5.x.

Environments: Production test, production.

This topic is part of an upgrade process. See How to Perform the Upgrade.

Release 7.7 introduced several architectural changes to the asset-based ordering workflows and views:

Asset-Based Ordering workflows. The asset-based ordering workflows have been modified. If you are upgrading from Release 7.0.4 or Release 7.5, and you have modified these workflows, you must reapply your changes to these workflows after the upgrade.

Quote > Orders view. The Sales Order button now uses a named method to invoke the SIS OM Quote To Order Workflow--PMT Version. You can now pass arguments to the workflow. In Release 7.5, this button was hard-coded. If you have written scripts or made other changes regarding the Sales Order button, consider modifying them to take advantage of the named method.

Order Header applet. The Submit button now uses a named method to invoke the SIS OM Submit Order Process. You can now pass arguments to the workflow. In Release 7.5, this button was hard-coded. If you have written scripts or made other changes regarding the Submit button, consider modifying them to take advantage of the named method.

Disconnect and Modify workflows. The named methods used to invoke the Disconnect and Modify workflows now pass the additional properties shown in Table 42. If you have written scripts or made other changes regarding these buttons or named methods, you must manually add these after the upgrade.

Table 42. Additional Properties Passed by Named Methods
Property	Explanation
"'Due Date'", "Today() + 1"	Sets the Due Date on all line items.
"'BC Context'", "'Asset'"	Passed as a property to the workflow.
"'Compound Product Number'", "[Compound Product Number]"	The Compound Product Number is used for Network Order Entry.

Delta-In-Place feature. Delta-In-Place updates the action code of a line item when a specific line item field value is updated. For example, if a user updates the Service ID value of a product in the Order Line Item applet, the action code changes from - (dash) to Update.

In Release 7.5, the Delta-In-Place feature was implemented through User Properties on the Quote Item and Order Entry - Line Items business components.

For example:

SIS OM On Field Update Set 6

"Service Id", "Action Code", "If([Action Code] = LookupValue('DELTA_ACTION_CODE', 'Existing'), LookupValue('DELTA_ACTION_CODE', 'Modified'), [Action Code])"

In Release 7.7, the Delta-In-Place feature was moved to the SIS OM PMT Service workflow. The SIS OM PMT Delta method that is used for changes made to products within the Configurator session is now used to generate the action code for changes to line-item level fields.

If you have added new fields to the Order Management process (quote, order, asset) and then used the SIS OM Field Update Set user property, you must create new user properties in the SIS OM PMT Service to replace these.

For example, if you created a new custom field called Point of Presence, you can delete the old SIS OM On Field Update Set user properties and create a new one as follows:

Name: Delta Line Item Compare Field 26
Value: [Point Of Presence]:[Point of Presence]

Siebel Configurator runtime: Done button. In Releases 7.0.4 and 7.5, when a user clicks Done in a Siebel Configurator session, Siebel EAI transfers user selections into Quote and Order line items. This process used Quotes, Orders, and Assets-related business components.

As of Release 7.7, this process uses new, smaller business components. This improves performance. The new business components begin with MACD. If you have modified the original business components, you must apply these changes to the MACD business components.