SR-D16427 · Issue 497221
Multi-nodes rebuild LibraryMetadata to ensure all RUFs are present on change
Resolved in Pega Version 8.2.3
When performing a complete Application import into a clean installation, references to certain RUFs went unresolved during the initial assembly. Investigation showed that after introducing a new RUL or RUF on one node in a cluster and then generating that, the other nodes in the cluster did not have the correct LibraryMetaDataCache for that RUL. Therefore assemblies on those other nodes could be bad and throw a runtime UnresolvedAssemblyError. This has been resolved by modifying the way the Library subsystem processes the node changes events for Library Generation to ensure that each node completely rebuilds the LibraryMetadata for that RUL so it contains all the RUFs.
SR-D22113 · Issue 498313
Multi-nodes rebuild LibraryMetadata to ensure all RUFs are present on change
Resolved in Pega Version 8.2.3
When performing a complete Application import into a clean installation, references to certain RUFs went unresolved during the initial assembly. Investigation showed that after introducing a new RUL or RUF on one node in a cluster and then generating that, the other nodes in the cluster did not have the correct LibraryMetaDataCache for that RUL. Therefore assemblies on those other nodes could be bad and throw a runtime UnresolvedAssemblyError. This has been resolved by modifying the way the Library subsystem processes the node changes events for Library Generation to ensure that each node completely rebuilds the LibraryMetadata for that RUL so it contains all the RUFs.
SR-D27695 · Issue 500838
Email Discussion Thread retains Formatting
Resolved in Pega Version 8.2.3
CSS styles were not being retained in the discussion thread when replying to InboundCorrespondence cases. This was traced to a missing value in Param.latestReply activity pzCreateExternalPostFromMail, and has been resolved by setting an initial plain text value to the param.latestReply before it is set with the HTML value. This prevents having a blank parameter value if the incoming HTML value is empty.
SR-D18690 · Issue 487615
Duplicate check repaired
Resolved in Pega Version 8.2.3
A case created with one of the "must match" values as blank was not being treated as a duplicate case. This was traced to a check inserted in an earlier release as part of work done to handle a null FirstName value in the 'Case Match' decision rule, and has been resolved by reworking the original solution and including the 'is same' usecase.
SR-D25560 · Issue 494556
Added DSS to handle BIX extracts under parse delimiter rules
Resolved in Pega Version 8.2.3
When parse delimiter rules were applied, the File Listener was not parsing the CSV manifest file generated from a BIX extract until the file was resaved. This was traced to a space after a comma in the extracted files, and has been resolved with the addition of a DSS which enables the use-specified delimiter to remove the space after the comma in the manifest files.
SR-D17037 · Issue 487530
Check added for backwards compatibility with Case Type when rules
Resolved in Pega Version 8.2.3
After upgrade, the When rules present on case type rules (used for skipping stages or showing/hiding stage-wide or case-wide actions) were not executing at run time. This was traced to the introduction of the pySkipOrAllowType property in recent versions, and was only reproducible when the ApplicationRuleset was locked and after upgrade irrespective of whether the condition for when was true or false. To resolve this and enhance backwards capability, a check has been added for the SkipOrAllowType property being empty.
SR-D19111 · Issue 496591
Improved compatibility for mapping pyMessageId with out-of-the-box email index rule
Resolved in Pega Version 8.2.3
After upgrade, the process used for retrieving a reply for an email sent automatically by the system and comparing it with the incoming email to determine if it was a reply or not was failing to trigger an index or find instances of the class Data-Corr-Email that was supposed to save the property pyMessageId. This was related to recent refactoring of the handling for email headers in the Send activity, which moved them from a created AttachmentPage to the Primary page. The code in SendEmailNotification was still checking for the headers to be in the old location when going and adding the messageID, and was not taking it from the parameters. To resolve this, the pyMessageID will be set on the Primary page and messageID will be set on the parameter page based on the messageID in emailHeaders on the PrimaryPage.
SR-D28502 · Issue 499412
Checkbox visibility after upgrade resolved
Resolved in Pega Version 8.2.3
After upgrade, checkboxes were not visible in the dashboard and widgets could not be selected. This was traced to a difference in the generated Java used for the markup for the checkboxes, leading to a call for the pzHeaderCell function to be missing an 'if' condition needed by the UI. This has been resolved.
SR-D16200 · Issue 494583
Support added for decimal values in RichTextDisplay HTML
Resolved in Pega Version 8.2.3
After upgrade, correspondence in Outlook was displayed with an incorrect left alignment and footer images were stuck together. This was caused by a difference in the Richtextdisplay mode, which was previously set to 'literal' and is now richtextdisplay.Issue. To resolve this, an enhancement has been added which supports decimal values for the HTML attributes.
SR-D14064 · Issue 490217
Support added for Tumbling Window size defined by field
Resolved in Pega Version 8.2.3
When using a Data Flow that called an Event Strategy that contained a Tumbling Window, all records were processed when given a user-defined option. However, trying to use a calculated "Defined by Field" option designed to time the windows out at the same time each hour resulted in only a small percentage of records being successfully written to the destination dataset. This was traced to the logic used by the out of order timers not supporting this use, and handling has now been added to resolve this issue.