SR-D18814 · Issue 493324
Enhancement added to fetch HTML attachment from CMS
Resolved in Pega Version 8.2.3
When email containing HTML was sent to the Listener, some of the characters were not getting decoded properly when viewing. In this case, HTML email content was saved as an attachment in CMS , and this error was traced to the system being unable to fetch the attachment. To resolve this, an enhancement has been added to fetch non-Pega database attachments using pxGetFileAttachmentContent.
SR-D25251 · Issue 493987
Added support for non-auto DisplayYesNo control
Resolved in Pega Version 8.2.3
A Change event on post value and refresh was not firing as expected in a section configured with a TrueFalse type property associated with a DisplayYesNo control. The same configuration worked correctly when used with a pxRadioButtons control. This was traced to non-auto control action JSON not generating on the second radio button(No) , and support has been added for this.
SR-D30955 · Issue 499872
Security updated for access roles
Resolved in Pega Version 8.2.3
Updates have been made in order to prevent a potential security issue related to browsing access for the Organization and Security: Groups and Roles view in Dev Studio.
SR-D16427 · Issue 495817
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-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.