Skip to main content

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.

Support Article

Strategy rule holds old references of deleted embedded property



User has configured an activity to call a DataFlow (Execute-DataFlow method), which in turn calls a strategy.

In this activity a Page called "DataTime" is setup using a Data transform just before calling the DataFlow with a 'Customer' page as the step page.

After the DF execution starts and goes into the subsequent Strategy the existing "DateTime" pages goes blank.

In order to overcome this issue the user has deleted the conflicting embedded page property from the customer class. (See SA-38902)
However, during the stratgey execution it still references the old PrimaryPage.PageProperty instead of the separate top level page.

Error Messages

Not applicable.

Steps to Reproduce

1. Create an activity.
2. Create a new page, say "AvailableOffer" in the activity with properties in it.
3. Configure a Customer page that will have customer data.
4. Create a blank embedded page of same name "AvailableOffer" under the "Customer" page.
5. Next call a Data Flow using the Execute-DataFlow method on the Customer page as the step page.
6. In the subsequent stratgey called from the above Data Flow access the "AvailableOffer" page.
7. It will be found that the AvailableOffer page in the stratgey scope is blank( The embedded AvailableOffer comes in the scope).
8. Next delete the AvailableOffer property responsible for the embedded page from the Customer class.
9. Skip the step 4 so that no embedded page of this name comes in the scenario.
10. Now run the activity again and check the "AvailableOffer" Page content this time. This time a blank page pointing to @baseclass appears.

Root Cause

This is expected behaviour in Pega 7.2, because the embedded page properties can be referenced directly as a top-level page within Strategy rule.
In this case there is a conflict in naming, and the one aliased by the strategy takes precedence. Thus the embedded with the same which has been a blank page comes within the scope.


The startegy rules that has refernces to this conflicting page names needs reassembly.
Resave and check in the strategy rules to resolve the issue.

Published August 26, 2017 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us