These release notes provide information about enhancements and known issues that were resolved in each Pega Predictive Diagnostic Cloud™ (PDC) release prior to PDC 1.77.

Current version

For a current list of enhancements to PDC, see What's new in Pega Predictive Diagnostic Cloud.

Versions released before 2019

The following enhancements were implemented in version earlier than PDC 1.77:

Pega Predictive Diagnostic Cloud 1.76 (December 21, 2018)

• Predictive Diagnostic Cloud recognizes the PEGA0098 alert: Job scheduler failed to register for the next run, and creates a unique case for each job scheduler that has the issue. You can subscribe to receive a notification for each occurrence of the alert by clicking Diagnostic Cloud > Scorecards > Manage Subscriptions.
• Predictive Diagnostic Cloud recognizes the PEGA0099 alert: Job scheduler failed to complete successfully, and creates a unique case for each job scheduler. You can subscribe to receive a notification for each occurrence of the alert.
• Predictive Diagnostic Cloud recognizes the PEGA0101 alert: Queue processor failed due to a missing or failed stream node, and creates a unique case for each queue processor. You can subscribe to receive a notification for each occurrence of the alert.
• Predictive Diagnostic Cloud sends alarm notifications about infrastructure issues to Global Customer Support. On the Alarm Ticket tab of the Enterprise menu, you can track and monitor all such notifications that the system has created.
• On the Elasticsearch tab of the Enterprise menu, you can view the status and size of the Elasticsearch indexes for searching cases, rules, and data instances. You can use this information to diagnose issues with Elasticsearch.
• To improve usability of the Enterprise menu, node type is now represented by icons. To view the text value, hover over an icon.

Pega Predictive Diagnostic Cloud 1.75 (December 17, 2018)

• In the Overview tab of a case, Predictive Diagnostic Cloud now provides actionable recommendations for resolving the underlying issue.
• Improvements to the PostgreSQL database system shorten the time required to complete database requests and increase the performance of Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 1.74 (December 11, 2018)

• When Pega Platform generates a Connect-SOAP time-out exception, Pega Predictive Diagnostic Cloud recognizes the exception as an INTG0004 event and creates a unique case for each connector that has a connection or read time-out. You can subscribe to receive a notification for each occurrence of this event.
• When Pega Platform generates a PEGA0005, PEGA0006, PEGA0007, or PEGA0042 alert, Pega Predictive Diagnostic Cloud now normalizes the SQL "IN ()" clause to create a single case, regardless of the size of the value list that was used as the report filter. As a result, fewer cases are created and you can identify the root cause of the issue more quickly.
• When Pega Platform generates a PEGA0005, PEGA0006, PEGA0007, or PEGA0042 alert, Pega Predictive Diagnostic Cloud now creates a single case, even if the SQL "AS" clause name is different every time that you run a query. As a result, fewer cases are created and you can identify the root cause of the issue more quickly.

Pega Predictive Diagnostic Cloud 1.73 (November 29, 2018)

• Event Viewer now displays the time of events with accuracy to one millisecond. This enhancement helps you to identify the exact order of events.
• The Improvement Plan now provides filtering and sorting so that you can find information more quickly.

Pega Predictive Diagnostic Cloud 1.72 (November 27, 2018)

• When Pega Platform generates a Lock gone exception, Pega Predictive Diagnostic Cloud recognizes the exception as a LOCK0001 event and creates a unique LockGone- case for each object type that has the issue.
• The New Items Daily email digest now includes cases that were created from exceptions.
• When Pega Platform generates a Postgres connection capacity exception, Pega Predictive Diagnostic Cloud now recognizes the exception as an OPS0007 event and creates a unique DBConnections- case for each database where the issue occurs.
• When Pega Platform generates an Apache Tomcat server connection pool exception, Pega Predictive Diagnostic Cloud now recognizes the exception as an OPS0008 event and creates a unique TomcatPoolProblem- case for each application server and connection pool where the issue occurs.
• You can now subscribe to the Database Configuration Issues email digest to receive a notification about each occurrence of the OPS0007 and OPS0008 events.
• You can now view tracking reference information by expanding a case in the Improvement Plan. Tracking information can include tickets from any system that you use for issue and project tracking, such as Pega Agile Studio, ServiceNow, Jira, or Pega Support.

Pega Predictive Diagnostic Cloud 1.71 (November 21, 2018)

