INC-173162 · Issue 650793
Certificate match will use Subject Distinguished Name
Resolved in Pega Version 8.6.1
Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.
INC-174298 · Issue 650257
Instance count logic updated
Resolved in Pega Version 8.6.1
A performance issue was seen during update that resembled an upgrade hang. This was caused by a combination of incorrect logic in DDLGenerator.getInstanceCountForClass() around counting instances of 'core' classes and all of the site history-data- tables being mapped to the same table that had 1.4+ billion rows. This behavior has been addressed with more correct query logic while performing instance counts. In addition, instance count will be supressed during command line invocations (prpcUtils, platform upgrade).
INC-180479 · Issue 659640
DSS partition count setting made backward compatible
Resolved in Pega Version 8.6.1
After update, the DSS to limit the number of partition counted was no longer working and instead used the default value of 20. This has been corrected and made backwards compatible.
INC-174661 · Issue 678823
Handling added for clearing node killed between assignment and processing
Resolved in Pega Version 8.6.3
An Offer flow was not resuming after it expired according to the wait shape. Investigation traced this to partitions which were assigned to a dead node in NEW state where they were not picked up by the dataflow. The problem was only encountered in the unusual situation when a dataflow node was killed in the brief period of time between the assignment and the processing, and has been resolved by adding an update which will clear unknown new assigned partitions for the batch run health task.
INC-179879 · Issue 664804
Localization added to DelegateDescription
Resolved in Pega Version 8.6.3
Localization was not working correctly for the description of a delegated rule due to pyDelegeteDescription being defined with a non-localized Property value. This has been resolved by localizing the property value for pyDelegeteDescription.
INC-183211 · Issue 667011
Compare-To-Empty-String support added to Analyzer
Resolved in Pega Version 8.6.3
An enhancement has been added to support a NotEquals decision function in the Analyzer.
INC-186437 · Issue 685013
Updated entity attachment extraction tokenizers
Resolved in Pega Version 8.6.3
After creating an entity extraction model, it was seen that one of the entities worked when there was a space after the semicolon but the detection was not working if there was no space. This has been resolved by updating the Tokenizers with extra examples to address tokenization when ":" is present between two words without any spaces.
INC-187267 · Issue 679369
Resolved error for custom relative dates
Resolved in Pega Version 8.6.3
An error was seen when parsing the [Date Property] [is before/after] [Last/Next x days] while using a custom amount of number of days in Customer Decision Hub (CDH). This was due to the system not supporting the [Last/Next x days] feature for SSA, but only detecting this during parsing for the prefixed values for Proposition Filters and not custom values. As the parser did not realize the construct referring to the relative date was not supported, it created an SSA that caused an exception during execution. This has been resolved.
INC-187520 · Issue 677874
Actuals sync clears data from cache and persistence
Resolved in Pega Version 8.6.3
When sync attempted to clear the existing data from Actuals before copying data from the interaction history, the partition was cleared from the cache but not from persistence. IH data that was then copied to the same partition time ranges had new field descriptors created that did not match the format of the old data in persistence. As a result, when a query triggered the loading of such a partition, the mix of data with the old and new formats caused the load to fail. This has been resolved by updating the system to ensure the data is deleted properly from both the cache and persistence.
INC-188309 · Issue 684703
Proposition filter populated for test business Issue
Resolved in Pega Version 8.6.3
When running the proposition filter rule, no drop down list appeared for a business issue. This was caused by the Issue list not being populated for the Action-Run test page, and has been resolved.