Software Customisation Reference Manual

Summary of Objects, Members and Methods : Gadget Syntax Graphs
1.
Each graph represents a command (or part of a command) to AVEVA E3D™ to perform specified actions with specified data. The graph is entered at “graph_name>--“ or “>--”, and exited at “-->”. The allowed flow in a graph is top to bottom, and left to right, except where indicated otherwise by a “*“ or “<“ symbol.
2.
Vertical lines with one or more “+“ symbols represent a new state. These are always traversed downwards. There should be a “+” for each allowable entry point into a state. The “+” symbols can only be traversed from left to right.
2.
Words enclosed in “< >“ represent a call to the named graph. These should be lower case. Graph calls can be recursive.
3.
Words in lower case only, represent ‘notionally’ atomic data items, e.g. text, integer, val (numeric value). Sometimes they are in fact graph calls, e.g. ‘fname’ and ‘gname’. Sometimes they are fictitious e.g. ‘tagtext’, but more helpful than just “text” and easier to understand than a reference to, say, <fgtag>.
4.
Continuous vertical and horizontal lines without a “ + “ symbol represent flow lines of the graph.
1.
The presence of a “*“ symbol in a vertical line indicates that the allowed direction of traverse is upwards.
2.
The presence of a “<“ symbol on a horizontal indicates that the allowed direction of traverse is backwards.
3.
The symbols “.“,/, “ are just cosmetic to help the graph to look better.

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo