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-116157 · Issue 165994
Improved crash recovery in a complex system
Resolved in Pega Version 7.1.7
During crash recovery in a clustered, load balanced system, attempting to recover a user's progress displayed a message that the session was recovered but the page did not then properly load the recovered data. To ensure proper crash recovery failover on complex systems, the user is now authenticated on the STANDARD thread instead of a work thread when restoring work in progress.
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-116556 · Issue 170813
AllLinksForParticularRule changed from Final to Available
Resolved in Pega Version 7.1.7
The list view reporting limit AllLinksForParticularRule has been changed from a Final rule to an Available rule in order to allow an increase in the number of links shown in the Application Profile. The default is 500.
SR-116585 · Issue 167063
Screen flow previous button repaired in obfuscated IAC
Resolved in Pega Version 7.1.7
When using IAC with obfuscation is enabled, the screen flow 'previous' button was not responding. This was caused by the '\' at the end of the URL parameter being accidentally obfuscated as well, and has been fixed.
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.
SR-116681 · Issue 169378
BIX Column length increased
Resolved in Pega Version 7.1.7
At runtime BIX checks the target DB metadata for column length. If it could not find the metadata with schema associated with the BIX DB user, it was setting the length at 32 characters even if a larger column length was specified in PRPC and SQL. This was due to a mismatch in the stored value location, and has been corrected so BIX will reflect the length specified on the Extract rule form.
SR-116716 · Issue 167507
Execute RDB runs in batch mode for very large data sets
Resolved in Pega Version 7.1.7
The executeRDB query was not able to handle very large large data sets, resulting in an OOM error after clicking on "Create Prior Authorization". ExecuteRDB (which is a select query) has been modified to run in batched mode, i.e. run the same query with limit on max rows, so as to avoid OOM when copying the whole result set into the memory object (similar to Report Definition paging).