INC-133951 · Issue 584147
Try catch added for templated refresh when
Resolved in Pega Version 8.4.4
After configuring a refresh when condition on a dynamic layout triggered by changes on D_worklist.pxResults, a component stack mismatch error was generated if client side UI template is enabled. Without templatization it worked as expected. This has been resolved by adding a try catch block to DynamicLayoutGenerator.java.
INC-153108 · Issue 614358
Added check to maintain disabled textarea 'when'
Resolved in Pega Version 8.4.4
The disabled text field became editable when the "Run required condition on client" checkbox was enabled. This has been resolved by adding a check for pyDisabled property to get the correct status for textarea control.
SR-D6555 · Issue 453265
Access When check added for pyStartCase privilege
Resolved in Pega Version 8.2.3
If a privilege was defined in the pyStartCase flow rule and the access role to object assigned a privilege based on 'Access When' (not production level), the user was not able to start a case. This was traced to the havePrivileges RUF passing an incorrect primary page to evaluate the privileges in combination with the 'access when'. To resolve this, the engine API will call tools.getAuthorizationHandle().havePrivilege for each privilege until it finds a match.
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.
INC-195387 · Issue 681673
HandleResponses updated for use with optimized campaign
Resolved in Pega Version 8.7
After updating from Pega 8.4, responses were not processed in the pxHandleResponses Data flow if the "pyCampaignOptimization" flag was set to true. This was traced to a missed use case for an optimized campaign, and has been resolved by modifying the condition in HandleResponses.
SR-B67903 · Issue 329428
Fix for Data Transform when Clipboard Page not found.
Resolved in Pega Version 7.4
Logic has been added to correct the scope references of the generated offline-Datatransform-JS when using AppendAndMapTo.
SR-B67903 · Issue 328792
Fix for Data Transform when Clipboard Page not found.
Resolved in Pega Version 7.4
Logic has been added to correct the scope references of the generated offline-Datatransform-JS when using AppendAndMapTo.
SR-C6156 · Issue 351338
Changed RDE 'when' process to avoid syntax errors
Resolved in Pega Version 7.4
The syntax of the Rule-Declare-Expression was incorrect, enclosing the expression in apostrophe('). There was no change in the functionality, but it was not possible to use 'save as' on the rule and an error was generated. In addition, the function calls syntax was missing the @ symbol before the function. These errors were traced to conditions previously fetched from the HTML form data: instead of parsing the html and retrieving the condition, the system will now check if a pyWhen value is available. If it is present, the system will directly use that to create the UI.
SR-C6156 · Issue 350820
Changed RDE 'when' process to avoid syntax errors
Resolved in Pega Version 7.4
The syntax of the Rule-Declare-Expression was incorrect, enclosing the expression in apostrophe('). There was no change in the functionality, but it was not possible to use 'save as' on the rule and an error was generated. In addition, the function calls syntax was missing the @ symbol before the function. These errors were traced to conditions previously fetched from the HTML form data: instead of parsing the html and retrieving the condition, the system will now check if a pyWhen value is available. If it is present, the system will directly use that to create the UI.
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.