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-131162 · Issue 201045

Corrected inheritance for Data classes

Resolved in Pega Version 7.1.8

After migration, an API used to pull the list of concrete classes from RootClass Work- was pulling an additional class (Data-Portal-Padportal) when work- was supplied as an argument for rootclass. This additional class caused issues with reports due to it pointing to pr_history_data table and looking for non-existent columns. These inheritance issues have now been corrected.

SR-131162 · Issue 201046

Corrected inheritance for Data classes

Resolved in Pega Version 7.1.8

After migration, an API used to pull the list of concrete classes from RootClass Work- was pulling an additional class (Data-Portal-Padportal) when work- was supplied as an argument for rootclass. This additional class caused issues with reports due to it pointing to pr_history_data table and looking for non-existent columns. These inheritance issues have now been corrected.

SR-129062 · Issue 194086

App Explorer enhancement sets number of properties displayed

Resolved in Pega Version 7.1.8

If there were a large number of properties in a navigation panel of App Explorer, only a few properties were shown and a link displayed 'Show all results'. It was then not possible to optimize a property inside a page list in Work Class as it was displayed under new tab when 'Show all results' was clicked. This was found to be an issue with the behavior of Property Optimization wizard being different when it is launched from App Explorer menu than from when it is launched from RuleForm-->Actions menu. The system now provides an extension point for clients to increase the number of properties that appear in the App explorer. The default is 100, with a max cap of 10000.

SR-129062 · Issue 195029

App Explorer enhancement sets number of properties displayed

Resolved in Pega Version 7.1.8

If there were a large number of properties in a navigation panel of App Explorer, only a few properties were shown and a link displayed 'Show all results'. It was then not possible to optimize a property inside a page list in Work Class as it was displayed under new tab when 'Show all results' was clicked. This was found to be an issue with the behavior of Property Optimization wizard being different when it is launched from App Explorer menu than from when it is launched from RuleForm-->Actions menu. The system now provides an extension point for clients to increase the number of properties that appear in the App explorer. The default is 100, with a max cap of 10000.

SR-129291 · Issue 201471

Added ability to configure node cluster timeouts

Resolved in Pega Version 7.1.8

If a cluster has many nodes, all nodes starting at the same time ended up contending for lock and throwing an exception if they timed out. When the cluster starts, none of the nodes have yet registered their cluster address in pr_sys_statusnodes. There is code that guards against a race condition and includes locking with a timeout controlled by the waitTime (set to 2000ms) and the number of attempts (set to 30) for a total of 1 minute. However, a large number of nodes contending for this lock could exceed these limits. In order to avoid this, the timeout for the lock during check cluster consistency is now configurable using "cluster/consistency/lockattemptdelayms" and "cluster/consistency/maxlockattempts". Additional tuning on this locking is anticipated to be included in ML9.

SR-129291 · Issue 201670

Added ability to configure node cluster timeouts

Resolved in Pega Version 7.1.8

If a cluster has many nodes, all nodes starting at the same time ended up contending for lock and throwing an exception if they timed out. When the cluster starts, none of the nodes have yet registered their cluster address in pr_sys_statusnodes. There is code that guards against a race condition and includes locking with a timeout controlled by the waitTime (set to 2000ms) and the number of attempts (set to 30) for a total of 1 minute. However, a large number of nodes contending for this lock could exceed these limits. In order to avoid this, the timeout for the lock during check cluster consistency is now configurable using "cluster/consistency/lockattemptdelayms" and "cluster/consistency/maxlockattempts". Additional tuning on this locking is anticipated to be included in ML9.

SR-126986 · Issue 197102

Added class handling for creation of embedded pages with page-new method

Resolved in Pega Version 7.1.8

After upgrade, an error was generated while using page-new method to create a new page unless the default page class was present. This occurred when an embedded property was created using page-new with a class that is a child class of the defined embedded class and the parent property of that embedded property was auto-populate/special-java. This was caused by the class being different than the defined embedded class, meaning it was considered as a change to pxObjClass (which is not allowed) and it was not handled. To resolve this, a check has been added to set the right class when creating a embedded page by page-new, using the class of the input page when setting value of a embedded property instead of the defined class if present in input page.

SR-127035 · Issue 193206

Improved opening custom flow rules with Microsoft Internet Explorer 9

Resolved in Pega Version 7.1.8

Opening up a flow rule with many sub-process references was taking an excessive amount of time when using Microsoft Internet Explorer 9 due to general browser slowness and the system loading all referenced flow rules at that time. This has been resolved by tuning the JavaScript code to improve the performance of the viewer and to disable drilldown functionality from the server.

SR-127039 · Issue 190388

Resolved error with Obj-Refresh-And-Lock Method for results browse

Resolved in Pega Version 7.1.8

If the useLightweight List checkbox was checked when trying to do an obj-browse, Obj-Refresh-And-Lock method was generating an error. This was an issue with the virtual clipboard, and has been resolved.

SR-127091 · Issue 193209

Forward chaining commit error resolved

Resolved in Pega Version 7.1.8

A sporadic pyCommitError was observed when performing 'Action' during a 'Phone call' interaction for a specific user. During forward chaining, a malformed variable change that occurs when a page copy happens on a embedded page of a work page is recreated in order to not corrupt the fragment collection cache. Previously, this was done only while evaluating the declare expressions. The system has now been updated to do the same during evaluation of other declarative flavors during forward chaining.

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