SR-125610 · Issue 189352
Added handling for property-defined declare value list indexing
Resolved in Pega Version 7.1.8
When adding or updating entries in a value list, the corresponding index entries were not getting created in the database. This was caused by handling that was missing from the minimum feature string clipboard properties that were recently introduced for better performance. These strings get created when it's not a reference property and has no declaratives defined etc. In this case, a declare index that is defined on the value list property should not have those elements be minimum feature properties. To correct this, the code has been changed to pass the featureID of the parent property.
SR-125769 · Issue 188698
ToolTip added for column filtering in bulk allocation
Resolved in Pega Version 7.1.8
While using bulk allocation, filtering a column resulted in reducing the number of results but it was unexpected that the select count was not similarly updated. The count is populated by pre-processing activities and not by the grid, but this information was not clearly conveyed. A Tool Tip has been added for SelectionIgnoresGridFiltering to clarify the usage of the "Select All xx Results" checkbox.
SR-125906 · Issue 192682
Work object locking improved for Advance Flow
Resolved in Pega Version 7.1.8
An Advance Flow call in SLA gave a 'lock not held' error on commit when it was used in subcases where the parent has a dependency (e.g. waiting for the child to resolve). This was a problem where the commit released the work object before the escalation action was executed, and has been resolved by modifying 'SpawnQueueItemForFlowDependency' to open and set the new transaction before and after the commit.
SR-126011 · Issue 195418
RUF 'hasMessages' working with Declarative Pages
Resolved in Pega Version 7.1.8
Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.
SR-126011 · Issue 195591
RUF 'hasMessages' working with Declarative Pages
Resolved in Pega Version 7.1.8
Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.
SR-126051 · Issue 188520
External assignment goal execution corrected
Resolved in Pega Version 7.1.8
When an external assignment was created and correspondence generated to provide the external link, using Goal Execution to send a follow up was not working as expected after migration. Previously, the .CorrHandle property was stored and retrieved from the pxflow pages with a reference to the main flow which contained the External Assignment, and the "ExternalGoal" activity used the CorrHandle property to retrieve the correspondence and send a follow up. This was no longer working as the .CorrHandle property was relocated under a different page (VerifySendCorr). CorrUpdate has been modified to handle the flowname properly.
SR-126092 · Issue 189635
Enhanced logging for SQL exceptions with BIX
Resolved in Pega Version 7.1.8
In order to enhance diagnostics while using BIX, logging has been added to print the stack trace for an SQL Exception while fetching the last updatedatetime.
SR-126121 · Issue 189977
Improved Global Search box dismissal on iPad
Resolved in Pega Version 7.1.8
On an iPad, prforming a search with any application that shows the global search control in its header displayed a pop-up that could not be dismissed by tapping on the application below the search box. This issue occured when the script pega_desktop_AppControllerLite.js is included in the header section of the harness.To address the problem, the event binding logic for search on mobile devices has been updated to listen for a tap event instead of a click event.
SR-126368 · Issue 196112
Application Wizard node validation improved
Resolved in Pega Version 7.1.8
When using the new application wizard on a FW which has multiple built ons, selecting cases from a built-on app caused the wizard to validate the classes incorrectly and expected the user to change class names. To correct this, the application express has been updated to track intermediate class nodes that are not class groups, and now tracks non-workgroup and case type leaf name components and aggregates them.
SR-126455 · Issue 189883
Stale thread issue resolved and logging updated
Resolved in Pega Version 7.1.8
The error "com.pega.pegarules.pub.context.StaleThreadError: Thread has been recycled" was appearing sporadically in the log files. The root cause was traced to the usage daemon, and has been resolved by changing the logic such that while capturing usage data, the system will avoid setting the last thread as processing thread while taking requestor lock. This avoids usage of a stale thread. Additionally, a change was made to avoid repeated logging of a stale thread error while creating a PRException object when exception occurs do occur due to a stale thread.