Environments

• Environments allow you to configure access to a series of versions without having to redeploy widgets or to change access keys.

• It is best practice to use an Environment for any long term use of an Agent over its lifetime eg. for Production, Testing or Development.

• Using the Agent allows you to avoid having to update a version access key with every new version deployed into that Environment. Instead, you can use an Environment access key.

• All Agents come preconfigured with a Production and a Development Environment.

• You are free to replace these and/or add or create your own Environments.

• An Environment has one active version.

• Any version can be assigned as the active version for an Environment.

• A version can be the active version for many Environments

Limits

• You can maintain up to 8 Environments for each Agent.

Environment Access Keys

• An Environment allows you to maintain one or more Environment Access Keys, each of which enables access to any version nominated as the active version for that Environment.

• Use multiple keys to coordinate frequent cycling of access keys for enhanced security purposes if you require it.

Widget Code Snippet

• You can also copy a code snippet configuring the Widget for use via the Environment.

• The Widget code will use the configuration settings associated with that Environment’s currently active Agent version.