Incidents consist of the following components:
Use the incident properties pages to define any view incident basics, such as its short description, category, status, urgency, and impact. In addition, you can convert the incident into a project or project task from the Incident Properties page.
Use the Associations menu to view a list of projects and project tasks from which this incident was converted.
Use this component to view a list of the resource effort on timesheets to resolve this incident.
Use this component to add notes to your incident or to view a list of notes posted to your incident.
You can use CA Clarity PPM processes to automate certain elements of demand management. For example, you can create a process that notifies the incident manager when the incident status changes to "Resolved". You can also define a process to implement your incident, such as setting the incident urgency to "High".
Your CA Clarity PPM administrator can define incident type-specific processes or global processes designed to work on a specific incident.
You can create and run processes on incidents.
See the CA Clarity Basics User Guide for more information.
This component provides a way to track the history of specific activities that occur for an incident. Your CA Clarity PPM administrator, who determines which fields are audited and what information is stored in the audit trail, sets up Auditing. If Audit Trail is enabled and you have the appropriate access rights, the Audit menu displays when you open your incident. Use this menu to view a log of change, addition, or deletion records for any of the fields chosen for auditing.
See the CA Clarity Basics User Guide for more information.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |