Support Article
Pre-loading activity differs in context at design and runtime
SA-7066
Summary
After upgrading from PRPC 6.2 to Pega 7.1.7, developer noticed that there is a different behavior for defer load activity on Tab Group.
With Pega 7.1.7, the application expects to find the activity in a different class.
But with PRPC 6.2 the expected class is one of the main section, instead now with Pega 7.1.7 application looks for the activity in the class of clipboard page defined as Page Context.
It seems, there is at least an issue with the modal dialog that allows to configure the layout properties. At design time the available activities listed are retrieved from the class of the main section, and not the class of the page context.
Error Messages
2015-01-29 12:54:27,879 [fault (self-tuning)'] [TABTHREAD5] [ ] [ CCSTop:01.10.01] (ocess.Rule_HTML_Section.Action) ERROR 127.0.0.1|127.0.0.1 my_user@my_org - Errors detected in FUA validation for Section 'pyWorkDetails' :.pySections(2).pyDeferLoadXXXActivity: LoadOpenYYYSF does not exist for use by this record (Validate).
.pySections(18).pyDeferLoadXXXActivity: PrepareZZZ does not exist for use by this record (Validate).
Steps to Reproduce
Upgrade from PRPC 6.2 to Pega 7.1.7 with defer load activity on TAB Group.
Resolution
1. Page Context value - When used "Use page defined by property"
Here one can provide property reference which holds the page name but not the page type property.
2. The pre-load activity refers the section class and its hierarchy. The pre load activity is executed before the section renders, hence it does not know the page context defined, so it is the section defined class itself.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.