SR-A94166 · Issue 262015
Fixed misaligned headers in decision table
Resolved in Pega Version 7.2.2
A misalignment of column headers was seen in a decision table when the number of columns added exceeded 18-20. This has been corrected by adding pixel adjustment of the scroll width to the decision table header when a range is selected for a column in pzRuleDeclareDecisionTableStandard js.
SR-A92650 · Issue 262402
PackageRuntime error resolved
Resolved in Pega Version 7.2.2
A pzPackageRuntime error when saving instance of custom rule was traced to the variable not being in the scope. This has been addressed.
SR-A97752 · Issue 271947
Test Suite operator ID error fixed
Resolved in Pega Version 7.2.2
After creating and executing a Test Suite, the error "Unable to open an instance using the given inputs: pxObjClass = "Data-Admin-Operator-ID", pyUserIdentifier = "System" appeared on the Dashboard landing page of the Automated Unit Test. This was due to the system not setting the operator identifier when doing the agent login, and has been corrected.
SR-A100251 · Issue 271797
Editing a decision table works on hardened system
Resolved in Pega Version 7.2.2
After enabling URL Encryption and URL Obfuscation in the Production Environment per Pega best practice recommendations to secure/harden an environment, an HTTP 400 error was thrown when attempting to Edit a Decision Table in Pega Marketing. This was an error in the URL decoding for the DisplayModalDialog HTML rules, and has been fixed.
SR-A88818 · Issue 261452
New pzPreMergeSave activity Rule-File- for multiple node propagation
Resolved in Pega Version 7.2.2
After merging rules of type Rule-File-Text across four nodes, there was a delay in the changes being reflected on the other nodes. The issue was caused by a simple save of Rule-File-Text not propagating pulseChange directly, and has been fixed by creating a new pzPreMergeSave activity Rule-File- to handle this merge.
SR-A87492 · Issue 256199
Strip "()" from Page name for Loop and Parameters for post-upgrade compatibility
Resolved in Pega Version 7.2.2
After upgrade, a change in system behavior with RUF Utilities.findClassOfPageReference returned the incorrect class name for pages that contained the string "()". For example, existing pages and classes has the entry TestPage.pxResults(), but the system is looking for an input page named TestPage.pxResults, and the startsWith check failed. To resolve this, the code has been updated with added logic in findClassOfPageReference to remove the empty () if it is present at the end of page and classes entry.
SR-A93033 · Issue 260830
Better visibility for preconditions after upgrade
Resolved in Pega Version 7.2.2
After upgrade, all preconditions (e.g.. WHEN rule) in Collection rules appeared to be missing. Though pyPreconditionWhen was populated, pzShowPrecondition was not set for a collection that was imported from v6.2 and did not display. To resolve this and create better backwards compatibility, pzShowPrecondition will be set to true/false based on whether pyPreconditionWhen is blank or not. This will be set in openDefaults activity for Rule-Declare-Collection .
SR-A98193 · Issue 266453
Black listed properties properly excluded from compare results
Resolved in Pega Version 7.2.2
After upgrade, properties that were included in the black list were showing up in the compare results. This was an error in determining which declaratives would be disabled when calling the applyIgnoreMap method directly, and has been fixed by removing declarative enabling / disabling from applyIgnoreMap, and moving them into the code for PageCompare.
SR-A77163 · Issue 252819
Associated rules locking fixed for PFM offer flow
Resolved in Pega Version 7.2.2
After using the "Release lock" option in the action menu for a flow (or offer rule from the Pega Field Marketing application), it was not possible to check-out the flow or offer and an error message appeared indicating another user had the record checked out even when that user did not see it in their own checkouts. This was traced to the "Release lock" feature not appropriately releasing locks on the associated rules, in this case, the binary that is generated in the background for the flow or offer. It was possible to work around this by opening the binary using the "Open stored flow image" option and then selecting "Release lock" in order to release the lock on the image, but the locking has now been corrected.
SR-A99969 · Issue 266109
Ruleset listing works without enabling UDFs
Resolved in Pega Version 7.2.2
All core Designer Studio features and Pega frameworks / applications are supposed to work without dependency on pr_read* UDFs, but an issue was found with attempting to list rulesets without enabling UDFs. This was due to the Designer Studio features used to list instances of a rule class performing behind the scenes filtering to exclude rules with pyMethodStatus = Internal pr Deprecated. Listing members of rule-ruleset-name then failed as this class does not have an exposed property pyMethodStatus. To fix this issue, a check has been added to decide if the rule type is rule resolved or not. If the rule is resolved, then there will be a check for pyMethodStatus exposed or not. If pyMethodStatus is not exposed, then it will fallback to old list view. In addition, a check was added to not to add filter conditions on pyMethodStatus for non-rule resolved rule types. The only exception to this is Rule-Utility-Library, i.e. even though library ruleform is non rule resolved, pyMethodStatus filter will be added.