SR-117428 · Issue 170976
Resolved performance issues when R-D-E referenced a data page
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
If a declare expression referenced a data page, loading or refreshing a section in update mode caused Rule-Declare-Expression to check whether inputs had changed. The R-D-E then loaded the data page (but didn't pass any parameters), causing the data page to load the max number of pages allowed. Subequently, a series of other R-D-Es fired on that data page as inputs had changed, ending up with a large number of R-D-E's firing that weren't required for a section. As a result, the elapsed time was higher than expected for every screen where this was happening and CPU consumption was high. Auto Population should only trigger on reference to a non-key and non-param property, and this has been implemented.
SR-118567 · Issue 167257
Enhanced task queue handling for custom applications
Resolved in Pega Version 7.1.7
In some situations, a custom agent would periodically fall over when processing a large backlog of queued items. This was caused by an exception thrown when placing a task in the queue when it is already present. The system has been updated to better handle this situation and allow agents to continue to execute with the present schedule when a duplicate task is found.
SR-117958 · Issue 166117
Alignment issues with IAC resolved
Resolved in Pega Version 7.1.7
When a dynamic layout of stacked style was used in conjunction with IAC, resizing the window caused the elements to not be properly aligned. CSS issues in the HTML handling of overflow properties have been corrected with the resizing harnesses.
SR-131612 · Issue 200253
Handling added for accent characters in DataTable editing
Resolved in Pega Version 7.1.8
When a DataTable had a key value with an accented character like "é", clicking on the "Open this item" icon to edit the row displayed a blank page in the editor. This was caused by the escape method of native JavaScript being deprecated, and the system has been updated to use encodeURIComponent method instead.
SR-122860 · Issue 183998
Added conversion of Turkish characters for Google Chrome
Resolved in Pega Version 7.1.8
Google Chrome was not correctly converting Turkish characters, causing JSON parse exceptions. In order to handle this localization, the system will check whether Google Chrome is being used, and if so will replace selective characters ( Turkish - İIŞĞÜÇÖ ) using a regex. Letters replaced are { "İ": "i", "I": "ı", "Ş": "ş", "Ğ": "ğ", "Ü": "ü", "Ö": "ö", "Ç": "ç" }. Other browsers are not affected.
SR-122860 · Issue 182083
Added conversion of Turkish characters for Google Chrome
Resolved in Pega Version 7.1.8
Google Chrome was not correctly converting Turkish characters, causing JSON parse exceptions. In order to handle this localization, the system will check whether Google Chrome is being used, and if so will replace selective characters ( Turkish - İIŞĞÜÇÖ ) using a regex. Letters replaced are { "İ": "i", "I": "ı", "Ş": "ş", "Ğ": "ğ", "Ü": "ü", "Ö": "ö", "Ç": "ç" }. Other browsers are not affected.