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.
SR-115934 · Issue 174331
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-116153 · Issue 165729
CaseTypeValues correctly created for child cases
Resolved in Pega Version 7.1.7
CaseTypeValues were not being properly set on the child case when it was added to the cover through agent creation, causing the trigger not to execute because the change was not detected. Manual creation was detected properly. This inconsistency was traced to the agent using the AddToCover activity vs. the manual creation using AddChildWork, and has been corrected.
SR-116242 · Issue 171896
Work item correspondence loading fixed for IE11 Enterprise
Resolved in Pega Version 7.1.7
When trying to view correspondence attached to a work item, using IE11 in Enterprise mode, an error "Error: Loading Open Authoring Control" is generated. This was caused by the Open Authoring ActiveX control APIs used by the correspondence viewing functionality: the currently used method of verifying that an ActiveX control has been successfully loaded into the HTML page was not working in IE11 Enterprise mode, and has been updated.
SR-116347 · Issue 166799
Error resolved for adding Stage Step Specifications using RTE and Google Chrome
Resolved in Pega Version 7.1.7
While configuring a stage behavior in Google Chrome, if a user had focus within the Rich Text Editor for a specification and submitted the modal, an error was generated. This was caused by an invalid post-value check, and the unnecessary post value has been removed.
SR-116587 · Issue 170222
Clarified default values for Create Class
Resolved in Pega Version 7.1.7
The Create Class screen was offering default values that had the potential to lead to classes being created in an incorrect / invalid part of the Class Structure. This has been corrected.
SR-116661 · Issue 169635
TrackSecurityChanges enhanced to capture index information
Resolved in Pega Version 7.1.7
While the properties of a pagelist are displayed in the TrackSecurityChanges history tab, the corresponding index of what was changed on the page list was not included. In order to more accurately track what is being changed, an enhancement was added with new field values for tracking the index history.