Performance Best Practices

• Use dict("String") instead of dict("string[]").

  The speed for processing and storing dict("string") is faster than dict("string[]"). In general, a simple structure is faster.

• Eliminate Revert to Default on line item attributes if you have any for those actions.

  They run X times, and they invoke the line item advanced default script every time they run.

• Eliminate line item summation attributes.

  They also run X times every update.

• If you need to loop through line items, store them into temporary variables such as a string or a float dictionary.

  After you store them, use the temporary variables instead of looping through line item documents collection.

• If you have Advanced Modify on those actions, optimize the code:
  • Eliminate nested For... loops
  • Eliminate parallel For... loops
  • Eliminate table calls done in For... loops

  • When building the result string, use a temporary result string in loops in order to minimize the number of large string concatenations.

• Eliminate calls to Global Functions.
• Eliminate or optimize Quote level summation attributes.
• Eliminate or optimize HTML/Read-Only attributes.
• Eliminate Revert to Default for quote level attributes on those actions.
• Delete any unused attributes.

• Ensure that the first main doc always has document number=1 instead of res=res+_quote_doc_number+"~varname~"+value+"|";

  Use res=res+"|1~varname~"+value; instead.

• Use the Run Once For All Line Items option on advanced line item default if you have any loops.

  Confirm the final results are correct. If you do not select run once, the advanced default will run for each line item added. If you have many recommended items you are adding at once, this can cause a significant performance penalty.

  Known Bug: "Run Once For All Line Items" is not respected when copying line items. If you make multiple copies of a configuration, the line item default will run for all copies being made.

• Rather than calling the same Data Table multiple times with slightly different queries, get table data once, put it into an array, and process the data as you loop through the array.

  The size of the Data Table and the number of queries will influence the impact of this change.

• If calling large tables, reduce the number of records by redesigning tables.

• Minimize the number of RTE fields on line item attributes.

  There should be no more than 5, as a general rule.

• Minimize the number of line item attributes and the number of attributes displayed in the line item grid.
• Do not put model/configurator-specific pricing in the pricing script. Instead, use the relevant configurator to calculate these.

• Do not put large text area attributes on the page.

  These will be submitted back to the server when an action is performed on the page, even if the action has "leave value unchanged" for the attribute.

• Regarding access rules, do not loop over line items to determine hiding behavior.

Oracle CPQ 21C enables the internal parallel processing of Commerce rules to improve end user response time. Concurrent rule processing improves performance in Commerce transactions for end users.

Having a list of items that repeats a word(s) in all the names is inefficient. Take advantage of labeling your groups more appropriately to avoid redundant content that distracts from the true distinct differences of the items.

• Identify words that are used in every line of a group of labels. Many groups of labels have one word that appears in all of them; it draws the eye away from what makes each line unique, and it creates clutter. Remove this word and incorporate it into the group header.

  Using the word "Total" on every line of the following list is unnecessary because they're all totals. Instead use a useful group label.

  Good List	Bad List
  TOTALS Retail Price Total Savings New Price Taxes Net Price	Total Retail Price Total Savings Total New Price Total Taxes Total Net Price

• Eliminate redundant attribute choices. It is common to have repeated words in the options listed for an attribute. Pinpoint the word being used in all of them and make each one look more unique.

  Redundant List
  MEMORY 2GB DDR SDRAM 4GB DDR SDRAM 6GB DDR SDRAM 8GB DDR SDRAM

The longer, redundant aspects of the names do not need to be repeated. All of the items in this list are memory of type "DDR SDRAM". We could label this Attribute as "MEMORY (in GB of DDR SDRAM)" or something similar and our list could simply be numbers.

Boolean attributes are designed to handle true/false and yes/no choices. It is recommended that you use a Boolean attribute instead of a two-option single select menu. It is considered best practice to be mindful of what you are asking the user:

• Example: If you are asking the user if they are a student...

  DO	DON'T
  Make a Boolean attribute that asks "Currently a Student"? The user will know to select the box next to it.	Make a Text Attribute with a drop-down or radio button list with the choices "Yes" and "No".

• Example: You are making a Boolean attribute to replace a text attribute you have called "Purchase History" with the following choices: "I have purchased items in the past" and "I am a new customer."
  • Change the label from "Purchase History" to "Have you purchased items from here before?" or "I have purchased items in the past" so that the user clearly knows what they are choosing to be True.

  • If the label is carefully reworded to avoid ambiguity, many two-option attributes can be turned into Booleans. The user should be able to understand the option that they are selecting.

  It is recommended to set the default to "False".

An internal property gives Oracle CPQ customers the option to prevent Commerce read-only fields from being posted back to the server after a Commerce action is invoked.

While enabling this property will have nominal impact on performance, it is recommended not to post information back to the server when the data will not have changed since it was last posted.

To enable this property, open a ticket on My Oracle Support.

When a desktop user opens a Transaction, its data will now be cached to reduce the need to access the database. As the user views and edits the Transaction, the data is accessed from the cache, not the database. When the Transaction is saved, the changes are written to the database and are then accessible to other users.

Desktop Transaction caching also allows faster processing of Ajax calls. Ajax is used throughout the Commerce module, such as in AJAX Hiding / Constraint Rules, Auto Update Advanced Modification, and AJAX Formulas. Therefore, faster processing can have a broad impact.

By default, desktop Transaction caching is enabled for both new and existing customers. Work with your Oracle CPQ application sales representative to discuss how this feature can be most effectively used for your specific implementation.

If Commerce attributes are not on the layout being viewed, or are hidden by a Participant Profile, they will be removed from the generated HTML sent to the browser. This reduces the amount of content that has to be delivered from the server.

If you need access to attributes not on the layout, see the section Reading Commerce Attributes not on the Layout in the topic Commerce Document Attributes for more information.

By default, this feature is enabled for both new and existing customers. Although we highly recommend using the optimized data request size feature, it can be disabled by opening a ticket on My Oracle Support. Note that since this degrades performance, the request will need to be approved.

Several Line Item Grid (LIG) pagination modes exist in the Commerce desktop layout, giving you more control over when data is sent to the browser and displayed to the user.

By enabling Grid Paging, the Line Item Grid will display the line items on a page by page basis when a Transaction is opened. The user can then page through the Line Item Grid to display the next page of line items.

In previous versions of CPQ, you could choose whether or not to enable pagination for a Line Item Grid. Now, you can also choose the way pages are retrieved.

Accessing Pagination Options

Pagination Modes

Page Navigation Enhancements