Deployment

Deployment shows the system and project versions running on each environment. Use it after testing completed work in development. A construction result, version creation and deployment are separate events.

Before you start — Have the development checks and affected user journeys ready. Identify the publication stream and required production domains. Creating a version records a release; staging checks it; production makes that reviewed release available to users.

Review the versions before acting

Compare versions in the intended component stream before deciding which publication action is appropriate.

1. Open Deployment.
2. Distinguish System version from Your project version.
3. Compare Current version and Latest version in the relevant stream.
4. Read the listed components and the environment concerned.

One project version covers your application and back office, API, database, documentation and website; on the Development row, the list under the next version shows which of them have pending changes. The system version has no button: OWOXO installs it automatically on Development, then Staging, then Production.

Note — The System and Application version numbers at the bottom of the left menu belong to the workspace itself, not to your project. Click one to open their release history, with Published on and Installed on dates.

Create a project version

Create the version from completed work that has already been checked in development.

1. Verify the completed user journeys in development.
2. Find Your project version.
3. Use Create a version when changes are available.
4. Follow the request until the version appears.

Creating a version groups changes for publication; it does not immediately replace production.

Deploy and test staging

Test the staged release with the real task, its next step and an important exception.

1. Review the project version available for staging.
2. Click Deploy to staging.
3. Wait for the request to finish and the staging version to update.
4. Open the staging service and test the changed journeys in the required languages.
5. Check links and the outcome of the complete task.

The expected version and user outcomes are verified before advancing to production.

Note — If Create a version first is shown, create a version before deployment. A deployment already underway must finish before the next request.

For a changed order-confirmation journey, test the normal confirmation and a missing-information case in development. Repeat them on the staged version, then check the production version and journey. A completed build or a successful request submission does not replace these release checks.

Publish the tested version

Publish the staged version only after its checks and required production prerequisites are satisfied.

1. Verify the required production domains.
2. Check the version running on Staging.
3. On the Production row of Your project version, click Deploy to production.
4. Wait for Production to show the expected version.
5. Open the live service and repeat the changed task.

The publication is verified when the production version and the user-facing result match the tested release.

Consult the deployment record

Use history to understand the version and outcome of an earlier publication request.

1. Read Latest deployments.
2. Compare version, environment and status.
3. Click View full history for earlier entries.

The relevant deployment record is identified by its version, environment and state.

Important — A failed prerequisite or a running request should be resolved before another publication. Do not treat a requested deployment as a finished one.

Resolve a publication prerequisite