SR-A4720 · Issue 212436
Corrected focus for tabbing Ruleset inclusion data entry
Resolved in Pega Version 7.2
Data entry for "RuleSets To Include" was behaving unexpectedly when using keyboard-only input: when a value was entered in the "Minimum Version" text field, pressing TAB on the keyboard shifted focus from the next textbox to the top of the sheet due to a row-refresh added for app context. This has been corrected.
SR-A4078 · Issue 211396
Eliminated duplicate results from Pega Usage Validation Utility (UVU)
Resolved in Pega Version 7.2
The Pega Usage Validation Utility (UVU) is a legacy tool for collecting data from older PRPC systems during system usage audits. Due to system changes, the results on newer installations included duplicate record counts caused by case differences between work table names. These duplicate records had the same work object ID but were coming from tables whose names were similar but with varying capitalization (Example_Table, example_Table, example_table). To avoid this issue, the ClassUsageDetail.equals() implementation has been updated to be case insensitive. There is also a newer tool available in the system to retrieve this data.
SR-A5645 · Issue 213208
Resolved FirstLogCreationTime error
Resolved in Pega Version 7.2
When the file PegaRULES-FirstLogCreationTime.log existed in the log directory, the following exception was generated: Exception caught while initializing context ... PegaRULES-FirstLogCreationTime.log exists, server cannot start". The file FirstLogCreationTime.log is a temporary file that gets created and used to hold the creation time stamp of the first log of the day (and help in avoiding the deletion of log files created in the previous day). If it becomes corrupted and is not readable, this error occurs. To correct this, code changes were made to make MaxBackupIndex applicable to all log files instead of only to log files of the day.
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.