SR-A438 · Issue 210728
Global Resource Settings syntax examples documentation updated
Resolved in Pega Version 7.1.9
An error was found in the documentation examples for using the Global Resource Settings; this has been updated to remove the dot in the syntax examples.
SR-A789 · Issue 205761
Enhancement added for handling DB2 BLOB sizes
Resolved in Pega Version 7.1.9
BLOB schema changes were not being picked up during import due to the schema import/export process being limited in its ability to preserve the BLOB size changes being dynamically set in the db. An enhancement has been added to make meaningful use of reported blob sizes (DB2 LUW and DB2 z/OS).
SR-A1350 · Issue 205576
Added support for adding custom GuardrailWarning
Resolved in Pega Version 7.1.9
A customer-created custom activity "addGuardrailWarning" with incoming parameter (WarningMessage) of type Rule-Message with the intent that whenever the new activity was called from another activity, the SmartPrompt-enabled parameter would provide a list of Rule-Message instances starting with any defined on the class of the Step Page (or the class of the calling Activity when the Step Page is blank), and then working up the inheritance hierarchy, much like the behavior provided on other activity methods such as the Data Transform parameter of the Page-New method. However, the SmartPrompt for this custom function only showed rule-messages of pyCategory "Error", or "blank" due to lack of support for this custom Guardrail Warning. In order to support this customization, the function alias pxAddGuardrailMessage has been created and this FA can be accessed by a call-function method in activity as 'Add a message to a page using [Name of the Message Rule]'.
SR-A2 · Issue 203635
Updated use and edit of the 'Search for work' rule
Resolved in Pega Version 7.1.9
After upgrade, an out-of-the-box functionality to search for work items by selecting the case status and selecting a particular field to add as filter on that search was not working correctly and the search icon (which gives the list of status window dynamically) was missing. An attempt to perform a private check out of of the rule generated an error and did not allow 'save as' because it was unable to identify a property pyStringType. This issue was traced to a missing property 'pyStringType' in @baseclass, and this has been added.
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-A4712 · Issue 211249
Repaired column header labels in Decision Table
Resolved in Pega Version Pega Platform, 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-A3716 · Issue 209598
Added conditional check for bulk check-in memo
Resolved in Pega Version 7.1.9
When performing a bulk rule check-in, the comment was being prefixed with a ?:?. This caused issues when using pyMemo as part of a code review with a report looking at check-in comments for specific changes associated with a project. This name difference was due to the different activities being called and how the pyTaskID parameters were being attached. There was a workaround of saving the Rule-.PreCheckIn activity into the application ruleset, then removing the existing java step and adding a property set to for setting the Param.InMemo value, but this situation has been resolved by conditionally appending task id to history memo.