SR-D20817 · Issue 499920
Async cache checking updated for interaction reload use
Resolved in Pega Version 8.2.3
A thread level data page using connect REST to get data from an external system with the "Reload once per interaction" checkbox ticked was being loaded asynchronously from the activity when by default the data page it was supplying needed to be loaded synchronously. Due to this, changes to the data in the external database were not reflected in the data page. This was caused when an async cache was referred and the freshness check for the data page instance did not consider the 'reload once per interaction' flag because it would cause the data page to load twice. The cache checking has been updated to resolve this.
SR-C95733 · Issue 444477
SendSimpleEmail modified to show complete attachment subject line
Resolved in Pega Version 8.2.3
The complete subject of the correspondence attached in a work object was not displayed in the UI. The clipboard page pyWorkPage -> Attachment (Link-Attachment) also showed an incomplete value in the pyMemo property, displaying only 64 characters. Investigation showed that pyCorrPage.pyLabel was being set to 64 characters in the Work-.SendSimpleEmail activity, and then used LinkMemo to show the value in the UI. To resolve this, the system will take HistMemo as the LinkMemo as well if it is available and then truncate it to the Link-Attachment.pyMemo size to store the entire value as exposed.
SR-C96552 · Issue 488911
WordMacroManager updated to support both 32-bit and 64-bit
Resolved in Pega Version 8.2.3
After upgrade, the FlowAction=> CreateMergedWordDoc was not working. This was traced to Word Merge failures due to 64-Bit incompatibility with the WordMacroManagerDot template file, and has been resolved by updating WordMacroManagerdot.dot so it supports both 32-Bit and 64-Bit.
SR-C97046 · Issue 485715
Added restriction to limit environment sending multiple OTP emails
Resolved in Pega Version 8.2.3
Multiple One Time Password (OTP) Emails were being sent for a single requestor on a change password screen when the password was expired. This was caused by the environmental settings refreshing the changepassword harness, and has been resolved by adding a restriction against sending multiple OTPs for a requestor to whom an OTP has been successfully sent once.
SR-D10666 · Issue 490865
InitializeRequestor utilized to prevent Inconsistent authentication requestor state
Resolved in Pega Version 8.2.3
A 'resource not found' issue was causing an inconsistent Robot status. This was traced to an improperly configured application where the service authentication requestor was left in a wrong state but was being returned to the pool. To prevent the issue of requestors being in an odd state if they try to authenticate and an error occurs, the system has been updated to now always call initializeRequestor, not just for Authenticated cases.
SR-D10775 · Issue 490170
Finalluy block added to Data-COS-.COS-Print streams
Resolved in Pega Version 8.2.3
A security scan detected a potential issue with the activity Data-COS-.COS-Print not closing the stream in a finally block. Although this activity is not in current use, a finally block has been added that will close all of the conditionally initialized streams if they are still initialized.
SR-D10889 · Issue 482668
Intervals for DateTime control inside table grid corrected
Resolved in Pega Version 8.2.3
The "allow time to be displayed in the interval of minutes" feature did not work as expected for a DateTime control configured inside a table grid. If a value for minutes was chosen, say 30 minutes, it displayed all the minutes from 00 to 59 instead of displaying 00 and 30. The same control used inside a simply dynamic layout worked correctly, displaying 00 and 30. This has been resolved by adding logic to support having only time with drop downs.
SR-D11289 · Issue 484055
Mobile support added for Report Definition chart slider
Resolved in Pega Version 8.2.3
Because the report definition ruleform chart slider was historically not supported on mobile devices, enabling the touch API in Chrome resulted in confusing behavior where the slider worked in mobile mode on a laptop but not on a mobile device. This was due to the chart slider being a jQuery UI slider component (ui-slider) that was built without support for mobile devices. An enhancement has now been added to utilize the jQuery UI Touch Punch library, which makes jQuery UI components mobile-friendly, by loading it at the start of pzRRChart.
SR-D11605 · Issue 485661
:JAWS correctly reads heading for Report browser/viewer
Resolved in Pega Version 8.2.3
JAWS 18 was not reading the titles in the report browser and report viewer as "heading level 1" as it should. For the Report Browser, JAWS was reading the title as "<title> - heading level 2", and for the Report Viewer, JAWS read the report title as "<title> - frame". This has been corrected by adding the appropriate aria tags to pzGetStyledLocalizedText.
SR-D1270 · Issue 488260
DB table mapping will check for existing properties before creating them
Resolved in Pega Version 8.2.3
Using the Database table class mapping tool to map an external database table to a class and create properties according to columns in the table was resulting in the property being created as 'not available' and not case sensitive if the property to be created while mapping was already present in the inheritance hierarchy. This led to an error caused by the property validation failing in the validateReportDesignTab activity. Previously the database table mapping tool did not check to see whether the properties to be created existed already in the parent class hierarchy. With this update, the system will check before allowing the mapping, and if the properties exist in the hierarchy already they will not be populated.