SR-D39003 · Issue 505998
Threads will be updated to maintain assembly context when using Static Assembler
Resolved in Pega Version 8.4
When running the Static Assembler utility from UI, the assembler process completed successfully but the PegaRULES.log was flooded with the FATAL exception "Usage error - next Executable not based on current". This error was generated from com.pega.pegarules.session.internal.mgmt.Executable constructor, and indicated an issue with the thread context being different from the assembly context. To resolve this, the system has been modified to update the context of thread to what is expected as assembly context.
SR-D42456 · Issue 510958
Case status correctly updated when using RDA
Resolved in Pega Version 8.4
When a Assignment was routed to a work queue and Flow Action post processing was set to trigger an RDA Automation to update some case property, an error appeared saying there was no data available on the Page and the case status was not updated when it moved to the next stage. This was an issue with case status not being correctly updated when using robotic automation, and has been resolved.
SR-D28869 · Issue 499317
Resolved Tooltip not relaunching after hide when using autocomplete controls
Resolved in Pega Version 8.4
When a tooltip was configured with SmartInfo and 'Auto-dismiss on hover away' was not checked, the tooltip disappeared when an autocomplete control was clicked and could not be reopened afterwards. The tooltip behaved as expected when it used input text control. This behavior was traced to autocomplete controls being set to hide all other active popovers because autocomplete results are displayed in a popover and only one active popover can exist on the DOM. However, it was seen that the tooltip's Smartinfo popover status was still active even though it was hidden, which is why it could not be launched again. To resolve this, when an autocomplete control is clicked, any active popovers being hidden will also be marked as inactive.
SR-D23906 · Issue 502577
Case status correctly updated when using RDA
Resolved in Pega Version 8.4
When a Assignment was routed to a work queue and Flow Action post processing was set to trigger an RDA Automation to update some case property, an error appeared saying there was no data available on the Page and the case status was not updated when it moved to the next stage. This was an issue with case status not being correctly updated when using robotic automation, and has been resolved.
SR-C19122 · Issue 359549
Behavior change for error handling when using "Call superclass data transform"
Resolved in Pega Version 8.1
Previously, when "Call superclass data transform" was enabled for data transfers, the initial data transform would continue working even if the subsequent transforms it called failed. As an example, given data transform A, which called another data transform B, which called another data transform C, and data transform A performed some actions after calling data transform B; If an error occurred while processing data transform C, data transform C ended processing, data transform B also ended processing, but data transform A continued working. This was confusing behavior. To create a more consistent environment, whether or not “call superclass data transform” is used, when any of the chained data transforms fail the entire process will exit. The documentation has also been updated to indicate this new behavior.
SR-C28389 · Issue 374701
Added check for parent page when using 'save-as' in PM BundleTemplate
Resolved in Pega Version 8.1
Pega Marketing has a longstanding shipped section called BundleTemplate which is used to render a page-list of bundle members for emails. Doing a save-as of this section (without ANY changes) was resulting in runtime errors with the exception ":com.pega.pegarules.pub.clipboard.InvalidReferenceException: The reference .BundleOfferMembers(1).BundleOfferMembers is not valid. Reason: Entry handle must have a page name specified." This happened because the Section in grid was run on a page without a name, and the exception came from test id generation code which expected a complete path of the grid page list property. In this case the path is not complete as it starts with "." (dot) and there is not a top level named page. To resolve this, the code has been modified to not generate a test ID when the parent page does not exist in Clipboard.
SR-C4280 · Issue 349923
Template fixed so JAWS reads menu name when an image is used
Resolved in Pega Version 8.1
When using template mode, JAWS was reading the image src text for navigation menus configured with an image on them. This was caused by the role="link" aria-haspopup="true" being wrongly generated on the <img> tag, and has been fixed by updating the template file to generate the role only for an anchor tag and not on img.
SR-C9824 · Issue 355932
Behavior change for error handling when using "Call superclass data transform"
Resolved in Pega Version 8.1
Previously, when "Call superclass data transform" was enabled for data transfers, the initial data transform would continue working even if the subsequent transforms it called failed. As an example, given data transform A, which called another data transform B, which called another data transform C, and data transform A performed some actions after calling data transform B; If an error occurred while processing data transform C, data transform C ended processing, data transform B also ended processing, but data transform A continued working. This was confusing behavior. To create a more consistent environment, whether or not “call superclass data transform” is used, when any of the chained data transforms fail the entire process will exit. The documentation has also been updated to indicate this new behavior.
SR-D42583 · Issue 514487
Label of a field is correctly rendered when a section is re-used with a visiblity condition
Resolved in Pega Version 8.4
The label of a field was not being rendered/visible when a section with a 'visible when' condition was re-used in different Page Contexts. The label was displayed correctly if 'Run visibility condition on client' was checked. As part of performance improvements made in a previous version, label generation was moved under the dlcellvisibility flag. Because of this, if a section was re-used at multiple places with different contexts and one place had visibility false and another had visibility true, the labels were not getting generated for the visible section. To resolve this, Label Generation has been moved out of dlcellVisibility to ensure label metadata will always be generated. Updated performance improvements have been made instead by way of a DSS setting (generateCellMetadata) so that when generateCellMetadata is true, the label generation will honor dlcellvisibility to generate the label metadata.
SR-C44375 · Issue 387180
Check added for multiselect object type when using Microsoft Internet Explorer 11
Resolved in Pega Version 8.1
Using the multi select control worked fine in Google Chrome but was throwing JS errors when used in Microsoft Internet Explorer 11 and causing the whole flow action to hang. Object.keys on a non-object throws error as per ES5, but on ES6 a non-object argument will be coerced to an object. This error was seen because the older version of Microsoft Internet Explorer still uses ES5. To better handle this, the system will check for the object type before using object.keys in pzpega_control_multiselect.js.