# Environments


The Environments feature is an add-on. Learn more.

Environments enable your team to easily plan, test, and deploy automation projects. This feature makes it easy to apply software development lifecycle (SDLC) best practices to automations.

In this guide, we'll cover:

# Environment Basics

# What is it?

The Environments feature simplifies the project lifecycle process by integrating dedicated environments into your Workato workspace. With Environments, you have built-in access to development, test, and production environments. Each environment includes a set of assets, members, and projects. Projects can include recipes, connections, lookup tables, and other asset types.

Projects can be quickly and easily deployed from one environment to another, ensuring the focus is on collaboration and recipe quality, not maintenance.

# What's included in Environments?

  • Robust change management - Builders can safely create and experiment in your DEV environment, and QA teams can review and test in your TEST environment. Once you've tested your changes, deploy them to PROD with confidence.
  • Compliance and auditability - Manage who can build, test, and deploy automations with collaborator roles. View a complete deployment history and roll back to a previous deployment at any time.
  • Business-friendly user experience - Manage change entirely within the Workato platform. No need for JSON manifests, git, or scripting tools.
  • CI/CD compatibility - Use Workato's platform APIs to integrate Workato into any existing CI/CD process.

# What environments will I have?

Workspaces with the Environments feature enabled will have the following environments automatically provisioned:

Environment Description
Main environment (DEV)
  • Used for recipe development
  • Used to deploy projects to other environments, including PROD
  • Used to maintain teams and the account, including collaborator roles, projects, folders, etc.
Test (TEST)
  • Used to test recipes in development
Production (PROD)
  • Used to run recipes that have been tested, reviewed, and approved

Refer to the Environment structure section for more info.

# How will environments affect my usage?

Usage is calculated across all environments in your account and includes billable recipes, tasks, or a combination of the two.

Using the Dashboard and Subscription plan pages, you can view usage by environment or across all environments.

# How do I monitor my usage?

There are two ways you can check your usage:

  • Using the Dashboard: Navigate to the Dashboard page to view metrics for the current environment and a high-level usage summary across all environments. When viewing this page, note that:

    • The Plan usage section summarizes your usage across all of your environments
    • All other sections and graphs reflect usage in the current environment
  • Using the Subscription plan page: This page, available only in the DEV environment, summarizes your usage across all environments over time. Navigate to Settings > Subscription plan (opens new window) to access this page.

# How do I get it?

The Environments feature is part of an additional add-on. Once purchased, how the feature is enabled depends on whether you're a new or existing Workato customer:

  • If you're a new customer after December 22, 2021, Environments will be automatically enabled in your workspace.
  • If you're an existing customer:
    • And you have multiple existing workspaces, contact your Customer Success Manager to initiate a migration request.
    • And you're purchasing new workspaces, Environments will be automatically enabled in the workspaces.

# Environment Structure And Planning

A typical software lifecycle uses three environments: One for development, one for staging and testing, and one for live production use.

Workato Environments uses separate but linked environments in your workspace to create a similar structure for recipe development:

Structure of standard environments in a workspace: Dev, Test, and Production

Projects and assets are deployed to other environments from the DEV environment. Changes to automations should only be made in the DEV environment to ensure modifications are captured and tracked accurately.

For example: A recipe in the DEV environment is ready for testing. It's deployed to the TEST environment where the recipe can only be run. Issues are reported as needed and addressed in the DEV environment.

To create a structured and predictable lifecycle management process, we recommend that you:

  • Define the criteria for promoting automations through the process. For example: What tests must be completed before assets can be moved to PROD?
  • Identify the teams participating in the process. What roles and responsibilities do these teams have? For example: Who will develop recipes? Who will test or deploy them?

# Collaborator Access

Access to each environment must be granted individually. Note: A collaborator must have access to at least one environment.

Where collaborators land when they sign into the workspace depends on the environments they have access to:

  • If they have access to DEV, they'll land in DEV regardless of other environment access
  • If they have access to TEST but not DEV, they'll land in TEST
  • If they have access to PROD but not DEV or TEST, they'll land in PROD

After they sign in, collaborators can switch between the environments they have access to by opening the sidenav and clicking the name of the environment.

Refer to the Managing environment access guide for more info.

# Deploying Assets


Collaborators must have access to more than one environment to deploy assets. For more info, refer to the Understanding Project Deployment with Environments guide.

In Workato, deployment is a process that pushes projects and assets from one environment in a workspace to another environment as part of the recipe development lifecycle (RDLC).

Recipes are typically developed in DEV, moved to TEST when they're ready for review, and then finally moved to PROD after testing and approval.

Refer to the Understanding Project Deployment with Environments guide for more info.

# What's next?

Ready to dive into Environments? Check out these resources to get started: