SR-A7590 · Issue 216110
Corrected parameter page used when Flowproblems restarts
Resolved in Pega Version 7.2
Restarting the problem flow was not taking the mandatory parameters defined in the flow, instead generating the error "Required parameter Parameter_name." To correct this, the flow method body has been modified to populate the parameter page from the pyFlowParameters page before checking for mandatory parameters.
SR-A10189 · Issue 222038
Handling added to set baseclass when using Bulk as Update
Resolved in Pega Version 7.2
The use case was missing to properly handle setting the baseclass when Bulk action was selected as an Update process. This has been added.
SR-130442 · Issue 212468
Added support for localization of the 'Advanced' value of the When rule
Resolved in Pega Version 7.2
If the "Advanced" value was localized in the When rule form, it failed as it was trying to compare with localized text. To resolve this, WhenTabListener has been modified to use the ID attribute instead of text for comparison.
SR-A12587 · Issue 224456
Added support for localization of the 'Advanced' value of the When rule
Resolved in Pega Version 7.2
If the "Advanced" value was localized in the When rule form, it failed as it was trying to compare with localized text. To resolve this, WhenTabListener has been modified to use the ID attribute instead of text for comparison.
SR-A6363 · Issue 216182
Resolved Where AM I issue when there is flow on embedded page
Resolved in Pega Version 7.2
Clicking on the "Where Am I?" option when there was a subprocess defined on embedded page in a flow failed to display anything on screen and an error was logged. This was caused by the obj-open referring to the wrong flow class value, and has been corrected.
SR-A9389 · Issue 219242
File name truncation used for File Listener recovery
Resolved in Pega Version 7.2
The Property Data-WorkAttach-.pyNote default of Max Length = 60 caused a failure in File Listener's recovery mode if the system added a long string at the end of the file name. This has been fixed by trimming and setting pyNote if the length is more then 60 characters.
SR-122809 · Issue 182677
Application Wizard updated to use long-form function name
Resolved in Pega Version 7.1.8
When using the Application Wizard in some environments, clicking 'Preview' or 'Create' on the Data Objects screen caused a refresh and no summary of the created rules was generated. This issue was traced to an error in the library/function rule resolution where the short-form reference to a function was finding more than one suitable rule resolution candidate if there was more than one version of a ruleset function with the same formal parameters and the function was called using the short form of the function name. In this particular scenario the PageListContains function was causing a problem as this function exists in both the PegaSurvey framework and the Pega-AppDefinition ruleset. There was a workaround of doing a private checkout of the CopyFrameworkClassGroup activity and changing the short function rule reference to the long function rule reference (specifying ruleset and library, but the Wizard has been updated to use long-form function name to prevent this issue.
SR-A2750 · Issue 211790
Made custom ruleset versions available when saving custom rule types
Resolved in Pega Version 7.2
When trying to save certain rules, users were getting a limited number of rulesets even though there were unlocked versions. Specifically, this issue occurred for custom rule types. The rulesets available were not the same as when non-custom rule types were utilized. This has been resolved by adding the class of custom rule type for required rulesets so that all required rulesets will appear in the dropdown.
SR-A10163 · Issue 221183
Fix added for accessing WO correspondence using Microsoft Internet Explorer11
Resolved in Pega Version 7.2
When using Microsoft Internet Explorer11, the error ?Error-Open Authoring control failed to load? was generated when attempting to access correspondence attached to a work object. This has been fixed.
SR-A8915 · Issue 220454
Jump-back page reference fixed for Tree Navigation and TabbedScreenFlow
Resolved in Pega Version 7.2
When starting a ScreenFlow from a SplitForEach using using TreeNavigation7 and TabbedScreenFlow7, the navigation harnesses were not taking the correct interested page for a jump-back on a previous assignment. This has been resolved.