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-115839 · Issue 166347
Corrected radio button visibility behaviors
Resolved in Pega Version 7.1.7
Previously, some erroneous behaviors were seen with the visibility of a mandatory radio button when used in conjunction with a conditional read-only option. This has been resolved by a recent change that makes the "Required" checkbox a dropdown, fixing the design time issues.
SR-115896 · Issue 167002
Corrected flow handling for failed tickets
Resolved in Pega Version 7.1.7
Raised flow tickets using pre-existing flow-ticketed utility shapes were intermittently failing to transfer to the expected place in the flow. This was found to be an improper copy action in the task, and has been corrected. The error message has also been clarified.
SR-115896 · Issue 167322
Corrected flow handling for failed tickets
Resolved in Pega Version 7.1.7
Raised flow tickets using pre-existing flow-ticketed utility shapes were intermittently failing to transfer to the expected place in the flow. This was found to be an improper copy action in the task, and has been corrected. The error message has also been clarified.
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-115931 · Issue 169804
Fixed read-only cascading dynamic select in Google Chrome
Resolved in Pega Version 7.1.7
The cascading dynamic select was not working in Google Chrome with ReadOnly Mode. This was traced to an error in the dynamicselect.js, and has been corrected.
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.