INC-198326 · Issue 690316
Tab key menu navigation updated
Resolved in Pega Version 8.5.6
Using the tab key to navigate links in the left menu would intermittently skip links or not appear to advance. This was an unintended side effect of work done to use the tab key to move out of the portal menu and to the next focusable element, and has been resolved by modifying the re-setting tabindex for left navigation so it will anchor on the first element in the menu list for tab traversal.
INC-164012 · Issue 640039
Source edit with formatting resumes process automatically
Resolved in Pega Version 8.7
When opening a paragraph rule and clicking on Actions > checkout out to branch, the rule refreshed and the modal never appeared to allow the selection of a branch on the current application. This was an inadvertent side effect of work done to resume the event queue if it was paused when applying styles, and has been resolved by modifying the work so it resumes the action sequence only when source mode is initialized in the Rich Text Editor.
INC-188605 · Issue 673597
Missing property added for permission check on CanPerformAssignment Go button
Resolved in Pega Version 8.7
With the introduction of the pzCanPerformAssignment When Rule to control the visibility of the Go button in the Assignment lists, the context for checks is now within the D_CaseAssigments Data Page. One of the checks executed by this When Rule is performed by the function @pzCanPerformAssignment() which calls an API to examine the RARO configuration for the Assignment Class in question. When the Read permission is controlled by the canPerform Access When Rule, a function is called which relies on the presence of the .pxRefObjectClass to check the privileges; In the new D_CaseAssignments Data Page the .pxRefObjectClass was not mapped during construction and as such the value for workClass passed to the API method was "" meaning the relevant checks were not executed. This has been resolved by adding the missing property pxRefObjectClass that is needed for execution permission checking.
INC-178579 · Issue 657742
Corrected blue line showing on grid expansion
Resolved in Pega Version 8.5.6
When a grid configured on the portal had an overlapping case preview, a blue vertical line was displayed on the preview window when expanding a row. This has been resolved by increasing the z-index for the preview panel to cover the underlying grid resize indicator.
INC-176742 · Issue 657070
DX API JSON response maintains special characters
Resolved in Pega Version 8.7
When processing a Pega workflow with external UI through the DX API, entering some value with special characters like "(" and saving the case resulted in "(" being replaced with junk characters that were displayed on the UI when the case details were sent back from Pega. This was traced to special chars not being supported in the validation error message when displayed on c11n system, and has been resolved by consuming the 'message' value in the error object instead of localizedValue.
INC-191674 · Issue 681576
Cosmos Stakeholders menu updated to prevent loss of work party change
Resolved in Pega Version 8.7
The Stakeholders menu for adding work parties to cases available in Cosmos Utility panel was not saving work party changes as expected when the case was also open for performing assignments. When the assignment was completed, the work parties were reset to the values present when the case was opened. The list of stakeholders is saved as a property in work page. When an assignment is opened there are two threads, and any stakeholder added is then added only in the first thread. Because it was not added in the second thread (acprimary Ajax container - processing assignment) the stakeholder addition was lost due to the second thread overriding the first thread. To resolve this, if an assignment is being processed while trying to open the stakeholders model, an additional modal will be displayed with the following options: - resign from opening stakeholders modal and continue process assignment or, - resign from processing assignment (all unsaved changes will be discarded) and open stakeholders modal
INC-191674 · Issue 681575
Cosmos Stakeholders menu updated to prevent loss of work party change
Resolved in Pega Version 8.5.6
The Stakeholders menu for adding work parties to cases available in Cosmos Utility panel was not saving work party changes as expected when the case was also open for performing assignments. When the assignment was completed, the work parties were reset to the values present when the case was opened. The list of stakeholders is saved as a property in work page. When an assignment is opened there are two threads, and any stakeholder added is then added only in the first thread. Because it was not added in the second thread (acprimary Ajax container - processing assignment) the stakeholder addition was lost due to the second thread overriding the first thread. To resolve this, if an assignment is being processed while trying to open the stakeholders model, an additional modal will be displayed with the following options: - resign from opening stakeholders modal and continue process assignment or, - rresign from processing assignment (all unsaved changes will be discarded) and open stakeholders modal
INC-177104 · Issue 666334
Resolved-by field reflects queue processor close
Resolved in Pega Version 8.7
When a case was resolved by the queue processor, for example when the SLA ended and a case was automatically Resolved-Withdrawn by the system, the "Resolved by" field was blank. This was caused by the pyOperatorInfo control looking for the system account user data in the application users pool, and has been resolved by updating the control to display the localizable "System" name in this scenario.
INC-177104 · Issue 666332
Resolved-by field reflects queue processor close
Resolved in Pega Version 8.5.6
When a case was resolved by the queue processor, for example when the SLA ended and a case was automatically Resolved-Withdrawn by the system, the "Resolved by" field was blank. This was caused by the pyOperatorInfo control looking for the system account user data in the application users pool, and has been resolved by updating the control to display the localizable "System" name in this scenario.
INC-166444 · Issue 642114
FlexModalTemplate Modal window size consistent
Resolved in Pega Version 8.7
The FlexModalTemplate modal window size was changing on second click. This was a missed use case for dirty dialog CSS implementation, and has been resolved by moving the CSS necessary into the isDirtyDialogOpen if condition.