Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

INC-148853 · Issue 609319

Corrected password comparison handling for CopyMerge Ruleset Wizard

Resolved in Pega Version 8.5.3

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-151662 · Issue 626578

Handling added for application which includes production ruleset

Resolved in Pega Version 8.5.3

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 by updating the logic to account for the scenario where an application includes a production ruleset.

INC-151669 · Issue 618041

Formulas corrected for GenerateExcelFile

Resolved in Pega Version 8.5.3

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-153697 · Issue 625984

Dragon successfully navigates to user profile icon

Resolved in Pega Version 8.5.3

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-155401 · Issue 630448

Circumstance Definition rules save correctly

Resolved in Pega Version 8.5.3

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;".

INC-159238 · Issue 624304

Handling added for identical property and page names in test case recording

Resolved in Pega Version 8.5.3

When trying to record a test case, the error "WrongModeException: The property PostProsSnapOfWorkpage.Name was of mode String while was expecting Page mode" was generated. This was an edge case caused by property and page names being the same on the "PostProsSanpOfWorkPage" page, and has been resolved by accessing the page with the full path so it has the proper prefix.

INC-160437 · Issue 629646

Upgrade compatibility enhanced for Pega-ConditionBuilder ruleset

Resolved in Pega Version 8.5.3

In Pega v8.2.5, the Pega-ConditionBuilder ruleset was added as part of the PegaMarketing application. When these enhancements were promoted to a platform ruleset beginning with Pega v8.4, the function names were modified with PZ/PX prefixes due to the corresponding validation standards in place for rules created in platform rulesets. Unfortunately, this introduced an upgrade impact. Due to the function name change, strategies failed when attempting to evaluate the functions configured in the filter component. Eg: @string.ContainsIgnoreCase function is part of the Pega-ConditionBuilder ruleset, which was not available. To resolve this, the following function aliases have been created in this release:ContainsIgnoreCase StartsWithIgnoreCase EndsWithIgnoreCase CompareDateTimeToSymbolicDate

INC-160446 · Issue 627381

Updated Time Zone dropdown control

Resolved in Pega Version 8.5.3

The RF_Timezonelist control was deprecated in Pega v8.4 and withdrawn in Pega v8.5 and a replacement datapage was provided to give the same list of time zones. Unfortunately, some references were not corrected to point to the replacement, causing an issue with custom functions that were attempting to set the time zone on an OperatorID calendar instance in order to calculate goal and deadline properties before setting the SLA. The work has been reviewed and updated to ensure all referencing rules are now correctly replacing the RF_Timezonelist with a dropdown sourcing the data page.

INC-143036 · Issue 599190

SurveyPage loads when ruleset is locked

Resolved in Pega Version 8.5.3

When the ruleset containing the survey rules was locked D_pzSurveyPage did not load and errors were generated. Investigation showed that if the flow was in a locked version, the PopulateShapeNodesFromFlowData activity did not call EvaluateConnectorState, causing the mapping of the transitions for connectors to fail in the activity MapBranchShapeConnectors. This has been resolved.

INC-148392 · Issue 610670

File type handling added for cloud downloads on mobile app

Resolved in Pega Version 8.5.3

When using the Pega cloud storage repository (Application -> Integration -> Content Storage) with the mobile app, it was possible to upload attachments but re-downloading the attachments failed. Investigation showed that this was due to the content-type appearing as application/* so the file type was not able to be identified. This was a missed use-case for returnFileForDownload(), and has been resolved.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us