Support Article
Included Section Class in Flow Action changes post Pega7 upgrade
Summary
When a Flow Action that has a Section configured with 'using page' is upgraded from PRPC 6.2 SP2 to Pega 7.1.8, it changes the Section's 'Applies to' class to that of flow action.Error Messages
There are no warnings or error messages but it will corrupt the existing functionality.Steps to Reproduce
In PRPC 6.2 SP2 environment, create a flow action with applies to class ‘XYZ-FW-EWFW-Work-Incident’ with section that belongs to ‘XYZ-FW-EWFW-Work-Claim’.
Upgrade it to Pega 7.1.8 and observe that it is modified to ‘XYZ-FW-EWFW-Work-Incident’.Root Cause
The Activity Rule-Obj-FlowAction.OpenDefaults is setting the applies to class for the Section wrongly.
This issue originated out of a design decision to exclude pyIncludedRuleXML from the Flow Action/Section rules that holds the included Section's information.
Flow Action depends on this page to set the class. Since this page does not exist, the class defaults to current Flow Action's primary class.Resolution
In Activity Rule-Obj-FlowAction.OpenDefaults, if pyPrompt class is blank, try to get the page name from the Flow Action rule, iterate across its pages and classes, get the class name where the page name matches and set that as the applies to class for the Flow Action's Section.
HFix-23315 has been devised to address this issue. Post HFix installation, all the Flow Actions from older PRPC version must be packaged and imported in Pega 7.
Published August 14, 2015 - 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.