Application lifecycle

Draft, active, and archived Application status; wizard completion; badges and primary actions in the UI.

Written By Zoro

Last updated 3 days ago

Every Application moves through product states

Every Application moves through product states that match the badges you see in the list and on the overview: draft, active, and archived. The model is shared with Environments under Core Concepts in the sidebar at the Environment layer (draft vs active environments); this page is only about the Application entity.

Draft

  • Meaning: Setup is not finished; typically the Create New Application wizard has not reached the final Services activation step.
  • List actions: Continue setup (returns to the wizard) and a delete control to discard the draft.
  • Overview: Continue setup and Delete application (under the more menu).

Create path: Create an application.

Active

  • Meaning: The Application is fully configured for normal work: environments, compute, and services behave as configured.
  • List actions: Open application; when the default environment shortcut applies, the overflow menu can include Open default environment and Delete.
  • Overview: Actions such as Deploy from template, Open environment, and Delete application (exact layout depends on highlighted environment and setup state).

Archived

  • Meaning: Decommissioned in the product model: the Application is retained but not treated as live for shortcuts the same way as active.
  • List actions: View application.
  • Overview: Restore application (returns status toward normal operation) and Delete application.

Operational detail: Archive / delete / manage applications.

Default environment through the lifecycle

While active, the default environment drives highlights and shortcuts such as Open default environment. See Default environment.

See also