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-B37115 · Issue 286705

PegaUnits bulk testing updated

Resolved in Pega Version 7.3

AUT test cases were failing while running in bulk, though running a single unit worked as expected. This was found to be a conflict with the way a test case uses a current parameter page from the start of execution to end of execution and then passes it to the next test; if there are two data page test cases where one is configured to have a non-blank value for a given parameter while the second one has a blank value for same parameter, the second test unexpectedly encounters the non-blank value. To resolve this, the code has been modified to reset the value of only RUT params before set up is called, so that every test case behaves truly independently.

SR-B38034 · Issue 297014

Improved error handling for Usage Daemon

Resolved in Pega Version 7.3

The Usage daemon was exiting due to DB error and did not recover, leading to PALSnapshotImpl multiplying and causing an OOM. This was traced to missing error handling, and UsageDaemon has now been updated to handle a DB error without exiting.

SR-B38157 · Issue 301486

Added post-upgrade compatibility for agent tracing

Resolved in Pega Version 7.3

After upgrade, tracing agents was not working due to a change between versions in the method of tracing rules in rulesets of a remote requestor. Previously, rules were traced in the rulesets of the current requestor who initiated the trace; in newer versions, rulesets are fetched for batch requestors so all rules in rulesets accessible to browser requestor are not traced. In order to resolve this, a traceAllRulesets flag has been added for agent tracing so that all rulesets are traced and a note has been added to the settings window stating that in case of agents, all rulesets are traced.

SR-B38248 · Issue 293250

Rule search works after indexer cancel

Resolved in Pega Version 7.3

If the indexer was canceled from within the engine, the rule search function would not work until node restart. This was an error in the method used to call the cancel API, and has been corrected.

SR-B38330 · Issue 297411

Added code to ensure cursor closes on null-pointer exception

Resolved in Pega Version 7.3

Open cursor issues were occurring with out-of-the-box queries.SPPR_SYS_RESERVEQUEUEITEM_B Stored Proc when an exception was raised. Code has been added to ensure the cursor is closed in this situation.

SR-B38578 · Issue 295917

Fixed null-pointer exception in external DB extract

Resolved in Pega Version 7.3

When using a class which maps to a table in an external database, running an extract caused a database permission error when trying to access the pr_log table in the PegaRULES database. This exception was caught and logged but then processing continued, resulting in a NullPointerException being thrown. To correct this, the sequence number generator has been modified to use the pr_log table instead of the class on which extract is defined.

SR-B38578 · Issue 272419

Fixed null-pointer exception in external DB extract

Resolved in Pega Version 7.3

When using a class which maps to a table in an external database, running an extract caused a database permission error when trying to access the pr_log table in the PegaRULES database. This exception was caught and logged but then processing continued, resulting in a NullPointerException being thrown. To correct this, the sequence number generator has been modified to use the pr_log table instead of the class on which extract is defined.

SR-B39476 · Issue 297525

addCalendar() RUF logic updated

Resolved in Pega Version 7.3

The addCalendar() RUF logic has been modified to correctly set the operator time zone and correctly add the given years, months, days etc. This fix will be active based on a DASS setting as addCalendar() cannot be directly changed due to backward compatibility with DateTime issues.

SR-B39528 · Issue 303927

Node startup modified to support very large clusters

Resolved in Pega Version 7.3

Node startup was failing if the cluster had more than 50 nodes. This issue was caused by the query to the "pr_sys_statusnodes" table only returning 50 records; this limitation has been removed.

SR-B40706 · Issue 297501

Unmapped columns from an external table skipped in DDL query generation.

Resolved in Pega Version 7.3

The OBJ-SAVE method was generating a query in which unmapped columns were also getting updated. As these columns were not mapped, DB columns were being updated with the value NULL. This was due to the Obj-Save function always saving the entire object, causing an issue when only part of a table is mapped to a class. To correct this, new prconfig and DASS settings have been added to exclude unmapped columns of an external table as part of DDL query generation.

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