SR-123241 · Issue 182735
Localization added for pyDashboardMiddle
Resolved in Pega Version 7.1.8
The pyDashboardMiddle section has been made available for localization in both the Pega-EndUserUI and UI-Kit-7 rulesets.
SR-123242 · Issue 183215
Stage names now incuded in localization wizard
Resolved in Pega Version 7.1.8
Previously, Stage names were not picked up by the localization wizard unless each Case Type was saved in the application. An enhancement has been added to allow them to be localized more efficiently.
SR-123245 · Issue 185467
Resolved frame stack error with Flow GenerateAndProcessRequirements
Resolved in Pega Version 7.1.8
Flow GenerateAndProcessRequirements had an error in step Utility2 that generated a Frame stack error. This was caused by the method used for ClipboardObjectImpl.getThread(): in the case when owning thread is from a different requestor, it is possible that two requestors are simultaneously executing on the owning thread. In this case, the PRStackFrame push pop calls from both the requestors (foreground browser requestor and background declare trigger activity requestor) interfered with each other and caused the error. This has been fixed. / UpdateOpenCoveredTasks was causing null pointer exception due to the trigger activity, 'Work-Cover-. UpdateOpenCoveredTasks' not being available to this activity - the trigger is defined to run in background. Exceptions are thrown because the system was checking for messages on tempWorkPage page and tempWorkPage was being deleted in few cases. To fix this, a condition has been added to check whether tempWorkPage exists before checking for messages on it.
SR-123245 · Issue 185150
Resolved frame stack error with Flow GenerateAndProcessRequirements
Resolved in Pega Version 7.1.8
Flow GenerateAndProcessRequirements had an error in step Utility2 that generated a Frame stack error. This was caused by the method used for ClipboardObjectImpl.getThread(): in the case when owning thread is from a different requestor, it is possible that two requestors are simultaneously executing on the owning thread. In this case, the PRStackFrame push pop calls from both the requestors (foreground browser requestor and background declare trigger activity requestor) interfered with each other and caused the error. This has been fixed. / UpdateOpenCoveredTasks was causing null pointer exception due to the trigger activity, 'Work-Cover-. UpdateOpenCoveredTasks' not being available to this activity - the trigger is defined to run in background. Exceptions are thrown because the system was checking for messages on tempWorkPage page and tempWorkPage was being deleted in few cases. To fix this, a condition has been added to check whether tempWorkPage exists before checking for messages on it.
SR-123249 · Issue 184707
Stale stage completion checkmarks cleaned up
Resolved in Pega Version 7.1.8
When using a Split-For-Each shape with "Join" field set to "Iterate" and the Harness set to "TreeNavigation7" on a sub process tabbed screen Flow, the green tick marks which appear after completion of every stage in screen flow were not resetting for new items in the page list. Closing the workobject by clicking on red (X) mark and then reopening the same work object reset it properly. This was caused by missing logic to check whether FlowData should be reused or not, and has been fixed.
SR-123260 · Issue 184319
Resolved error with Declare Index rule validation
Resolved in Pega Version 7.1.8
An error occurred when trying to save a Declare Index rule with a source page context of .Page.PageList(). This was caused by a resolution error, and has been corrected.
SR-123292 · Issue 188135
Property Optimization Wizard working for Page level properties
Resolved in Pega Version 7.1.8
The Property Optimization Wizard was not working on Page level properties in a PageList due to due to the 'PropertyPath' Param in the displayResults activity having "()" characters that did not exist in previous versions. To resolve this, the "()" are stripped off in the Rule-Declare-Index name.
SR-123302 · Issue 186407
Row alignment corrected for tree grids in repeating tabs
Resolved in Pega Version 7.1.8
When a tree grid layout was included inside a repeat tab layout, the rows were not rendered with the correct alignment. This was due to a fixed row height, and the rendering will now use 'auto'.
SR-123303 · Issue 185053
Corrected Case match rule reporting
Resolved in Pega Version 7.1.8
The Case match rule was not reporting results that were greater than the cut off score. This has been corrected by changing the rule RunDuplicateCasesReport to check on InsKey instead of pyID as InsKey is available for all pages of different classes where pyID is not.
SR-123303 · Issue 176110
Corrected Case match rule reporting
Resolved in Pega Version 7.1.8
The Case match rule was not reporting results that were greater than the cut off score. This has been corrected by changing the rule RunDuplicateCasesReport to check on InsKey instead of pyID as InsKey is available for all pages of different classes where pyID is not.