SR-A76381 · Issue 252860
Customizable when added for PegaPULSE delete button
Resolved in Pega Version 7.2.2
In order to support more customization, an enhancement has been added to hide the delete link on PegaPULSE entries based on conditional circumstances (i.e. entry is older than x hours). The overridable when rule 'pyCanDeletePost' has been provided and is referenced in the pzISCurrentUser when rule with AND condition to the existing condition.
SR-A76381 · Issue 252811
Customizable when added for PegaPULSE delete button
Resolved in Pega Version 7.2.2
In order to support more customization, an enhancement has been added to hide the delete link on PegaPULSE entries based on conditional circumstances (i.e. entry is older than x hours). The overridable when rule 'pyCanDeletePost' has been provided and is referenced in the pzISCurrentUser when rule with AND condition to the existing condition.
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-D26785 · Issue 495892
Corrected error when persisting temporary work object
Resolved in Pega Version 8.2.4
When persisting a temporary work object using the Persist case shape, the internal assignment handle was not updated to include the work object's ID. Subsequent attempts to access the internal assignment (such as the "Edit" button on the Review Harness) resulted in errors. Investigation showed that when a temporary case was persisted, pyInternalAssignmentHandle was not getting recalculated after pzInsKey was updated. To resolve this, the configuration on the edit button has been modified to use .pxFlow(pzInternalCaseFlow).pxAssignmentKey which is what pyInternalAssignmentHandle declare expression was also returning.
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-A24719 · Issue 252331
Correct Bulk processing status when no transfer occurs
Resolved in Pega Version 7.2.2
Searching by Work bulk processing was not transferring items when there were multiple assignments yet was showing a Transferred status and not displaying an error. This was traced to a missing 'when' condition check in the handling, and has been fixed.
SR-B1873 · Issue 271608
Fork shape works with both when and percentage connectors
Resolved in Pega Version 7.2.2
An error was generated when trying to save a flow rule that contained both percentage connectors and When rules fork shapes. This was due to the 'ValidateModelProcess' activity getting all connectors in the flow and checking if there is at least one connector with Percentage, then iterating each decision shape by iterating the connectors and checking for percentage error scenarios. To fix this issue, the system will get the connectors from the decision shape in context and check if at least there is one percentage connector, then check for validation after that.
SR-B238 · Issue 271610
Fork shape works with both when and percentage connectors
Resolved in Pega Version 7.2.2
An error was generated when trying to save a flow rule that contained both percentage connectors and When rules fork shapes. This was due to the 'ValidateModelProcess' activity getting all connectors in the flow and checking if there is at least one connector with Percentage, then iterating each decision shape by iterating the connectors and checking for percentage error scenarios. To fix this issue, the system will get the connectors from the decision shape in context and check if at least there is one percentage connector, then check for validation after that.
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-D32525 · Issue 505467
Dirty check added to offer save/discard changes when closing tab
Resolved in Pega Version 8.2.4
With the OOTB section enabled, performing a change in the form (changing a text value, selecting a option in a dropdown, etc.) and closing the case generated an unexpected alert indicating that the case was changed and the modifications were lost. This differs from the previous behavior of showing the section pyDirtyCheckConfirm which offered the opportunity to save the work. This was a missed use case and has been resolved by updating the system to perform a check for the dirty state when closing the interaction and show a modal dialog asking the user to choose either save/discard if dirty.