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-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-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-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.
SR-115798 · Issue 167885
Improved handling for abstract case classes
Resolved in Pega Version 7.1.7
An extra hyphen was being inserted into a newly created case's class when the parent class was an abstract class already indicated by '-'. To correct this, a check has been added to avoid appending a dash if the parent class name ends with "-".
SR-115808 · Issue 169924
Instantiation logic enhanced
Resolved in Pega Version 7.1.7
In an application with a parent case (CaseInstancePOC) and two lower levels of cases (Case_Level2 and Case_Level3), the top level case starter flow CaseInstancePOC creates multiple subcase instances of type Case_level2. This is caused by automatic case instantiation of Case Level3 based on Case level2 Work Status - Open being configured. In some cases, this may not be the desired behavior. For example, when there are two Case_Level2s and one work status is changed to Open, the user may want a child case to be instantiated for only that particular Case_Level2and not the other Case_Level2. To allow more flexibility, an enhancement has been added to limit scoping through the AddChildWork setting.
SR-115912 · Issue 168208
Updated failure handling for Word editing with IE
Resolved in Pega Version 7.1.7
When using IE, failure to load correspondence for editing in Word generated the message "Error: Loading Open Authoring Control". This was caused by the carried-over use of a span tag that is not valid under HTML5, and has been corrected with updated JavaScript.
SR-115934 · Issue 170092
Corrected deadline escalation for reassigned work
Resolved in Pega Version 7.1.7
When reassigning work with an escalating deadline, the reassignment flowed properly but the corresponding SLA queue item was deleted after reassign and passed deadline events defined in the SLA rule were not triggered. This was traced to the new queuepage being created with a different processEvent activity, meaning Queue Manager could not locate it. A check has been added to ensure the correct queuepage is attached to reassigned work.
SR-115934 · Issue 170387
Corrected deadline escalation for reassigned work
Resolved in Pega Version 7.1.7
When reassigning work with an escalating deadline, the reassignment flowed properly but the corresponding SLA queue item was deleted after reassign and passed deadline events defined in the SLA rule were not triggered. This was traced to the new queuepage being created with a different processEvent activity, meaning Queue Manager could not locate it. A check has been added to ensure the correct queuepage is attached to reassigned work.