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-B64309 · Issue 315889

PDN help properly reflects FlowAnalysis implementation in the Diagram tab

Resolved in Pega Version 7.3.1

The documentation has been updated in the PDN to reflect that the ruleform "Flow Analysis" option is no longer available. The references to this were mistakenly left visible due to a build issue and the help files have now been republished so they match the current implementation of the Flow Analysis option, which is available on the Diagram tab.

SR-B65469 · Issue 330983

Connect-SQL documentation updated to clarify no milliseconds in Oracle TIMESTAMP

Resolved in Pega Version 7.3.1

The documentation for Connect-SQL rules has been updated to clarify that the datetime hint in rdb-save will not store millisecond precision in the TIMESTAMP column type of an Oracle database.

SR-B77020 · Issue 326989

Help file update to clarify Precondition exceptions do not have error handling

Resolved in Pega Version 7.3.1

The rule-/rule-obj-/rule-obj-activity/stepstransition help file documentation has been corrected to indicate the Exception handling does not cover any conditions that might occur in the precondition.

SR-B37334 · Issue 314101

Cleaned up unexpected tooltip

Resolved in Pega Version 7.3.1

Attempting to set automatic input validation of HTML5 forms to be disabled within a Pega-based application by using "Change control settings -> Presentation -> Editable Format- > Type = text" resulted in a tooltip appearing for the field in the desktop. As it is only required for mobile, the system will avoid the same for desktop.

SR-B41092 · Issue 315609

Large Data Page works on repeating layout

Resolved in Pega Version 7.3.1

Using LDPs for Dynamic selects worked as expected in a mobile app, but not when used for a repeating layout in a mobile app or offline. This was traced to an issue when DP with node scope was used; regex to get the actual DP name from hashed version was not working. This has been fixed.

SR-B46212 · Issue 315461

fr_FR localization added for BrowseMultiDD labels

Resolved in Pega Version 7.3.1

French localization has been added to the labels Browse, Subject, Category and File for the pzAttachFileBrowseMultiDD section.

SR-B46588 · Issue 305524

Encoding of "&" fixed for New Document harness launch

Resolved in Pega Version 7.3.1

If the input property contained the "&" character anywhere in the parameter passed to data transform to launch a "New Document" harness, an error was seen on the screen and the logs. This issue was caused by improper partial encoding of the parameter, and has been corrected.

SR-B48649 · Issue 310650

doUIAction revised to work better with frameless Harness

Resolved in Pega Version 7.3.1

When the DynamicContainer used in Harness was frameless, calling workunlock in doUIAction resulted in "Obj-Save" failing and the activity pyWorkPage being deleted. To resolve this, changes were made in the doUIAction activity to skip deleting pyWorkPage if it is a primary page and to skip releasing the lock if the action is 'display harness replace current'.

SR-B51458 · Issue 308564

PegaMarketing localization tuned

Resolved in Pega Version 7.3.1

While localizing the Pega Marketing application, English strings were found in several places from Decisioning in particular, but also in the Platform in general. The localization for these has been fixed.

SR-B52673 · Issue 312131

Focus issue fixed for expanding DL header in Microsoft Internet Explorer 11

Resolved in Pega Version 7.3.1

When the dynamic layout collapsed header was expanded in Microsoft Internet Explorer 11, the focus did not stay on the current dynamic layout but instead went to the top of the section (i.e., the topmost dynamic layout in the section). This issue was caused by Microsoft Internet Explorer 11 firing the focus handler even on the elements which did not have tabIndex, and has been resolved by adding a check for Microsoft Internet Explorer to prevent firing focus on the wrong element.

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