Why not all relationships are visible on the Portal

How relationships are handled in versions

When you create a version, Mavim includes:

• All topics explicitly selected in the version definition.

• All relations from those topics, but only one level deep for topics not included in the version definition.

This means second-level relationships (links that originate from a topic that is only indirectly included) won’t appear on the Portal.

Example scenario

Let’s look at a practical example:

1. In the process After sales meeting (under Move into house), a hyperlink is created to the process Complaints (under Improve).

   

2. The process Complaints has a field relation to Joe Fonda.

   

3. You create a version for Move into house, which includes After sales meeting.

In this version:

• The link from After sales meeting to Complaints is visible (it’s a first-level link).

• The field relation from Complaints to Joe Fonda is not visible (it’s a second-level link).

You can confirm this in the version view:

• The process Complaints appears under External references, which lists all first-level links not directly included in the version definition.

  

• Since Complaints isn’t explicitly part of the version, its relations (like the one to Joe Fonda) aren’t included on the Portal.

How to make all relations visible

To make deeper relationships visible:

1. Open your version definition.

2. Explicitly include the related topic (in this example, Complaints).

   

3. Save and republish the version.

Once included:

• The Complaints process and its relation to Joe Fonda become first-level links and visible in the Portal.

  

Note: Including the topic explicitly means it will also appear in the Portal’s tree structure, which may not always be desirable.