SR-B38602 · Issue 296751
Login error message modified for increased security
Resolved in Pega Version 7.3
When an operator was configured to use External authentication and then attempted to login through other servlets, the error message included the operator ID. This could be used maliciously to discover valid IDs on the system, so in order to improve security, the process has been modified to remove the ID from the failure message. If authentication fails, the message "The information you entered was not recognized." will be displayed and the system will log an error message in the PegaRULES log file with the actual message "Error authenticating , : This user must use external authentication."
SR-B38602 · Issue 297290
Login error message modified for increased security
Resolved in Pega Version 7.3
When an operator was configured to use External authentication and then attempted to login through other servlets, the error message included the operator ID. This could be used maliciously to discover valid IDs on the system, so in order to improve security, the process has been modified to remove the ID from the failure message. If authentication fails, the message "The information you entered was not recognized." will be displayed and the system will log an error message in the PegaRULES log file with the actual message "Error authenticating , : This user must use external authentication."
SR-B38619 · Issue 298574
Action item refresh properly triggers
Resolved in Pega Version 7.3
Refresh was not clearing the temporary filters applied on the report definition results if the refresh option was triggered by the actions button. This has been fixed by adding a new java step to pzRunWrapper activity to clear the previously applied filters.
SR-B38627 · Issue 298635
Calendar icon refresh updated for Internet Explorer browser
Resolved in Pega Version 7.3
Intermittent responsiveness issues were seen when trying to select/pick date from calendar icon. This issue was traced to the combination of having the "Contract ID" option enabled and using the Internet Explorer browser, leading to unexpected refresh of particular scripts used in the section. The script timing has been modified to resolve the issue.
SR-B38627 · Issue 298840
Calendar icon refresh updated for Internet Explorer browser
Resolved in Pega Version 7.3
Intermittent responsiveness issues were seen when trying to select/pick date from calendar icon. This issue was traced to the combination of having the "Contract ID" option enabled and using the Internet Explorer browser, leading to unexpected refresh of particular scripts used in the section. The script timing has been modified to resolve the issue.
SR-B38647 · Issue 297399
ServiceExport folder access restricted for guest users
Resolved in Pega Version 7.3
In order to increase data security, access to the 'ServiceExport' folder has been blocked for Guest users (Un-Authenticated users who have pre-atn cookie) on single-tenant sites. Once the user is logged in with valid credentials, the folder contents will be available. For backward compatibility the PRConfig setting 'serviceexportcontent/allowtoguestusers' has been added; if set to true then guest users will have access. The default is false.
SR-B38649 · Issue 296249
Corrected ClassCastException error on Connect-REST
Resolved in Pega Version 7.3
After a REST Connector was run with the QUEUE Method Parameter, executing the "System-Queue-ExecutionRequest- ProcessQueue" activity resulted in an error. This was traced to the invoke activity of class RULE_CONNECT_REST, and has been fixed.
SR-B38649 · Issue 295456
Corrected ClassCastException error on Connect-REST
Resolved in Pega Version 7.3
After a REST Connector was run with the QUEUE Method Parameter, executing the "System-Queue-ExecutionRequest- ProcessQueue" activity resulted in an error. This was traced to the invoke activity of class RULE_CONNECT_REST, and has been fixed.
SR-B38674 · Issue 301022
Descendant class logic made more robust
Resolved in Pega Version 7.3
The 'Report on descendant' option in the report definition/Listview was giving incorrect results. This was caused by the code used to execute the RD looking up the descendant class from the current application that inherits from the applies-to class (tools.getDatabase().getConcreteDescendantsInCurrentApplication(class name);) of the RD and executing the RD against this class. While this is appropriate when an application is built on another and case types are directly inherited into the new layer, this will not work when application layers are added which do not include equivalent case types for every case from the built upon applications. This becomes a more common problem when the MBO feature starts getting used more often on the customer implementations. To ensure the descendant class is correct, the Useimplemenation class has been updated to be more robust.
SR-B38802 · Issue 295105
Resolved error for data flow using abstract start shape
Resolved in Pega Version 7.3
A Data Flow starting with a Data Set was running correctly, but when refactored to start with an Abstract the same flow generated errors in Production. This was traced to an error in the code that was attempting to write a null value to the array, and has been fixed.