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.
SR-D13388 · Issue 485169
Handling added for minor case creation errors
Resolved in Pega Version 8.2.3
When creating a case, if any step status failed due to a non-critical reason which did not impact case creation (for example, a mandatory parameter was missing from the data page), that failure state was propagated to SaveNew and ultimately to the case creation API. As a result of this failure report, no case ID information would be reported back to the requestor even though the case was created, and the API responded with status 500 - internal service error. This has been resolved by removing the StepStatusFail check from pzCreateCaseInternal so that non-breaking errors will not result in a 500 error, and a check has been added for page messages in svcAddWorkObject and svcPerformFlowAction so that validation messages are returned.
SR-D13450 · Issue 488137
Corrected Query logging level for Populate_UsepxRequiredSkillsCount
Resolved in Pega Version 8.2.3
A Query was being logged with Logging level of Error in pzPopulate_UsepxRequiredSkillsCount. This has been corrected.
SR-D13514 · Issue 489432
Data-test-id handling updated to resolve testing issue with custom controls
Resolved in Pega Version 8.2.3
After configuring a custom control, the control did not render as expected when trying to capture the scenario testing. Investigation showed that in readonly mode, two spans were wrapped with same data-test-id when formatType is number. This caused a ‘no unique selector’ issue with scenario tests. To resolve this, pzpega_ui_template_displayText.js has been updated to not include data-test-id on outer span when formatType is number.
SR-D13569 · Issue 491715
Additional parameter format added for multiselect controls
Resolved in Pega Version 8.2.3
Attempting to pass a parameter like "Value1", "Value2" to a data page used for the MultiSelect Control was not working even though the same format worked for autocomplete control. This was an issue where the flow of fetching the data differed between the two controls, and support for this parameter format has now been added for multiselect controls.
SR-D13880 · Issue 483332
Support added for using WorkPage class for FieldValue evaluation
Resolved in Pega Version 8.2.3
The Instructions provided under the Assignment details section of an assignment shape were not evaluating the FieldValue for the work object's audit history entries unless the field value was defined only at @baseclass. This was due to WorkPage class not being considered while evaluating a FieldValue, and has been resolved by modifying the InstructionsLookup control to use work class instead of the hard coded @baseclass.