SR-A4940 · Issue 211386
Improved performance for large History-Work reports
Resolved in Pega Version 7.1.9
When History-Work- contained a very large number of rows, performance issues were seen while running the History-Work-.pyGetStatusChanges report. To resolve this, the RD History-Work-.pyGetStatusChanges has been updated with modified filtering conditions and improved error handling for blank param.InsKey fields.
SR-A5054 · Issue 211505
Corrected revalidateAndSave modifying the 'Applies to' class
Resolved in Pega Version 7.1.9
During upgrade, revalidateAndSave was modifying the 'Applies to' class of the included rule. The issue was caused by modification of the pyIncludedRuleXML in the flow action / section rules that holds the included section's information; flow action was depending on this page to set the class, but since this page no longer existed the class was defaulting to the current flow action's primary class. To resolve this, if pyPrompt class is blank in activity Rule-Obj-FlowAction.OpenDefaults, the system will try to get the page name from the flow action rule, iterate across its pages and classes, and find the class name where the page name matches and set that as the applies to class for the flow action's section.
SR-A903 · Issue 204613
Added handling for agent activity with no primary page
Resolved in Pega Version 7.1.9
Running an agent activity with no primary page generated an NPE even though all step pages were correctly specified. This was caused by the out-of-the-box referring to the nonexistent primary page in a context where it was not necessary. While there was a workaround of specifying a primary page for the agent activity, a change has been made to set and retrieve messages from pyPDFAttachWorkPage instead of a primary page in this situation.
SR-A1536 · Issue 205669
Fixed exception for read-only edit on data page
Resolved in Pega Version 7.1.9
Exceptions were being logged for a data page when edit mode was set as Read Only. This was caused by setIsReadonly in ClipboardPropertyImpl directly using the mPageValue which would be null for ref-type properties. The system has been updated to use getPageValue() instead of mPageValue directly.
SR-A3157 · Issue 207690
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-A3170 · Issue 213298
Stabilized encoding and decoding of Thai characters in imported CSV files
Resolved in Pega Version 7.1.9
While importing CSV files containing Thai characters, the methods of encoding and decoding were different and JVM differences could lead to output from the file being garbled. This has been updated to uniformly ensure the Thai characters will be properly recognized and converted.
SR-A3170 · Issue 212348
Stabilized encoding and decoding of Thai characters in imported CSV files
Resolved in Pega Version 7.1.9
While importing CSV files containing Thai characters, the methods of encoding and decoding were different and JVM differences could lead to output from the file being garbled. This has been updated to uniformly ensure the Thai characters will be properly recognized and converted.
SR-A3559 · Issue 208309
DataPage sourced Grids now able to launch local action
Resolved in Pega Version 7.1.9
An exception was being generated from SFA when attempting to copy a read-only data page of scope id requestor level during redirectAndRun. Copying of read-only data pages was not supported because it was expected the page would be loaded on a new thread when accessed, but for parameterized data pages this loading was not true because the parameters were missing. A read-only data page was also not copied because the lookup maps in the container would have to be populated. In order to support applications containing a grid sourced with DataPage and a section inside the grid contains an icon that launches a localAction, copying of read-only data pages is now allowed. During copy, if the page being copied is read-only the data page will get the parameter page for the instance from the container and do findPage() on new thread with this information. For other pages, it will continue to copy into new thread.
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.