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-C51065 · Issue 390587

Corrected unexpected date error for imported propositions

Resolved in Pega Version 8.1

While importing a proposition with a specific start date and end date, even though the start and end dates are valid the error: "Start date should be prior to end date" appeared. This has been corrected with code that will convert the start and end dates before comparing them in pyPostCSVUpload activity.

SR-C51065 · Issue 390653

Corrected unexpected date error for imported propositions

Resolved in Pega Version 8.1

While importing a proposition with a specific start date and end date, even though the start and end dates are valid the error: "Start date should be prior to end date" appeared. This has been corrected with code that will convert the start and end dates before comparing them in pyPostCSVUpload activity.

SR-C51371 · Issue 391235

Removed cluster notification executed by the VBD client on start/stop

Resolved in Pega Version 8.1

A cluster notification executed by the VBD client on start/stop can put unnecessary pressure on the Hazelcast cluster executor during node restarts. The system has now been modified to remove the loop during the cluster scan.

SR-C51670 · Issue 390540

Delta sync handling updated for cases in multiple workpools

Resolved in Pega Version 8.1

When trying to open work item in mobile offline mode, cases that belonged to multiple workpools were causing delta sync issues. During deltasync, the system tries to package the work items and ASSIGN- by check running pzGetWorkObjDataFromAssignment RD. However, this RD runs only in the context of the current workgroup name set on the pxThread page. To correct this, the system will get all of the workpools from the worklist item page's pxRefObjKey and run the RD on each workpool to return the proper results.

SR-C5169 · Issue 349818

Tabs maintain state when new RDL item added

Resolved in Pega Version 8.1

Adding a new item to a repeating Dynamic layout switched all the currently selected tabs in an embedded Tab Layout Group to be the same as the last item. This was an issue with complex configuration RDL having another repeating layout (DLG) with an active 'when' based on repeating context property, and code has been added to handle the previous selected tab state and active when so tabs will retain integrity.

SR-C51948 · Issue 390951

ZipFileListOnServer activity modified to only create instances for zip files

Resolved in Pega Version 8.1

When the Hotfix Manager was run on the ServiceExport directory, the Next and Cancel buttons did not render. Analysis showed the system was creating the PRFile instance for all of the files from the directory, and an exception was being thrown when am instance was created for a file that had illegal characters in its name. To correct this, the pzZipFileListOnServer activity has been modified to only create the instances for files which start with "dl-" and end with ".zip".

SR-C5215 · Issue 357353

Added code to support Sybase DBs in report definition

Resolved in Pega Version 8.1

Running a report definition that is connected to a Sybase DB produced no results in the report browser. This was an issue with the column delimiter not working for Sybase; to resolve this, the code has been modified to rely on the database type rather than the getColumnDelimiter method.

SR-C5234 · Issue 360596

openIfStale() AP updated to ensure aUnlockOnCommit flag is honored

Resolved in Pega Version 8.1

Resolve- Pega-ProcessEngine:07-10-26 (Final out-of-the-box) was acquiring a lock on case but not releasing it later due to Opener not properly honoring the aUnlockOnCommit flag that was passed in via the openIfStale() API. This meant the the database value was always taking precedence over the passed-in flag. To correct this, the openIfStale API has been updated to remove a problematic "else" case. In addition, the system will check whether the lock is available in the map already: if it is, it will set unlockOnCommit to true, or otherwise, under all cases, honor the passed-in unlockOnCommit value.

SR-C53091 · Issue 391230

AddOnly bulk import correctly does not check for existing records

Resolved in Pega Version 8.1

When doing an extremely large bulk import using Addonly, the import API code was performing an existing record check when mapping pagelist properties. This was not the expected behavior, and has been corrected by updating the import java code.

SR-C5318 · Issue 388898

Silverlight digital signature updated

Resolved in Pega Version 8.1

Silverlight Prerequisites have been updated with the latest digital signature.

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