SR-C65757 · Issue 406951
Support added for POST binding in SAML logout
Resolved in Pega Version 8.2
Enhancements have been added in code and rule changes to support POST binding for SAML logout. In addition, handling has been added to resolve an ArrayOutOfIndexException error that was appearing if IDP sent parameters without any value.
SR-C67870 · Issue 407162
Added evaluation client thread name check to Change Tracker
Resolved in Pega Version 8.2
The Change Tracker was intermittently not working as expected between main DC and micro DC div when trying to use a change in microdc context (specifically an update to D_Interaction.InteractionHeaderRefreshDateTime) to refresh the document in the main DC. In order to ensure consistent updating, a check has been added for the current thread name while executing evaluate client conditions.
SR-C50355 · Issue 407421
Corrected applies-to class in Test case rule
Resolved in Pega Version 8.2
On test case rule form with assertion type Result count Filter class MIDAS-SR and filter condition @endswith(.cid,".html"), opening the function builder using the gear icon and trying to use the Test feature of the Function builder resulted in an incorrect applies-to class. The result was for the Test case instead of showing correct Applies to class of MIDAS-SR. This was traced to the Filter class of the context page not being passed to the function builder in Test case rule, and has been fixed.
SR-C69567 · Issue 407730
ICMP ping flag enabled and Hazelcast alerts/info messages added
Resolved in Pega Version 8.2
Hazelcast Professional Services recommends enabling ICMP ping as a method to detect network failures more quickly. This can also help to determine whether a failure is due to a network outage: if the ICMP ping is successful but the heartbeat timed out, that may be an indication of a unresponsive (GC pause, long running process, etc) node. To facilitate this use, the ICMP ping flag can now be used in conjunction with enabling ICMP ping on EC2 through the security group and enabling ICMP in the Hazelcast configuration. In order to facilitate determining root causes for Hazelcast errors in the logs, the following alerts and info messages have been added: Actionable Events (Alerts): Each of these events is worth noting an alert for. An action may be necessary. - [Partition] Lost - A partition was lost. Possible data loss has occurred - [Lifecycle] Merge Failed - A member’s attempt to merge with the cluster has failed - [Migration] Migration Failed - A partition migration has failed Non-Actionable Events (Info): These events are of interest but don’t require any actions. - [Membership] Added - A new member was added to the cluster - [Membership] Removed - An existing member has left the cluster - [Lifecycle] Merging - A member is merging with the cluster - [Migration] Started - A partition migration has started - [Migration] Completed - A partition migration has completed - [Lifecycle] Shutting Down - A member is shutting down
SR-C62835 · Issue 408359
pzReindex defaults to true during branch merge and initial save
Resolved in Pega Version 8.2
When using Declare Indexes intended to be fired when a KYC rule type was saved, merging a KYC rule type from a branch to a ruleset which contained the rule resulted in the declare indexes not firing from Rule-pyMergeInstance. If the branch was merged into a ruleset which did not contain the KYC rule, the Rule-pyMergeInstance fired the declare index rules as expected. This was an issue with using Declare Indexes in an unexpected way: Declare Index works only when a property that is tracked is changed, and merging a branch rule to base ruleset does not change any tracked property. However, there was a Force Reindex happening when the saved instance had a different pzInskey than one that already existed in the db. This occurred when the rule was merged to new ruleset where the pzInskey in the DB would be null, and was expected behavior. In order to ensure Declare Indexes fire during a merge, pzReindex will be set to true in the Merge Wizard before saving the rule while doing branch merge. It will be reset/set to false after the rule has been merged and saved to avoid the additional overhead of triggering re-indexing every time the rule is saved afterwards. Further enhancements will be made in an upcoming release regarding parameter handling in templatised UIs.
SR-C66633 · Issue 408773
Corrected DADT mapping for PegaDATA tables during upgrade
Resolved in Pega Version 8.2
After upgrading, old data tables being upgraded to new data tables (local storage) had the DADT table mapping changed from PegaDATA to CustomerDATA schema even though the tables themselves remained in PegaDATA format. This was traced to a missed use case in an enhancement that allowed creating a data type only in a CustomerData data base. To resolve this issue, the validation for restriction of PegaDATA has been removed and the param.nonPegatable will be set to false in cases where the database type is PegaDATA in pzCreateLocalDataStorage.
SR-C70639 · Issue 409664
Node ID correctly transmitted for PEGA0066 Alerts
Resolved in Pega Version 8.2
The PEGA0066 alert containing information about synchronization errors or connection lost did not contain the correct value in the Node ID field, causing PDC to not be able to handle the alerts on mobile. This has been corrected.
SR-C68443 · Issue 410236
Changed French locale to use getshortmonths to descriminate between June and July in datepicker
Resolved in Pega Version 8.2
When using the French locale, there was a problem selecting the month of July from the date picker because the three-letter abbreviations of June and July are the same in French. To resolve this, the system will now use the Java API getShortMonths in the French locale which gives 4 characters for the months.
SR-C62635 · Issue 405290
Changed French locale to use getshortmonths to descriminate between June and July in datepicker
Resolved in Pega Version 8.2
When using the French locale, there was a problem selecting the month of July from the date picker because the three-letter abbreviations of June and July are the same in French. To resolve this, the system will now use the Java API getShortMonths in the French locale which gives 4 characters for the months.
SR-C41102 · Issue 410423
Resolved error in editing flow rule assignment shapes
Resolved in Pega Version 8.2
The submit of an assignment properties modal window was not closing the modal, and instead opened a new window with an error page indicating a NullPointerException. This happened whether or not there were changes made to the assignment properties, and occurred for the assignment shapes on any flow. This was traced to a UI limitation in the backward compatibility of the "parent.parent.pyWorkClass" property which caused the property reference to not be resolved for hidden controls in client side template. To correct this, updates have been made to "pzAssignmentTab" (in Data-MO-Activity-Assignment class ) and "pzPropertyPanel" (in Data-MO-Activity-Assignment-WorkAction class).