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-C47868 · Issue 391533

Corrected code error in executeMBeanOperation

Resolved in Pega Version 8.1

An null pointer exception was generated while trying start listeners from executeMBeanOperation. This was due to an error in the code related to String names in ListenerManagementAPI, and has been fixed.

SR-C48072 · Issue 388475

Corrected URL formation problem when using Tomcat

Resolved in Pega Version 8.1

A blank screen was seen when trying to open Decision Table headers, and the color picker pop-up was blank when trying to choose a color for the skin. This was traced to an incorrect URL formed when using Tomcat, caused by the prweb/hash being appended twice in the URL. The root cause was unnecessary decoding of extURL in 'pzDisplayModalDialog' , and this has been fixed by adding the proper urlCrossScriptingFilter.

SR-C48084 · Issue 388816

Repaired Activate Feature in revision management

Resolved in Pega Version 8.1

After creating a revision package jar and importing it into the environment, attempting to Activate the revision to the users resulted in the error message "There are changes from another session. Replaced with latest revision data." This issue was traced to an error in the pyActivateToAll activity from Pega-DecisionManager:07-10-31, and has been fixed.

SR-C48633 · Issue 390528

Missing rules will be inserted into pr4_rule_vw table

Resolved in Pega Version 8.1

On running ExposeCols from prpcutils, if pr4_rule_vw table was truncated or had some rules missing, then the records were not being updated. Logging indicated there were view rules which were present in pr4_rule_vw but not present in the actual class, causing a duplicate key exception when the system tried to insert the same rule again into the pr4_rule_vw table. Previously, ExposeCols functionality always updated the rule record and its corresponding Data-Rule-Summary record but would never insert a new rule or Data-Rule-Summary record. This meant that if the pr4_rule_vw table was truncated before running the column expose, none of the rows were getting updated as the table was empty. To resolve this, if the rule is missing in the pr4_rule_vw table, insert queries will be executed and the rule will be populated in the corresponding Data-Rule-Summary record.

SR-C49089 · Issue 388092

File input handling added to trigger file browsing popup

Resolved in Pega Version 8.1

When the 'Browse' icon received focus in the operator ID rule with tab navigation, pressing the 'Enter' key did not open the file browsing popup. This was due to the Enter event not working with file input, and a check has been added for file input in pzega_ui_events to allow it as an enter key event.

SR-C49089 · Issue 388866

File input handling added to trigger file browsing popup

Resolved in Pega Version 8.1

When the 'Browse' icon received focus in the operator ID rule with tab navigation, pressing the 'Enter' key did not open the file browsing popup. This was due to the Enter event not working with file input, and a check has been added for file input in pzega_ui_events to allow it as an enter key event.

SR-C49097 · Issue 389781

Added missing tooltips for JAWS to read "+" and other buttons in Operator ID and Access Group rules

Resolved in Pega Version 8.1

A few buttons like "+", "Open", etc., were being read by JAWS as unnamed buttons in operator ID and Access Group rules. This was due to missing Tooltips, and has been corrected.

SR-C49124 · Issue 391107

Resolved null stream error on mobile

Resolved in Pega Version 8.1

When clicking on certain events quickly one after another on mobile, the error "Failed to load stream: null" appeared. Analysis showed ActionQueue has timeout logic which unblocks the Queue after 2 seconds. Due to this, the next action in the queue was executed before the first one was done and ended up modifying the variable of the first action. To resolve this, the timeout has been removed and pega.process.engine.ActionQueue.complete(); will be called as required.

SR-C49133 · Issue 387543

Scheduletaskprocessor amended with exit activity to release locking

Resolved in Pega Version 8.1

Scheduled guardrail reports were not emailed, and exception appeared regularly referencing "Error locking scheduled task : PX-ST-1 close scheduling window to release lock." Investigation showed the activity pzscheduledtaskprocessor was lacking an "Exit Activity" condition, and this issue has been resolved by updating the activity step to check for proper activity exit.

SR-C49274 · Issue 388984

Expiry dates displayed in Authentication Service Rule SSO certificate

Resolved in Pega Version 8.1

Inconsistent behavior was seen in the Authentication Service rule SSO certificate expiry information between Pega versions. Previously, the system displayed Expiration Dates on the Authentication Service rule form after selecting the signing/decryption certificate, whereas after upgrade the expiry dates were not getting displayed. This was an error resulting from enhancements made to support different keystore types (Upload, File Reference, URL Reference, Data Page source) and introduce Keystore cache: during these modifications the "pzGetCertificateExpiry" activity was not modified to get the certificate from Keystore Cache instead from DB. This has been fixed.

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