Working with Deployed Global Variables (without overwriting them)

Global Variables, (along with Next Numbers and Control Number Generators) are unique Clarify objects in that, once deployed to a remote server, function to continually increment and variabalize on the remote server with little if any manual interaction. Modifying or even removing these resources can impact your integration Projects that have dependencies, so it’s important to follow specific practices when doing so.

Cleo Services Methodology

This is the recommended process to update a Global Variable that is deployed to a remote server – without resetting or overwriting deployed objects and their values.
  1. Change the Global Variable from the Settings view in the Admin Console.
  2. Make sure the Global Variable object is synched with whatever change you've made.
  3. Do not undeploy a Project; redeploy if necessary.

How to change Global Variables from the Settings View

Click in the Value column for the Global Variable to change the value. As soon as you hit enter, the change is applied on the remote server.
Note: Cleo-supplied Global Variables can’t be changed (indicated by the Read-Only check box).

Don’t Undeploy

Undeploying is the removal of Projects from a remote server. This approach, especially on a Production server, should be done with caution (if at all). Generally, Projects are only removed (undeployed) when that Project is no longer part of your integration.

When a Project is undeployed (or removed) from a production server environment, Global Variables, Next Numbers, and Control Number Generators are also removed from the server.
Note: This is why Cleo does not recommend undeploying. Alwaysredeploy, don’t undeploy when working with Global Variables!

When working in different server environments

While the steps to update a Global Variable in one remote server are the same as any other, there are important things to remember:
  • While the update process is the same, each server environment has specific (and different) values that need to be configured in the Global Variable specific to that server.
  • Always synchronize Global Variables (and all other resources) in your different Workbench environments.

Other Recommendations when working with Global Variables

  • If used across multiple Projects, Cleo recommends creating Global Variables in a CORE Project, so the object can easily be shared with other Projects. This is useful for multiple Projects that refer to the same folder or database, an administrator email address, etc.
  • If you want to use a Global Variable from one Project in another Project, you must enable sharing between those Projects.
  • A Global Variable can contain another Global Variable.