Defining Event Reason Codes in Classes

Reason codes allow detailed history of certain project events, such as changing a project manager on a project or changing a gate date. For reporting purposes, define a set of reasons for events that may occur in projects that use models based on each class, and ensure reasons for similar events are the same across classes. For example, ensure the event reason code for the gate decision to cancel a project is the same for all classes. If the reason codes are different across classes, you also need to create separate gate decision reports for each class.

Note:  Event reason codes are not used for automated gate decisions set for gates in the process model or through an automated workflow step.

To define an event reason code in a class:

1. From the System menu, select Process > Classes. To narrow the class list, search by the class name, system name, or category.
2. Either create a class, or select the class to edit.

3. Click the Event Reason List tab and select a project event type from the Event Type field.
4. If necessary, click Add New to display a new line for the event code and complete the following information:

Field	Description
Order	Enter a number to specify the reason's place when it displays in a list of reasons. Lower numbered reasons display higher in the list.
Code	Enter a unique, shorter name that identifies the reason in queries, reporting views, and in Accolade Office Extensions. Codes help to maintain project history if changes are made to the reason name.
Name	Enter a name, up to 64 characters long, which identifies the reason to users who assign it to events within projects.

5. Select the Active check box when the reason code is ready to use in projects.
6. Click Apply to save your changes.

Notes:    To delete a reason code, click the at the end of the reason code's row, and click Apply to save your change. See Classes Best Practices for information about recommended practices when deleting event reason codes.