×

Please give details of the problem

Docs

Find

Project Lifecycle

To manage the iterative deployment of business changes, the version management features support you in labeling a project version for deployment in one of the three execution modes.

Version Management

A version is always created in Test mode. You can push it forward from Test to Acceptance to Live, and back from Live to Acceptance to Test. In addition, a version can be pushed directly from Test to Live and vice versa.

Multiple application versions can run concurrently in Test mode as well as in Acceptance mode. In Live mode, only one version is available for productive use.

A version running in Test mode is characterized as follows:

  • Only users with designer access rights are authorized to access and test the application. The designer has access to all resources, is assigned all manual tasks, and receives all notifications sent by the application.
  • The Live content of the defined roles is used.
  • The Test connector configuration is used.

A version running in Acceptance mode is characterized as follows:

  • A set of selected users is authorized to access the application.
  • Each user in Acceptance mode has the same rights as the end users will have in Live mode.
  • The Acceptance content of the defined roles is used.
  • The Acceptance connector configuration is used.

A version running in Live mode is characterized as follows:

  • The version can be accessed by the end users only.
  • The Live content of the defined roles is used.
  • The Live connector configuration is used.
  • If no mode parameter is set when launching the application, the Live mode is set as default.

Refer to the Lifecycle Guide for details on deploying applications to the three environments.