SR-B49995 · Issue 308428
Proposition filter rule description updated to match decision data description changes
Resolved in Pega Version 7.3.1
Updating the description field of a proposition in the decision data did not update the description in the proposition filter rule involving that proposition as expected. This has been resolved by updating the rule which is refreshing proposition name changes to handle description change as well.
SR-B56530 · Issue 316311
Reworked destination assumptions for child dataflows
Resolved in Pega Version 7.3.1
When activating a Real time data flow run containing a Stream dataset as input which was then output to two child dataflows containing different event strategies, an IllegalArgumentException error appeared. This was traced to the pzDataFlowContainsEventStrategy activity assuming that the last shape had "Destination" in the ID in addition to an error obtaining the class. This has been fixed by properly setting the KVS type: the DataFlowRunConfig.getKeyValueStoreType() will not return NONE but default instead, and the pzDataFlowContainsEventStrategy now Iterates through all subflows and fixed secondary destination name.
SR-B69595 · Issue 317880
Fixed UnsupportedOperationException from decision table
Resolved in Pega Version 7.3.1
When using embedded properties (e.g. .OfferData.Action) within a decision table, an UnsupportedOperationException appeared on the DSMClipboardProperty if it was executed via a Strategy rule. The issue was with a function being not implemented within DSMClipboardPage, and has been fixed.
SR-B66996 · Issue 312205
Access control policy logic added for non-work/data/assign classes
Resolved in Pega Version 7.3.1
As part of ABAC (Attribute-based access control) restrictions, if a class property was of type PageList, security had to be created in the PageList property class type. However, if the pagelist was of type "Embed-" class then it was not possible to create security policy due to the inability to apply property masking for page list properties of that class. To resolve this, property masking implementation logic has been added to support page list properties of non-work/data/assign classes for access control policies.
SR-B66996 · Issue 315524
Access control policy logic added for non-work/data/assign classes
Resolved in Pega Version 7.3.1
As part of ABAC (Attribute-based access control) restrictions, if a class property was of type PageList, security had to be created in the PageList property class type. However, if the pagelist was of type "Embed-" class then it was not possible to create security policy due to the inability to apply property masking for page list properties of that class. To resolve this, property masking implementation logic has been added to support page list properties of non-work/data/assign classes for access control policies.
SR-B55119 · Issue 312817
Handling added for absent property in Access When
Resolved in Pega Version 7.3.1
Configuring Access Control Policy to automatically restrict access to certain records by including an Access When rule to compare a custom property (.Consultant) on the OperatorID (Data-Admin-Operator-ID) page generated an exception if that property did not actually exist on the current operator. This has been resolved by revising the security policy engine to handle the exception.
SR-B71077 · Issue 323027
IDP Encrypted connections working on SAML
Resolved in Pega Version 7.3.1
IDP initiated SAML 2.0 was not working, and generated the error "Unable to process the SAML WebSSO request : Missing Relaystate information in IDP Response". Authentication worked fine with unencrypted SAML token. This schema validation failure happened because encrypted attributes were previously being ignored by Pega due to an issue in the underlying openSAML library. To resolve this, a custom PegaSAMLValidator has been inserted to validate the assertion and honor encrypted attributes.
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.