Environments

Assuming your other systems support separate testing and production environments, Frends includes easy to way manage and differentiate functionality and values by the Environment the Process is deployed to.

Environments & Agent Groups

To separate different uses for different publications of the Processes, Frends provides Environments. These can be used to separate development, testing and production sites from each other by their use and target systems, by defining and using Environment Variables. When defined and used in Processes, Environment Variables can hold different values by the Environment the Process is deployed to.

While Environments separate the different sites logically by use purpose and shared values, Agent Groups in them define the actual location where the Processes will be executed. Because Frends supports hybrid architecture for execution environment, the Agent Groups essentially define whether the execution is done in dynamic containers, in the cloud or on an on-premise server.

In order to push the changes to other Environments and Agent Groups in Frends, all you need to do is to deploy the Process or Processes to another Environment and Agent Group. The centrally managed Environment Variables will be applied directly and immediately to the Processes being deployed, making sure that no development values will be used in production.

Selecting the target Environment and Agent Group for Process deployment.

In case you need to take down a Process from Production or return to older version of the Process, is just as easy as deployment. Simply select another, older version of the Process to deploy, and the changes will be rolled back from the target Agent Group. You can also of course deactivate the Process Triggers or delete the Process from the Agent Group you no longer need it in, and that makes sure the Process will no longer run in that Agent Group, without affecting others.