INC-139085 · Issue 589553
Documentation updated for using Custom Stored Procedure after upgrade
Resolved in Pega Version 8.6
Documentation has been updated to reflect that when upgrading an environment to Pega 8.3+, the following two prconfig/DSS settings should be removed. This is the preferred approach to use the new ID generation mechanism. Additionally, if a database sequence was previously used to generate IDs, pc_data_uniqueid should be added or updated to make sure each case type has a row defined, and that the pyLastReservedID matches the maximum of the relative database sequence value plus 1. env name="pega/sequenceid/useOldOOTBIDGenerator" value="true" or DSS: prconfig/pega/sequenceid/useoldootbidgenerator/default env name="database/databases/customUniqueIDproc" value="sppc_data_uniqueid_custom" or DSS: prconfig/database/databases/customuniqueidproc/default To keep using the old custom stored procedure, the following settings should be given either through prconfig or DSS setting (prefixed with "prconfig/"). The sppc_data_uniqueid_custom can be replaced with a custom procedure name with the same signature as the standard stored procedure. env name="pega/sequenceid/useOldOOTBIDGenerator" value="true" env name="database/databases/customUniqueIDproc" value="sppc_data_uniqueid_custom"
INC-139843 · Issue 594083
WSDL for Connect SOAP documentation updated
Resolved in Pega Version 8.6
SOAP integration documentation has been updated to include information regarding handling a WSDL that contains references to external XSD documents.
INC-143033 · Issue 607836
Access Control Policy documentation updated
Resolved in Pega Version 8.6
The documentation for the ACP rule (https://community.pega.com/knowledgebase/articles/security/85/creating-access-control-policy) has been updated to clarify that these rules must be checked in for the policy change to take effect. Access control policies only work when a rule is checked in. Therefore, any changes in a checked out rule will be ignored. When changing or modifying any ABAC policy rules, the rule must be checked out, updated, saved, and checked in for the changes to take effect.
INC-145944 · Issue 612847
Product Rules help updated for Report Definition filters
Resolved in Pega Version 8.6
The Product Rules help documentation has been updated to remove references to the deprecated use of When filters and List View filters as these have been replaced by Report Definition filters.
INC-158784 · Issue 625592
Throttling during email processing help documentation updated
Resolved in Pega Version 8.6
The IMAP section of the support article for throttling email has been updated to include more detailed information about the dynamic system setting used for throttling, Pega-IntegrationEngine Email_throttling_pattern_regex, and how to configure it.
SR-SR-D89339 · Issue 550312
Ping service documentation updated
Resolved in Pega Version 8.6
The documentation for ping service architecture and output has been updated to reflect that the response now includes more parameters.The response contains JSON text in the following format: {"node_type": [""],"health": [{"last_reported_time": "","test_name": "","status": ""},{"last_reported_time": "","test_name": "","status": ""}],"state": "","node_id": ""}
INC-127102 · Issue 602697
Synchronized BatchStatus email available for multi-node
Resolved in Pega Version 8.6
An enhancement has been added which will handle synchronization between BatchStatus used in different events on different nodes and send email notifications.
INC-128880 · Issue 592816
Handling added for angle brackets in legacy Chart control
Resolved in Pega Version 8.6
When using Investigative Case Management, some report charts were not rendering correctly. This has been resolved by updating appendFormattedString in AbstractJsonDataGenerator.java to escape angled brackets (< and >) before appending the input.
INC-132169 · Issue 584760
NativeSQL will use inline rule resolution for core components
Resolved in Pega Version 8.6
After upgrade, nodes were going down with a heartbeat error. This was traced to issues with NativeSQL taking a very long time to generate queries due to the overhead in calling multiple complex functions to resolve rules. To correct this, updates have been made to resolve the standard set of functions used by core components inline in NativeSQL function resolution.
INC-133482 · Issue 605003
Corrected isExternal flag not resetting
Resolved in Pega Version 8.6
Corrected isExternal flag not resettingIf an extraction referred to external tables, an isExternal flag that was set to true during the Extraction process did not get reset to false for the tables which were not referring to external. This has been corrected.