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-B30305 · Issue 288126

Fixed double encoding from Authorize URL scope

Resolved in Pega Version 7.3

If a scope had multiple values in Authentication Profile, then Pega Platform inserted '+' between them in run-time. This was due to the scope parameter value being double-encoded for the Authorize URL, and has been fixed.

SR-B30485 · Issue 287734

Tenant ID check added to Ruleset Wizard for MT

Resolved in Pega Version 7.3

Attempting to deleting a ruleset in a multi-tenant environment using the Ruleset Wizard resulted in the error message 'Getting records from the database' and the application would hang. This was due to a missing tenant ID in the SQL statement, and a check has been added to the query generation to ensure the prepared values for "pzTenantID" are included.

SR-B30914 · Issue 290290

PurgeExtraRecents logging changed from error to info

Resolved in Pega Version 7.3

In order to support increasing the number of recent items to display to more than 30, the existing logging function in System-User-Recents!pzPurgeExtraRecents activity has been changed from error mode to info mode so the logging can be disabled if desired.

SR-B30935 · Issue 289403

CMIS files stored according to application config

Resolved in Pega Version 7.3

Files uploaded to the CMIS repository were being stored in the "Root" Folder of the repository rather than the folder selected in the Application configuration. This was unexpected behavior caused by an implementation error, and has been corrected. The setFolderID in CMISConnector has been refactored in order to stop dropping the Folder ID in the request unless the Folder with that ID cannot be found. The name will be used if the folder ID is not found, and the root folder will only be used as the last resort.

SR-B30962 · Issue 291933

SaveOperatorUnavailability error message made generic

Resolved in Pega Version 7.3

Data-Admin-Operator-ID.SaveOperatorUnavailability generates the error message ("You are not authorized to create, modify, or lock operator instance "+myStepPage.getString("pyUserIdentifier")); if the request is not sent with the proper privileges. In order to obscure what the privileges are from potentially malicious use, this message has been made more general with the text "You are not authorized for this operation".

SR-B31094 · Issue 288810

Removed uppercase shift from GetColumnInfo and ValidateDBTable

Resolved in Pega Version 7.3

The Connector wizard was failing against external Sybase DBs due to the schema name being sent uppercase. This has been resolved by updating the activities GetColumnInfo and ValidateDBTable to remove the code that converts the names to uppercase.

SR-B31524 · Issue 293666

File Listener help updated to clarify duplicate checking

Resolved in Pega Version 7.3

The help file for File Listener has been update to clarify that the duplicate checking from 'Ignore duplicate file names' will be across ALL listeners once the file name has been processed by one listener. The duplicate is flagged for ANY listener processing the file

SR-B31631 · Issue 289775

Installation documentation updated re: postgis use

Resolved in Pega Version 7.3

To avoid confusion, the documentation for the installation process has been explicitly updated to indicate that data and rules schema cannot have postgis extension applied.

SR-B31667 · Issue 289067

Consistent Work IDs between case types created in different implementations

Resolved in Pega Version 7.3

Creating an Implementation layer on the Warranty application using the New Application wizard of Pega 7.22 GA was resulting in a different Work ID prefix of some case types like Claim Unit or Appeal than when the same case types were created in the built on application. This was traced to different activities being used to populate the data page, and has been updated to ensure uniform work ID generation.

SR-B3208 · Issue 293911

Check added to ensure Tracer finds regular pages

Resolved in Pega Version 7.3

Page D_Properties was mentioned in pages to trace, it was present in clipboard, but was not passed to tracer due to an error in page handing. An extra check has been added as a fallback to look for a regular page if Tracer's data page check does not return a named page.

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