21.   It should be noted that the lifecycle of a module subscribing to a defined process model is in parallel with not instead of the normal DC controlled lifecycle.

22.   Certain fixed process models are inherent within LIFESPAN and operate on object classes.

23.   The process model searches the tree of users within LIFESPAN for a match with the roles specified in the model.

24.   This enables the history of a process model to be tracked easily along with the exact period when a particular model was active.

25.   A process model is defined textually via a pmodel module using the Process Model Definition Language.

26.   Individual modules are ordered to follow a specific process model by defining them to be of a particular subtype.

27.   It is only created if a QAO log entry is actioned by a process model for that module.

28.   Having defined your process model using the process model definition language, the pmodel module must be entered into LIFESPAN and installed before it will take effect.

29.   Once a process model is deinstalled only outstanding actions will be performed including tasks.

30.   If PURGE-TASKS is set to ALL then only the latest version of a module will continue to follow its defined process model.