LinkedIn
Copied!

Table of Contents

Understanding globally optimized strategies

Introduced in version 8.6, globally optimized strategies (GOS) are a new type of decision strategies that focus on providing the best performance at runtime. Strategies created by using Next-Best-Action Designer support GOS out of the box, but you can also configure other strategies to benefit from the performance improvements that GOS provides.

Globally optimized strategies are defined as top-level decision strategies in a data flow, that is, the first strategy that the data flow calls during the decisioning process.

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.

When a globally optimized strategy runs, it brings several types of decisioning artifacts into a single program and executes them all together. Because rules are executed together rather than called one by one, overall strategy execution performance is greatly increased.

Use GOS when you want to improve the performance of your decisioning strategies that are referenced from a data flow.

Globally optimized strategies cannot be used as sub-strategies, in proposition filter conditions, or as target for the Check decision strategies for optimizations upgrade tool.

Globally optimized strategies can be used in simulations that support them, such as distribution test, value finder, and ethical bias simulations. In the current version of Pega Platform, decision funnel simulations do not support GOS. If you use a globally optimized strategy in a decision funnel simulation, it will instead run the strategy that the GOS references.

Supported rule types

GOS can import and execute the following rule types:

  • Proposition Filter rules
  • When rules, if used in a proposition filter
  • Strategies, if used as a sub-strategy on the strategy canvas, or in a proposition filter
  • Decision tables, if supported by SSA.

Supported strategy components

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

  • External sub-strategy
  • Embedded sub-strategy
  • Decision table
  • Data join
  • Set property
  • Filter (including expression and proposition filters)
  • Prioritize
  • Champion-challenger
  • Exclusion
  • Switch
  • Group by

Have a question? Get answers now.

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