Configuration variables

You can use variables in place of explicit directory paths in certain fields in project property pages. Besides reducing typing errors, using variables and then sharing settings can lessen the need to specify new paths when importing properties to a project. The following predefined variables are available at the project and workspace level:

• @{DLC}—The root directory of your OpenEdge installation.
• @{ROOT}—The project root directory, specified when you create the project.
• @{WORK}—The project working directory, specified on the Progress OpenEdge properties page page. (You can enter a period (.) to represent @{WORK}.)
• @{RCODE}—The directory (if any) specified in the Build destination field on the Build properties page page.
• @{APP}—The application root directory, if any, specified on the Configuration variables properties page page.
• @{DB}—The database root directory, if any, specified on the Configuration variables properties page page.
• @{TEMP}—The directory where temporary files are created.

The following is the list of the locations where these variables apply:

• In the Configuration File field (for Dynamics) on the AppBuilder properties page (Windows only) properties page.
• In the Build destination field and Source entry on the Build properties page properties page.
• In the Source tab of the Build properties page properties page.
• In the alias directory entries on the SpeedScript properties page properties page.
• In PROPATH entry in the PROPATH properties page properties page.
• In Assemblies properties page for assemblies.xml file location.
• In File Destinations properties page for ESB and REST invocation files.

In addition to the above predefined variables, you can also define new configuration variables and use them to define project properties. See Defining new configuration variables for more information.