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-C24478 · Issue 353695

BIX files generated with unique id

Resolved in Pega Version 8.1

BIX extraction files were overwritten when the same extract was run the next day. This was due to duplicate filenames, and the system has been modified to add the date the the zip file name, ex. BIX_classname_runID_date_squencenumber, to ensure it is unique.

SR-C24478 · Issue 365059

BIX files generated with unique id

Resolved in Pega Version 8.1

BIX extraction files were overwritten when the same extract was run the next day. This was due to duplicate filenames, and the system has been modified to add the date the the zip file name, ex. BIX_classname_runID_date_squencenumber, to ensure it is unique.

SR-C24537 · Issue 367642

Guardrail updated to redirect 'When filter' to 'listview filter' in product rules

Resolved in Pega Version 8.1

The 'When' rule is deprecated on product rules and can cause issues if used. To clarify this and create more helpful guardrail messages, the following warning message has been added to situation where the 'when filter' is used in the Class instances to include section:"Using when rule filter is deprecated. Instead use list view filter."

SR-C24834 · Issue 368176

SOAP attachment resolved and additional Apache updates made

Resolved in Pega Version 8.1

An error was encountered when attempting to attach a file using SOAP service invoked from the SOAP UI. This has been fixed by changing the type of configuration used for the process. In addition, Apache-mime4j-core has been updated to v0.8.1 and Apache POI has been upgraded to v3.17.

SR-C24834 · Issue 373044

Multiple Universal SMA fixes made

Resolved in Pega Version 8.1

The following issues in Universal SMA have been fixed:1) “STOP” button not working in Sys Queue Mgmt 2) ClassCastException appearing in Requestor Mgmt 3) Mbean Exception being generated for “Rebuild Classmap" 4) Agent Mgmt Runnable icon always shows X, and Agents were not starting 5) "Get Rule detail" was not working 6) API not found, java.lang.NoSuchMethodException

SR-C24834 · Issue 367704

Multiple Universal SMA fixes made

Resolved in Pega Version 8.1

The following issues in Universal SMA have been fixed:1) “STOP” button not working in Sys Queue Mgmt 2) ClassCastException appearing in Requestor Mgmt 3) Mbean Exception being generated for “Rebuild Classmap" 4) Agent Mgmt Runnable icon always shows X, and Agents were not starting 5) "Get Rule detail" was not working 6) API not found, java.lang.NoSuchMethodException

SR-C24834 · Issue 367706

Multiple Universal SMA fixes made

Resolved in Pega Version 8.1

The following issues in Universal SMA have been fixed:1) “STOP” button not working in Sys Queue Mgmt 2) ClassCastException appearing in Requestor Mgmt 3) Mbean Exception being generated for “Rebuild Classmap" 4) Agent Mgmt Runnable icon always shows X, and Agents were not starting 5) "Get Rule detail" was not working 6) API not found, java.lang.NoSuchMethodException

SR-C25043 · Issue 367314

Corrected displayed records for DT show complete

Resolved in Pega Version 8.1

When @equalsIgnoreCase(, somepropvalue) was used in a column header, clicking on the the Decision table's option "Show Completeness" was displaying all the combinations of each cell value with "<" and ">" appended. This was due to a code fragment left from a logic revision and has been removed.

SR-C25043 · Issue 367544

Corrected displayed records for DT show complete

Resolved in Pega Version 8.1

When @equalsIgnoreCase(, somepropvalue) was used in a column header, clicking on the the Decision table's option "Show Completeness" was displaying all the combinations of each cell value with "<" and ">" appended. This was due to a code fragment left from a logic revision and has been removed.

SR-C25092 · Issue 366511

Fixed proposition status calculation by removing stale calendar object

Resolved in Pega Version 8.1

The status of a proposition was not getting calculated correctly due to the class Calendar object being static. Once it was cached it was being used for all the propositions for the entire server session until next server restart. To correct this, the calendar object has been removed as static final and the time zone object has been made static final.

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