INC-216416 · Issue 713848
Elasticsearch will split queries to avoid URL length limits
Resolved in Pega Version 8.8
Elastic Search Functionality was not working and showed the status as Offline. Investigation showed that when an external Elasticsearch setup had an index prefix length = 200 and a large number of dedicated indexes, the error "too_long_frame_exception, reason: An HTTP line is larger than 4096 bytes" was generated. In this case, the system was working with approximately 87 dedicated indexes and the name for each of them was sent over the URL, resulting in this error message. This has been resolved by updating the system to split queries so as to not exceed the HTTP line limit in Elasticsearch.
INC-207307 · Issue 709716
Corrected OAuth jar version for custom Keystore rule
Resolved in Pega Version 8.8
Attempting to create a custom JKS and Keystore rule so it could be pointed to the Pega cipher and use the encrypt and decrypt functionalities failed with an error indicating it was not a valid KMS keystore. This was traced to an issue with a jar version mismatch: upon checking the dependencies for the nimbus-oauth-sdk jar, even though version 6.18.1 was specified the system picked the 8.27 version through transitive dependencies, and the 8.27 version doesn't have the needed CommonContentTypes class. This has been resolved by reducing the version to 6.18.1 in conflicting build.gradle.
SR-123717 · Issue 192182
Purging of covered objects improved
Resolved in Pega Version 7.1.8
When purging a Cover item, the history of certain covered objects was not purged. This happened when the Cover and Covered classes belonged to different class groups. This happened because the 'getHistoryKeys' function tries to fetch the history details of a given key by looking into its history table. This was using the class group information from the archive configuration, which was not always the same for covered objects. To resolve this, the classgroup info will be fetched from its key - looking up Class map using the constructed class name will give the actual History Class name.
SR-125929 · Issue 189682
Add Child navigation rule timing improved
Resolved in Pega Version 7.1.8
Attempting to set "Add Child" as a Navigation rule that performed an action on the selected row within a tree Grid using a modal dialog was generating a JavaScript error if used on the last row. When the "Add Child" action was selected, it attempted to add a child to the current row also set focus on the new entry, but at the time of the call to the selectRow function the Tree Grid has not yet been updated to include the additional child element. This caused the row variable to be evaluated as null. To correct this, a null check has been added that will correct the timing issues.
SR-127754 · Issue 192902
Modified TransferAssignment to pass SLA parameter with Reassign
Resolved in Pega Version 7.1.8
Assigning the work object configured with an SLA from workbasket to worklist using the out-of-the-box Transfer flow function before the Goal/deadline was reached caused the SLA escalation action to not be triggered when the deadline expired. This was due to the UpdateSLA parameter not being sent when Reassign was called as a post processing activity of the Transfer flow action. This flow action has been deprecated in later releases and replaced by the new flow action pyTransferAssignment, and the ReassignAssignment activity has now been modified to pass the updateSLA param while calling Reassign.
SR-A168 · Issue 203378
Enhancements added to ensure visible 'when' after upgrade
Resolved in Pega Version 7.1.9
After migration using systems upgraded in place, all pre-existing Default controls no longer showed the "Required" option in the cell properties, and the validation no longer functioned correctly (the form submitted successfully with previously required fields empty). The root cause was that pyAutoHTML was not set in XML, so the Visibility condition expression evaluated to false. This has been resolved by adding a check for empty visible-when conditions and by inserting pzNonAutoHTML, a newly created when rule which checks for empty or false values of pyAutoHTML for required checkbox visibility.
SR-A4314 · Issue 210533
Enhancements added to ensure visible 'when' after upgrade
Resolved in Pega Version 7.1.9
After migration using systems upgraded in place, all pre-existing Default controls no longer showed the "Required" option in the cell properties, and the validation no longer functioned correctly (the form submitted successfully with previously required fields empty). The root cause was that pyAutoHTML was not set in XML, so the Visibility condition expression evaluated to false. This has been resolved by adding a check for empty visible-when conditions and by inserting pzNonAutoHTML, a newly created when rule which checks for empty or false values of pyAutoHTML for required checkbox visibility.
SR-A3331 · Issue 208297
Enhanced added for non-logging config settings
Resolved in Pega Version 7.2
Both the upgrade process and Pega7 run-time make use of non-logged operations for major performance improvements. However, High Availability Disaster Recovery (HADR) database environments use database logs to replicate data from the primary database to the standby database. This caused a conflict that resulted in the unexpected termination of upgrade scripts. An enhancement has been added to make the logging function configurable (the default is No Logging = true), and tuning was done to make logged SQL generation faster to improve system performance when logging is enabled.
SR-A86465 · Issue 257770
Updated partial search from the Case Manager portal to return consistent results
Resolved in Pega Version 7.2.2
After upgrade, the search functionality was not working as expected. Launching the Case manager portal to search and then open a case worked, but then searching for another case and opening it resulted in the contents of the first search being displayed again. This was traced to inconsistent results when partial search was used from case manager portal,, and has been resolved by showing all the results (top 20) every time partial search is used from case manager portal, irrespective of the ranking ES provides to the search results (i.e., even if the work id is present in the top 20 or not).
SR-A38580 · Issue 252790
Improved Extended Interaction History cache handling for column removal
Resolved in Pega Version 7.2.2
The Interaction History Component was generating an error when IH was extended with additional attributes in the transform rule:Data-Decision-IH-Configuration -pyInteractionHistoryConfiguration and then deleted at a later stage. Once the new property was mapped and the IHFact table was altered to add the new column, the Interaction History component in the strategy which retrieves the IH data was not able to handle the removal of that column from the IHFact table or from the data transform due to a static marker in the rule not being updated with the deletion. The cache function has been modified to correctly reflect the deletion of the column.