SR-B56328 · Issue 312168
RARO rules more secure against deletion
Resolved in Pega Version 7.3.1
In order to make RARO rules more secure, the system has been updated such that Class Permissions can't be deleted from the role unless the operator has permission and is operating in a valid context (unlocked ruleset). This has been done by revising the Role rule form to disable the delete button when RARO/RADO is in a locked ruleset.
SR-B57046 · Issue 314358
Parameters removed from on-screen error messages to protect sensitive data
Resolved in Pega Version 7.3.1
It was discovered that sensitive information such as account numbers used as parameters were being displayed in exception error messages displayed on the screen. Including the parameters as part of the error is intended to aid in debugging the problem, but these parameters do not need to be displayed in the UI. In order to protect potentially sensitive data, parameter values have been removed from the exception message. When the DeclarativePageDirectoryImpl logger is enabled, the parameters will be entered into the Pega log files and not shown on screen.
SR-B67143 · Issue 316168
Proxy configurations made available to OAuth2 and other clients
Resolved in Pega Version 7.3.1
Setting up Proxy for the REST Connector was not working when using OAuth2. When using OAuth2 authorization for Connector features including REST Connectors, the com.pega.pegarules.integration.engine.internal.client.oauth2.OAuth2ClientImpl class is used for connections to the OAuth2 Provider for interactions such as fetching authorization tokens. However, OAuth2ClientImpl does not have the required code for "picking up" the JVM-level proxy settings and applying them to the HTTP Client it uses, so the HTTP calls to the OAuth2 provider were always bypassing the configured HTTP proxy. In order to resolve this and enhance future use, the code in the RESTConnector module that allows REST Connectors to use HTTP Proxies has been extracted out into the "HTTPClientUtils" module so that it can be used by any consumer to apply the system's Proxy configuration to any instance of PegaRESTClient. OAuth2ClientImpl has been updated to call this during HTTP client setup, prior to making the request for data from OAuth2 Providers, and RESTConnnector has been updated to call this new implementation to replace the universal Proxy code that was refactored out of it.
SR-A101514 · Issue 316396
Busy indicator memory leak fixed for multiple iframes
Resolved in Pega Version 7.3.1
A memory leak was found with the client side script busy indicator when multiple iframes were involved. As part of this change, a part of the code in pega_ui_busyindicator.js which removes the status div within hidden iframes has been reworked to avoid memory leakage.
SR-A101514 · Issue 317772
Busy indicator memory leak fixed for multiple iframes
Resolved in Pega Version 7.3.1
A memory leak was found with the client side script busy indicator when multiple iframes were involved. As part of this change, a part of the code in pega_ui_busyindicator.js which removes the status div within hidden iframes has been reworked to avoid memory leakage.
SR-B64971 · Issue 316298
Added alt text attribute to paperclip icon for accessibility
Resolved in Pega Version 7.3.1
A paperclip icon in the pzMultiDragDropControlStandard rule did not have alternative text, impacting its accessibility. An alt="" attribute has been added to the image tag to correct this.
SR-B14710 · Issue 288487
Accessibility added for down arrow button access
Resolved in Pega Version 7.3.1
Accessibility has been added to the tooltip on a button when it is accessed via Down Arrow key so it will be read by JAWS.
SR-B52773 · Issue 312408
Improved null/blank parameter handling when using Microsoft Internet Explorer.
Resolved in Pega Version 7.3.1
After upgrade, opening an assignment in Microsoft Internet Explorer, clicking the save button, and then hitting Function F5 (PF5) caused a null pointer exception on the screen. When OK was clicked in the exception popup it displayed a blank case content screen. This issue was caused by some null parameters on the stored parameter page, and has been resolved by updating the API to better handle null and undefined parameters.
SR-B52773 · Issue 312968
Improved null/blank parameter handling when using Microsoft Internet Explorer.
Resolved in Pega Version 7.3.1
After upgrade, opening an assignment in Microsoft Internet Explorer, clicking the save button, and then hitting Function F5 (PF5) caused a null pointer exception on the screen. When OK was clicked in the exception popup it displayed a blank case content screen. This issue was caused by some null parameters on the stored parameter page, and has been resolved by updating the API to better handle null and undefined parameters.
SR-B70481 · Issue 322272
Scrollbar works when text area disabled
Resolved in Pega Version 7.3.1
After upgrade, scroll bars were disabled when a text area is disabled. This was traced to code that stopped the scrolling due to the disabled text area CSS style pointer-events being set to "none", and has been fixed by adding the needed CSS in the py-enduser71-workarea-overrides.css file.