SR-133183 · Issue 205535
Fixed flow line distortion in Process Modeler
Resolved in Pega Version 7.1.9
When clicking through to a subprocess from a parent flow (by clicking the + sign in the blue subprocess shape), flow lines in the subprocess were shown in a distorted fashion. When opening the same flow in a separate tab (by right clicking the blue subprocess shape and selecting Open Flow) the flow lines were correctly painted. This was an issue caused by the different renderings of the flow depending on whether there was a click through to it (with the + on the parent flow?s subprocess shape), or the subflow was opened in a separate tab (with open Flow). After the Process Modeler saved and checked-in the flow, the connector lines were re-drawn in ways that were non-intuitive and hard to interpret due to the edge routing in PM being calculated off incorrect input data that was taking into account shapes that were not represented on the screen. To fix this, the system now ensures the edges are routed without taking into account any shapes not represented on the canvas.
SR-133184 · Issue 203710
Fixed flow line distortion in Process Modeler
Resolved in Pega Version 7.1.9
When clicking through to a subprocess from a parent flow (by clicking the + sign in the blue subprocess shape), flow lines in the subprocess were shown in a distorted fashion. When opening the same flow in a separate tab (by right clicking the blue subprocess shape and selecting Open Flow) the flow lines were correctly painted. This was an issue caused by the different renderings of the flow depending on whether there was a click through to it (with the + on the parent flow?s subprocess shape), or the subflow was opened in a separate tab (with open Flow). After the Process Modeler saved and checked-in the flow, the connector lines were re-drawn in ways that were non-intuitive and hard to interpret due to the edge routing in PM being calculated off incorrect input data that was taking into account shapes that were not represented on the screen. To fix this, the system now ensures the edges are routed without taking into account any shapes not represented on the canvas.
SR-132352 · Issue 202264
Corrected Filter criteria Pick Value button behavior
Resolved in Pega Version 7.1.9
The Pick Value filter criteria pop-up was only working if the property was a direct class property and did not work with an embedded property. This has been corrected.
SR-132827 · Issue 202511
Adding handling for 'today' date field in RD filtering
Resolved in Pega Version 7.1.9
The 'today' link in calendar popup selects the current date when clicked and automatically closes the popup, but attempting to use the 'today' link in a Report definition with a date field as a filter did not select the current date and did not autoclose. This has been corrected.
SR-132946 · Issue 202933
RD with multiple joins now displays all properties in Data Explorer to end user
Resolved in Pega Version 7.1.9
Given a Report Definition with two joins defined on it, the end user was not able to view or select from all of the properties from the joined classes due to the myStepPage adding entries outside of the WHILE loop. This has been corrected by updating the pzGetPropsForTreeGrid activity to handle this scenario by iterating through all of the join classes and showing them in Data Explorer.
SR-A1705 · Issue 205449
Fixed scrumboard intermittent failure
Resolved in Pega Version 7.1.9
After upgrading, it was seen that the scrumboard would intermittently fail to load, partially displaying and then hanging if the columns did not fit within the window boundaries due to the number of elements. This was traced to an error in the functionality that resizes parts of the scrumboard, and has been fixed.
SR-A4995 · Issue 213355
Fixed flow line distortion in Process Modeler
Resolved in Pega Version 7.1.9
When clicking through to a subprocess from a parent flow (by clicking the + sign in the blue subprocess shape), flow lines in the subprocess were shown in a distorted fashion. When opening the same flow in a separate tab (by right clicking the blue subprocess shape and selecting Open Flow) the flow lines were correctly painted. This was an issue caused by the different renderings of the flow depending on whether there was a click through to it (with the + on the parent flow?s subprocess shape), or the subflow was opened in a separate tab (with open Flow). After the Process Modeler saved and checked-in the flow, the connector lines were re-drawn in ways that were non-intuitive and hard to interpret due to the edge routing in PM being calculated off incorrect input data that was taking into account shapes that were not represented on the screen. To fix this, the system now ensures the edges are routed without taking into account any shapes not represented on the canvas.
SR-A1139 · Issue 204433
Ensured threshold checkbox honored in Report Wizard
Resolved in Pega Version 7.1.9
Validation errors were being generated in the custom report wizard when 'threshold' was not selected. This was an issue where the validations were being added without checking the value of the checkbox, and has been corrected.
SR-A1220 · Issue 204961
Corrected SQL exception on Monitor Processes reports
Resolved in Pega Version 7.1.9
Some Pega out-of-the-box summary reports under 'Monitor Processes' like "Created in last 30 days by Operator", "Created in last 90 days by operator, etc., were throwing SQL exceptions on drill down if they had data. This was caused by the DrillDown activity getContentWeekly that was being used for some of the SVs not having the flags pyCanUseVirtualList and pyUseVirtualList set to true, unlike the default DrillDown activity getContent. This was causing the query generated for DrillDown to have the prefix "PC0" only for the drilldown filter condition. This has been resolved by modifying getContentWeekly to set the flags properly.
SR-A1267 · Issue 207657
Refined ScheduledTask-Reporting-pyExecuteTask to improve system performance
Resolved in Pega Version 7.1.9
An issue was found with performance degradation and excessive logging caused by the repeating of a scheduled report that had an exception and did not terminate after xx retries. Checks have been added to Pega-ScheduledTask-Reporting-pyExecuteTask in order to prevent this problem.