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-C86952 · Issue 428817

Viewing screen capture attchments no longer requires IE/Silverlight

Resolved in Pega Version 8.1.4

Previous versions of the Pega Platform required the use of the IE browser with Silverlight to access old attachments added using the screen capture feature. In order to support multibrowser compatibility, the system has been updated to use javascript functions to display these images so IE/Silverlight are not required.

SR-C87309 · Issue 430091

Shortened cleanup time for unauthenticated requestors

Resolved in Pega Version 8.1.4

Any type of probing done to the system with a public URL was generating many unauthenticated requestors that had a one hour lifetime if the user hit /PRAuth and left before reaching the postAuthenticationActivity. In order to speed cleanup in such cases, the system has been updated to ensure the postAuthActivity that sets setShortTimeout(true) is called even if the authentication isn't completed.

SR-C87399 · Issue 426185

pzEditSkills activity updated for better skill matching

Resolved in Pega Version 8.1.4

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-C87463 · Issue 432615

Required image replacing Mandatory Asterisk displays correctly

Resolved in Pega Version 8.1.4

After creating a mandatory text input field in a section and uploading the required image in place of the default image, the previous default image was still displayed in the portal even after clearing the browser cache and /temp folder on the app server. This was caused by the CSS rule 'pzbase-div-layouts' using specific selectors that had a hard-coded content hash for the image, which has been corrected.

SR-C87665 · Issue 424612

CPU time will be fetched from MBeanServer instead of the JRE application to provide consistency

Resolved in Pega Version 8.1.4

The value of CPU time in the Enterprise health metrics was being given in nanoseconds instead of seconds after the IBM JRE version was upgraded by applying Websphere Application Server patches. The CPUTimer is a platform class which has logic specific to different JRE vendors; in order to provide consistent results regardless of which JRE is used, the system has been updated to always fetch the values from the MBeanServer.

SR-C87757 · Issue 431645

Country Code for Austria saved correctly

Resolved in Pega Version 8.1.4

When trying to save an address with CountryCode=AT, the code was saved as "at" instead. This was caused by a temporary field value not being correctly cleared, and has been resolved.

SR-C87881 · Issue 427102

Additional dropdown options exposed for RD column definitions

Resolved in Pega Version 8.1.4

When using Column formatting in Report Definition ruleform, the "Negative format" option was losing its custom style after opening and submitting the "Format" popup using the magnifying glass. This was caused by the submitted popup overwriting the inherited style reference. Previously, the style ref options were hidden from the dropdown because the same UI is shown in the ruleform and the end user portals and the desire was to avoid end user confusion. In order to support developer use, pzPopulateNegativeFormat has been updated to expose the missing options in the dropdown.

SR-C87986 · Issue 428573

Resize handle correctly changed for RTL locale

Resolved in Pega Version 8.1.4

When the locale was set to RTL, dragging sections to the left caused a resize and dragging sections to the right moved them to the left. This has been resolved by ensuring the resizable handle for workarea is correctly changed when the locale is RTL.

SR-C88178 · Issue 429527

docx4j jar updated for compatibility with Office365

Resolved in Pega Version 8.1.4

After generating a docx file with Office365, an error appeared indicating the document had invalid XML data and couldn't be opened. Once the error message was dismissed, the file could be opened normally. This was caused by an incompatibility between Office365 and the Plutext docx4j jar, and the Plutext jar has now been updated to version 6.1.1 to resolve this issue.

SR-C88236 · Issue 428788

Debug logging added to HTTP API for improved diagnostics

Resolved in Pega Version 8.1.4

Debug loggers have been added to the HTTP API to provide more complete diagnostics for an error where users are redirected to login screen after providing valid credentials. As a workaround, restarting the node server will resolve the login issue.

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