• When Pega Platform generates events related to the decisioning capabilities, Pega Predictive Diagnostic Cloud now creates corresponding cases in the Decisioning category. The new category appears in the Improvement Plan, so that you can find and analyze decisioning-related issues more quickly.
• Pega Predictive Diagnostic Cloud now calculates the urgency of all cases based on the number of occurrences and on the metric. As a result, you can accurately prioritize resolving issues with your application.

Pega Predictive Diagnostic Cloud 1.70 (November 14, 2018)

• When Pega Platform generates a Connect-REST time-out exception, Pega Predictive Diagnostic Cloud creates an INTG0001 alert and a ConnectRESTTimeOut- case. You can subscribe to receive a notification for each occurrence of this alert.
• When Pega Platform generates a Connect-FTP method failure exception, Pega Predictive Diagnostic Cloud creates an INTG0002 alert and a ConnectFTPFailure- case. You can subscribe to receive a notification for each occurrence of this alert.
• When Pega Platform generates an OutboundMapping exception, Pega Predictive Diagnostic Cloud creates an INTG0003 alert and a ConnectMap- case. You can subscribe to receive a notification for each occurrence of this alert.
• When Pega Predictive Diagnostic Cloud fails to connect to Global Customer Support to create an alarm ticket, Pega Predictive Diagnostic Cloud creates an OPS0006 alert and an ALTicketFailure- case. You can subscribe to receive a notification for each occurrence of this alert.
• When conflicting queries cause a blockage in the PostgreSQL database system, Pega Predictive Diagnostic Cloud provides an enhanced description and advice that helps you to resolve the issue.
• On the Event tab of a case, the summary now contains an Interaction ID, which is a combination of the requestor ID and the interaction number separated by --, for example, <requestor ID>--<interaction number>. Pega Predictive Diagnostic Cloud uses this value to correlate events that occur within the same interaction.
• When you click a case in the Event Viewer, you can access information about the case more quickly.

Pega Predictive Diagnostic Cloud 1.69 (November 5, 2018)

• When Pega Platform sends the PEGA0037 alert, Pega Predictive Diagnostic Cloud now creates a case in the Platform Tuning category. This change helps you to address the cause of the alert in a timely manner. For more information, see PEGA0037 alert: Rule assembly time exceeded threshold.
• Pega Predictive Diagnostic Cloud now assigns the correct urgency to cases that have been reopened. This enhancement ensures that you do not treat low-impact issues as urgent.

Pega Predictive Diagnostic Cloud 1.68 (October 31, 2018)

• You can now track external references associated with a case. Tracking references can include tickets from any system that you use for issue and project tracking, such as Pega Agile Studio, ServiceNow, Jira, or Pega Support. You can view and update tracking reference information in the new Tracking tab of a case.
• Pega Predictive Diagnostic Cloud now identifies performance issues that affect the sppr_sys_reservequeueitem_b queue management stored procedure and creates cases with specific advice for these issues.

Pega Predictive Diagnostic Cloud 1.67 (October 22, 2018)

• On the Improvement Plan landing page, you can now choose to view up to five hundred of the most urgent cases in each category. This view allows advanced users to browse many cases on one page.
• For each case in the Case view of the Event Viewer, the Affected column shows the requestor type that the issue affects: web interactions, service interactions, or batch processing.
• In the Case view of the Event Viewer, the cases are now sorted according to the number of occurrences. This enhancement helps you identify the most frequent problems with your system.

Pega Predictive Diagnostic Cloud 1.66 (October 16, 2018)

• Pega Predictive Diagnostic Cloud now notifies Pega Customer Support when a monitored system sends a PEGA0055 alert. The text of the ClockDrift- case has been updated to reflect a better understanding of the common causes of this alert. For more information, see PEGA0055 alert: Clock drift exceeded the configured time threshold.
• You can now subscribe to the New Exception notification (scorecard) to receive a message for every exception that occurs on the monitored system. To receive the New Exception notification, you must subscribe to it specifically, because it is not covered by the All option. Do not select this notification for unstable systems, because if the volume of messages is high, your email provider might block Pega Predictive Diagnostic Cloud.
• The New alert action item notification is now sent only when a case has more than ten associated events. This enhancement ensures that the application sends messages only about cases that need attention.
• Pega Predictive Diagnostic Cloud now removes potentially sensitive literal values in query text from SQL strings that come from Connect SQL rules. All literal text in a relational database (RDB) query is replaced by the string [REMOVED].
• The use of pr_read* functions in an SQL query, which cause guardrail violations, is now highlighted in the Observations tab for query and packaging case types, so that you can prevent further impact on the system's performance.

