INC-215046 · Issue 714674
Deleting case in create stage returns user to home/Dashboard
Resolved in Pega Version 8.6.5
When using a multi-step form in Create Stage, performing a Cancel + Save&Close, then re-opening the case and using a Cancel + Delete, the result of the cancelation is not shown and the user is not returned to the Home/Dashboard screen. This was caused by an issue where the specific AJAX container was not closed, and has been resolved by modifying the pyCaseActionAreaButtons to execute the pyCloseCase local action when clicked to close the case.
INC-215215 · Issue 713856
Validations fire on collapsed accordion layouts
Resolved in Pega Version 8.6.5
Client validation was not firing on the selected tab of a layout group if the accordion layout was collapsed. If focus was switched to the second tab, the client validation on the first collapsed tab did not work. This has been resolved by modifying the 'else if' condition to pass the validation for the fields places in layout group tabs.
INC-215725 · Issue 716663
Go Button accessible via keyboard
Resolved in Pega Version 8.6.5
When worklist was launched using the Mozilla Firefox browser, the Go Button used to advance the case to the next stage was inaccessible via keyboard and did not have the proper focus. This has been resolved.
INC-216404 · Issue 721512
Table alignment corrected for PDF
Resolved in Pega Version 8.6.5
The align="center" styling was not getting applied whenever the Rich Text Editor was in readonly mode. To resolve this, the CSS style has been updated to correct table center alignment for readonly Rich Text Editor documents and paragraphs in the pzbase-gadgets-ckeditor and pzbase-div-layout CSS files respectively.
INC-216923 · Issue 722207
Event reset added for delegated data type horizontal scroll
Resolved in Pega Version 8.6.5
Clicking on the horizontal scroll bar and dragging it to the right to enter data/records in a delegated screen in the Case Manager portal was not working correctly. This has been resolved by adding special handling to clear the event queue for the horizontal scroll in a repeating dynamic layout grid.
INC-216927 · Issue 714497
Conditional handling added for perceived invalid valuelist reference in design time
Resolved in Pega Version 8.6.5
After adding a value list property '.pyDateTimeValue(2)' in a section configured in the view editor, the design time error "config issue" was shown. There were no errors at run time and the application's behavior was correct. Changing the subscript of the value list property to (1) ran without an error. In this scenario, the actual usecase configuration will populate .pyDateTimeValue(2), but the view editor believed there was an error in the section because there was no reference to pyDateTimeValue(1) first. This has been resolved by conditionally changing the pyValue to a template property in design time when a perceived invalid valuelist reference is provided as property in the panel.
INC-217304 · Issue 714590
Regex handling updated for non-empty inputs
Resolved in Pega Version 8.6.5
Expression evaluation for non-empty regex has been updated to include testing for unicode characters to align with recent updates made to CKEditor.
INC-217655 · Issue 723564
Resolved validation check freeze for Dynamic Layout Group
Resolved in Pega Version 8.6.5
After creating a multi-step form where step 1 had a Dynamic Layout Group(tabbed) that used form fields configured with validations, clicking next with empty/invalid values in the form intermittently caused the screen to freeze and a javascript exception was logged. This was traced to a missed use case related to templates in the childNode, and has been resolved by adding the necessary safe checks in lgtemplate and lgcelltemplate.
INC-217680 · Issue 717606
Tab name displayed correctly in embedded mashup portal
Resolved in Pega Version 8.6.5
"Work Item" was given as as the tab header instead of the Case ID# when a case link was clicked/opened in an application embedded in an external site (IAC). This was traced to the pega.desktop.support.doGadgetAction function not calling the regular handleGadgetLoad function in this scenario, and has been resolved by explicitly directing work items opened in a multi-doc mashup portal to use handleGadgetLoad.
INC-218265 · Issue 720613
DoClose updated to resolve lock and context issues
Resolved in Pega Version 8.6.5
An interaction case was closing when intent tasks were closed from CSRecents. Investigation showed this was due to the doClose activity not being triggered in the right context, and has been resolved. An additional issue with locks not being correctly released after opening the new case Create stage and clicking Cancel in the modal was traced to a missing pyWorkPage in the safeURL params that was needed by the doClose activity, and this has been resolved by adding the primary page name.