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-A18902 · Issue 237052

Updated tab generation for failed 'when'

Resolved in Pega Version 7.2.1

When visible 'whens' were configured on accordion, the content was not properly displayed below the header if the 'when' condition was false. This was caused by an error in the generation of defaultTab based on visible 'when's, and the GenerateTabbedSectionLayout RUF has been updated.

SR-A18905 · Issue 235333

OrgName error resolved for MobileOffline:Obj-Open-By-Handle

Resolved in Pega Version 7.2.1

If Obj-Open-By-Handle was configured on the Org Name link in MobileOffline for the master details of a Contact Work Object, clicking on the link generated an "Empty Work Item Handle" error despite the OrganizationID(Handle) being present on the data page. This was an error in the actions array for the "runScript" API, and has been fixed.

SR-A18920 · Issue 235519

Corrected positioning of autocomplete popover on mobile

Resolved in Pega Version 7.2.1

When using Safari, the autocomplete popover on mobile devices was not correctly positioned. A browser check has been added, and this has been fixed.

SR-A18959 · Issue 236651

Corrected results display for upgraded pysearchResultWork filters

Resolved in Pega Version 7.2.1

When applying the pysearchResultWork filter on the native work objects search bar, some results were not displayed as expected after upgrade. This was caused by an error in setting the property for ad hoc cases inside a child activity, and has been fixed.

SR-A19079 · Issue 237094

Made date-time control height consistent

Resolved in Pega Version 7.2.1

Control height was inconsistent for date time controls that did not allow text entry, depending upon the control type and presentation setting. This was particularly noticeable when dynamic layout was configured with "inline double" or "inline triple". Extra padding of 2px was found in the non-text-entry control, and this has been removed to make it align to what it is in the text-entry-allowed date time.

SR-A19181 · Issue 240871

dropdown menu item names correctly persist after click

Resolved in Pega Version 7.2.1

Once a dropdown was selected from a number of menus in the user portal, the name of the clicked menu disappeared upon recheck. The API has been updated to read the tooltip from the icon element if it is not already present.

SR-A19249 · Issue 238895

Edit validate rule fires properly

Resolved in Pega Version 7.2.1

When submitting a flow action, the edit validate rule would catch properly catch and report an error, but the the same error submitted a second time did not fail. This has been corrected.

SR-A19287 · Issue 240328

Static value ProgressBar corrected

Resolved in Pega Version 7.2.1

Using the pzProgressBar control to display integer value on the UI screen was not working after upgrade if the progress bar was bound to a static value and not a update activity. This was caused by a Boolean parameter and an integer parameter to the control being passed as a string, and has been fixed.

SR-A19336 · Issue 237165

Fixed always red state for pxDeadlineTime

Resolved in Pega Version 7.2.1

An error in the section Assign-pxDeadlineTime in UI-Kit-7 caused the time to always show up in red when that control was used. The two Date Time properties in the section have custom formatting specified under Advanced Presentation Options in Presentation tab, but this was being masked by the Custom CSS Class specified on the Dynamic Layout presentation. This has been fixed.

SR-A19341 · Issue 242249

Resolved null value entered by tabbing in date field

Resolved in Pega Version 7.2.1

Tabbing in and out of a date/time field without entering a value caused an null value to appear when a value was then selected from a calendar and the tab key was hit. This was caused by a 'done' setting not being properly attached to an empty field, and has been fixed.

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