Pega Predictive Diagnostic Cloud 1.65 (October 11, 2018)

• When a monitored system sends a PEGA0044 alert, Pega Predictive Diagnostic Cloud now identifies the cases that caused the alert, and the events related to those cases, so that you can address the issue behind the alert.
• Pega Predictive Diagnostic Cloud no longer sends the Weekly Scorecard. Subscribers to the Weekly Scorecard will receive the Improvement Plan: Details email digests instead.

Pega Predictive Diagnostic Cloud 1.64 (October 8, 2018)

• When the PostgreSQL database system is in recovery mode, Pega Predictive Diagnostic Cloud creates an OPS0005 alert and a DatabaseMode case, so that you can address the issue.

Pega Predictive Diagnostic Cloud 1.63 (September 25, 2018)

• You can now view all recent cases and analyze their causes more quickly by using the Cases view in the Event Viewer.
• You can now periodically receive the following types of Improvement Plan notification emails, which replace the Improvement Plan Summary:
  • A detailed Improvement Plan in HTML format. You can open each case in Predictive Diagnostic Cloud by clicking it.
  • A summary of cases that are divided by category, which contains the total numbers of cases, occurrences, and assigned cases.

Pega Predictive Diagnostic Cloud 1.62 (September 24, 2018)

• When a summary view fails because the query execution exceeds a time-out in the PostgreSQL database connection, Pega Predictive Diagnostic Cloud creates a DBMS0002 alert and a SocketTimeOut action item.
• When Pega Predictive Diagnostic Cloud receives a DSM: Data Flow Run Failed (PEGA0072) alert, it sends a notification to Global Customer Support to ensure a timely response.

September 18, 2018

• The Improvement Plan tab is now loaded more quickly and without interruptions even on systems with very large amounts of data.
• The Dashboard tab has been renamed to the Welcome tab, and it is now easier to find shortcuts for performing basic configuration steps.
• The redesigned SQL Analysis tab facilitates the review and analysis of data.

August 31, 2018

• When a service is unable to process a service request for a pool or package because of a requestor pool lock, Pega Predictive Diagnostic Cloud now creates an OPS0003 alert and a RequestorPool action item.
  You can subscribe to the Requestor Pool Problem scorecard by clicking Diagnostic Cloud > Scorecards > Manage Subscriptions.
• The DBMS0003 alert that is created when a report fails because query execution exceeds the time-out in a report definition has been improved to support Oracle.

August 25, 2018

• The action item view has been redesigned to ensure easier access to the Pulse gadget. Details such as SQL analysis or stack trace are now displayed on dedicated tabs.
• The Improvement Plan subscription email now contains a PDF file attachment with a detailed list of the items that are listed on the Improvement Plan tab.
• Processing action and exception cases has been unified for performance and stability with the following results:
  • Existing exception cases are no longer updated. Beginning with Predictive Diagnostic Cloud 1.59, new exception cases are created.
  • All the information about exception cases has been moved from the deprecated Dashboard tab to the Improvement Plan tab.
  • You must update custom reports for exception items to ensure that the reports function correctly.

August 18, 2018

• Pega Predictive Diagnostic Cloud now detects the following conditions:
  • When a report fails because query execution exceeds a time-out in the PostgreSQL database connection, Pega Predictive Diagnostic Cloud creates a DBMS0002 alert, and a SocketTimeOut action item.
  • When a report fails because query execution exceeds a time-out in the PostgreSQL report definition, Pega Predictive Diagnostic Cloud creates a DBMS0003 alert, and a ReportTimeOut action item.
  • When a report fails because of unexposed properties (for example, a database column is missing), Pega Predictive Diagnostic Cloud creates a DBMS0004 alert, and a ReportJoinFailed action item.
• The PEGA0106 alert has been converted into the DatabaseDeadlock action item. You can also subscribe to the Database Deadlock Detection scorecard. To subscribe to a scorecard, click Diagnostic Cloud > Scorecards > Manage Subscriptions.

August 10, 2018

