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-B71423 · Issue 319981

Localization added to pyAccountSettings field labels

Resolved in Pega Version 7.4

Field label localization for the pyAccountSettings section rule has been added to the Pega-IntegrationArchitect ruleset.

SR-B54277 · Issue 336406

Trimmed unneeded properties from doUIAction call

Resolved in Pega Version 7.4

Null pointer exceptions were generated when relaunching the manager portal after saving a work-object, and the error "Request-URL Too Large. The requested URL's length exceeds the capacity limit for this server" appeared. This was traced to the number of properties included in the doUIAction call; unnecessary parameters have been removed to resolve this issue.

SR-B66164 · Issue 325166

Handling improved for pzActiondropdown's Action label value

Resolved in Pega Version 7.4

When an alternate flow action was picked from LocalAction's list and then submitted, the presence of any page-set messages would cause the submission to fail and the flow remained on the same flow action. This was an issue with handling the changed value of the FlowAction label, and the pzActionDropdown control has been modified to get the correct pyDefaultActionIndex parameter value.

SR-B70422 · Issue 326897

Removed unnecessary add/delete history entries related to empty page properties

Resolved in Pega Version 7.4

The field level auditing configured for page group or list property types was creating multiple add and delete entries in the history of the case even though the pagelist/pagegroup had not been modified. This was traced to method used by the pagelist change audit process to compare current pages to the previous value of the pagelist pages: during pagetostring conversion, sometimes the empty properties in page are present in the String and sometimes they are not, resulting in a difference that generated the non-essential audit entries. This has been fixed by changing the getProperty references in getPageAsString function to use getIfPresent instead. Null checks have also been added.

SR-B70595 · Issue 328754

Out of box REST API creates Page Lists with pxObjClass

Resolved in Pega Version 7.4

Page-Merge-Into was implemented in such a way that the pxObjClass was added for a page but not for a Page List until the case was created. This interfered with validating pagelists and identifying problems with the message data that would allow the case to be rejected before creation. To allow for more flexibility, the pzCreateCaseInternal activity contains an added a property-set so that the pxObjClass is updated on embedded pages.

SR-B74583 · Issue 325617

SendEmail smart shape fixed to populate PartyRole correctly

Resolved in Pega Version 7.4

Due to issues with populating the pxPartyRole property, emails were not being sent to all members in a repeat party after upgrading. This was traced to a missing call in the modified SendEmail smart shape, and has been fixed.

SR-B75096 · Issue 329151

Bulk actions filter clears previous value

Resolved in Pega Version 7.4

When running Bulk Actions, attempting to delete filter conditions was resetting clipboard values and no results were displayed. This was an unintended consequence of changes that retained pyUserIdentifier on the conditions page even when "Assigned to Operator" was not in the filter list. To correct this, it will be removed when pyUsage is not equal to Operator.

SR-B75096 · Issue 329225

Bulk actions filter clears previous value

Resolved in Pega Version 7.4

When running Bulk Actions, attempting to delete filter conditions was resetting clipboard values and no results were displayed. This was an unintended consequence of changes that retained pyUserIdentifier on the conditions page even when "Assigned to Operator" was not in the filter list. To correct this, it will be removed when pyUsage is not equal to Operator.

SR-B78236 · Issue 332447

Add file correctly saves pxCreateOpName

Resolved in Pega Version 7.4

Attaching a file using the out-of-the-box functionality was not saving the pxCreateOpName in the pc_link_attachment table. Only the pxcreateoperator was saved. This was caused by pxCreateOpName being blank for link-attachment on file attach, and has been fixed by setting pxCreateOpName in the Work-AttachFile activity.

SR-B78236 · Issue 328422

Add file correctly saves pxCreateOpName

Resolved in Pega Version 7.4

Attaching a file using the out-of-the-box functionality was not saving the pxCreateOpName in the pc_link_attachment table. Only the pxcreateoperator was saved. This was caused by pxCreateOpName being blank for link-attachment on file attach, and has been fixed by setting pxCreateOpName in the Work-AttachFile activity.

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