SR-A279 · Issue 203592
Layouts modified to indicate ApplyTo is required for New/SaveAs declare pages
Resolved in Pega Version 7.1.9
For declare pages, though pyClassName is not a key, it is still a mandatory field on form. This was causing confusion in cases such as a valuation error on a data page that had the apply-to class set as blank because there was no indication it was a required field. To clarify this use, layouts have been modified to always show ApplyTo as a mandatory field on New/SaveAs screens.
SR-A299 · Issue 204842
Filtering performed ahead of retrieving results in GetRulesets
Resolved in Pega Version 7.1.9
The GetRulesets activity has a MaxRecord ResultCount of 10,000. If a site exceeded that number of rulesets in total, the report of all available unlocked rulesets would not return the correct results even if the number of unlocked rulesets did not exceed the limit. To handle complex installations, the @baseclass.GetRuleSets activity has been modified to filter the rulesets before retrieving to allow for the return of complete and accurate results.
SR-A325 · Issue 203740
Added Params to activity display before check-in
Resolved in Pega Version 7.1.9
When calling an activity from another activity, parameters were not being properly retrieved in the calling activity call step unless there was a check-in that called activity. This happened when a private ruleset was not in the user's context and therefore the checked out rule was not picked up. To correct this, the open activity method has been modified to use db.open() .
SR-A4712 · Issue 211249
Repaired column header labels in Decision Table
Resolved in Pega Version 7.1.9
Clicking on a column header and opening the property changer, then closing it using the X in the top-right corner of the popup caused the label to change to the label of the rightmost column. This was traced to incorrect behavior by the modal dialog where closing the window did not return the correct value from the previous launch. This has been corrected.
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.