SR-114807 · Issue 162848
"Transfer to an Operator" dynamic list was not sorted
Resolved in Pega Version 7.1.7
The "Transfer to an Operator" dynamic list was not sorted, while the "Transfer work from" dynamic list was. This was caused by different function calls in the system, and has been corrected so the lists sort properly by property name.
SR-115000 · Issue 165234
Operator substitutions restored to the availability settings
Resolved in Pega Version 7.1.7
The operator availability setting links for Case Manager portal and Case User portal were missing substitute assignee details. These have been restored.
SR-115133 · Issue 166141
Localization added for column section summaries in Report Definition
Resolved in Pega Version 7.1.7
The summarize column section displayed while running the Report Definition now accepts localization.
SR-115268 · Issue 166797
Cleanup improved for resolved work-items
Resolved in Pega Version 7.1.7
An error in the logic for Stage Flows caused improper cleanup of resolved work items, leading to outsized assignment tables. This has been corrected.
SR-115308 · Issue 173906
Japanese character support added to Report Definition PDFs
Resolved in Pega Version 7.1.7
When Report Definition contains Japanese characters in its report name, column, value, etc., the exported PDF was not showing the Japanese characters incorrectly. This was due to a missing font-family for the PDF export mode, and has been corrected.
SR-115378 · Issue 168818
Corrected horizontal scroll bars for listviews with custom searches
Resolved in Pega Version 7.1.7
Horizontal scroll bars were not appearing when using custom search section in a list view. This error was caused by missing logic for resizing the window width, and has been corrected.
SR-115511 · Issue 168772
Application Express Wizard updated to correctly bind rulesets
Resolved in Pega Version 7.1.7
New Rule-Access-Role-Obj (RARO) rules created using Application Express wizard were being bound to specific ruleset versions vs. ruleset names. This caused failure to any modification to those RAROs, since modifying a RARO with a ruleset version would mean the save-as would fail if the validation found a RARO already present for that ruleset. In order to ensure proper binding and aid migration, a RARO with ties to a ruleset version will have that the version information removed automatically upon saving of the RARO.
SR-115711 · Issue 165363
Flow Action class correctly retrieved for subprocesses
Resolved in Pega Version 7.1.7
When running a Process Flow in a Data- class that is called from a Work- process flow via a SubProcess, the error "Failed to find a 'RULE-OBJ-WHEN' with the name 'CANMAINTAINCASEREPORT'" was being generated. This was caused by incorrect handling for the class: the flow action and WHEN rule are in a WORK class, but when the sub-flow is executed it looks in the DATA class of the embedded page instead of the WORK class relevant to the overall case. There was a workaround of saving the WHEN rules into the Data- classes, but the system now uses workPage instead of interestPage for localcase to ensure the correct class is retrieved.
SR-115717 · Issue 168256
Rearranging columns in multi-tab sections corrected
Resolved in Pega Version 7.1.7
When using a multi-tab section, re-arranging the columns was only effective in the first tab. This was caused by the tabs lacking individual global variables to give them unique IDs, and has been fixed.
SR-115776 · Issue 164938
Improved definition of Remote Work Objects
Resolved in Pega Version 7.1.7
Previously, a work object was considered remote only when it was from a different system than the Master. This caused an issue in cases when the Master and Remote Applications existed on the same PRPC instance, and the behavior has been changed to consider the WO to be remote when it is from a different application even if it is from same system.