User Requested Exception Lifecycle

The User Requested Exception policy defines the lifecycle state of an exception.

The User Requested Exception lifecycle includes these states:

This page discusses:

Request

A user requested exception is created in the Request state. Any Author can request a user requested exception. The setup for the exception is performed in the Request state. After the setup is performed, the user requested exception is promoted to the Inactive state.

Inactive

In the Inactive state, the owner of the related class is notified. At this time, the owner must determine whether to promote the exception to the Active state. The owner of the exception or any Leader can modify the setup of the exception in the Inactive state.

Active

The exception is available. The owner of the exception or any Leader modifies the setup of the exception in the Active state and promotes the exception to the Archived state when it is longer used.

Archived

Activity is complete and the user requested exception is no longer available.