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-A5746 · Issue 213321

Ensured DateTime maintains read-only state when used with editable dates

Resolved in Pega Version 7.2

In a DateTime control with a read-only format set differently from an editable date format, the read-only format was being set to an editable date format when other fields were refreshed. This was an issue with calling the API, and has been corrected.

SR-A5815 · Issue 213981

Ensured validation messages display properly with changed inheritance

Resolved in Pega Version 7.2

After upgrade, changing inheritance from Work- to Work-Cover- caused validation messages to be cleared from the screen on press of a button. This was traced to the NewAction parameter in the Work-Cover-.ActionSection HTML rule causing the system to treat the action request as new and not display the error messages, and has been corrected by adding conditions to properly display errors found on the step page/primary page.

SR-A6069 · Issue 215077

Expanded debug information generated by pzUpdateElementModel

Resolved in Pega Version 7.2

The error message generated by pzUpdateElementModel has been updated to log more complete debugging information on the exception in the oLog.

SR-A6227 · Issue 217784

Fixed logic for property as dynamic label

Resolved in Pega Version 7.2

Property reference is visible instead of property value. User is When using a property as label to show dynamic labels, the property reference was visible instead of the expected property value. This was traced to a logic flaw during the markup generation for the 'GenerateCellContent' RUF, and has been corrected.

SR-A3064 · Issue 218100

Form submit disabled while Action List is processing

Resolved in Pega Version 7.2

When an Action List was being processed in response to a user action, there was no way, using out-of-the-box tools, to prevent the user from clicking on the Submit button while the process is running. This additional click or enter could cause a change in the transaction ID, which then caused incorrect data to be used in the assignment. In order to ensure the proper calculations are run, logic has been added such that once the action list processing has been fired, the buttons in the section are disabled until everything on the action list has completed.

SR-A8231 · Issue 218303

Form submit disabled while Action List is processing

Resolved in Pega Version 7.2

When an Action List was being processed in response to a user action, there was no way, using out-of-the-box tools, to prevent the user from clicking on the Submit button while the process is running. This additional click or enter could cause a change in the transaction ID, which then caused incorrect data to be used in the assignment. In order to ensure the proper calculations are run, logic has been added such that once the action list processing has been fired, the buttons in the section are disabled until everything on the action list has completed.

SR-A3064 · Issue 215647

Form submit disabled while Action List is processing

Resolved in Pega Version 7.2

When an Action List was being processed in response to a user action, there was no way, using out-of-the-box tools, to prevent the user from clicking on the Submit button while the process is running. This additional click or enter could cause a change in the transaction ID, which then caused incorrect data to be used in the assignment. In order to ensure the proper calculations are run, logic has been added such that once the action list processing has been fired, the buttons in the section are disabled until everything on the action list has completed.

SR-A4799 · Issue 213996

Frame resize resolved for SFDC Process Extender Bulk Processing

Resolved in Pega Version 7.2

The list and flow actions frames were not resizing properly in SFDC Process Extender Bulk Processing. This was caused by an 'access denied' error thrown if the top frame is not a PRPC frame, and the frameset method has been updated with a check to handle this issue.

SR-A5821 · Issue 214777

Included sections now added as referenced rules

Resolved in Pega Version 7.2

When including one section in another section with the page context as "Use clipboard page", the included section was not being correctly added to the pxRuleReferences page list when the embedded Page property of the section class was set as the using page. RUF pzValidateSectionIncludes has now been modified to consider the embedded Page property of the section class while adding the section in referencing rules.

SR-A1408 · Issue 206581

Localization added for @baseclass field values on iPad Fat Lists

Resolved in Pega Version 7.2

When using localized field values in the Fat List mode on an iPad, the RUF GenerateCellContent wasn't localizing the value but instead directly displayed the pyValue (i.e. the value entered for Value under Cell properties). This was due to the data-attribute-name not being localized for field values created only at @baseclass, and has been resolved.

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