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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-B95191 · Issue 341933

Conditional Required fields fixed when working with accessibility

Resolved in Pega Version 7.4

When Accessibility is in place, the Conditional Required for fields was not working as expected, instead making the fields always required. To correct this, the tag will be generated conditionally after evaluation of required configuration.

SR-B95701 · Issue 341895

Fixed localized non-operators seeing rule status

Resolved in Pega Version 7.4

A UI discrepancy in the new ruleform creation form led to Rule status dropdown being shown to non-operators who were using localization. This was due to a missing 'when' rule, and has been fixed.

SR-B96109 · Issue 344391

Calendar control fixed for Buddhist dates

Resolved in Pega Version 7.4

The Calendar control was not showing the Buddhist calendar when using the Thai locale (th_TH). This was an inadvertent result of an implementation update in calendar, and has been fixed.

SR-B96378 · Issue 342548

Error importing RAP with Japanese characters fixed

Resolved in Pega Version 7.4

When trying to import a RAP that contained Japanese characters (including application, organization, case type, data type, flow, flow action, property etc.), the preview was fine but the import wizard finished with the message "This archive is empty -- it contains no instances". This was due to a null pointer exception, and has been fixed by ensuring ClassTableMap.properties from the schema.jar will be read with UTF8 when needed.

SR-B97032 · Issue 342812

Target stale check added to cascading dropdowns

Resolved in Pega Version 7.4

The system was hanging when hovering on the drop down after selecting a parameter for which the dropdown did not have any values. This was due to the target element becoming stale when cascaded dropdowns were used, and has been fixed by adding a check for this condition.

SR-B97336 · Issue 343370

Minimized window stays minimized on auto-refresh in Microsoft Internet Explorer

Resolved in Pega Version 7.4

If a section was configured to auto-refresh every 30 seconds, the minimized window would maximize automatically when using the Microsoft Internet Explorer browser. This was caused by the way the focus was being set in Microsoft Internet Explorer9, Microsoft Internet Explorer10, and Microsoft Internet Explorer 11, and has been fixed.

SR-C1026 · Issue 344634

Able to add When condition for DisplayYesNo

Resolved in Pega Version 7.4

An exception was generated when attempting to add 'when' conditions for DisplayYesNo control in Section. The pzActionConditionSource activity was fetching the pyUIElement value from the Primary Page and setting it to UIELement as intended, but when the pyUIElement value is empty, a null-pointer exception occurs. Handling has now been added to avoid this scenario.

SR-C1835 · Issue 346650

Timeline enhancement

Resolved in Pega Version 7.4

An enhancement has been added to the setDefaults API to allow for use of a custom moment function for the out-of-the-box pxTimeline. This can be used to set the Timezone for displaying the events.

SR-C2963 · Issue 347630

Added handling for always show page level errors

Resolved in Pega Version 7.4

Property level errors were shown, but Page level properties were not shown even when the harness field was checked to always show both field level and form level errors. This was due to missing handling for the 'always show' option, which has now been added.

SR-C2963 · Issue 346977

out-of-the-box section Errors shown

Resolved in Pega Version 7.4

After upgrade, error messages were not shown in some scenarios such as lazy loaded layouts in Templatized UI. This was due to missing error handling, 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