Skip to main content

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

Creating globally optimized strategies

Updated on August 4, 2022

Create a globally optimized strategy by referencing an existing strategy that you want to optimize.

Pega Customer Decision Hub
Note: If you use the Next-Best-Action Designer component of Pega Customer Decision Hub, you do not need to manually optimize the resulting strategy framework. For more information, see Understanding the Next-Best-Action strategy framework. However, you can still choose to optimize strategies created manually outside of the Next-Best-Action strategy framework.
  1. Log in to your application as an operator with access to Dev Studio.
  2. In Dev Studio, in the left navigation pane, click RecordsDecisionStrategy.
  3. Click Create.
  4. On the Create Strategy form, select Create globally optimized strategy.
  5. Enter a label for the strategy, and then click Create and open.
  6. On the Global optimization tab, select a top-level strategy that you want to optimize.
    A globally optimized strategy cannot reference another globally optimized strategy.
  7. Optional: To see the optimization status of individual substrategies and strategy components, click Expand strategies.
    Note: A strategy may have Partially optimized or Not optimized status when its components contain expressions with unsupported functions. To learn how to optimize such strategies, see Optimizing strategies with allow list functions.
  8. Click Save.
  9. Optional: In the Test tab, compare the results of the optimized strategy to the normal version by clicking Compare.
    Note: Most fields should have exactly the same value for GOS execution and normal strategy execution, except some special fields, such as Interaction ID, Decision Reference, or Decision Time.
  10. Reference the globally optimized strategy in a data flow by using a Strategy component.
    Caution: Do not reference globally optimized strategies from legacy data flow components such as Run Strategy, or legacy rule types such as Interaction rules. GOS does not support legacy ways of invoking strategies, so referencing GOS from an unsupported component may result in issues. Instead, to use globally optimized strategies, edit the data flow to include a Strategy component.
  • Previous topic Understanding globally optimized strategies
  • Next topic Frequently asked questions about globally optimized strategies

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us