SR-A1273 · Issue 204576
PRPCTask is now tenantized
Resolved in Pega Version 7.1.9
On a multi-tenant environment with HTTP event, it was not possible to see the options for warm\blind transfer with interaction from a tenant layer. This was an issue with the task taking the user ID information but not taking the tenant information, so the acceptance of the interaction on the portal was not getting delivered to the desktop. To correct this, PRPCTask is now tenantized.
SR-A1390 · Issue 204953
Added qualification to avoid RequestorInitialize conflicts
Resolved in Pega Version 7.1.9
In the out-of-the-box activity RequestorInitialize, RUF CompareDates was invoked by using a short hand notation which was causing conflicts. This has been solved by qualifying the function with @Ruleset:Library.
SR-A1588 · Issue 211728
Content file path handling updated for Linux
Resolved in Pega Version 7.1.9
In Linux systems, a problem was seen with deleting or updating static content due to a difference in the designated directory name: the directory name is case sensitive, but the code to delete the image forced lower case. This has been resolved by leaving the file path as-is for these systems rather than forcing it to lower case.
SR-A1648 · Issue 206014
Resolved file permissions for Java2 security on WAS8.5
Resolved in Pega Version 7.1.9
After enabling Java 2 security on WAS8.5, access denied file permission exceptions were being generated when deploying and starting ML7. This has been resolved by adding permissions for the temp files in both the WAS and rules policy files, and by adding a doPrivileged block code to borrow a compiler.
SR-A2473 · Issue 206389
Concurrent Modification Exception resolved
Resolved in Pega Version 7.1.9
When attempting to open a case from the instances tab (Right click on case -> View -> Instances), a ConcurrentModificationException was generated on the pyWorkPage . This was a problem with a JSP fragment which iterated on and unexpectedly modified the mContent. To avoid this error, the system will create a copy of the content for use in iteration.
SR-A2721 · Issue 206236
Fixed logging directories for PegaRULES
Resolved in Pega Version 7.1.9
After upgrading to a split schema, PegaRULES and PegaRULES-ALERT were written to a single file in the home directory despite the prlogging.xml file specifying the file name and path. This was due to a missing prlogging.xml function in the prresources-non-config.jar, and has been fixed.
SR-A2798 · Issue 205394
Ensured consistent Modal window open in RDL
Resolved in Pega Version 7.1.9
In some cases, an action to open a Modal window from Repeated Dynamic Layout was failing. The root cause of this issue was the subscript which was not being generated for RDL. To resolve this, GenerateSimpleLayoutCellHTML has been modified to ensure every pagelist/pagegroup respective subscripts will be generated in base_ref attribute.
SR-A2930 · Issue 206575
Concurrent Modification Exception resolved
Resolved in Pega Version 7.1.9
When attempting to open a case from the instances tab (Right click on case -> View -> Instances), a ConcurrentModificationException was generated on the pyWorkPage . This was a problem with a JSP fragment which iterated on and unexpectedly modified the mContent. To avoid this error, the system will create a copy of the content for use in iteration.
SR-A3421 · Issue 205720
Corrected Refresh based on clipboard property changes
Resolved in Pega Version 7.1.9
Refreshing the Dynamic layout whenever a property in the clipboard changed was not working in one of the cases in base CPM: when passing "ProcessAction" activity as a pre-activity for any flow action, change tracker did not send the changed values from the newAssignPage. This has been resolved by adding a condition for "ProcessAction" on pre-activity.
SR-A3559 · Issue 207393
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.