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 681577
Cosmos Stakeholders menu updated to prevent loss of work party change
Resolved in Pega Version 8.6.3
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-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-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.
INC-197243 · Issue 687412
Locking up+E975dated for EmailLink
Resolved in Pega Version 8.7
After clicking a work link from email and opening the work object in a new window, opening the work object in the perform harness and performing a browser refresh by way of Actions -> Refresh resulted in a locking error when trying to submit the case. This was traced to the handling in the Ajax container: when an assignment is opened from the todo list, it will open it in primary Ajax container. If the complete web page was refreshed, the contents in the Ajax container were cleared and loaded back to previous state. While doing this process the lock of the Work Object was released and not added back. In order to achieve the lock after the refresh, the doUIAction activity has been updated to lock the case when the case is opened and reloaded.
INC-197243 · Issue 687413
Locking updated for EmailLink
Resolved in Pega Version 8.6.3
After clicking a work link from email and opening the work object in a new window, opening the work object in the perform harness and performing a browser refresh by way of Actions -> Refresh resulted in a locking error when trying to submit the case. This was traced to the handling in the Ajax container: when an assignment is opened from the todo list, it will open it in primary Ajax container. If the complete web page was refreshed, the contents in the Ajax container were cleared and loaded back to previous state. While doing this process the lock of the Work Object was released and not added back. In order to achieve the lock after the refresh, the doUIAction activity has been updated to lock the case when the case is opened and reloaded.
INC-198484 · Issue 689007
Tab error message localized
Resolved in Pega Version 8.7
Localization has been added for the message that is shown at a tab when a section in tabbed layout contains errors.
INC-198484 · Issue 689006
Tab error message localized
Resolved in Pega Version 8.6.3
Localization has been added for the message that is shown at a tab when a section in tabbed layout contains errors.
INC-198021 · Issue 686630
Corrected blank areas on maximized view
Resolved in Pega Version 8.7
A blank section was displayed when maximizing the reply screen. Investigation showed that when the editor was inside a positioned container with overflow hidden and the editor had a scrollbar with its body height greater than the document, the scrollIntoView would scroll to grey spaces which were originally hidden by overflow. This has been resolved by commenting out scrollintoview, since it is not necessary and scroll position/cursor will be retained without it.