Skip to main content


Making custom Strategy Result properties available for real-time container data flows

Suggest edit Updated on September 21, 2021

Every property output from a decision strategy associated with real-time containers in the Next-Best-Action Designer must be identified in the pyDefaultWorkingSet data transform. Update this data transform if you use real-time containers and if you have configured custom action properties.

  1. In Dev Studio, create a new data transform called pyDefaultWorkingSet in your top level SR class.
  2. On the Definition tab of the data transform, select the check box Call superclass data transform.
    Enabling the Call superclass data transform option ensures that all properties defined in the built-in pyDefaultWorkingSet data transform are available. You do not need to define them again in your new data transform.
  3. Add any properties which you want to make available as output properties from Strategy in the generated data flows, as shown in the following example:
    An example configuration of the pyDefaultWorkingSet data transform
    1. In the first row, in the Action column, enter: Append and Map to
    2. In the first row, in the Target column, enter: defaultWorkingSetPage.pyWorkingSet
    3. In the second row, in the Action column, enter: Set
    4. In the second row, in the Target column, enter: .pyPropertyName
    5. In the second row, in the Source, enter the name of the property which you want to make available.
  4. On the Pages & Classes tab, enter the following information:
    1. In the Page name field, enter: defaultWorkingSetPage
    2. In the Class field, enter: Data-MO-DDF-DecisionStrategy
  5. Click Save.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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