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.

INC-151669 · Issue 618042

Formulas corrected for GenerateExcelFile

Resolved in Pega Version 8.4.4

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-144597 · Issue 598307

Updated handling for MT query of pr_data_admin table

Resolved in Pega Version 8.4.4

When using a multi-tenant environment with Oracle, as the number of users in the environment increased, the number of queries of the pr_data_admin table "WHERE pyEnableAuthService" increased exponentially and causes system slowness. This was traced to missed handling for the @ character in the authentication service cache while requesting, and has been resolved by updating authservicecache.java.

INC-144555 · Issue 603071

Changelog cleanup added for de-optimized properties

Resolved in Pega Version 8.4.4

Unwanted optimization was automatically added to properties for the Application-Work-Casetype class created using the wizard in the App Studio. Attempts to remove the optimization did not work: the property advance tab was showing the optimized classes details even after deleting and recreating the property. When a property is optimized the system adds entries to pr_changelog for the list of classes it has optimized. When the property was deleted, the pr_changelog was not cleared. This was a missed usecase, and has been resolved by overriding the Cleanup activity at Rule-Obj-Property class to delete the pr_changelog entry associated with that if it is present.

INC-141595 · Issue 602715

CSRF and Browser fingerprint tokens added for testing custom scripts

Resolved in Pega Version 8.4.4

After upgrade, the test window appeared blank when attempting to test Decision Table rules. This was traced to there not being CSRF token and Browser fingerprint handling in the custom script used to show a prompt screen to the user. Because the CSRF token validation was missing, the request failed. To resolve this, CSRF and Browser fingerprint tokens have been added as hidden fields.

INC-153152 · Issue 613685

Privilege on table cells updated for non-template mode

Resolved in Pega Version 8.4.4

When using a table sourced from a report definition where certain cells were hidden or shown based on privilege, the configuration worked as expected in regular tables but did not work correctly for optimized tables. This was traced to an issue with image control rendering in non-template mode related to privileges for the image, and has been resolved by updating the pzgenerateicon Rule-Utility-Function.

INC-143320 · Issue 602282

Support added for email addresses with hyphen in domain name

Resolved in Pega Version 8.4.4

When attempting to enter a email with a hyphen '-' in the domain part of an email ID ([email protected]), the reply button was getting disabled. This was caused by the regex validation implemented in the "pzValidateEmailAddress" (Work-Channel-Triage-Email) standard activity not covering all the possible cases. To resolve this, regex has been changed to instead use a platform-provided rule to ValidateEmailAddress.

INC-154458 · Issue 620211

Calendar picker placement corrected for Ajax container

Resolved in Pega Version 8.4.4

When using inline edit and clicking date picker, the calendar popover was displayed in a blank space away from the position of the date picker. This was due to a popover inside a screenlayout having scrolltop and scrollleft values added to the popover position; in the case of an Ajax container these values resulted in incorrect position of a popover. To resolve this, adding the scrolltop and scrollleft will be bypassed if the element where the popover is attached is inside a Ajax Container.

INC-151050 · Issue 610678

Added check for empty string to custom Timeline Date Range

Resolved in Pega Version 8.4.4

When using the Timeline control and selecting Date Range as a custom value, the loading icon (busy indicator) showed continuously on the screen and no other operations were possible. Selecting any Date Range other than the custom field value worked as expected. Investigation showed that the Timeline control was not working when the Date Range value was empty, which in this case was traced to a value being entered at design time and then cleared. In timeline options, the Date Range end option was checking for the value being undefined and did not consider the empty string (""); this has been resolved by adding a condition to check if the Date Range option end is an empty string.

INC-154627 · Issue 619570

Re-enabled users are able to log in

Resolved in Pega Version 8.4.4

When disabled operators were re-enabled through operator management, the forced password change on next login was manually unchecked but the operators were unable to login because the change password screen was displayed without any password entry fields. This was a missed use case for handling the change password flag on a requestor , and has been resolved by having the system skip setting the change password on next login flag for disabled users.

INC-145467 · Issue 617216

isDCSPA flag added to ensure correct harness after reload

Resolved in Pega Version 8.4.4

When moving from a Process Flow to a Screenflow configured with tabbedscreenflow7, the first reload caused a switch to a Perform Harness that resulted in the error "Unable to open an instance using the given inputs", and footer buttons disappeared until multiple refreshes were done. This was an issue specific to the environment configuration at the site, but to avoid future issues a code update has been made that will add the isDCSPA flag if the value is not present in the parameter page.

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