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-117674 · Issue 170571
Smart Shapes use properly limited to work class
Resolved in Pega Version 7.1.7
An error in the code made Smart Shapes visible when creating a data-class flow. Attempting to include them by dragging them into the flow design pane resulted in an "empty" utility shape that was missing many of the options normally offered. Because Smart Shapes are designed only for work classes, Smart Shapes will not be visible in shape menu when a flow is created in data class.
SR-108805 · Issue 149539
Help updated to explain When Rule "ALL" Evaluation behavior
Resolved in Pega Version 7.1.7
A 'when' rule evaluating all pages in page list will only evaluate the properties on pages in the list that contain that property. This may cause a "true" result that does not match customer expectations. The hover help has been clarified to explicitly state that the evaluation results apply only for those pagelist entries where the property exists and not for all the page list entries.
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-116908 · Issue 168347
When rules now display all text fields for function aliases
Resolved in Pega Version 7.1.7
Creating a new Access When rule failed to show the text fields for most available function aliases when a condition was added to the rule. This was an error in the passing of the classname to the function, and has been fixed.
SR-116347 · Issue 166799
Error resolved for adding Stage Step Specifications using RTE and Google Chrome
Resolved in Pega Version 7.1.7
While configuring a stage behavior in Google Chrome, if a user had focus within the Rich Text Editor for a specification and submitted the modal, an error was generated. This was caused by an invalid post-value check, and the unnecessary post value has been removed.
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.