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.
SR-D14159 · Issue 493082
Toggle added for displaying exception stack trace
Resolved in Pega Version 8.2.3
When text like "%25" was added to the login URL, the full exception stack was displayed on the screen. To resolve this, when the prconfig 'initialization/displayexceptiontraceback' is set to false (default value), the system will render the status.jsp instead of error.jsp and will not populate any sensitive data in the request object. If its set to true, the system will fall back to the old approach which renders error.jsp and emits the stacktrace.
SR-D14161 · Issue 490594
XSS protection added to decryptURLString
Resolved in Pega Version 8.2.3
In order to secure against Cross-Site Scripting attacks, decryptURLString will return a blank string instead of plain text if it is not given valid encrypted text.
SR-D14521 · Issue 486528
Added support for sorting by field value instead of localized value
Resolved in Pega Version 8.2.3
In a datapage-sourced dropdown with 'group by functionality' enabled in ascending order, the values were being sorted according to their localized value and not their field value. This was a difference between templatized and non-templatized handling, and has been resolved by adding the ability to sort the group label by field value in the templatized UI.
SR-D14591 · Issue 485929
Check added to resolve intermittent console errors
Resolved in Pega Version 8.2.3
An intermittent issue where an autocomplete control was hanging after repeated use has been addressed by adding an additional check (dispElem && dispElem.parentNode) to avoid console errors.
SR-D14601 · Issue 488289
Unique ID generation added for simultaneous multiple text area boxes
Resolved in Pega Version 8.2.3
In the Interaction portal, adding a task for a interaction using a form with a character-count enabled text area worked as expected when the interaction first opened a task with the character counter text area. However, if a second version of the same task was opened before the first task was completed, the second text area was not responsive or working as expected. This was traced to the system generating the same ID attribute for both instances of the text area character counter span, and has been resolved.