Overview
References define the relationship between components. Well-defined references provide clarity into how elements of your organization are tied together and form the basis for uncovering insights into making organizational improvements.
References have a source component and a target component. In the example below, the Person component and the Organizational Unit component are connected together with the Belongs To reference β indicating that, in other words, that a person belongs to an organizational unit.
A component can have multiple source references and destination references β both of which are necessary for creating complex metamodels. For example, in the Application Rationalization metamodel, the Application component has 5 incoming and 5 outgoing references.
For a video walkthrough of references, take a look at our video guide to references.
Reference Types
By default, Ardoq has a generic built-in reference type called an implicit reference. It is intended to specify that two components are related in some way, but it doesn't make their relationship explicit. We don't recommend using implicit references unless you intend to make the reference explicit later.
Instead, we recommend creating re-usable references that clearly establish a relationship between components. For example:
Person Owns Application
Person Reports to Person
Application Runs on Server
Once a reference type is created, it can be re-used throughout the workspace it was created in.
Creating References
There are a number of ways to create references between components within Ardoq:
From the sidebar in Workspace view
From the Grid Editor
From the Tabular Importer when using an out-of-the-box integration
From the Ardoq REST API
Create References Directly in the Navigator Sidebar
By hovering over the source component you want to start the reference from, you will see a "link" icon showing on the right side. Click it once (do not hold it), and drag it to the component you want to target , then click again.
If you need to open a Parent to access child components after you clicked on the source component, just right-click.
This will open the Reference tab on the right side. You can then choose the right reference and additional information if necessary.
Create Multiple References At Once in Ardoq
This is how you create multiple references at once:
Bulk select components in the navigator (hold down shift or control/command while clicking).
Click the link icon on one of the selected components.
Select whether the references should be incoming or outgoing.
Edit details for all references.
Using the Grid Editor To Create References
As you might be using the Grid Editor to create new components, you can also use this for creating references.
First, open your Grid Editor at the bottom of the page:
Choose References and adjust window:
Start creating new references or change existing ones in the Grid Editor by choosing Target components and Source. As with most functions in Ardoq, be aware that what you see and can choose from is context-sensitive. You will only see the components from the workspace you are standing in, and the level of components that you are standing in.
Choose Workspace level for all Parents, and the correct Parent for the underlying children components:
Using the View Dependency Matrix For Making References
First, choose the View "Dependency Matrix", and open up the Workspace containing your Source Component(s). Then choose the Targets component(s) Workspace. The Target Workspace has to be opened as well.
Choose the kind of Reference you wish to create by clicking on the "On cell click" and choose between references already created for the Source Workspace. You will now be creating that reference when you click. The component left side will be the Source and the component showing at the top will be the Target.
If you clicked the wrong field, just right-click and choose Delete Reference.
Note
The parent-child relationship is not implemented as a reference but instead derived from hierarchy. As such, you cannot define parent and children components across different workspaces.