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-B47227 · Issue 304654

Requirements template sets Excel input cells as text for security

Resolved in Pega Version 7.3

For increased security in Pega Platform Excel files, the Requirements template has been changed to set all the input cell types as text instead of general.

SR-B48146 · Issue 305146

CheckedOutRulesBulk updated with null check

Resolved in Pega Version 7.3

The MyCheckedOutRulesBulk ruleset was taken as null for operators with rule checkout disabled, causing them to see all the non-rule resolved classes as private edits. To correct this, additional criteria have been added to fetch records only with pyClass starting with 'RULE-' and the List views MyCheckedOutRulesBulk and MyCheckedOutRulesBulkPM have been changed to check for null values.

SR-B6428 · Issue 280748

Bulk process with only 'case type any' properly assigns all processes

Resolved in Pega Version 7.3

When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.

SR-B6770 · Issue 280879

Cleanup improved for embedded page properties

Resolved in Pega Version 7.3

pyPreviousValues was retaining embedded page properties that were no longer used in pyWorkPage, causing the field level auditing to fire and write to the audit history every time the work object was updated. This has been resolved by changing the function rule pzAddHistoryMemoForScalar to remove an embedded page property in pyPreviousValues when the property is removed from pyWorkPage.

SR-B6904 · Issue 278482

Ensure CallVirusCheck is called only after populating data in UploadedFilePage

Resolved in Pega Version 7.3

Pega 7 provides the out-of-the-box extension activity Data-WorkAttach-File.CallVirusCheck which is intended to be customized with virus checking functionality to check the content of uploaded files. However, placing the activity too early in the customized process meant the check would not be correctly performed. To correct this, CallVirusCheck and the subsequent Property-Set-Messages steps have been moved to the end of the @baseclass.pzFileUploadGadget activity to ensure the existing java step populates file information on the UploadedFilePage and makes it available for the CallVirusCheck activity.

SR-B7355 · Issue 277915

Actions visible in Perform harness for cases without active assignments

Resolved in Pega Version 7.3

When a stage configured with SLA did not have any active assignments, local actions could be launched from the Review harness but were not visible in the Perform harness. This was caused by the handling for cases without active assignments: virtual assignments are used to process the stage/case wide local actions, but the name of the virtual assignment page was not set and therefore not available later to fetch the local/flow actions. To resolve this, the assignment page name will be checked and set if it is empty.

SR-B7620 · Issue 290018

PopulateCaseContents activity updated

Resolved in Pega Version 7.3

The PopulateCaseContents activity has been updated to better handle missing or empty properties to ensure the flow name and RefObjectClass values are populated properly.

SR-B7621 · Issue 278634

Activity created cases open correctly

Resolved in Pega Version 7.3

When a case was created through an activity, an error was generated when opening the case and clicking to open assignment. This was traced to an incorrect page name being passed if the primary page was different, and has been resolved by modifying the CompleteAssignment activity Step 19 to check the precondition of Page name.

SR-B8696 · Issue 279855

Support added for FCM GetNextWork

Resolved in Pega Version 7.3

When using Federated case management (FCM) to get next work, the work object pulled was not assigned to the operator. This was due to the implementation of FCMR not supporting the moving of workbasket assignments to worklist through get next work. To support this use, the following functions now accept extra parameters as last param: FCMRGetNextWork FCMRGetNextWorkItem FCMRProbeNextWorkItem This will enable distinguishing between normal GNW and federated GNW, and it is possible to override any py rule call MoveToWorklist.

SR-B9998 · Issue 279141

Improved handling for apostrophe in email addresses

Resolved in Pega Version 7.3

In order to improve mail handling, the system will now only remove the the starting and ending apostrophe in an Email address and will not strip apostrophes in the middle of an address.

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