To create a new configuration (empty or default), select File, then New. There are two options for new configuration files, refer to Empty Configuration or Default Configuration for further information.
|
|
An Empty Configuration file provides some simple default settings but will contain no rules for building and comparing elements.
|
|
A Default Configuration provides a copy of the out-of-the-box project configuration file containing a complete set of example rules that can be used out of the box but are available for customisation.
|
|
To open an existing configuration file, select File, then Open, from the displayed Open Project Configuration File window, select the ProjectConfiguration.xml file. By default the appropriate folder is displayed, defined as the Model Management folder under the folder indicated by the project defaults environment variable, for example: for the TTP project:
If required, use the project defaults environment variable to get quickly to the appropriate folder. For example, in the Open Project Configuration File window, for the TTP project, enter %ttpdflts%\ModelManagement in the Filename field and then press Enter.
|
|
To discard any changes made to the configuration file but keep it open, select File, then Revert to Saved.
|
|
To close the Integrator Project Configuration Explorer, select File then Close. If there are unsaved changes, a prompt is displayed save them.
|
•
|
Create rules
|
|
Assign rules
|
Note:
|
Note:
|
Quotes are not required in selector rules as Integrator will automatically include quotes for text selectors, for example: a rule with SCSTYP OF source operating on an SCVALV with SCSTYP PTFE-LINED will generate Choose with STYP |PTFE-LINED|.
|
•
|
Operators eq, ne, lt, le, gt, ge, test for equality, inequality, less than, less than or equals, greater than, greater than or equals, and apply to a pair of numerical expressions or a pair of alphanumeric expressions or a pair of Boolean expressions. (The result will be unpredictable if expressions of different type are compared.)
|
•
|
•
|
Operator not is used to negate the Boolean expression that follows it.
|
double Sine (double angle)
|
|
double Cosine (double angle)
|
|
double Tangent (double angle)
|
|
double Acosine (double value)
|
|
double Atangent (double value)
|
|
double Sqrt (double value)
|
|
double Log10 (double value)
|
|
double Logarithm (double value)
|
|
double Alog10 (double value)
|
|
double Alogarithm (double value)
|
|
double Absolute (double value)
|
|
integer Fix (double value)
|
|
integer Ceiling (double value)
|
|
integer Round (double value)
|
|
double Atant (double x, double y)
|
|
double Minimum (double a, double b, …)
|
|
double Maximum (double a, double b, …)
|
|
integer Length (string text)
|
|
integer Occurs (string text, string sub)
|
|
integer Instring (string text, string sub)
|
|
string Asstring (object value)
|
|
double Asreal (object value)
|
|
boolean Asboolean (object value)
|
|
string Substring (string text, integer start [, integer length])
|
|
string Left (string text, integer length)
|
|
string Right (string text, integer length)
|
|
string Before (string text, string sub)
|
|
string After (string text, string sub)
|
|
string Uppercase (string text)
|
|
string Lowercase (string text)
|
|
string Trim (string text)
|
|
string Lookup (string dictName, string key)
|
|
Integer Listposition
|
// the list order position of the current target element.
|
An expression to generate the value for the target attribute, and can contain references to source. For build rules it should not contain references to target as this will be undefined at build time.
|
Note:
|
Name rules based on target are not well supported in Integrator as target is undefined until it is actually created. In some cases it defaults to the source object for data if the target object is not available at that point. Consider an owner rule for building a ZONE when source is SCPLIN and target is the PIPE. It would seem reasonable to set the value of the ZONE name based on the SITE name plus a prefix, for example: ”format(‘{0}-{1}’, owner of owner of target, LNTP of source)”. But the ZONE is created before the target exists and so this rule will not give the desired result.
|