This project has moved and is read-only. For the latest updates, please go here.


ACMA is designed to support using the same configuration file across development, QA and production environments. However, each environment likely has settings that differ between these environments. Constants are stored in the database, meaning they can be used to store environment-specific settings, and can be referenced from the configuration file.

Constants are a simple mapping between a constant name and a value. To ensure the configuration file stays truly portable between these environments, values can be stored as constants in the database, and referenced from the configuration file.

A good example would be the name of the Active Directory domain in each environment. A constant adDomain can be created that stores the NetBIOS name of the domain. In the configuration file, wherever the domain is required, it can be referenced using the %adDomain% declaration.

Another example might be the user's home profile path. In production, users may have a path of \\domain.local\users\accountName, while in the development environment it may be \\dev-domain.local\users\accountName. Given an attribute called accountName which stores the user name, creating a constant called homeFolderPrefix and setting the value to \\domain.local\users or \\dev-domain.local\users, the config file can simply contain a value declaration of %homeFolderPrefix%\{accountName}. The declaration will always expand to the correct value for that environment.

Constant names must be unique, and cannot be the same name as any of the built-in variables or sequences.

Last edited Feb 21, 2015 at 11:24 PM by ryannewington, version 2