INC-145939 · Issue 606896
Updated handling for ID value change during REST connection creation
Resolved in Pega Version 8.5.3
When using the REST Connector Wizard to create a connector, if the ID was changed on the 4th (last) step of the Wizard and then the Create button was pressed, the screen would freeze and a display a javascript error. Investigation showed that when the ID was changed on the screen, the new value was not updated properly and subsequent function calls threw errors. This has been resolved.
INC-146396 · Issue 608827
Upgraded pd4ml library to support Hindi text
Resolved in Pega Version 8.5.3
Some Hindi letters were not displayed properly in PDF . This was caused by Hindi text being only partially supported with earlier versions of the pd4ml library. It is now fully supported with the 4.0.9fx3 version, and the system has been upgraded to 4.0.9fx3 jar for better rendering of Hindi characters.
INC-147245 · Issue 612868
Expand Pane icon responds to enter key when using JAWS
Resolved in Pega Version 8.5.3
In an Operator ID rule in Dev Studio, pressing the Enter key when focused on an Access Group expand icon caused the focus on the page to move to the top of the Contact Information frame (top left corner of the Frame). The only way to use the enter key to expand the pane without the refocus was to tab to the arrow icon and then tab a second time before pressing enter. This was traced to the expand caret icon being focussed twice due to the tabIndex for both the TD and SPAN elements holding the caret icon: TD had a focus element for accessibility of the grid, and SPAN had it for the expand pane accessibility. This has been resolved by adding a check condition before adding tabIndex to the first cell in the Grid.
INC-147757 · Issue 620011
RecordFieldValuesList page cleared
Resolved in Pega Version 8.5.3
Investigation of web node crashes traced the issue to a condition where the RecordFieldValuesList page was not cleared. This has been resolved.
INC-148272 · Issue 609001
Increased specificity for collapsed DL
Resolved in Pega Version 8.5.3
When using the collapsible header functionality of a container skin format, the styling was not being applied correctly to the header. This has been resolved by increasing the specificity for a collapsed dynamic layer.
INC-149953 · Issue 613729
Increased specificity for collapsed DL
Resolved in Pega Version 8.5.3
When using the collapsible header functionality of a container skin format, the styling was not being applied correctly to the header. This has been resolved by increasing the specificity for a collapsed dynamic layer.
INC-150072 · Issue 621294
Section Include error handling updated
Resolved in Pega Version 8.5.3
When trying to add or include a section in the design template mode of a section rule or during run time of the application, the error "java.lang.StringIndexOutOfBoundsException: String index out of range: -1" was generated. Investigation showed this was originating from the SectionIncludeForm_Post activity of the class Rule-File-Form, and was traced to a system error related to the 'if' condition which verifies the circular reference of the section being newly added. Because this was a system error and not one generated by Pega, there was no handling for it. To resolve this, the sectionincludepost activity in rule-form class has been updated to determine the source and properly handle the error messages.
INC-150188 · Issue 613655
Dirty dialog flag reset added for custom modals
Resolved in Pega Version 8.5.3
When a discard button in a custom Cosmos modal dirty dialog was clicked, pega.u.d.isDirtyDialogOpen was not reset to false. This caused the modal dialog to not be shown the next time. This has been resolved by modifying pzpega_ui_doc_dirtyhandling to support this dirty handling discard use case.
INC-150222 · Issue 612577
Custom client-side future date validation works on mobile
Resolved in Pega Version 8.5.3
After developing a custom client side validation based on documented examples that used jquery to locate two input fields (date pickers) and added an on-change function, the validation worked as expected on the desktop but gave a validation error for any future date when using the mobile app or browser. This was an issue with the name attribute handling on mobile, and has been resolved.
INC-150325 · Issue 616994
Child case has correct context when created from smart shape
Resolved in Pega Version 8.5.3
The Cosmos Summary Panel was not always updating as expected when a child case was created via a smart shape in the current case flow; the new case opened, but the summary panel still showed the details of the previous case. This occurred when using a create case smart shape in a flow where the case is assigned to the current user, and was due to the child case assignment being opened inside the parent context. This has been resolved by ensuring the child case is opened in the correct context.