SR-B13647 · Issue 291863
Security Policy updates to handle big strings
Resolved in Pega Version 7.3
The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.
SR-B13647 · Issue 291683
Security Policy updates to handle big strings
Resolved in Pega Version 7.3
The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.
SR-B43602 · Issue 306874
Check added to handle unexpected RTE scroll in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
When using Microsoft Internet Explorer, pressing the enter key in the RTE field caused the page to scroll down even when the RTE area with the cursor in it was completely visible on page. This was caused by an error in the position calculation for scrolling in quirks mode, and has been resolved with the addition of a check which will avoid calling the scroll function when using RTE with Microsoft Internet Explorer.
SR-B43602 · Issue 311133
Check added to handle unexpected RTE scroll in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
When using Microsoft Internet Explorer, pressing the enter key in the RTE field caused the page to scroll down even when the RTE area with the cursor in it was completely visible on page. This was caused by an error in the position calculation for scrolling in quirks mode, and has been resolved with the addition of a check which will avoid calling the scroll function when using RTE with Microsoft Internet Explorer.
SR-B71969 · Issue 326817
Date fixed for Export to Excel
Resolved in Pega Version 7.3.1
Dates were not being formatted correctly on Export to Excel of a report definition. This was due to an error in exporting just the date field that was not previously considered when repairing the date/time function. To fix this, Export_Date_RD has been updated to export the date in a consistent manner that Excel will understand (similar to how its being done in pzExport_Datetime_RD).
SR-B88128 · Issue 338448
CompletedSubFlow paths fixed for final shapes
Resolved in Pega Version 7.4
The function getPreviousShapeFrompxFlow was not accounting for the last shape in a flow being a completed subprocess, instead skipping over it and returning the second-to-last shape instead of opening the subprocess and returning the last shape. In the mobile app, clicking on the Next button caused the application to hang and show a busy indicator. This was an issue with pyCompletedSubFlow paths not being handled properly in process_flow, and has been fixed.
SR-C50324 · Issue 393499
Synchronized block method added to load keystore set with RUF
Resolved in Pega Version 8.2
A recent enhancement allows for the SAML auth service to use a reference to an external file for the signing certificate keystore. When the keystore had the password set using a Rule-Utility-Function, rather than being static, there were intermittent login fails with the error "unable to process SAML WebSSO request1" on the screen, and the RULES logs contained thousands of entries of an error indicating "Password is wrong". It was sometimes possible to log in by starting a new browser sessions and trying again. This was an issue with the PasswordHash property being changed from a static to a non-static field: it was not thread safe, though each object got its own copy of the instance, because if two or more threads call the setPasswordHash() method on the same object, all of these threads tried to simultaneously update the passwordHash instance variable and incorrect results were seen. To correct this, the system will use a synchronized block when loading the entries into cache in the getKey() method - Caller function of KeystoreCacheImpl.java.
SR-C73100 · Issue 411034
Synchronized block method added to load keystore set with RUF
Resolved in Pega Version 8.1.2
A recent enhancement allows for the SAML auth service to use a reference to an external file for the signing certificate keystore. When the keystore had the password set using a Rule-Utility-Function, rather than being static, there were intermittent login fails with the error "unable to process SAML WebSSO request1" on the screen, and the RULES logs contained thousands of entries of an error indicating "Password is wrong". It was sometimes possible to log in by starting a new browser sessions and trying again. This was an issue with the PasswordHash property being changed from a static to a non-static field: it was not thread safe, though each object got its own copy of the instance, because if two or more threads call the setPasswordHash() method on the same object, all of these threads tried to simultaneously update the passwordHash instance variable and incorrect results were seen. To correct this, the system will use a synchronized block when loading the entries into cache in the getKey() method - Caller function of KeystoreCacheImpl.java.
INC-151716 · Issue 618440
Resolved Screenflow overflow
Resolved in Pega Version 8.4.4
Screenflow bread crumbs were overflowing out of the action area when more than 10 assignments were configured. An error in the console indicated the navigation.navigate function was not defined. This behavior was observed in general when a screenflow was called from another screenflow and 'enable navigation links' was set on all assignments in the screenflows, and the issue has been resolved by updating the implementation.
SR-C28672 · Issue 371101
Timing issue fixed with switchLocale refresh
Resolved in Pega Version 8.1
When using a function call to have a section refreshed so that it shows in Spanish, the section instead loaded in English and did not change. This was traced to a timing issue: the pega.clientTools.switchLocale method is asynchronous, and immediately refreshing Sections and Harnesses after the asynchronous call may not have time to reflect the changes. To resolve this, a callback mechanism has been introduced in the pega.clientTools.switchLocale method.