Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Globally optimized strategy

Updated on April 5, 2022

A globally optimized strategy is an instance of the Strategy rule that has improved performance. Strategy designers create globally optimized strategies to reduce the computation time and memory consumption when running large-scale batch data flows and simulations. Improvements to the Strategy rule performance are the results of decreased run time and quality changes to the code generation model. Strategy designers create a globally optimized strategy by referencing an existing strategy that they want to optimize and by selecting output properties that will be in the optimized strategy result.

Strategy optimization is done on the component level. The following strategy components can be optimized:

  • Sub Strategy (only the Current page option)
  • Proposition Data (without the Interaction History option)
  • Split
  • Data Join
  • Set Property
  • Filter (only the Filter condition option)
  • Prioritize
  • Champion Challenger
  • Switch
  • Group By
  • External Input

Optimized strategies can work with non-optimized components.

  • Previous topic Strategy rule form - Completing the Pages & Classes tab
  • Next topic Creating a globally optimized strategy

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us