SR-D33227 · Issue 510826
Check added for lock expiration when using Save for Default locking
Resolved in Pega Version 8.4
With the default case locking policy, during the process from creating a Case Object to Submit it was possible for multiple users to edit and save the same work object if the lock expired for the original user. No warnings appeared. To resolve this, handling has been added for a lock expiration scenario: previously, Save for Default locking was not considered. This has now been updated with a check that will evaluate whether or not the lock is gone before attempting to save.
SR-D24651 · Issue 495766
Proper assignment instructions sent when transferring
Resolved in Pega Version 8.4
Assignment instructions were not getting added properly when transferring to Workbaskets. Because both .pyInstruction and Param.InstructionNote are set in call Reassign (to workbasket), the same instruction value was being given twice. To resolve this, step 8 (Call Reassign) of Work-.pyReassignAssignment has been modified and will not send the InstructionNote param as instruction is already updated on the newassign page with the instruction value on reassign page in the previous step (step 7).
INC-175630 · Issue 653863
Application selections only announced when visible
Resolved in Pega Version 8.7
The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.
SR-B95830 · Issue 344260
Better handling for case updating when switching applications
Resolved in Pega Version 7.4
When using two applications, the application 1 case lifecycle view was shown at login. After switching to application 2, the case life cycle was not updated until the refresh icon was clicked. This was an issue with the pyCurrentCase value not being updated while switching apps, and an additional condition has been added to the pzSetCurrentCase Data transform to better handle application switching.
SR-B82049 · Issue 341054
pxCoverInsKey set in audit history when childcase created
Resolved in Pega Version 7.4
On adding an audit note during the creation of the child case, the audit history did not contain the reference to the parent case. Eventually, when the case was referenced, the pxCoverInsKey was populated in the history table. This was caused by an ordering error in the logic and the system has been updated to correct it.
SR-D39264 · Issue 518841
Multiple files uploaded using "select file" will be handled asynchronously
Resolved in Pega Version 8.4
In order to resolve an intermittent error when uploading multiple files using the "select file" button, each file will be uploaded asynchronously to avoid overloading the browser threshold.
SR-D30687 · Issue 500892
Update message clarified for manual case update after SmartEmail shape used
Resolved in Pega Version 8.4
For a case with #1 Optimistic Lock and #2 a SendEmail smart shape in the middle of a flow, once the SendEmail updated the case in the background, updating the case manually resulted in a "Please re-submit" message being displayed without any explanation. This has been resolved by ensuring that instead of a resubmit message (system update), the system will show a refresh message (normal update).
INC-173725 · Issue 656480
Logic updated for DX API retrieving View/Action ID using embedded property
Resolved in Pega Version 8.7
While calling the DX API using Assignment ID and action ID, a 500 error response was logged indicating that the server encountered an unexpected condition that prevented it from fulfilling the request. Investigation traced this to the logic used for resolving an embedded property referenced in a control/field to identify the correct page class. In a non-work object context for flow actions the new assign page doesn't exist, but the system was checking for it and clearing off errors from the named page. This has been corrected.
SR-B89155 · Issue 337930
Case stages correctly displayed in Microsoft Internet Explorer
Resolved in Pega Version 7.4
Case stages were not being properly displayed when using Microsoft Internet Explorer. This was due to the UI kit version of the "pxDisplayStages" rule using the Dynamic Layout with inline format, causing the parent div to not be used for width in Microsoft Internet Explorer. This has been fixed.
INC-170514 · Issue 653762
Lock conflict resolved for AssignmentCheck
Resolved in Pega Version 8.7
The error "Unable to unlock this work object" sporadically appeared in both the runtime log and Pega RULES log when the robot was trying to create a case in Pega using an API call. Investigation showed that as the case was created, it was pulled by another robot (another requestor) which was using the GetAssignments API. This caused the perform assignment check to fail. To resolve this, a 'when' rule has been added to the performAssignmentCheck Activity.