Overview

Connected Environments is a module within UnifyApps that allows users to link different environments and seamlessly move changesets between them. Once two environments are connected, transferring assets becomes simple and efficient. 

Two environments, however, cannot be created arbitrarily — they must follow defined authentication mechanism, ensuring safety and security in how environments are linked

Configuring Connected Environments

Step 1: Access Change Set Settings

• Navigate to Settings in the main navigation.

• Under the Change Set section, select Connected Environments.

• You will now see a list of all Connected Environments

Step 2: Generate an Env Token in the destination environment

The Environment Token is used for authentication. You generate it in the DESTINATION environment and use it in the SOURCE environment.

• In the destination environment, open Settings › Change Set › Connected Environments.

• Click Generate Env Token. The Environment Credentials dialog shows the Domain and a Token.

• Copy both. The token is valid for 10 minutes, and you can't see it again once you click Done.

Step 3: Create a New Connected Environment in the source environment

• Click on New Connected Environment 

• Provide the following details

  •  Environment Name: Add a unique name for the connected environment

  •  Domain: Specify the domain (ex: acme-uat.unifyapps.com) of the connected environment

  •  Environment Token

    : Add the short lived token for the environment that you want to connect to. Paste the token you generated in Step 2

    
    

• Click Connect. Do this within 10 minutes of generating the token.

Configuring Settings for Connected Environments

Once two environments have been connected, click one to define the settings that govern the change set process. Following options are available:

• Retain Role Mapping: copy valid team and role mapping from the source environment. Any teams or roles not present in the destination are skipped.

• Approval Settings

  • Type 1: Auto Approval: 

    • This is the default. All assets within a change set are auto-imported. Choose a Deployment Type: Update Records (update records if they already exist) or Skip Records (skip records if they already exist)

  • Type 2: Manual Approval: 

    • If this is selected , changeset will need manual approval before deployments

    • Define one or more approval levels. Each level has a Level Name, a No. of Approvals (1-6) and the users or teams who can approve

• Retain Asset Owner

  • Enable this to preserve asset ownership during import

  • MATCHING PROPERTY: This is used to Map custom user attributes to match identities between environments. This can have values like Email, Name, UserId etc.

  • JIT Provisioning: Choose Auto Create User (the default) to create a new user when no matching user exists, or Map Deployed User to map asset ownership to the user deploying the change set

    
    

If Retain Asset Owner is off, imported assets are owned by the user who deploys the change set.

Best Practices

1. Use Descriptive Names: Give your Connected Environments clear, descriptive names that indicate their purpose and destination.

2. Test After Connection: After connecting 2 environments, test the connection using a sample/dummy changeset.