Corelate issues in your system with your recent system updates by using the Changes Summary landing page. Changes Summary lists the changes that occur in a monitored system or environment of that system during the last 30 days. You can use the page to troubleshoot unusual behavior in your system.

You can use the Changes Summary landing page to accomplish the following activities:

• Diagnose issues, for example, to check whether periods of very slow response times coincide with system updates
• Control the deployment process, for example, to ensure that the recent updates were properly tested

The Changes Summary shows the following lists of changes in your system:

• Platform imports – Files that developers import into your application, such as JAR and ZIP packages containing application updates, and the developers performing the imports. This section displays packages imported by any merthod into Pega Platform, including manual imports, custom scripts, and any version of Deployment Manager.
• Artifacts deployed by Deployment Manager – Imports completed by Deployment Manager version 5.5 or later. You can compare this data with your Platform imports to distinguish between manual imports and imports that are completed by Deployment Manager.
• Rule updates – Snapshots of recent rule updates. You can view a detailed list of up to the 50 most recently updated rules, and the developer that updated the rules, by clicking the number of updates.
• Pega Platform updates – Changes to the Pega Platform version in your system.
• Configuration changes – Configuration changes in the Dynamic System Settings (DDS) in your application. The list includes the following information:
  • type of configuration change
  • ID of the node on which the change occurred
  • Value before the change
  • New value
• Topology changes – Changes that include node startups and shutdowns, and situations in which nodes stop sending health messages. You can click a link to quickly view each change in the Event Viewer. The changes include the following statuses:
  • Node started – A PEGA0008 alert confirms a successful node startup. For more information, see PEGA0008 alert: PegaRULES engine started.
  • Node shut down – A PEGA0036 alert confirms an intentional node shutdown. For more information, see PEGA0036 alert: PegaRULES engine intentionally shut down.
  • Node status lost – PDC fails to receive three consecutive health messages from the node.
  • Node alive – A node starts sending health messages, but a PEGA0008 alert does not confirm the startup of the node.
  • New type – Your system detects a new type of node, for example, if all the nodes are Stream nodes and WebUser nodes, and then the system detects a BackgroundProcessing_BIX_Search node.

The following figure shows different functionalities of the Changes Summary landing page in PDC: