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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-C87399 · Issue 426183

pzEditSkills activity updated for better skill matching

Resolved in Pega Version 8.2.1

In the pzEditSkills activity, a select skill is added to the operator. A check is made using a comparison of pyRuleName equal to pySkillLabel to see whether this skill exists in the system; if it exists it is directly added to the operator profile, and if it does not it is created and added to the operator profile. However, pyRuleName uses a short skill identifier string, for example ‘XML’ whereas pySkillLabel is the longer human readable string, for example ‘XML programming skill’. Therefore, it was possible for Pega to determine the skill did not exist and proceed to creating a new skill with pyRuleName equal to the pySkillLabel of the existing skill in the first available unlocked ruleset. In order to ensure the proper matches are made, the pzEditSkills activity step 4.1 has been modified to get the rule name instead of skill name.

SR-C85315 · Issue 422729

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

Resolved in Pega Version 8.2.1

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-C85853 · Issue 425288

Currency codes updated

Resolved in Pega Version 8.2.1

The list of Currency Codes has been updated with the latest ISO changes, including Venezuela and Sao Tome & Principe.

SR-C89675 · Issue 428596

Case name caption security inserted

Resolved in Pega Version 8.2.1

In order to protect against the possibility of executing malicious JavaScript code by entering an appropriately modified name while adding new case type, pyCaption in menu items has been made HTMLSafe by converting JSON through the GSON library. Additional handling for Firefox has also been added to normalize tabName to properly display Recents.

SR-C76668 · Issue 424444

skipDocsRecreation option added to remove flickering during application launch

Resolved in Pega Version 8.2.1

In order to avoid visible flickering resulting from a dynamic container refresh conflicting with custom code during application launch, an enhancement has been added that can be used to skip the SDM refresh functionality based on the "pega.u.d.skipDocsRecreation" JS property. This can be enabled in Userworkform.

SR-C88309 · Issue 426996

Tooltip added for data table refresh icon

Resolved in Pega Version 8.2.1

An enhancement has been added to provide a tooltip for the refresh icon during data table edits.

SR-C86126 · Issue 423258

CSV import for delete date values will be formatted before row processing

Resolved in Pega Version 8.2.1

In order to support using CSV import for delete purposes, date/time class keys will be formatted before processing the row.

SR-C91521 · Issue 428627

DX API updated for improved security

Resolved in Pega Version 8.2.1

Modifications have been made to the DX API to improve system security.

SR-C84643 · Issue 423855

Logs now support RandomAccessFileAppender

Resolved in Pega Version 8.2.1

Support has been added to the LogFileDownload and LogViewer HTML final rules for using RandomAccessFileAppender. This is in addition to the existing support for RollingRandomAccessFileAppender and RollingFileAppender.

SR-C82549 · Issue 422847

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

Resolved in Pega Version 8.2.1

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.

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