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-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-A8396 · Issue 218579
Corrected duplicate work object IDs
Resolved in Pega Version 7.2
The out-of-the-box section pyAssignmentListGadget was generating duplicate work object ids when pyAssignmentsLabel was used to display the case/Assignments label & ID in Case contents. This was caused by changes made in a previous version intending to enhance the displaying of labels, and has been modified to avoid duplicate workobjectIDs.
SR-A8848 · Issue 219083
Correct class being passed in SubProccessTab flow
Resolved in Pega Version 7.2
n the pzSubProcessTab section. the value for the "RuleClassProperty" was not being passed as blank to the pzRuleCallParamsWrapper section when the flow was defined on the current page and was instead defaulting to Work Pool Class. The system has been modified to pass the proper class.
SR-A9211 · Issue 220239
Corrected highlighting in calendar gadget
Resolved in Pega Version 7.2
When using the calendar gadget, selecting the weekly view generated a blue box around the monthly tab instead of the expected weekly tab. An error in the section reload was causing the focus to move to the next action element, and this has been corrected.
SR-A10178 · Issue 219880
"ExportToExcel" activity updated to match Java API upgrade
Resolved in Pega Version 7.2
After upgrade, the "ExportToExcel" out-of-the-box activity was returning an error when clicking 'save as' on the rule in application ruleset. This was caused by the code in the activity not being upgraded after the Java API version was upgraded, and has been corrected by updating the "ExportToExcel" activity.
SR-A5588 · Issue 212799
Added check to halt case progression if open assignments present in parallel flow
Resolved in Pega Version 7.2
If "Launch On Re-entry" was unchecked and parallel flows were present in the current stage, it was possible to progress to the next stage even if open assignments were present in the current stage. In addition, all steps in the parallel flow were created if the open assignments in the activated flow were completed. To avoid this, the stage history will be checked for all the stages whether or not the 'Stage on Re-entry' check-box is in use. Previously, only the last stage was checked: with this update. if the requested stage has any unprocessed flow missed in previous visit then it will be considered.
SR-A8496 · Issue 219309
Corrected page property setting for pxAddChildWork smart shapes
Resolved in Pega Version 7.2
The page property parameter was being ignored in favor of the WorkPage in the the pxAddChildWork activity. This should only have happened if the PageProperty Param was null or empty, but was occurring in scenarios where a child case was created using the Create Case smart shape. A check has been added to consider the top level page of the step page as the Primary Page parameter in order to prevent this issue.
SR-A11576 · Issue 222779
pzShowConflicts message localized
Resolved in Pega Version 7.2
Localization has been added for pzShowConflicts by adding the configurable field "pyMessageLabel.ShowConflictMessage".
SR-A11935 · Issue 223901
Application creation allowed without case selection
Resolved in Pega Version 7.2
When attempting to create an application based on CS 7.1.4 using the New Application Wizard with no cases selected, the application was not created and an error was displayed. This was traced to the RulesetName and rulesetversion params not being passed to the "pyPrepareFrameworkAssetsForGenerationPost" activity: those params are set only when Case Types from FW are selected. The system has now been updated to pass the RulesetName and rulesetversion params to the activity even when Case Types from FW are not selected.