SR-133048 · Issue 202946
Enhancement added to filter list of bulk processing operators
Resolved in Pega Version 7.1.9
When opening Case Manger portal > Open bulk Actions, selecting the Filter condition as 'Assigned To Operator' showed all operators in the autocomplete list. An enhancement has been added to create the extension activity 'pyGetListOfOperators' for RD which can be updated as per the user requirement to filter the list of operators to be shown in the Bulk Processing Search.
SR-133048 · Issue 202342
Enhancement added to filter list of bulk processing operators
Resolved in Pega Version 7.1.9
When opening Case Manger portal > Open bulk Actions, selecting the Filter condition as 'Assigned To Operator' showed all operators in the autocomplete list. An enhancement has been added to create the extension activity 'pyGetListOfOperators' for RD which can be updated as per the user requirement to filter the list of operators to be shown in the Bulk Processing Search.
SR-133545 · Issue 206691
Closed potential vulnerability in (deprecated) pyNote attach function
Resolved in Pega Version 7.1.9
In order to close a potential vulnerability with pyNote executing a script that is embedded in the note, the handling has been replaced with 'richtext'. However, while the Notes feature is still included in the system for backwards compatibility, please note that Notes has been deprecated and replaced by Pulse.
SR-132185 · Issue 205500
Corrected reference matching for relative pagegroup properties
Resolved in Pega Version 7.1.9
During page copy, the references in pagegroup property were becoming corrupted when given as a relative reference. Reference matching has been updated to resolve this.
SR-133606 · Issue 204762
Corrected reference matching for relative pagegroup properties
Resolved in Pega Version 7.1.9
During page copy, the references in pagegroup property were becoming corrupted when given as a relative reference. Reference matching has been updated to resolve this.
SR-133681 · Issue 206951
Added handling for two declare index rules on two pagelist properties in the same work class
Resolved in Pega Version 7.1.9
Given two declare index rules on two pagelist properties in the same work class, the second declare index was working while the first declare index was behaving inconsistently. It was found that even though there were two records for the property, at run time only the second record was getting inserted because only one insert command fired for Accounts Pagelist and the Declare index did not update even after using pzReindex is true. To ensure proper function firing, the system has been updated so when pzReindex is true, the existing pzIndexes page group value will not be considered.
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-132637 · Issue 203591
Added path checking to FirstLogCreationTime.log
Resolved in Pega Version 7.1.9
FirstLogCreationTime.log was being written to a temp folder using hard-coded logic to use a relative path within the install directory. This caused errors if the installer was trying to write the logs in an absolute path. FirstLogCreationTime.log should be written to the same directory as the rest of the logs, and this issue has been fixed by adding a condition in LogDeleteUtil.getLogCreationTimeFile() method to check for absolute paths.
SR-132987 · Issue 205014
Enhanced Expression Builder icon availability
Resolved in Pega Version 7.1.9
Previously, the Expression Builder gear icon was only available for text type properties: this has been updated to make the EB icon visible for all property types.