10.2. Lifecycle Terminology

Engineering Knowledge Manager

Administration Guide | Chapter 10: Defining and Configuring Lifecycles |

10.1. Introduction to Lifecycles |  | 10.3. Basic Steps for Creating, Configuring, and Managing Lifecycles
Prev |  | Next

## 10.2. Lifecycle Terminology

Let's start with defining some lifecycle terms that are used throughout EKM Studio.

Stages

  Stages are phases within a lifecycle where you can set permissions for who can access, modify or do other operations on an object and set criteria for automatic deletion of the object from the connected EKM repository. They are represented in a lifecycle diagram with the icon shown above.

  Lifecycles must adhere to the following rules:

  - Lifecycles should have exactly one start stage. A “start” stage is the stage that is not the destination of any transition. Lifecycles can have more than one end stage. An “end” stage is the stage that is not the source of any transition.

  - Lifecycles must be acyclic. For example, if you have a transition from stage A to stage B, then you cannot have a transition from stage B to stage A. Similarly, if you have defined transitions from stage A to stage B and from stage B to stage C, you cannot have a transition from stage C to stage A. Lifecycles are always directed acyclic diagrams.

Transitions

  A transition is a link between a starting stage (source) and an ending stage (destination). It is used to specify the subsequent and preceding stages of a lifecycle stage. A transition can also optionally specify a signoff process for moving to the next stage. Transitions are represented in a lifecycle diagram as an arrow.

Signoff Process

  A signoff process is a separate process automatically generated by EKM when completion criteria for a stage transition require that the object undergo review and approval before being promoted or demoted. Members are sent an email notifying them that an action is needed, and a new task is placed on their My Tasks page.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.