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-116761 · Issue 169833

FormatNumber use clarified

Resolved in Pega Version 7.1.7

Attempting to use the "pxFormatNumber" function in an activity step generated the error message "com.pega.pegarules.session.internal.mgmt.Executable cannot be cast to com.pega.pegarules.pub.runtime.StreamBuilderToolKit". Formatter RUF were not intended to be called directly from activities, but RUF has been enhanced to work with reduced functionality in case it is called from activity. The documentation has also been updated to reflect preferred usage.

INC-178417 · Issue 670114

Flag reset added for grid with 'Expand When'

Resolved in Pega Version 8.7

A grid using an 'Expand When' condition worked as expected when the condition was true, but once expanded the grid did not collapse if the expand condition was changed to false even if a section/harness refresh was performed. This has been resolved by adding an update which will reset the flag when the result of 'Expand When' is false.

INC-165992 · Issue 657691

Table Filter save uses correct harness

Resolved in Pega Version 8.7

After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.

INC-173760 · Issue 658069

Table Filter save uses correct harness

Resolved in Pega Version 8.7

After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.

SR-118159 · Issue 174990

Improved handling for Case notes when spellchecker is active

Resolved in Pega Version 7.1.7

If a lot of content was added for a case Note, clicking on the Notes tab caused the text to display in a big yellow box which could not be dismissed. This was traced to the spell checker not properly handling RTE's hidden textarea field, and the code has been modified to correct this.

INC-185847 · Issue 669526

Handling added for disabling weekends when no weekends are available

Resolved in Pega Version 8.7

A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.

SR-118725 · Issue 174420

Corrected focus for filter window using WAI

Resolved in Pega Version 7.1.7

With WAI enabled for work object - Audit window- History table - Time column, clicking on Filter window did not properly move the focus to the first element i.e., Add/Remove columns link. The getFirstInputElement API has been modified to fix the reported issue.

INC-173162 · Issue 650795

Certificate match will use Subject Distinguished Name

Resolved in Pega Version 8.7

Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.

INC-189047 · Issue 674759

Session timeout adjusted for use with Apple Safari

Resolved in Pega Version 8.7

A configured browser session logout timer was not working with the Apple Safari browser. This was traced to browser-specific handling for self.location.href and has been resolved by adjusting the logic and moving it inside a setTimeout to improve cross-browser compatibility.

SR-118081 · Issue 169902

Focus correctly set for dynamic select using accessibility

Resolved in Pega Version 7.1.7

When using a cascading dynamic select control configuration with the PegaWAI accessibility ruleset, setting the focus of the first DS list did not work when attempting to navigate the UI components via the keyboard. When reaching the first DS control, users could only select the next item in the list and then the focus switched to the second DS list immediately. The DynamicSelect control was missing a name attribute, and has been updated to address the focus 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