Read-Only Operation Optimization in Collaborative Quoting

Beginning in Oracle CPQ 24D, collaborative quoting action requests that don't modify the transaction (i.e. read-only operations) may be executed and may not be added to the collaborative queue. The following actions are read-only operations: Interact (read and polling requests), Refresh, and Display History. In addition, the first Open Transaction action will execute the normal full lifecycle including integrations as before, but each subsequent Open Transaction action will behave like a read-only operation and will not make any modifications to the transaction including executing integrations. Thereby, subsequent users collaborating on a quote will immediately be able to open the transaction.

This feature prevents the addition of unnecessary read-only operations in the collaborative queue.

Steps to Enable

This feature is disabled by default. Customers can submit a Service Request (SR) on My Oracle Support to enable read operation optimization in collaborative queue.

Tips And Considerations

If your site has modification functions (e.g. Save BOM) associated with Interact (read and polling requests), Refresh, or Display History actions you should enable read operation optimization in collaborative queue only after analyzing the impact of these modification functions failing, or after changing your implementation to not modify the quote during read operations. Once the read-only operations are executed in parallel as part of the optimization, there are guardrails that will prevent these functions from modifying the transaction.