SR-120468 · Issue 185827
Appearance order retained for multiple swimlanes
Resolved in Pega Version 7.1.8
After putting multiple swimlanes in a flow, the order of their appearance was returning to the original state after saving it. This was caused by the rendering being performed in the order the server store/sent the swimlane data. To ensure proper behavior, the swimlanes are now reordered based on the swimlane layout (horizontal, vertical) and their coordinates before being rendered.
SR-121825 · Issue 181670
Multiple annotations now allowed for swimlane objects
Resolved in Pega Version 7.1.8
When two annotations were used with swimlanes, the description in the annotation is unexpectedly changed or the annotation itself disappeared due to an ID conflict. There was a workaround of adding the shapes using the right click, but the annotation shape is now correctly added to the work flow using the proper unique ID.
SR-122025 · Issue 181153
Dropped rule added to DSM rules for SR properties
Resolved in Pega Version 7.1.8
A set of rules was inserted into the UI of Proposition LP and Strategy rules in DSM (Designer Studio) for use in retrieving a list of SR properties. This set was inadvertently missing the rule 'Activity Embed-Decision-SPContainer . pyRefreshSPList', and this has been added.
SR-122902 · Issue 182835
Shutdown issue with Tomcat resolved
Resolved in Pega Version 7.1.8
During shutdown, errors were reported on the App Server window. Shutdown did not complete and the App Server Window remained open. This was due to the "Shutdown" button/feature not properly terminating Tomcat. There was a workaround to manually close the Tomcat window, but the DNodeServiceListener has been modified to release all of the threads properly.
SR-123031 · Issue 182673
Corrected inheritance logic for ComputeSegment
Resolved in Pega Version 7.1.8
ComputeSegmentLogic activity logic was not considering inheritance path. This was an issue with having the run-time rule resolution at design-time, and has been changed to pass propagate the apply-to class to sub-activity calls so that it can pick up the right rule.
SR-123968 · Issue 194580
Added special character handling to Process Modeler
Resolved in Pega Version 7.1.8
After migration, some sites attempting to open flows through Process Modeler saw only the 'loading' message for a long time and then an error was displayed. This was traced to the use of user-input strings containing special characters in the canvas-based rule data, and has been resolved by adding character escaping during the model generation.
SR-123968 · Issue 194306
Added special character handling to Process Modeler
Resolved in Pega Version 7.1.8
After migration, some sites attempting to open flows through Process Modeler saw only the 'loading' message for a long time and then an error was displayed. This was traced to the use of user-input strings containing special characters in the canvas-based rule data, and has been resolved by adding character escaping during the model generation.
SR-124054 · Issue 189568
Simulation delete timing issue resolved
Resolved in Pega Version 7.1.8
When attempting to delete a simulation, if the deletion process exceeded the system time-out or the space on the database required for undo was too small (as can occur when many simulations have been run and the simulation output table contains many millions of records), the mass deletion failed and the system became hung or returned a time-out screen which required logging out and in again. At that point it was seen that the simulation results had been removed from the list but the actual results deletion did not complete. This was caused by the simulation work item being closed first, followed by the delete of the table. In the case of a failed deletion because of any DB issue, manual intervention was required to delete the records from the table as the simulation object was no longer available. To resolve this, the sequence of steps while deleting the Batch WO from LPhas been updated to show the relevant error message in case of failures for any reason, and the work object is closed after the output table is deleted.
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-131162 · Issue 201045
Corrected inheritance for Data classes
Resolved in Pega Version 7.1.8
After migration, an API used to pull the list of concrete classes from RootClass Work- was pulling an additional class (Data-Portal-Padportal) when work- was supplied as an argument for rootclass. This additional class caused issues with reports due to it pointing to pr_history_data table and looking for non-existent columns. These inheritance issues have now been corrected.