Historically a delimited object reference was known as a 'DOR' but now we simply say an 'object reference', or when the object type is known a 'SCALAR reference', 'LIST reference' etc….

In EASA a delimited 'object reference' allows an object on the Tree to be used:

1. Within a parameter value for another object
2. As a variable in an 'expression' in an object parameter, see Expressions
3. As an output value from an EASAP to be injected into a text file input for a PROCESS
4. Following a PROCESS submission, to import output values from a text file into an EASAP

For 1. and 2. above where a parameter value accepts a combination of literal text, operators and object references the name of the object must have a special character directly before and after the name (ie. a 'delimiter').

By default in EASA uses ' % ' or the percent-sign to delimit an object reference.

For 3. and 4. the same applies except the delimited object name is entered within the Template Editor, again the default delimiter is: %

For example: %objectname1%

Once the EASAP Builder recognizes the above format the color of the text will change according to the specific object type of: objectname

• A SCALAR reference will turn blue: %objectname1% goes to objectname1
• A LIST reference will turn green: %objectname1% goes to objectname1

Additionally, in the EASA Help Pages, an object name, either with or without delimiters, is written in boldface.

An object reference may be used in various locations within the EASAP Builder. For example in:

• CHOICE LIST > Choices:
• Many parameters of child objects under a DATA PROCESSING
• DIAGRAM child objects > Points:
• A template file for a batch file input or output
• Many parameters of many objects within the OUTPUT or USER INTERFACE branch

To view values of all objects after an EASAP has been run:

• Go to: EASA > Authoring > Testing
• Click: DORs column for a test run, see EASA > Authoring

An inline unit may be displayed within the delimiters for an object reference, see Inline Units in Expressions

By default, if no units are specified within the object reference the object value will be in base units.

An 'inline unit' is a unit name in brackets immediately following the object name.

For example: %object1 [ft]%

For the above syntax object1 is to be evaluated in 'feet', instead of the base unit of 'meters' (or ' [m] ').

The text abbreviation used to inline a unit must be an existing unit name defined either in Default: or User Units: for the dimensional group associated with the object-type being referenced.

In addition to units, the number format of an SCALAR number may be specified inline for a delimited SCALAR reference.

The following formats are supported:

• Integer
• Real
• Exponential
• Mixed

The format of a number is important for an input file when a batch software application process requires a specific number format.

An inline number format may include an inline units as well; number format specifier must follow the unit specifier.

The four number format specifiers are as as follows:

• Integer: ad
  a - is the total number of digits
  d - is a literal ' d '

• Real: a.bf
  a - is the total number of characters including digits, decimal point and ' + ' or ' - ' signs
  ' . ' - is a literal ' . '
  b - is the number of digits after decimal point
  f - is a literal ' f '

• Exponential: a.be
  a - is total number of characters including digits, decimal point, ' e ' character and ' + ' or ' - ' signs
  ' . ' is a literal ' . '
  b - is the number of digits after decimal point
  e - is a literal ' e '

• Mixed: a.bg
  a - is total number of characters including digits, decimal point, ' e ' character and ' + ' or ' - ' signs
  ' . ' is a literal ' . '
  b - is the number of digits after decimal point
  g - is a literal ' g '
  Mixed defaults to a Real, but will switch to an Exponential if the number is too large/small for a Real to be valid.

Examples of inline number formatting within a delimited object reference are as follows:

• %object1 [ft] 9.3f%
• %object1 5d%
• %object1 12.4e%
• %object1 12.4g%

Notice the use of inline units in the first example.