SR-D37980 · Issue 512436
Data page triggered from SLA reloads per interaction
Resolved in Pega Version 8.4
After configuring an SLA goal activity which takes one parameter from a thread-level data page with 'Reload once per interaction' checked and the source of the datapage was a data transform which used pyWorkPage.pyID to set a property value, goals were not updated as expected. If multiple cases reached their SLA goal at the same time, the first case ID was being sent as a parameter to the goal activity for all of the other case IDs. For example, if case 1, case 2, and case 3 reached their goal at the same time, the case 1 ID was passed as the goal activity parameter to case 2 and case 3. This was traced to multiple items that were getting processed in a single agent run picking up the stale data present in data page because it was not being cleared, and has been resolved by removing the Read-Only data pages after every item that is processed, ensuring that it will be reloaded the next time the data page is triggered.
INC-148944 · Issue 604100
Email Listener auto-reply evaluation updated
Resolved in Pega Version 8.5.2
Email Listener auto-reply evaluation updatedAfter upgrade, messages were being read but not getting processed for a specific Email listener (RCEmailListerner). The error "Email flagged as an autoreply email and will not be processed" appeared in the logs. Previously, an email was not considered to be an auto-reply only when the 'auto-submitted' header didn't exist or existed with value 'no'. This caused issues with auto-forward or auto-redirect emails where 'auto-submitted:auto-generated' could be in the header. Due to this, email was marked as auto-reply and email listener stopped processing it. To resolve this, the system has been modified to mark the message as auto-reply if it finds 'auto-submitted: auto-replied' in the header, but not 'auto-submitted:auto-generated'.
INC-131384 · Issue 584856
Documentation updated for troubleshooting inline images for email
Resolved in Pega Version 8.5.2
Inline images were not showing by default when sending emails. To assist in this, the troubleshooting information for email has been updated with the following information: Correct configuration for display of inline images via Email bot is one that is shipped standard. To support Rich text in email display via Email bots, Email body must be stored 'As HTML attachment' (the setting on auto generated Service Email rule). In addition, no other setting on listener must be changed especially 'Embed inline images'(should remain unchecked) on Email listener rule. Combination of these 2 settings causes Email bot to save - 1. Email body as attachment 2. All inline images as attachment At runtime UI display, these 2 are recombined to display proper email. This is done in order to increase performance because images are lazily loaded.
INC-130695 · Issue 587660
Enhancements for upgrading in multi-tenant environment
Resolved in Pega Version 8.5.2
Some muti-tenant installations use the same applications or rule instances with the same pzInsKeys for different tenants. This can cause upgrades to time out due to the system fetching all pzInsKeys (which will have duplicates) and working with them in a default batch size of 500 each over 4 threads. This led to the same keys potentially being allocated and processed in different threads, resulting in duplicate processing and timeouts. This has been resolved by updating the select query to fetch the tentantid and pzInskeys in the MT system to avoid duplicate work in multiple threads. In addition, running Generate Declarative indexes fetches the pzinskeys and generates indexes for each record, but before generating, the existing index for the record is deleted and then inserted. Because the delete query to generate the index was not tenant aware, all of the records for the key were deleted for the tenants for that key, but the new index was created only in one tenant. This has been resolved by enhancing the DELETE query to be tenant aware, which will avoid deleting the indexes for all the tenants given an index key.
SR-D42888 · Issue 511452
ElasticSearch startup modified
Resolved in Pega Version 8.4
Search was broken on the app-tier node due to the Full-text search startup failing during a re-initialization. As part of normal re-initialization, the existing node is shut down and the Elastic Search node started. However, in this case because the shutdown process was not properly invoked, the system attempted to start the second instance of an ES node on the same machine. The shutdown process is reliant on a boolean flag which indicates if the current status of the full-text search initialization is successful: this flag indicated initialization had failed when actually the ES node had started but failed to validate all the cluster level settings due to topology changes in the Pega cluster. In order to avoid this scenario, the restart has been split so that the node can be marked as started but not initialized. This allows the follow-up reinitializations a greater opportunity to succeed. In addition, the shutdown FTS code has been modified to shutdown ES regardless of the search initialization status.
INC-196389 · Issue 690786
ConfigurationReconciliationTask updated for greater compatibility
Resolved in Pega Version 8.7
After updating from Pega 8.3 to Pega 8.6, models which previously had learning and performance AUC greater than 0.7 reported an AUC of 0.5. This was traced to the update handling in ConfigurationReconciliationTask. AdmRuleBrowser does not perform ruleset resolution, so all rules were returned, for example the rule for model A in both the 08-01 and 08-03 ruleset. The system then iterated over all of the adaptive model rules returned by AdmRuleBrowser in order to assess whether a configuration update was necessary. The condition to update the model rule was met when either the config key did not exist (indicating a newly added configuration) or the model rule was "old" (version <2). For models generated in Pega 8.3 or earlier the version number for all rules must be 1, and the update to Pega 8.6 therefore caused the ConfigurationReconciliationTask to be applied to all adaptive model rules. To resolve this, the configuration update check in ConfigurationReconciliationTask has been removed.
INC-201335 · Issue 690733
ConfigurationReconciliationTask updated for greater compatibility
Resolved in Pega Version 8.7
After updating from Pega 8.3 to Pega 8.6, models which previously had learning and performance AUC greater than 0.7 reported an AUC of 0.5. This was traced to the update handling in ConfigurationReconciliationTask. AdmRuleBrowser does not perform ruleset resolution, so all rules were returned, for example the rule for model A in both the 08-01 and 08-03 ruleset. The system then iterated over all of the adaptive model rules returned by AdmRuleBrowser in order to assess whether a configuration update was necessary. The condition to update the model rule was met when either the config key did not exist (indicating a newly added configuration) or the model rule was "old" (version <2). For models generated in Pega 8.3 or earlier the version number for all rules must be 1, and the update to Pega 8.6 therefore caused the ConfigurationReconciliationTask to be applied to all adaptive model rules. To resolve this, the configuration update check in ConfigurationReconciliationTask has been removed.