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-125910 · Issue 194305
Corrected data population in report for exposed column
Resolved in Pega Version 7.1.8
Data was not being populated in a report for an exposed column when it was dragged and dropped from the data explorer of Report Editor. This was caused by the CreateColumnPage fieldName being hard-coded to Param.FieldName for embedded page properties, and has been changed to set FieldName conditionally.
SR-125937 · Issue 190307
Aligned Connector lines in Process Modeler
Resolved in Pega Version 7.1.8
Upon opening a flow rule, the Connector lines in Process Modeler were rerouted inconsistently with what was the saved state of the rule. The root cause was traced to code defects that resulted in the incorrect display of an error message and the incorrect drawing of the connector lines when the process modeler is loaded. These have been corrected.
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-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-126335 · Issue 192177
Added support for custom mixed property types for listview filter
Resolved in Pega Version 7.1.8
When the out-of-the-box listview pySearchResultsWork was modified to add two columns with one property having Datetime control and the other having Date Control, the data was retrieved but the filter criteria was not working. This issue was specific to Date/Datetime control, and was traced to missing configurations for this scenario. Those have been added.
SR-126335 · Issue 194307
Added support for custom mixed property types for listview filter
Resolved in Pega Version 7.1.8
When the out-of-the-box listview pySearchResultsWork was modified to add two columns with one property having Datetime control and the other having Date Control, the data was retrieved but the filter criteria was not working. This issue was specific to Date/Datetime control, and was traced to missing configurations for this scenario. Those have been added.
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-126490 · Issue 190168
Disabled unneeded PEGA0050 alerts
Resolved in Pega Version 7.1.8
PEGA0050 alerts were triggered when a clipboard page list was copied to another list. In general these copies happened when lightweight page lists are involved. In Pega 7, lightweight lists have been enhanced and these copies are not required in most of the cases. Because it is no longer needed, the "alerts/virtuallists/copy" setting has been changed to false to disable the alerts
SR-126545 · Issue 189937
Added remote case handling for password protected implementation applications
Resolved in Pega Version 7.1.8
There was a problem creating an implementation application in Application Express if the built-on application was password protected and the current logged-in application was also password protected, and the cases from built-on have remote case types. This was caused by validation issues, and has been corrected by modifying 'CreateObjectByPage' to pass the parameter 'SkipAddRemote' while calling save activity as true. Save will use this activity to skip current validation through 'ManageRemoteWorkTypesInApplication'.