Working with Deployment Package States

As an Administrator, you create Package States to define the lifecycle of a Package. Package state change events allow the owners of Applications to configure Workflows (execution templates) that are started when the package state changes.

A change in the package state typically means that some significant events have happened or will happen (for example "ready for test" means that development can start testing). Package state changes are logged to the history of the Application.

For deployment packages a typical scenario is that they have to be installed on a certain environment when a package reaches a certain state. Then, Release Managers have to change the state of the package and start the installation workflow manually. Alternatively an administrator can configure a workflow to be triggered in the custom type XML.

Package states can be configured for each application individually from the Application main section in Advanced / Package States.

The corresponding actions can be configured in the sidebar:

Owner Change - you can set a new owner (a user or a user group) of the package when it enters a certain status. If no new owner is set, the owner will not be changed on state change.
Folder Change - you can set a folder to which the package will be moved when it enters that state, if no new folder is set, the package folder will not be changed on state change.
Workflows - you can assign workflows (execution templates) that will be scheduled for execution if the packages enter the corresponding state (see below). Execution templates can be exported/imported via the import/export CLI. For more information, see ExecutionTemplate.
Errors & Warnings - some errors & warnings may be displayed if the application contains deprecated package states which are no longer available for the current version.

Adding or Changing Planned Workflow Executions

When you add a workflow, you must set the following parameters:

Workflow
The workflow (general or application workflow) which shall be executed on state change. Only application workflows of the current application can be selected.
Profile
The deployment Profile which should be used. The field is hidden if you select a general workflow.
Starts

If the workflow should start immediately, or scheduled in a queue.
Manual confirmation required

If the workflow has to be released manually for execution you can select a user or group which can release the workflow. This is independent of any approvals which may be required.
Installation mode

If existing packages should be overwritten or skipped. This field is only available for application installation workflows.
Execute As

The user and password which will be used to execute the workflow. The password should be evaluated and an error message should be shown if it is incorrect.

If the user does not have the required rights, a warning icon will be shown next to the username (Tooltip: "The user does not have the rights to start the execution."). No password check is done.