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.

INC-148154 · Issue 602921

Hot Fix Manager updated to use installation order for schema import

Resolved in Pega Version 8.3.5

Schema changes were not being imported during the hot fix manager DL import process. Investigation showed this was due to hotfixes in the DL being iterated over from newest to oldest, causing older hotfixes to replace the value added to a map by the newer. To resolve this, the system has been updated to use hotfix install order, which considers selected and dependent hotfixes, rather than ordering newest to oldest. This ensures that newer table representations will override older rather than the other way around.

SR-A11447 · Issue 243018

Importing an archive no longer fails when using DynaTrace

Resolved in Pega Version 7.2.1

Importing an archive was failing when using the third party program DynaTrace. This was due to passivation during the import process, and the system has been modified to prevent this.

SR-A14359 · Issue 232227

Context-aware paths for SMA jmxclient.css and global.js files

Resolved in Pega Version 7.2.1

In some cases the jmxclient.css and global.js files were not found when running SMA due to the use of relative path names. The path names have now been made context-aware.

SR-A15710 · Issue 236472

Additional logging added to diagnose stale thread errors

Resolved in Pega Version 7.2.1

In order to better diagnose issues with stale threads, loggers have been added to the ThreadData class to capture and print any stack trace which is causing the thread to be cleared or destroyed. These loggers will only be printed whenever a stale thread error is thrown in order to maximize log space.

SR-A15710 · Issue 236472

Improved BIX extract handling for multiple active agents

Resolved in Pega Version 7.2.1

When multiple agents were scheduled to run extracts at the same time by utilizing pxExtractDataWithArgs, there was intermittent failure in creating the manifest files. The BIX log would not contain an entry for the files being created, no error was displayed, and agents sometimes needed to be restarted. This was an issue with incomplete extraction of the output data and manifest files due to the PAL timer overriding the current thread context as it handled each of the multiple calls. To resolve this, the previous static variables used to store thread and requester instances have been made private to ensure reliability when handling parallel extracts and simultaneous runs.

SR-A16337 · Issue 232778

OCXinstaller install.bat script for Windows explicitly sets .cab file path

Resolved in Pega Version 7.2.1

The OCXinstaller install.bat script for Windows failed if it was run from the command line in a directory other than the one the script was stored in. The root cause was the batch file not finding the actual .cab files, as the batch file assumes the cab files are in the current path. The install.bat file has been updated to always uses the path of the batch file as the current path.

SR-A16582 · Issue 233320

Improved BIX extract handling for multiple active agents

Resolved in Pega Version 7.2.1

When multiple agents were scheduled to run extracts at the same time by utilizing pxExtractDataWithArgs, there was intermittent failure in creating the manifest files. The BIX log would not contain an entry for the files being created, no error was displayed, and agents sometimes needed to be restarted. This was an issue with incomplete extraction of the output data and manifest files due to the PAL timer overriding the current thread context as it handled each of the multiple calls. To resolve this, the previous static variables used to store thread and requester instances have been made private to ensure reliability when handling parallel extracts and simultaneous runs.

SR-A16736 · Issue 232994

Query table counts updated for IIF file with nulls

Resolved in Pega Version 7.2.1

While importing a jar through Import wizard in Designer Studio for a DB2 database, any Alter queries with SET NOT NULL or SET NULL fired the query 'CALL SYSPROC.ADMIN_CMD' to re-organize the altered table. That query generated the error "The number of host variables in the EXECUTE or OPEN statement is not equal to the number of values required" due to it not including the table names, and this has been fixed by populating the parameters in the place of '?' when downloading the SQL.

SR-A17544 · Issue 236778

Removed pagination size restriction on listview if page size is set

Resolved in Pega Version 7.2.1

When an application had more that 50 data-types, not all data-types were shown in the application packaging wizard due to the page size being set to 50 while the list view function was set to return a maximum of 50 results if pagination was enabled. The pagination size limit on listview has been disabled in cases where page size is set in order to remove this conflict and display the results as expected.

SR-A18100 · Issue 234215

BIX documentation updated for new "-J" timezone conversion option

Resolved in Pega Version 7.2.1

A -J option has been added to BIX to allow the specifying the timezone for datetime properties to be converted to when written to the XML output file. The documentation is as follows: A new command line option J is being added to take in a user specified time zone for e.g., UTC+05:00 format(s); If the specified timezone is not valid, it defaults to GMT example :How to specify this option: "-J" "UTC+5:30"

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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