SR-C81111 · Issue 417908
Performance improvements made for IG summary use
Resolved in Pega Version 8.2
Enabling IH summaries in an adaptive model or using them in a strategy was impacting performance by as much as 300 milliseconds. Improvements have now been made to streamline Cassandra node health checks, to eliminate unnecessary duplicate calls to the DB, and to stop the DSS from being read on each single case dataflow execution.
SR-C72252 · Issue 415223
isAncestorOf function now checks whether a child class is defined in the tenant layer
Resolved in Pega Version 8.2
After upgrade, the isAncestorOf function was not returning the correct result. Checking the inheritance path for the tenant work class showed the shared layer work class, but after upgrade of the tenant layer, the IsAncestorOf function returned false and the functionality that uses isAncestorOf function failed if the parent class was in the shared layer and the child was in the tenant layer. To correct this, the logic has been updated so that rather than always checking in the shared layer, the system will check whether the Descendant class is defined in the tenant first.
SR-C79205 · Issue 416399
OnChange event only triggered on date field when value changes
Resolved in Pega Version 8.2
After configuring the onchange event for a date control field with some action, clicking on the Date picker option and selecting the same date triggered the onchange even when the value had not changed. This has been resolved by updating the code to store the previous value and check for a value change before firing the change event.
SR-C73994 · Issue 415479
OnChange event only triggered on date field when value changes
Resolved in Pega Version 8.2
After configuring the onchange event for a date control field with some action, clicking on the Date picker option and selecting the same date triggered the onchange even when the value had not changed. This has been resolved by updating the code to store the previous value and check for a value change before firing the change event.
SR-C77062 · Issue 416406
Improved security for Cassandra/Kafka process
Resolved in Pega Version 8.2
In order to improve system security for Cassandra and Kafka processes, the binding for the Kafka JMX port will only be applied to 127.0.0.1, and the JMX addresses have been made configurable.
SR-C76861 · Issue 415854
Handling added for undefined pxReqURI to ensure UI loading
Resolved in Pega Version 8.2
The Declarative Expression Network Viewer did not provide a text input box to enter in the property values and then update the network with these new values. This was traced to a failure in the UI loading caused by pxReqURI being undefined, and has been corrected by modifying the DeclarativeNetworkWithValues section to handle this condition.
SR-C79032 · Issue 417172
Pulse outgoing email character limit removed
Resolved in Pega Version 8.2
Previously, only the first 2000 characters of a Pulse entry would be displayed in the email notification. An enhancement has now been added to remove that limit and display the entire Pulse text in the related email.
SR-C78664 · Issue 417564
Container format for dynamic layout configuration passed to the view API
Resolved in Pega Version 8.2
The layout format field for the dynamic layout configuration was passed to the view API as "groupdFormat", but the container format remained unchanged. This has been corrected.
SR-C79560 · Issue 417566
Editable format configuration passed through DX API
Resolved in Pega Version 8.2
The editable format configuration of the OOB controls was not being passed through the DX API. In order to present the information in the right format as well as reduce the amount of roundtrips to the server to validate inputs, support has been added for modes(1) and modes(2) in editable and readonly formats.
SR-C80050 · Issue 417603
Schema name made consistent for DDL generation
Resolved in Pega Version 8.2
A platform upgrade failed if there were application schemas configured with a table configuration that specified a schema other than the rules schema. This was an issue caused by the generated DDL having the incorrect schema name for the table due to the name being hard-coded in the Data-Admin-DB-Table entry definition. The system was using this schema name to find the table and generate the correct changes, but the SQL statement used the table from the database connection instead of the override. When the XML that represents the difference between the "source" and "target" state is generated, the system is supposed to replace the schema name with the target schema name. However, if the source schema name is blank that step was skipped in order to defer to the connection for shipped tables. In order to ensure that the system can generate the correct DDL and complete the upgrade, the system will now always replace the schema name regardless of the source or target value.