The following fields are available on the Create New Change Order and Update Change Order pages:
The user name of the person who created the change order ticket. The user name is entered automatically and cannot be edited.
(Optional) Enter your phone number when creating a change order ticket. This number appears in the History section of the change order record and cannot be edited.
(Optional) Enter your e-mail address when creating a change order ticket. This address appears in the History section of the change order record and cannot be edited.
Select a priority ranking for the change order, to specify the amount of attention it should receive. Your system administrator can modify the default priority codes, so they may vary from one installation to another. This is a required field.
(Optional) Indicates the general subject the change order ticket addresses. Categories provide default values that automatically appear on all change orders that are assigned to that category. Your system administrator defines Change Categories for your installation, so they vary from one installation to another. Enter a value directly, or click to select from the defined change categories. When you edit the Category and a CA Process Automation workflow is already running, the workflow cancels.
Important! Your administrator can associate the category with a risk survey. A Risk Survey button may appear when you save the change order. This option opens a risk survey questionnaire and is submitted to evaluate the risk of implementing your change order.
Note: Your administrator may add custom properties to change categories. If custom properties have been added, they are displayed on the Properties section of the ticket record.
Enter a detailed description of the reason for opening the change order ticket. Be sure to provide enough information so the person who works on this ticket can understand and evaluate the change you are requesting. This field is required.
The following fields appear on the Change Order Detail page:
Indicates the general subject the change order addresses (for example, Add.IT.Server).
Indicates the amount of attention the change order should receive. Your system administrator or an active automatic priority calculation can modify the default priority codes, so they may vary from one installation to another. The predefined priority codes are:
1 = High priority
2 = Medium-high priority
3 = Medium priority
4 = Medium-low priority
5 = Low priority
None = No priority is assigned.
Indicates the status of the change order within the overall processing cycle, for example RFC (Request for Change), Approval Started, or Closed..
Indicates the date and time the change order must be implemented.
Indicates the date and time the change order implemented was begun.
Indicates the date and time the change order ticket was closed.
Indicates date and time the change order ticket was created.
Indicates how much the change order affects the normal work flow within the service area. Your system administrator can modify the default impact codes, so they may vary from one installation to another. The predefined impact codes are:
1 = Entire organization
2-Multiple Groups
3-Single Group
4-Small Group
5-One person
None
Indicates whether the change order record is active or inactive.
Provides a brief description or purposes of identifying the change order.
Explains in detail what the change order is intended to accomplish. This field can also refer to attached documents or web sites for further information.
Indicates the date and time the change order is expected to be completed.
Indicates the actual date and time the change order is completed.
Displays any custom properties your administrator may have added to the change category associated with the change order. The Example field displays explanatory text your administrator provides about each property.
Displays a log of all activities that have been performed on the change order.
Provides a list of links to any documents or web sites that have been attached to the change order.
Copyright © 2013 CA.
All rights reserved. |
Tell Technical Publications how we can improve this information |