SR-C79762 · Issue 419157
Decision table decision shape produces correct connector
Resolved in Pega Version 8.2
After adding a decision shape and making its type "Decision Table", the connector that was automatically built showed the condition type as "Result", but incorrectly labeled it as a When rule. This was traced to a missed use case in the decision related connectors, and has been corrected.
SR-C77106 · Issue 416869
API modified to prevent potenial security issue with JSON objects
Resolved in Pega Version 8.2
A potential security issue was found where the Pega API allowed a different JSON object to be posted back than had been retrieved. This has been corrected.
SR-C75278 · Issue 415735
Extension added to wrapper activity to allow skipping completed assignments
Resolved in Pega Version 8.2
The withdrawal of the pyPopulateCaseContentsWrapper activity rule from the PegaCardSd ruleset caused the wrapper activity in Pega-EndUserUI to be utilized instead, but that activity included a different behavior which resulted in the Completed Assignments checkbox being set as 'true' during processing instead of staying 'false' unless checked by user. This resulted in additional assignments showing when previously only open assignments would show as default. In order to correct this, a new extension "DT(pyPopulateCaseContentsWrapperExtension)" has been provided to set the required fields in order to skip fetching the completed assignments. To utilize this, set the pyShowCompletedAssignments property to true in the extension DT to hide the assignments.
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.