• When you log in to Pega Predictive Diagnostic Cloud for the first time, basic information about getting started with Pega Predictive Diagnostic Cloud is displayed.
• Information about the time zone that applies to the current operator is displayed at the top of the page, next to the search field.
• The action item view has been redesigned to ensure easier navigation. The most important details are now listed at the top of the screen.
• The Improvement Plan subscription email now contains a detailed list of items in each category.

August 03, 2018

• The following alerts have been converted into action items:
  • DSM: VBD has used 90% of allocated memory (PEGA0071)
  • DSM: Data Flow Run Failed (PEGA0072)
  • DSM: Data Flow Throws an Error (PEGA0073)
• You can now subscribe to the following scorecards that correspond to the preceding action items:
  • DSM 90% VBD Memory Usage
  • DSM Flow Execution Failure
  • DSM Flow Execution Error
  To subscribe to a scorecard, click Diagnostic Cloud > Scorecards > Manage Subscriptions.

July 27, 2018

• The action item view includes additional information:
  • In the upper right part of the screen, the Impact summary area displays the priority of the action item, affected applications and requestor types, and weekly trends.
  • In the center of the screen, a graph displays the number of occurrences for the action item on each day within the last two-week period.
• The Event Viewer has been enhanced:
  • The Event Viewer now displays action items that are correlated with events. You can use this information to sort and filter the events that are listed in the table.
  • If you filter the list of displayed events, when you click the Refresh button, it no longer resets the filters.

July 20, 2018

• In the Enterprise menu, you can view the Node ID and Node Type on the Health tab.
• In the Enterprise menu, you can view the Node Type on the Agent tab.
• The "Can’t connect to SMTP host" exception has been converted to the SMTP0001 action item.
• The "Connection reset while sending mail" exception has been converted to the SMTP0002 action item.
• You can view the Email Transport Error scorecard that displays issues with email communication. To receive a scorecard by email, subscribe to the scorecard by clicking Diagnostic Cloud > Scorecards > Manage Subscriptions.
• To see the following change, request the new AESRemote ruleset from Global Customer Support:
  • Deadlocks are now detected in the PostgreSQL system and are reported as PEGA0106 alert.

July 17, 2018

• You can now subscribe to the Improvement Plan Summary. To receive a scorecard by email, subscribe to the scorecard: click Diagnostic Cloud > Scorecards > Manage Subscriptions.
• You can now set the preferred time zone for viewing all Pega Predictive Diagnostic Cloud systems. Click your operator name in the upper right corner of the screen and click Preferences.

July 6, 2018

• To see the following changes, request the new AESRemote ruleset from Global Customer Support:
  • You can view Memory Management Data for a monitored node.
  • You can view MRU Cache Data for a monitored node.

June 29, 2018

• In the Event Viewer, you can now filter out action items generated within the last month.
• You can now restrict the systems that Pega Predictive Diagnostic Cloud users can see. If you have been using this function, you need to reconfigure restrictions for each user.

June 27, 2018

• You can now view changes in the Pega database size daily. In the Enterprise menu, select the system, and then click the Database Usage tab.
• You can now view the agent details to determine whether an agent is working correctly or if it is not working at all. In the Enterprise menu, select the system, and then click the Agents tab.
• You can now view the queue details to determine whether a queue has failed. In the Enterprise menu, select the system, and then click the Queues tab.
• You can now view listener details to assess the listener's health and performance. In the Enterprise menu, select the system, and then click the Listeners tab.
• You can now view the list of the hotfixes that are installed on your system. In the Enterprise menu, select the system, and then click the Hotfix History tab.

June 18, 2018

• In the Stability and Improvement Plan menu, you can now view action items that affect a single application, multiple applications, or all applications. By viewing the action items by an individual system and by application, you can prioritize the issues that must be resolved.
• In the Enterprise menu, you can see the number of agents that are running on a node and have a status of Normal. In the Enterprise menu, select the system with agents that have the Normal status, and on the Health tab, in the SYSTEM DETAIL section, in the AGENTS column, the number of currently running agents is displayed.
• To see the following changes, request the new AESRemote ruleset from Global Customer Support:
  • You can delete stale nodes from the Enterprise menu. In the Enterprise menu, select the system with the inactive node, and then on the Health tab, in the SYSTEM DETAIL section, click the Delete icon.
  • You can view the system configuration information. In the Enterprise menu, select the system, and then on the System Info tab, expand the Configuration Settings Info section.

June 14, 2018

