SR-A5110 · Issue 214245
Fixed exception generated by 'getclassname' used with autocomplete
Resolved in Pega Version 7.2
An issue was found in some new installations using autocomplete where trying to set and execute 'getclassname' after a name change caused a conflict between the old and new values. The problem was traced to a function that set the new value and then repeated a call to the old one, nullifying the change. This did not effect upgraded systems due to a difference in the storage stream versions, and the conflict has been resolved by updating the logic
SR-A4488 · Issue 214464
Improved system performance for SQL using ReserveQueueItem
Resolved in Pega Version 7.2
The SQL generated using the stored procedure sppr_sys_reservequeueitem_b has been tuned to improve system performance for all database implementations; DB2, MS SQL Server, and Oracle.
SR-D39547 · Issue 505859
Check added for backwards compatibility with Case Type when rules
Resolved in Pega Version 8.1.7
After upgrade, the When rules present on case type rules (used for skipping stages or showing/hiding stage-wide or case-wide actions) were not executing at run time. This was traced to the introduction of the pySkipOrAllowType property in recent versions, and was only reproducible when the ApplicationRuleset was locked and after upgrade irrespective of whether the condition for when was true or false. To resolve this and enhance backwards capability, a check has been added for the SkipOrAllowType property being empty.
SR-A6363 · Issue 216182
Resolved Where AM I issue when there is flow on embedded page
Resolved in Pega Version 7.2
Clicking on the "Where Am I?" option when there was a subprocess defined on embedded page in a flow failed to display anything on screen and an error was logged. This was caused by the obj-open referring to the wrong flow class value, and has been corrected.
SR-D51554 · Issue 514064
Local UUID cache will be updated when merge event is detected
Resolved in Pega Version 8.1.7
Cluster-related issues were seen in multiple production clusters. For some nodes in the cluster the Cluster Management screen showed all expected nodes with valid Node IDs displayed, and on other nodes the Cluster Management screen showed the node ID of itself, SERVER@localhost:5701. On an impacted node displaying the wrong ID, the Node Information landing page did not work and displayed the error "Unable to execute job on ." Multiple advanced agents running on nodes in the affected clusters, both with correct and incorrect IDs, also failed with a similar error "Unable to execute job on <node's job id>". This was traced to a merge performed after a split brain. To resolve this, the code has been updated to handle merge events: when the node UUID is changed as part of a split brain recovery, the local UUID cache will be updated when the merge event is detected.
SR-A6168 · Issue 217424
Updated encoding for "&" in dropdowns using defer load
Resolved in Pega Version 7.2
In case of dropdowns with defer load, options having "&" were being double-encoded and displayed as '&'. The API has been updated to correctly handle the special character.
SR-A9389 · Issue 219242
File name truncation used for File Listener recovery
Resolved in Pega Version 7.2
The Property Data-WorkAttach-.pyNote default of Max Length = 60 caused a failure in File Listener's recovery mode if the system added a long string at the end of the file name. This has been fixed by trimming and setting pyNote if the length is more then 60 characters.
SR-D42159 · Issue 508942
Large report pagination should use "Previous and Next only"
Resolved in Pega Version 8.1.7
Some Report Definitions were getting timed out or facing gateway exceptions, primarily due to high time consumed by the DB Queries. Investigation showed the total result count process appeared to stop at the configured pyMaxRecords value as long as it was nonzero. This indicated the issue was related to changes made to fix the inaccurate behavior of the "Last" button in the responsive paginator which included removing logic that set pyMaxRecords to anything other than zero. To resolve this issue, those pagination changes have been reverted. The "Last" button should not be used when the paging mode is set to Numeric: in the case of large reports, the paging option should be set to "Previous and Next only".
SR-D42670 · Issue 510185
Force order added to inner join when running a Rules Resolution filter
Resolved in Pega Version 8.1.7
After upgrade, D_getResolvedWorkStatuses was not loading properly due to a Report Definition that used a Filter by Rule Resolution option timing out on the SQL Server. When the Filter by Rule Resolution option is selected in RD, it will generate a rule resolution query with an inner join which can cause a time out on the SQL Server while it tries to find out the join order for tables with multiple joins. To resolve this, the SQL server will provide a Force order, merge inner join hint option by way of an added DSS reporting/useForceOrderHint. Additionally, reporting/useMergeHintForRRquery should be set on Pega-Reporting to set things up for using the Merge Inner join hint in the query.
SR-D32525 · Issue 505469
Dirty check added to offer save/discard changes when closing tab
Resolved in Pega Version 8.1.7
With the out-of-the-box section enabled, performing a change in the form (changing a text value, selecting a option in a dropdown, etc.) and closing the case generated an unexpected alert indicating that the case was changed and the modifications were lost. This differs from the previous behavior of showing the section pyDirtyCheckConfirm which offered the opportunity to save the work. This was a missed use case and has been resolved by updating the system to perform a check for the dirty state when closing the interaction and show a modal dialog asking the user to choose either save/discard if dirty.