Gtype/Tracking

This tab enables the administrator to specify which MDBs and controlled GTYPEs are to be included in a Track Changes operation. Additionally, the tab provides facilities for specifying Tracking Selection Rules that further restrict the range of controlled GTYPEs to be included in the operation.

MDBs

At the top of the tab, a pane called MDB displays a listing of the MDBs defined in Clash Manager. Against each MDB is a checkbox, which is checked by default when the MDB is first defined. As required, the administrator can un-check a checkbox to remove the particular MDB from the Track Changes operation.

Controlled GTYPE

In the middle of the tab, a pane displays a listing under headings of GTYPE and State. The listing is used to present a list of available GTYPEs and to enable certain of them to be made Controlled or Uncontrolled. (Only a Controlled GTYPE is the subject of a Track Changes operation.)

Except in the case of Standalone Clash Manager, a range of controlled GTYPEs is predefined in VPE Workbench. These predefined GTYPEs appear in the list and cannot be made uncontrolled or deleted at this form. Also, GTYPEs that are Group Level Elements (see the Group tab) and certain others that may be group level elements, such as ZONE, are always controlled and cannot be made uncontrolled or deleted at this form.

Further GTYPEs can be added at this form and these can be made controlled or uncontrolled, or deleted, as required. A popup menu is available for this purpose. Its options are as follows:

Examples for hull, room design and cable way objects are shown in the picture above, with CPANEL, CTWALL and CWAY made Controlled GTYPEs.

Note:
You must first make a GTYPE Controlled before you can select it in a Group Rule (Refer to Group).

Tracking Selection Rules

At the bottom of the tab, a pane is available for specifying rules that further restrict the range of GTYPES to be included in the Track Changes operation. For the syntax of the Tracking Selection Rules refer to Notes on Element Rule Syntax.

Note: Any GTYPE (for example, BBLOCK, BLEVEL) included in a rule must first be added to the GTYPE list even if it is not to be Controlled.

Note: A DB (and its hierarchy, that is, sites, zones, pipes, branches, etc) may be included in many MDBs. For example, Site 12 (through the inclusion of containing DBs) may be visible in two MDBs:

MDB1 /site1, /site12

MDB2 /site2, /site12.

Each Site and everything below it will exist in a single DB [name clashes are not impossible, two sites with the same name may exist in different DBs, but only one would be generally accessible through its name when included in the same MDB]. All branches of a PIPE would be in a single DB, but that DB and thus the PIPE may be visible through more than one MDB.

Clash Manager can combine MDBs and in the process may encounter duplicates, in which case Selection Rules may return other starting points in the hierarchy, for example, a list of ZONES.

It is important that the Selection Rules, when evaluated, return a list of unique items.

A popup menu is available. The options and their purposes are as follows:

Note: Double-clicking a GTYPE name leads to the 'Browse Model' form. Double-clicking on an expression leads to the in-place edit window.