• You can delete stale nodes from the Enterprise menu. In the Enterprise menu, select the system with the inactive node, and click the Delete icon in the SYSTEM DETAIL section, on the Health tab.
• You can see the system configuration information. In the Enterprise menu, select the system, and expand the Configuration Settings Info section, on the System Info tab.

June 1, 2018

• You can review the raw data that your application sends to Pega Predictive Diagnostic Cloud by using the Event Viewer. Advanced users can review the more detailed and technical information that is provided in the alert or exception description.
• Improvements were added for applications that use PostgreSQL database. To see these changes, request the new AESRemote ruleset from Global Customer Support. The following improvements are now available:
  • On the DB Query Stats tab, you can see hourly database query statistics by selecting the specific date and time in the Enterprise menu.
  • On the DB Table Usage tab, you can see how a table size has changed by selecting the specific date and time in the Enterprise menu.
  • On the DB Current activity tab, you can see the currently running query in the Enterprise menu.

May 25, 2018

• Pega Predictive Diagnostic Cloud shows indexes that are defined on a database table. To view the database indexes, in Predictive Diagnostic Cloud, click Enterprise and select the system that you want to view. To view the INDEX INFO section, click the DB Table Usage tab and expand the table. By viewing the database indexes, you can verify the number of indexes, whether the database contains the appropriate index, and whether any indexes are missing.

• The Improvement Plan has been updated with the following information:

  • The Affected column shows which requestor types are affected by the issue (web interactions, service interactions, batch processing).
  • The Impact column shows how much time your system spent on processing this issue in the last seven days and a percentage increase or decrease compared with the previous week.
  • The Occurrence column shows the number of occurrences for this issue within the last seven days and a percentage increase or decrease compared with the previous week.
  • In the Trend column, the red (higher) and green (lower) arrows show you action items that are gaining or decreasing in importance. The change is calculated based on the data from the Impact column.
  • In the top right corner, a Refresh button has been added.
  • The Exception category was added as a basic issue category.

• A Refresh button was added to the System Summary in the top right corner.

May 8, 2018

• You can view the preliminary Improvement Plan Preview and System Summary Preview scorecards, which present data in an easier and more intuitive format than the existing scorecard.
• All memory pool collection action items have been improved and provide more accurate troubleshooting information.
• Pega Predictive Diagnostic Cloud detects reports that run slowly because they contain inefficient starts with or contains pattern-matching conditions.

April 19, 2018

• Pega Predictive Diagnostic Cloud now automatically detects the name of a report definition or SQL query that extracts data by using case-insensitive conditions.
• Pega Predictive Diagnostic Cloud lists properties that you need to expose to prevent SQL queries from retrieving data from the BLOB. This improves your troubleshooting process and allows you to quickly resolve your issue.
• Browser and service performance metrics are fixed and do not show zero alerts when performance issues occur.

April 11, 2018

• Each monitored node shows information about the Java virtual machine in use and the Pega Platform build. To see this information, click the Enterprise menu, and then click the System Info tab. By looking at the system information, you can determine whether the system that you are working on is up to date.
• Action items for connectors and database connections have more meaningful descriptions, so that you can quickly assess an issue.
• The name of the table that is called from the Obj-Save method and that is running slowly is automatically detected to help you research the issue.

March 20, 2018

• The name of the activity or table that is called from Obj-methods and is running slow is now automatically detected to help you research the issue.
• The name of the activity that is called from RDB-methods and is running slow is now automatically detected to help you research the issue.
• Action items regarding guardrails and security violations have more detailed information so that you can quickly assess and troubleshoot an issue.
• All systems that do not have alert exceptions and health data are automatically deleted from the Current System list that is on your dashboard.

March 8, 2018

• All Runtime Guardrail Violations action items have more detailed information so that you can quickly assess and troubleshoot an issue.
• The correlation in stored procedures has also been improved. All calls to a single stored procedure are now assigned to one action item. As a result, the number of action items have been reduced and the scorecard readability has been improved.

February 23, 2018

• All action items that are related to data processing from internal system tables pr4_*, spr_*, pr_sys* are now automatically identified and assigned to the Pega Cloud work queue for further action. By automatically triaging certain action items, Pega Predictive Diagnostic Cloud enhances your troubleshooting process.
• The Advice tab on each action item has been renamed the Observation tab. This tab describes issues and provides troubleshooting.

For more information, see Pega Cloud support and help resources.