INC-148853 · Issue 609317
Corrected password comparison handling for CopyMerge Ruleset Wizard
Resolved in Pega Version 8.6
When running the CopyMerge Ruleset Wizard, entering the password failed with the error "pyPassword: Invalid Password for" Temp:01-01-01 for each ruleset. Investigation showed that the system was calling an activity which encrypted the user input, causing the comparison with the stored password of the system to fail the match. This has been resolved by removing the extra encryption so the call to the comparison evaluates correctly.
INC-149728 · Issue 608106
Application wizard security updated
Resolved in Pega Version 8.6
A user having PegaRULES:User1 role only was able to run the Create Application wizard until an authorization block was reached, yet some rules were created. No operator records were created as part of this process. This was traced to code left in place after the creation of pxAppConfig and pzAppConfig portals, and has been resolved. The New Application wizard UI will display a message to a user when they lack access to build a new application, and an error will be displayed for any attempt to create a new application directly via pzCreateNewApplication to address a scenario where a user might be trying to call the activity without the front end.
INC-150039 · Issue 608043
Adjusted validation of literal value of a parameter
Resolved in Pega Version 8.6
When mapping a parameterized when rule to the proposition filter, parameters passed from the proposition filter page were not getting flown to the when rule. This was caused by special character validation for a literal value of a parameter which necessitated putting the parameter value within quotes and which resulted in a parameter value mismatch at run time. To support this use, this validation has been disabled as parameter values would not get included within quotes. This change does not have any impact on when rule or proposition filter rules java generation.
INC-150845 · Issue 606343
OpenRule logic updated for GetRuleInfo
Resolved in Pega Version 8.6
The exception "InsufficientPrivileges:RuleExecutionDenied RULE-OBJ-ACTIVITY @BASECLASS PZGETRULEINFO" was thrown for some access groups when attempting to view a section from the end-user perspective on the Opportunity screen. Investigation showed this happened when a section had a table in which "Optimize code" was unchecked. If "Optimize code" was checked, then the exception was not thrown. This was traced to recent security changes in pzGetRuleInfo which affected the BAC registration process, and has been resolved by updating the way the openRule action registration logic invokes the activity.
INC-151662 · Issue 626577
Handling added for application which includes production ruleset
Resolved in Pega Version 8.6
When creating the Email channel or Webchat channel, the Text Analyzer and its respective class (Data-Decision-Request-MCP-WebChat-xxxxx) was being saved in the ruleset of the built-on application while there were rulesets open in the top application. This was a missed use case, and has been resolved byupdating the logic to account for the scenario where an application includes a production ruleset.
INC-151669 · Issue 618043
Formulas corrected for GenerateExcelFile
Resolved in Pega Version 8.6
After upgrade, using pxGenerateExcelFile to generate an Excel file resulted in some formulas and values not displaying. This scenario used an Excel template with two tabs - one showing direct page values and the second displaying the calculated values of first sheet. In the exported file, the formula was not getting evaluated unless and until the cell was activated with the enter key. This is a known limitation, and a temporary solution has been made here to add parameters that force the formula evaluations on the saved Excel document when editing is turned on. A more complete solution will be included in the next patch release.
INC-152321 · Issue 612364
docx4j libraries updated
Resolved in Pega Version 8.6
After performing a Microsoft Word merge with a Word template, the error “Word found unreadable content in….” appeared while opening the Word document. This was traced to the older versions of docx4j not handling the latest Microsoft Word features, and has been resolved by upgrading the docx4j and related jars.
INC-153697 · Issue 625983
Dragon successfully navigates to user profile icon
Resolved in Pega Version 8.6
Attempting to navigate to the user profile icon when using Dragon software was not working. This is an issue with how Dragon interacts with the "< i >" element operator icon, and has been resolved by replacing "< i >" with a button and appropriate aria label.
INC-154524 · Issue 613893
SortColumn direct invocation set to true
Resolved in Pega Version 8.6
Sorting on email account rules was generating an error. This was traced to previous security work that removed the ability to use direct invocation of the activity sortColumn from the client or a service, and has been resolved by setting "Allow direct invocation" to be true as well as adding the "AllFlows" (based on @baseclass) privilege.
INC-155401 · Issue 630449
Circumstance Definition rules save correctly
Resolved in Pega Version 8.6
After upgrade, attempting to save any circumstance definition that used multiple "or" conditions consistently failed during conflict detection. This was an inadvertent side effect of work done to resolve an out of memory error and has been resolved by modifying the Rule-Declare-!testConsistency java step:"int numRows = numOrs;" to"int numRows = numSubRows;".