INC-195511 · Issue 693218
Check added for child join class when using ABAC
Resolved in Pega Version 8.5.6
When a join was applied on a report definition and the same join class had a child class to which ABAC was applied (for some property eg., isABC), an "invalidreference" exception (isABC) was generated. This was traced to the system taking into account the child class of the join class while running the report, and has been resolved by adding a check to handle this scenario.
SR-C49274 · Issue 388984
Expiry dates displayed in Authentication Service Rule SSO certificate
Resolved in Pega Version 8.1
Inconsistent behavior was seen in the Authentication Service rule SSO certificate expiry information between Pega versions. Previously, the system displayed Expiration Dates on the Authentication Service rule form after selecting the signing/decryption certificate, whereas after upgrade the expiry dates were not getting displayed. This was an error resulting from enhancements made to support different keystore types (Upload, File Reference, URL Reference, Data Page source) and introduce Keystore cache: during these modifications the "pzGetCertificateExpiry" activity was not modified to get the certificate from Keystore Cache instead from DB. This has been fixed.
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-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.
SR-C36057 · Issue 387665
Required field error message appears under multiple controls when using multiple multiselect
Resolved in Pega Version 8.1
Error messages for multiple controls in a repeating dynamic layout displayed only for first control instead of the expected behavior of an error message displayed under all controls. The required error messages were not showing up when multiple multiselectlist control was being used due to a missing name attribute for multiselectlist control, and this has been added to correct the problem.
SR-C19285 · Issue 358754
Blacklist when performance improvement
Resolved in Pega Version 8.1
When running a performance test, the when delta sync blacklist when rule generated 1.6BG of garbage. In order to improve performance, a data page will be created to hold blacklisted delta sync data pages.
INC-192464 · Issue 681858
PackageComponent updated for use with repositories
Resolved in Pega Version 8.5.6
Exporting a zip file created by the Component wizard to a repository resulted in an error, however the same process worked as expected when the zip file was created by the Product wizard. Investigation showed that pxPackageComponent was not kept up to date with new metadata requirements for Artifactory export. This has been resolved by modifying pxPackageComponent step 7 to set Param.ArtifactType to "component" and Param.ArtifactName to [component name]_[component version]. A privilege check has also been added to zipMoveExport.