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.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C84167 · Issue 422476

Corrected issue with Field Level Auditing re-adding deleted page list items

Resolved in Pega Version 8.3

Pressing a Save button that invoked the pyTrackSecurityChanges data transform caused deleted items to be added back to a page list. This was caused by pyPropertyIndex being set on the removed page in RUF-pzAddHistoryMemosForPageList, and has been corrected by removing that unneeded action.

SR-C84649 · Issue 422543

Consecutive PreJS properly triggered after Save & Refresh Harness

Resolved in Pega Version 8.3

Consecutive PreJS were not being triggered after using Save and Refresh Harness on Android HC. For example, creating a survey case would trigger PreJS for Name, but after using Save and Refresh Harness the PreJS for Gender was not triggered. This has been corrected by modifying the catch and callback for handling failures on the display harness save.

SR-C84231 · Issue 422665

Merge multiple branches tool updated to resolve selection error

Resolved in Pega Version 8.3

When an application was configured to not allow branches to be merged without being reviewed, the "Merge multiple branches" tool did not allow any branches to be selected even if they had been reviewed. This was traced to the pzLoadBranches activity using local.reviewStatus even though the local variable was not required in this case. To resolve this, the activity has been modified to use Param.reviewStatus to pass the parameter page to pzSetBranchReviewStatus activity. If the 'when' rule pyAllowMergeWhenNotReviewed is set to false, the checkbox will be enabled for branches which are reviewed. For branches which are not reviewed, the checkbox will be disabled and the message "Please review the branch before merge" will appear.

SR-C85315 · Issue 422728

New Activity added to ease cleaning up Thread-level data pages

Resolved in Pega Version 8.3

It is an expected behavior that the system will not automatically remove read-only data pages, as the decision of which pages need to be removed is system-specific. However, it was noted that an accumulation of Thread-level Data Pages may eventually cause performance degradation. In order to make it easier to clean these up, the new extension Activity "pyRemoveThreadLevelPages" has been introduced that is called from the DoUIAction activity.

SR-C84033 · Issue 422744

Added handling for legacy page adaptors to get all messages

Resolved in Pega Version 8.3

If a validation message was present on the Clipboard, the front-end screen was turning blue and displaying the error "There has been an issue, please consult with administrator". This happened when getMessagesAll was called for pyWorkPage and an auto-populate property was present in the embedded pages/properties. To resolve this, cast has been removed when getting all messages and a new API has been added for legacy page adapters to get all messages.

SR-C82549 · Issue 422846

Check added to getRuleNameFromInsKey to clip version name from rulseset name in the dataflow

Resolved in Pega Version 8.3

After changes were pushed to the datasets, dataflows were failing on a DT2 environment with an error related to rule resolution and a failure to find a specific property. The dataflows did not fail on a DT1 environment. Investigation showed that if the ruleset name was empty and the ins key was used to get the rulesetname, a mismatch occurred with the returned value due to the version information being included in the name. To resolve this, when a rule name is retrieved by getRuleNameFromInsKey, the system will check if aObjClass is Rule-RuleSet-Version. If so, the version part will be trimmed.

SR-C74652 · Issue 422901

Grid alignment and headers corrected for Opportunities screen in RTL locale

Resolved in Pega Version 8.3

When using the RTL locale, the Opportunity detail screen and search screen had grid alignment and header issues. This has been resolved by updating the py-portal-stages CSS attached to the enduser skin.

SR-C74648 · Issue 422904

Autocomplete arrow placement corrected in Right to left local mode

Resolved in Pega Version 8.3

When using the Autocomplete control, the blue arrow was seen to have an incorrect placement/orientation in RTL mode. This was traced to the autocomplete background-image in RTL mode being the same as that for LTR, and has been resolved by adding specific background-image for RTL.

SR-C74650 · Issue 422907

Grid alignment and headers corrected for Opportunities screen in RTL locale

Resolved in Pega Version 8.3

When using the RTL locale, the Opportunity detail screen and search screen had grid alignment and header issues. This has been resolved by updating the py-portal-stages CSS attached to the enduser skin.

SR-C84788 · Issue 422936

Handling added to maintain custom modal template name after errors

Resolved in Pega Version 8.3

When using a grid where each grid row had an Edit button which launched a modal dialog with a custom modal template, the post action activity of the flow action introduced error messages on a top level page (not on primary or pyWorkPage). Clicking the submit button again caused the modal dialog size to shrink and not work after that. This was traced to the second submit using the system's pyGridModalTemplate instead of the custom modal template due to the modal submit button being replaced with new markup. To resolve this, the modal launch will now use the "pega.u.d.submitModalDlgParam.modalSection" variable which will have the modal template name. In addition, a check has been added to ensure this is not passed as null.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us