SR-D30687 · Issue 500892
Update message clarified for manual case update after SmartEmail shape used
Resolved in Pega Version 8.4
For a case with #1 Optimistic Lock and #2 a SendEmail smart shape in the middle of a flow, once the SendEmail updated the case in the background, updating the case manually resulted in a "Please re-submit" message being displayed without any explanation. This has been resolved by ensuring that instead of a resubmit message (system update), the system will show a refresh message (normal update).
SR-D15844 · Issue 496777
Flag set for using defer load context switching with Microsoft Internet Explorer
Resolved in Pega Version 8.1.6
Defer load section was not working as expected due to Microsoft Internet Explorer 11 not maintaining the context of the section during busyIndicator hide. To avoid this, a flag 'pega.ctxmgr.skipContextSwitching' will be set during the hide of busy indicator if Microsoft Internet Explorer is used, and the harness switching context will then be decided based on this flag.
SR-D25902 · Issue 510083
DSS added for reference Page Group fields extraction using Dictionary
Resolved in Pega Version 8.4
Reference properties were not being resolved when the useDictionary option was set to false, resulting in empty data being extracted from the blob for embedded pagegroup and pagelist properties. To resolve this, a new dynamic system setting in Pega-RULES ruleset, "BIX/enableDictionaryLookUpForDBExtract", has been added to enable dictionary resolution so that the embedded page group reference property values are resolved for extraction. The default value is "false".
INC-217974 · Issue 715428
Handling added BIX extraction failure when called from custom activity
Resolved in Pega Version 8.8
After update, BIX extraction was failing but email from the schedulers indicated success. Investigation showed that when extract was called from a custom activity by calling pxExtractDataWithArgs, the stepStatusFail 'when' rule in the custom activity was not capturing all the exceptions specific to database extracts. This has been resolved by adding the necessary handling.
SR-D43272 · Issue 516441
Local user lookup modifed to use requestor level data page to improve performance
Resolved in Pega Version 8.4
In a system with many users (over 40k), attempting to search for a user to send a private message was taking an excessive amount of time. Analysis found that all of the users were being loaded at once in a page list of type Code-Pega-List. This led to errors indicating the Page List property had more elements than the specified threshold, but pagination could not be added as the activity and RD are final. To improve performance, this process has been modified to use a data page at the requestor level instead.
INC-173725 · Issue 656480
Logic updated for DX API retrieving View/Action ID using embedded property
Resolved in Pega Version 8.7
While calling the DX API using Assignment ID and action ID, a 500 error response was logged indicating that the server encountered an unexpected condition that prevented it from fulfilling the request. Investigation traced this to the logic used for resolving an embedded property referenced in a control/field to identify the correct page class. In a non-work object context for flow actions the new assign page doesn't exist, but the system was checking for it and clearing off errors from the named page. This has been corrected.
SR-D20075 · Issue 516574
DSS added to convert empty spaces for use between Old and New Assembler
Resolved in Pega Version 8.4
After switching to the Old Assembler (via the DSS switch UseOldAssembler=false), MQ Requests were failing. This was due to a difference in behavior with the Old and New Assembler: the Old assembler treated empty spaces as an empty string and did not pass them along. In this use case, the response of a prior MQ call was parsed with the appropriate number of spaces to a new request while expecting the characters to remain in that format. Since the Old Assembler was converting these to "", this caused a difference in behavior when switching between the two options. To correct this, a DSS has been added that will compensate for this behavior of removing the spaces for Parse XML rules. This new DSS must be set in conjunction with using switchToOldAssembler: set "SOAPConnectorPreserveWhiteSpaces" in "Pega-IntegrationEngine" to true. Once this is done, all Parse XML rules need to be reassembled by either saving each manually, or running the "Revalidate and Save" wizard off of the Designer Studio Menu > System > Release > Upgrade > Validate.
SR-D24318 · Issue 494060
Dom API updated to resolve Microsoft Internet Explorer 11 not loading async data with refresh when calling an activity
Resolved in Pega Version 8.4
The browser was continuously showing "loading" if Microsoft Internet Explorer 11 was used for a section which was sourced from a data page and configured to load the data asynchronously from a external service while calling an activity and using a 'refresh when' rule to refresh the section if a property changed. Investigation showed that the initial data load was successful and the section with the data was visible, but if the property changed and the section loaded once again due to the 'refresh when' condition, the browser was unable to render the defer loaded section case because the dom returned had the wrong value. To resolve this, the API used to check for the dom element has been updated.
SR-D51725 · Issue 516468
DSS added to rpevent logging of sensitive data used as input during async batch task processing
Resolved in Pega Version 8.4
When running Async Batch Task Processing, the whole set of inputs was logged when an error occurred during ADP load. Because this might result in sensitive data such as SSN, DOB, IDs, etc, being included in the debugging output, a DSS has now been added which when set will avoid printing any sensitive information in the log.
INC-215343 · Issue 711143
Security updates
Resolved in Pega Version 8.8
Security updates have been made relating to rulesets using allow lists, checks for Java code injections, SAML-based SSO code, and supporting SFTP as part of the validation in the pxValidateURL rule.