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": ""}
SR-69015 · Issue 619995
Unescaping characters implemented for expressions
Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6
An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.
INC-121460 · Issue 569118
IH Summaries correctly loads aggregated count
Resolved in Pega Version 8.4.2
After the IH Aggregated DataFlow has processed more than 34 million records from an Oracle database, the IH Fact table contained only ~120,000 records. Running a browse on the pxInteractionHistory DS resulted in an infinite loop. Investigation showed that this was caused by the handling of Oracle timestamps: using Pega DateTime in query parameters generated Oracle DATE instead of TIMESTAMP, causing all query parameters to be rounded to the second and interfering with the IH pre-aggregation. This has been resolved by updating the handling.
INC-122180 · Issue 563270
Null check added for Entity Extraction result
Resolved in Pega Version 8.4.2
Training data for an Entity Extraction model was not getting distributed correctly, as per the given % data. This was due to the result of the Entity Extraction result being null, and has been resolved by adding a check that will consider detected types as primary candidate for grouping if the result column is null.
INC-125838 · Issue 561484
Ignore Case feature updated
Resolved in Pega Version 8.4.2
In Pega Marketing 8.4 on the Action rule form, configuring an eligibility criteria and selecting the option for the comparison to ignore case did not copy this part of the criteria to the back proposition filter rule, so the case of the comparison was not ignored at runtime. This has been corrected.
INC-125900 · Issue 560788
ResolveFTCR flow Draft mode turned off
Resolved in Pega Version 8.4.2
When using the FastTrack Change Request functionality of Revision Manager 8.3 the submission was going to Pending packaging instead of Resolved-Completed with the error "flow is in draft mode; it cannot be executed". This was due to pxResolveFTCR flow having been checked in with Draft mode turned on, and has been corrected by turning Draft mode off.
INC-126129 · Issue 569668
PropertyToColumnMap made more robust
Resolved in Pega Version 8.4.2
The DF_ProcessEmails dataflow was intermittently failing with a StageException error. This was traced to schema changes being propagated asynchronously by system pulse, which seem to have caused PropertyToColumnMap to cache stale schema. To resolve this, if the property mapping is not found the first time, the system will make a second attempt to get the mapping. Additional logging has also been added for better diagnostics.