Commerce Service Center allows the modification of orders that have been submitted but not yet fulfilled. When an agent modifies an order, the order’s state determines how the edit process is handled.

When a submitted order is modified, the order is cloned into a transient order that captures all of the modifications made by the agent. The transient order is then reconciled with the original order in a single transaction. Updates are not committed to the original order unless the reconciliation process is successful. If the agent abandons the transient order, any modifications made will be lost.

The cloning technique is performed on selected orders based on their state. The CSROrderHolder shouldCloneOrder(Order pOrder) API determines if a particular order qualifies for this process. This API returns a result based on the following criteria:

Additional states can be added by modifying these two properties in CSRAgentTools.

The order is cloned in an initialization pipeline that uses Repository cloning from RepositoryUtils. The order repository item is cloned to make a copy, and the copy is then loaded using OrderManager’s loadOrder API.

When the order has been cloned for modification, the application is in clone-edit mode. When an agent is working on a clone order there will be no indication in the UI. The UI always shows the original order ID. The isCloneEditMode() API in the CSROrderHolder determines when this mode is active. The getOriginalOrder() API returns the original order when required.


Copyright © 1997, 2012 Oracle and/or its affiliates. All rights reserved. Legal Notices