Application processes, like component processes, are created with the process editor. Serena Release Automation provides several common process steps, otherwise application processes are assembled from processes defined for their associated components.
Application processes can run manually, automatically on some trigger condition, or on a user-defined schedule. When a component has several processes defined for it, the application determines which ones are executed and in which order.
An application process is always associated with a target environment. When an application process executes, it interacts with a specific environment. At least one environment must be associated with the application before the process can be executed. Application processes are environment agnostic; processes can be designed independently of any particular environment. To use the same process with multiple environments (a typical scenario), you associate each environment with the application and execute the process separately for each one.
In addition to deployments, several other common processes are available, such as rolling-back deployments. Serena Release Automation tracks the history of each component version, which enables application processes to restore environments to any desired point.