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-A11690 · Issue 234461

Filtering added for bulk workbaskets

Resolved in Pega Version 7.2.1

Workbasket filtration has been added for bulk actions workbaskets.

SR-A11817 · Issue 233321

Skim_Validate rule made available

Resolved in Pega Version 7.2.1

In order to resolve issues with Offer flow rules not being moved after skimming the ruleset, a new version of Skim_Validate was added to Rule-Obj-Flow-Offer, deleting all steps except for the call to Rule-.Skim_Validate. To make this function fully available, Skim_Validate has now been marked as available to allow extending the activity to a rule form.

SR-A13926 · Issue 230498

Resolved invalid page causing missing bulk items

Resolved in Pega Version 7.2.1

When trying to perform bulk transfer, some of the work objects were sporadically not displayed in the bulk processing list. This was caused by an invalid page getting passed while invoking checkActionWhens to act on the 'when' for showing the assignments list. The proper page is now set by updating the GETBULKPROCESSCONTENT activity to set pxRefObjectKey to the assignment page while invoking checkActionWhens.

SR-A14004 · Issue 231765

Flow designer XML fixed when using copy/paste

Resolved in Pega Version 7.2.1

Copy and paste are available in the Flow Designer, but tickets where the End shape was copy/pasted and a new ticket set created for the new End shape resulted in incorrect XML. To correct this, the flowmethodbody function will use pyTicketShapes instead of pyModifierRefs for java generation.

SR-A14106 · Issue 227981

Improved sender handling for custom email activities

Resolved in Pega Version 7.2.1

A custom email related activity was producing an authentication exception due to an attempted call to a User ID stored in Param.FromUsername made after that parameter was cleared by SendEmailNotification. To avoid this, if Param.FromUsername is blank, it will be set to the value of Param.AccountID.

SR-A14168 · Issue 230039

Unique page names generated for nested child work items

Resolved in Pega Version 7.2.1

When multiple child work items were created using pxAddChildWork in one transaction, the same page name was getting used and causing errors. This has been fixed by making pagename unique by appending currentdatetime.

SR-A14403 · Issue 230497

Confirmation Message no longer appearing twice in confirm harness

Resolved in Pega Version 7.2.1

When the out-of-the-box pyWorkConfirmMessage section is included in an application and displayed in one of the steps while running the application, the pyWorkConfirmMessage section will display pyConfirmationNote property value of the work object present in pyWorkPage and will also display the pyConfirmationNote value defined at assignment level present in pxFlow page. This was traced to an additional call step in the function, and the handling has been modified to produce the expected results.

SR-A15013 · Issue 233710

Localization added to AddCoveredWork InsAudit

Resolved in Pega Version 7.2.1

Localization has been added to param.InsAudit in the Pega Final activity AddCoveredWork.

SR-A15491 · Issue 231066

Access control added for duplicate work baskets

Resolved in Pega Version 7.2.1

out-of-the-box functionality allows a user to add duplicate workbaskets to all users. An option has now been added to set restrictions on this ability: the 'when' rule "PYHAVEWORKBASKETSEDITACCESS" can be used to control access to the ability to add or modify the workbaskets as desired. In addition, a validation check will be performed on any duplicate entry of WorkBaskets for an operator.

SR-A15491 · Issue 231387

Access control added for duplicate work baskets

Resolved in Pega Version 7.2.1

out-of-the-box functionality allows a user to add duplicate workbaskets to all users. An option has now been added to set restrictions on this ability: the 'when' rule "PYHAVEWORKBASKETSEDITACCESS" can be used to control access to the ability to add or modify the workbaskets as desired. In addition, a validation check will be performed on any duplicate entry of WorkBaskets for an operator.

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