INC-201991 · Issue 692861
Explicit connectivity close added to Queue Manager error handling
Resolved in Pega Version 8.6.3
Performing a connectivity test on the MQ Connector page with an invalid queue name aborts the test connectivity but the MQ connection was not closing. This can become an issue when using IBM MQaaS (MQ as a service) where only a limited number of connections are allowed. This has been resolved by adding an explicit Queue Manager close in the error handling block.
INC-202510 · Issue 695890
SOAP connector supports OAuth2 profile
Resolved in Pega Version 8.6.3
Support has been added for using an OAuth2 profile as one of the allowed profiles for SOAP connector.
INC-202743 · Issue 697115
Cleanup added for disabled/deleted operator passivation data444
Resolved in Pega Version 8.6.3
In some scenarios, a passivated session for a non-active operator was able to be resumed after cluster restart. This has been resolved by adding a check for disabled or deleted operators which will then delete any lingering passivated data.
INC-206240 · Issue 698248
Custom headers work in MS Graph
Resolved in Pega Version 8.6.3
Custom headers were not working for MS Graph. This was a missed use case for checking headeractualname to identify whether it is a custom header, and has been corrected.
INC-176138 · Issue 723082
Performance improvements for save-as
Resolved in Pega Version 8.6.5
Performance issues were seen when using save-as for rules such as Declare expression, When rules, activity, etc. This was traced to a very large number of extra database queries that were being executed while building the Declarative Cache. To resolve this, an update has been made so the queries used for the Declarative Cache will only be executed when required.
INC-186904 · Issue 669744
Removed duplicate alert events
Resolved in Pega Version 8.6.5
Duplicate applications were seen in the PDC Event Viewer, e.g. ‘Adviser 01.01’ and ‘Adviser:01.01' - one without a colon and one with a colon. Investigation showed that alert events logged via AsyncServices were being logged as "ApplicationName Version" instead of "ApplicationName:Version", and this has been resolved by updating AsyncServiceBatchTask.java to use the expected application name while logging alert events.
INC-193485 · Issue 695641
REST authentication settings use fully qualified name for resolution
Resolved in Pega Version 8.6.5
The application setting used in REST connectors for authentication was resolving to similarly-named rules instead of matching the exact name of the rule. This has been resolved by enhancing pzGetSettingID to use both parts of the fully qualified name (name and category) provided by the pzSettingsORA control when determining which setting from the report to return.
INC-198555 · Issue 720901
Performance improvements for save-as
Resolved in Pega Version 8.6.5
Performance issues were seen when using save-as for rules such as Declare expression, When rules, activity, etc. This was traced to a very large number of extra database queries that were being executed while building the Declarative Cache. To resolve this, an update has been made so the queries used for the Declarative Cache will only be executed when required.
INC-203040 · Issue 721057
Null value handling added for CBU
Resolved in Pega Version 8.6.5
After update, changes made to the Operator record were not reflected and the Actions menu in Operator record did not show all available actions after the Operator was saved. This has been resolved by adding handling for null values passed as String for arguments from cbu.xml for the PegaCBU utility.
INC-207159 · Issue 707617
Localization added for delegated datatype tab
Resolved in Pega Version 8.6.5
Localization was not working for the title of a thread which opened when attempting to edit the delegated datatype. This has been corrected.