Simple graph definition
The following example shows a graph definition structure that has a single expansion from a non-mergeable grouping object to a set of mergeable items of one type:
-
CommissioningSystem 001
-
CommissioningSystemTag
-
Tag001
-
Tag002
-
Tag003
-
-
All of the items retrieved and submitted for merge as a result of expanding the graph
definition are restricted to Tags in this case.
Detailed graph definition
The following example shows a more complex graph definition structure configured to locate a broader data structure.
-
CommissioningUnit
-
CommissioningUnit,CommissioningSystem
-
CommissioningSystem001
CommissioningSystemDoc
Doc001
Doc002
CommissioningSystemTag
Tag001
Tag002
CommissioningSystemEquipment
Equip001
Equip002
-
CommissioningSystem002
CommissioningSystemDoc
Doc003
Doc004
CommissioningSystemTag
Tag003
Tag004
CommissioningSystemEquipment
Equip003
Equip004
-
-
-
All object types exposed from this graph definition example are configured as mergeable. If any items are not configured to be mergeable, they would be excluded from this merge.
-
Where a grouping object is at a higher configuration, a merge from a sub-configuration may also reference the higher configuration item. Items from sub-configurations on a common grouping object are ignored when processing this merge type.
-
If the grouping object is not mergeable and is located at project level, it will not be terminated on completion of a successful merge.
-
Items can be located in the data structure of more than one grouping object. When the first grouping object is used for a merge, all the items will be merged up to the higher configuration. However, when the second grouping object is used for a merge, the software will not attempt to merge those items, unless the items have been claimed to the project again.