23 August 2013

1. Miscellaneous Settings

1.1. Job Macros

In many places one can use macros that during runtime are resolved to real values. Depending on the context the possible macros varies, but in general, the table below illustrates the syntax of the macros and what they are resolved to.

Macro Descriptions

${job.id}

Resolves the id of the current job

${destination.id}

Resolves the id of the current destination

${tif.instance.id}

The ID of the TIF instance

${tif.setting.ABC}

A setting from TIF named ABC

${system:AAA}

A Java system parameter named AAA

${job.enoviauser}

The ID of the ENOVIA user

${job.source.id}

The ID of the source object in ENOVIA which the job relates to

${job.source.type}

The TYPE of the source object in ENOVIA which the job relates to

${job.source.name}

The NAME of the source object in ENOVIA which the job relates to

${job.source.revision}

The REVISION of the source object in ENOVIA which the job relates to

${job.source.current}

The CURRENT STATE of the source object in ENOVIA which the job relates to

${job.java.CLASSNAME:KEY}

CLASSNAME is a class implementing com.technia.tif.enovia.job.EnoviaJobMacroResolver

Example:

${job.java.a.b.c.TheResolver:the-key}
package a.b.c;

public class TheResolver implements com.technia.tif.enovia.job.EnoviaJobMacroResolver {
    public String resolve(EnoviaJob job, String key) {
        ...
    }
}
The class is only instantiated once and later reused to improve performace.

${job.source.selectexpression}

A custom select expression that is selected on the source object.

Note that this results in extra DB calls.

${job.rpe.ABC}

The ENOVIA RPE variable named ABC as set when the job was initiated

Note that there is a legacy format available that does the same:

${rpe:ABC}

This format should however not be used since it will be removed in a future release.

${job.param.ABC}

The parameter named ABC as specified when the job was initiated