JSON syntax: Edges section

The edges settings determine which directed relations should be traversed, and how they should be depicted on the diagram. Each edge represents a relation type between two nodes (asset types or complex relation types) in the view.

You have to ensure that the diagram view is a connected graph: each node in the diagram view is reachable from any other node.

JSON syntax Description
"from": "Business Asset"
  • Indicates which node is the head asset.
  • This setting is mandatory.
  • You must fill in a node ID ("id") from the nodes section.

"to": "Table Column1"

  • Indicates which node is the tail asset.
  • This setting is mandatory.
  • You must fill in a node ID ("id") from the nodes section.

"type": "00000000-0000-0000-0000-000000007038"

  • Indicates the ID of the relation type.
  • This setting is mandatory.
  • You have to fill in the resource ID of the relevant relation type. You can copy and paste these resource IDs from the Settings UI:
"roleDirection": true, false
  • Determines the direction of the edge; is it the role or co-role.
  • This setting is mandatory.
  • You can pick one of the following values:
    • true: The edge is traversed from head to tail.
    • false: The edge is traversed from tail to head.
"style": "arrow", "boxed", "boxing"
  • Determines how edges are displayed.
  • This setting is optional.
  • You can pick one of the following values:
    • "arrow": The edge is represented by an arrow. The arrow starts at the 'from' node and ends at the 'to' node. This is the default setting.
    • "boxing": The edge is represented as a 'from' asset that boxes one or more 'to' assets. In other words, a head asset contains one or more tail assets.
    • "boxed": The edge is represented as a 'from' asset that is boxed by a 'to' asset. In other words, a tail asset contains one or more head assets.
"label": "Groups"
  • Determines the name that is displayed on edges in the diagram.
  • This setting is optional.
  • If you do not specify a label, the role or co-role of the relation type from the operating model is used, in both the diagram view and the diagram.
    If "roleDirection" is true, Collibra uses the role, if it is false, it uses the co-role.