You are here: Best Practices > Performance Best Practices

Performance Best Practices

OVERVIEW

ClosedMaximizing Performance


ADMINISTRATION

ClosedIncreasing Performance on a Site with Large Quotes


ClosedConfiguration Performance Best Practices


ClosedAvoiding redundant lists

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.


ClosedHiding irrelevant content for different user types


ClosedUsing Boolean attributes

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:


ClosedPrevent Posting of Read-Only Fields

An internal property gives CPQ Cloud 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.


ClosedDesktop Transaction Caching

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.

The Desktop application’s auto update behavior is the same whether the Desktop Transaction caching is on or off.

By default, desktop Transaction caching is enabled for both new and existing customers. Work with your Customer Success Manager to discuss how this feature can be most effectively used for your specific implementation.

Although we highly recommend using Desktop Transaction, this feature can be disabled by opening a ticket on My Oracle Support.


ClosedOptimized Data Request Size

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 an attribute is affected by hiding rules, and not by the layout or the Participant Profile, the data will still be sent to the browser.

If you need access to attributes not on the layout, see the section Reading Commerce Attributes not on the Layout in the topic Commerce 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.

If you have questions about this feature, contact your Customer Success Manager. On upgrade, they can assess the impact of this feature and disable it if necessary.

This feature depends on Desktop Transaction caching functionality. Turning Desktop Transaction caching off disables this feature.


ClosedLine Item Grid (LIG) Pagination Modes

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 Cloud, you could choose whether or not to enable pagination for a Line Item Grid. Now, you can also choose the way pages are retrieved.

ClosedAccessing Pagination Options

ClosedPagination Modes

ClosedAfter upgrading to 2015 R1

ClosedPage Navigation Enhancements


ClosedSSO Performance Tracing

The duration of each step during a SAML SSO from an external application (such as Oracle Sales Cloud) into CPQ Cloud is now measured. This information can help troubleshoot the source of any delays.

If this is enabled, you can see this information in your log files.

For more information, or to enable this feature, open a ticket on My Oracle Support.


ClosedOptimized Printing

When printing a large Transaction, the Print XML is only generated once and updated as needed.

In previous versions, the Print XML was regenerated during printing when data was requested, even though that data already existed in the Print XML. For example, when another page was printed after the first page, the information that appeared on every page was requested again and the Print XML was regenerated.

Now, the XML recognizes that the data already exists and does not request it again.

This feature depends on Desktop Transaction caching functionality. Turning Desktop Transaction caching off disables the optimization.


RELATED TOPICS

Related Topics Link IconSee Also