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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-127385 · Issue 235813

Fixed user authorization filtering error in extracts

Resolved in Pega Version 7.2.1

Extraction was failing sporadically due to the filter condition not being picked up by all the extract rules when running BIX. This was due to an error in authorizing the requestor with username/password causing differences in datetime formats, and has been fixed.

SR-129197 · Issue 197995

Fixed Silverlight "Create Word Document" error

Resolved in Pega Version 7.2.1

A Silverlight issue appeared while using "Create word document". The older flow action CreateMergedWordDoc was running on the Current Page Context and had a reference to the Word Template used in the PegaSample application. To resolve this, the new Flow Action 'pyCreateWordDocumentCMGallery' has been created. This runs on the pyFlowActionTestPage page and uses the new Word Template pyCMTemplate which has limited set of related properties.

SR-A10491 · Issue 234174

Locking corrected for WebLogic BMT transactions

Resolved in Pega Version 7.2.1

Incomplete locking for WebLogic BMT transactions caused work items in the queue to be processed by duplicate agents even though the item was already processed. This has been fixed.

SR-A10653 · Issue 236942

Fixed NPE in the Connector and Metadata wizard

Resolved in Pega Version 7.2.1

The Connector and Metadata wizard was throwing a NPE in logs due to the inability to resolve a header schema definition during import. To fix this, the system will skip the unresolved header mapping processing and log an error message instead of creating an empty entry.

SR-A11534 · Issue 227038

ExecuteSLA activity modified to avoid requeue errors

Resolved in Pega Version 7.2.1

When a broken process SLA was requeued, it went back into the broken queue because the underlying problem assignment was never marked as repaired on requeue. When execution of SLA fails, the assignments are marked as problem assignments in ExecuteSLA activity. The ExecuteSLA activity has now been changed to avoid creating a assignment error by instead using Obj-Cancel to roll back the assignment submission so items can be requeued directly from the SMA portal.

SR-A11665 · Issue 229766

Fixed Bulk Process deselecting some sorted items

Resolved in Pega Version 7.2.1

In Internet Explorer using Bulk Processing, after selecting a column to re-order and several individual items resulted in unexpected checkbox results where certain selected items were deselected and not processed. These items could later be processed individually. The logic has been updated to ensure proper checkbox handling with all browsers.

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-A11695 · Issue 229147

EXCEPTION_BLACKOUT time calculation fixed

Resolved in Pega Version 7.2.1

When calculating the time for the EXCEPTION_BLACKOUT period in EmailListener, the dimensions were incorrect due to errors in the sleep time observed when email listener failed to establish connection. This has been fixed.

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-A12342 · Issue 226223

Standard System Usage Summary report updated with Daily Usage Table

Resolved in Pega Version 7.2.1

When the Standard System Usage Summary report was run, no users were shown even though users were able to access the system. The Hourly and Daily Usage Reports show data collection, but this was not propagated to the Summary report. This was an issue caused by the Summary Report not accepting values from the Daily Usage table, and schema updates have been made to fix this.

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