SR-D800 · Issue 487305
Mashup error resolved with try/catch block for Microsoft Internet Explorer framelement exception
Resolved in Pega Version 8.2.3
When a portal was launched using mash up, the intent tasks were not launched in Microsoft Internet Explorer when Add tasks button was clicked. This was found to be a site-specific use case only found with Internet Explorer, and has been resolved by adding a try catch block for a window.framelement exception thrown by IE.
SR-D17822 · Issue 490244
LastRecordedTime updated to ensure full audit history
Resolved in Pega Version 8.2.3
When running a test flow where a flow action was configured with a pre-processing activity that used a loop to add some audit history entries, some of the audit entries were getting skipped. For example, if the loop should generate 5 entries, only 3 were seen in the history. This was traced to the pxGetCurrentTimeStampThreadUnique() function where the system checks whether the current time is greater than the LastRecordedTime. The comparison handling of LastRecordedTime and gTimeValue have now been updated so LastRecordedTime is set correctly.
SR-D18814 · Issue 488258
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-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.