Environments

Use separate environments to build, test, and release changes before making them available to end users. Nintex supports application lifecycle management (ALM) by helping you move solutions and their supported assets through non-production and production environments. Nintex supports the following environment types:

Non-production: Used to build, preview, and test solutions and their assets before they are used by end users. Non-production environments can be used for development, testing, or both. If issues are found during testing, resolve them in a non-production environment before deploying to production.

Production: Used by end users. Deploy to production only after the solution and its assets have been tested and validated through your ALM process.

Your environments are automatically connected after they are provisioned. Each environment represents a pair of tenants for Nintex Workflow and Nintex Apps, such as a Development Nintex Workflow tenant and a Development Nintex Apps tenant.

To switch environments in your Nintex Workflow tenant, you must be assigned a non-participant role. Participants cannot switch environments. Select the environment from the drop-down next to the company logo at the top of the screen. The selected environment opens in a new tab.

Using separate environments is a core part of ALM. It lets you build and test changes in a non-production environment, then deploy validated solutions and their supported assets to production for end users. For more information about deploying across environments, see Deployment.