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-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.
INC-154754 · Issue 629907
Check added for portal when performing local actions
Resolved in Pega Version 8.6
When using an Interaction case with a service case, performing any local action on this service case and then creating a new service case resulted in the I-related properties like CAParentID and CurrentInteractionID taking the pyID of the previous Service case where the local action was performed. This was caused by the parentKey value not being updated correctly in redux state whenever a local action was opened in a service case in a particular portal, and has been resolved by modifying the pzpega_ui_redux_reducers file to update 'parentKey' only in case of a DC SPA portal.
INC-180184 · Issue 665091
Assistance and diagnostics added for issue with opening imported 'when'
Resolved in Pega Version 8.7
After upgrade, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again.
INC-165992 · Issue 657691
Table Filter save uses correct harness
Resolved in Pega Version 8.7
After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.
INC-173760 · Issue 658069
Table Filter save uses correct harness
Resolved in Pega Version 8.7
After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.
SR-C1507 · Issue 344564
Existing Kafka topic name used for connection
Resolved in Pega Version 7.4
When running a Kafka dataflow, Pega was using the dataset name instead of the topic name for the topic connection. This has been fixed, along with forcing a capital letter for the first character of the dataset name in order to ensure proper matching.