The best option is to create a global in your Editor and then override it via a configuration file on teh server with environment specific data. When the definitions are downloaded to the client the override value will be used instead of the default editor value. Since it is stored as a global it can be used just like any other global value as a property setting, in a rule, etc.
When publishing be sure to check the "Create override base files" to generate the templates. You can then rename and edit the GlobalsBase.ini to Globals.ini and only include those values you want to override for the environment. When removing entries be sure to leave the appropriate section headings for the values you are keeping.
Be sure to restart the Agentry app to pickup the file after changing.
--Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.