Environments

After you have built and published your workflow or page in a development environment, it’s important to test it. While Nintex Workflow and Nintex Apps enable rapid application development, it’s important to maintain a clear application lifecycle management process (ALM) while developing with it, which means having multiple environments with roles for testing. Some common set ups include:

Development: The primary development environment, where builders work on and preview workflows and apps often. Workflows and apps are published here to ensure their URLs are configured, but they are not used. Once a workflow or app has reached a usable point, it is deployed to the testing environment.

Testing: The primary testing environment, where test users validate that all aspects of the workflow or app are working as expected. Developers are informed about issues found here, and they then resolve those issues in the development environment. If all is well, then the workflow or app is deployed to the production environment.

Production: The primary environment for end users, where the workflow or app is expected to work as intended. We recommend only publishing to production after following clear ALM processes.

Your environments are automatically connected to each other once they are provisioned—with each environment representing a pair of tenants for Nintex Workflow and Nintex Apps (for example, a Development Nintex Workflow tenant and a Development Nintex Apps tenant).

To switch between environments in your Nintex Workflow tenant, you must be assigned a non-participant role. Participants cannot switch between environments. Then, select a different environment from the drop-down at the top of the screen next to the company logo. The selected environment opens in a new tab. For more information on assigning a tenant label to the environment to make it easier when switching environments, see Access the Tenant and user details page.