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-A3873 · Issue 208346

Next run in agent schedule updates after DB access issue

Resolved in Pega Version 7.1.9

It was discovered that if access to the database was interrupted, the Next run in agent schedule was not updating and not being run. This has been fixed by updating AgentQueue.handleProblem() to handle unexpected errors and ensure delayDueToProblem() is invoked always.

SR-A4279 · Issue 210830

Added handling for unknown UpdateDateType property

Resolved in Pega Version 7.1.9

Saving a Flow stream triggers the pzTrackChangesForFlow activity call, which then reads the pxUpdateDateTime property and converts it to Big Decimal for comparison. This conversion requires mode of the property (i.e. DateTime (?M?) in this case) to be known, which is specified in blob as encoded format. When using a PCI framework where the mode of the pxUpdateDateTime property is unknown(???), a NumberFormatException was generated. This has been fixed.

SR-A469 · Issue 210020

Reworked config file search to prevent WebSphere looping

Resolved in Pega Version 7.1.9

During server startup, the engine tries to populate the environment properties by reading the config files for the application server. A problem was found in some installations with WebSphere where trying to locate the XML file containing the information on the server port created an infinite loop that caused the engine startup to hang. To resolve this, the search function call now has been replaced by another method that tries to obtain the same information from config service without having to locate the XML file.

SR-A903 · Issue 204609

Removed primary page requirement for link-object activity

Resolved in Pega Version 7.1.9

When using the link-object activity method with the history checkmark and the specified step page without providing a primary page, the link-object activity method caused a null-pointer-exception when it attempted to fetch data from the pxRequestor page. This was caused by an unnecessary reference to the primary page, and the method to retrieve the value of pyUserIdentifier has been updated.

SR-A92 · Issue 203202

Removed extra slash character being appended in prconfig

Resolved in Pega Version 7.1.9

When configuring prconfig settings, an extra slash was getting appended when the sethtmlbasecontext had trailing slash in the URL. This has been corrected.

SR-A955 · Issue 204118

Fixed typo in error message

Resolved in Pega Version 7.1.9

A typo in an HA status message written to the log has been corrected.

SR-A1273 · Issue 197681

PRPCTask is now tenantized

Resolved in Pega Version 7.1.9

On a multi-tenant environment with HTTP event, it was not possible to see the options for warm\blind transfer with interaction from a tenant layer. This was an issue with the task taking the user ID information but not taking the tenant information, so the acceptance of the interaction on the portal was not getting delivered to the desktop. To correct this, PRPCTask is now tenantized.

SR-A3149 · Issue 209034

Added handling for Oracle functional indexes of length '1'

Resolved in Pega Version 7.1.9

The SchemaChangeUtils class was throwing a java.lang.StringIndexOutOfBoundsException when an administrator attempted to view the "Missing PRPC Shipped Schema" section of the "PRPC Schema Report" page after upgrade (System -> Release -> Upgrade -> PRPC Schema Report). This appeared to lead to the message "Can not render section" in the PRPC schema report UI. The StringIndexOutOfBoundsException was due to Oracle functional indexes of length '1' which were not handled while doing a substring in schemaChangeUtils class: this handling has now been added.

SR-A34 · Issue 204505

Pega Lookup JSP tag correctly retrieves Chinese characters

Resolved in Pega Version 7.1.9

When the pega:lookup JSP tag did a field value lookup on pyCaption to retrieve the field value consistent with the locale, any Chinese characters embedded in the HTML pages used to generate the PDF rendered correctly but '?????' appeared in the PDF content instead of the Chinese characters configured in the Field-Value pair. This was caused by an issue in the code which caused the system to incorrectly identify NVARCHAR columns as being VARCHAR columns. This has been fixed., and the encoding for TestDatabaseNew has also been set to be UTF-8 to ensure the Non-ASCII characters in the tests are handled properly in all workspaces.

SR-A3428 · Issue 212424

Modified ClassName pass method for external DBs

Resolved in Pega Version 7.1.9

When DB2 is used as external DB (external table has a date column) and PRPC is hosted on a DB other than DB2, performing an obj-save into an external DB2 database failed with an SQL error. This issue occurred when a class was mapped to a table in an external DB which was not same as Pega hosting DB. In class PageDatabaseMapperImpl.java , function getDatabaseTypeFromEngine is used to check the database type when column type is Date, but the function was using a hardcoded value of class to determine the database type. This has been changed to pass className as parameter and use it to determine database type.

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