Wrapper link type

Wrapper link types are used to represent existing or predictable links (e.g. project – project leader) in the Vertec model. This is about making an already existing connection visible on the interface.

If you want to create connections that do not exist by default in the Vertec model, create a Custom Link type instead.

Wrapper link types perform two tasks:

• Existing wrapper link types can be modified. For example, if you do not want to work with activities in Vertec, the corresponding wrapper link types can be deactivated and lists no longer appear on the interface.
• New wrapper link types can be created to show the user information in the right place. For example, you can create a wrapper link type that allows the project leader to get an overview of the activities of their active projects.

Here is an example of a predefined wrapper link type:

In a link type, the behavior of the two sides (roles) of the link must always be defined, so the window essentially consists of the two parts From and To, which define the two sides of the link type.

Field	Significance
designation	The designation entered here will be displayed on the interface for this role. In this example, the so-called link container shows own projects:
Sequence	Here you can specify the sort in the tree. Vertec sorts the link containers in ascending order. If nothing is specified, the containers are sorted alphabetically. The order can also be edited in the Standard line.
Icon	Here you can specify the icon that the container should show.
Class name	Name of the entry type (class) of this role. Can be assigned via the selection field.
Linkmember	See separate section Linkmembers below.
Expression	Specifies how to get to this end, looking from the other side. In the example, the project user (class name in To) navigates to projects with the expression ownprojects->select(active). As you can see, more complex expressions can also be used here.
Container class	Instead of the standard wrapper link container, specific container classes can be specified depending on the class. A list of container classes can be found here.
'new’ Menu	If this option is selected, the option to create a new entry and link it immediately appears in the New menu. Please also note the section about link members.
Show containers	If this option is checked, a container (subfolder) will be displayed as soon as links are present. It may be useful not to display both sides for some links, then this option can be deselected for a role.
Always show containers	If this option is selected in addition to Show containers, the container is always shown, regardless of whether links exist or not. An example of such a role is the list of open services on project users. The container for invoices on project, however, is not shown until invoices are available. For this role, this option is not selected. Especially with links to users, it makes sense to always show containers. Otherwise, Vertec always has to check whether the container needs to be shown or not, which can have an impact on performance.
Expandable	Vertec 6.7.0.17. If this checkbox is deactivated, the folder in the tree cannot be opened.
active	Only active link types are displayed on the interface. An existing wrapper link type can also be disabled with the Standard line.
Allow links	With this link type new links can be created between entries by Drag & Drop. Please also note the section on link members.

Sometimes you have to work with complicated expressions, expressions that filter or go through several levels. If a link type contains an expression that consists of more than just the member, a link member must be specified. This has the following features:

• If the Allow links option is activated, Vertec needs the link member to know to which member it has to link the entry when linking two entries via drag & drop.
• If the option 'New’ menu is set, Vertec needs the link member to know with which member to link the entry when creating a new entry.
• This means that the link member must be the association to which the “counter-entry” is attached. A single member (field) cannot be a link member (see example below).
• Permission check: The link type uses the link member to determine whether the container should be shown and whether new links are allowed or not. The link member must therefore be set to something for which the corresponding users have permission. When checking whether the link should be shown, the read permission is checked, while when determining whether new links are allowed, the write permission is checked.

  In such cases, if no link member is specified or if the user is not authorized to do so, the link is neither visible to the user nor can it be set. The link is then only visible to administrators.

In this example, the lower part of the link type is a complicated expression projectActivities->union(activities). In order for Vertec to know which member it is, projectActivities is specified as the link member. This means: If an activity is dragged and dropped onto a project and Role: Activities is selected, then the project is assigned to the activity as a project:

The link member always refers to the view from the other side. In this example, this means project.projectactivities.

Another example is Rechnungen auf eigenen Projekten. The expression eigprojekte.rechnungen is not shown to non-project administrators if the link member is not set to something readable.

For example, eigprojekte can be used here. If the user has (read) permission on it, the link will be shown on the interface. The link member no longer matches the result (an invoice is not part of own projects). A link cannot therefore be made directly, the option Allow links must be deactivated on such a link type.