FileNet P8 Platform's lifecycle and events objects provide a rich set of features for system designers to integrate document properties into their business processes.
With Content Engine's document lifecycle features, you can define a sequence of discrete states through which a document object will pass. A typical application might assign states to the progression of a document from creation, to "draft" status, to "in review", to "approved", to "make obsolete upon being superseded by another document".
Actions can be associated with each lifecycle transition. For example, the requirements for passing through a state could be met through one or more workflows. Making a state transition might then automatically initiate the workflow associated with the next state.
Permission to initiate the transition from one state to another is restricted to the proper individuals in the organization. By controlling which users and groups have "change state" permission on a document, you can ensure that transitions are executed only by properly assigned members of roles whose job it is to make the transition.
Any state can permit many iterations. For example, while in a review state the document could, without its content changing, require the approval of several people.
FileNet P8 Platform's object model does not require that you create a new version of the document upon passing from one lifecycle state to another, although you could design an application to do so.
See Lifecycles for more information.
With FileNet P8 Platform's object model, you can create events that can trigger the execution of scripts or ActiveX controls. For example, you can trigger automatic e-mail notification of some event, or launch a workflow process, in response to some other action.
See Event actions and subscriptions for more information.