Article last updated on the 2nd of June 2026.
Contents
1. Introduction
The Relations module is used for creating dynamic relations related to roles between entities across a solution. This is especially useful when creating many-to-many relations and can be used to always have an overview of relations between entities and personnel.
Administrators can set up specific relation types e.g. Lawyer and/or Client, and relation pairs, such as Lawyer <--> Client. Relation pairs always requires a setup with two relation types which must both be unique. Setting up a relation enables users to quickly navigate to and from entities which have some relation to each other.
Permissions can also be set up in such a way that only specific people can see certain relations. This is referred to as "Security trimming".
Relations can be set up to be displayed in a webpart on a WorkPoint page.
2. Configuration of Relations settings
Setting up and configuring the Relations module in a WorkPoint solution is done through the WorkPoint Administration, which can be accessed by following these steps:
- In your WorkPoint365 solution click the "Home" button in the upper left corner of the page.
- In the bottom of the side panel, click the gear icon to open the WorkPoint Administration.
From the WorkPoint Administration, follow these steps to access the Relations Module settings:
- When on the WorkPoint365 administration, click the “Relations” button in the left navigation menu.
- Click to either enable or disable security trimming. Security trimming makes it possible to control which people can see which relations. Security trimming introduces a minor performance impact when loading relations. This should therefore only be used when necessary.
An example of the use of security trimming could be users A and B who have access to a project. Users B, C, and D also have access to a company. In this example, only user B can see a relation between the two entities.
The relationship can be exemplified as in the following image:
- On the “Relation settings” page there are two tables: One for “Relation types” and one for “Relationtype pairs”
- Add the relation types that you might use. An example of a relation type could be “Lawyer”, “Client” or perhaps “Partner”. Relation types added in the left table will automatically be available for use when you add a “Relationtype pair” in the right table.
- Add some relation type pairs based on the relation types you just added. These relationtype pairs define the kind of relationships that can be formed between business module entities (eg. Companies, Projects or others)
- When satisfied with the setup, press the “Save settings” button below the “Relationtype pairs” table.
3. Setting up processes for creating relations
When you have defined a set of relation types and relation type pairs, you can start setting up WorkPoint Automate processes to actually facilitate creating relations between entities in your WorkPoint solution.
You can read more about how to create such processes in this article.
Once you have set up the necessary processes for your setup, you can set up My Tools buttons to run these processes.
5. Adding the Relations webpart on a page
Relations can be shown in WorkPoint 365 with a specialized webpart for the purpose. This webpart is called the "WP365 - Relations" webpart.
The webpart can be set up in the following way:
- When editing a page, click the "+" button to add a new webpart.
- Search for a fraction of the word "Relations".
- Select the "WP365 - Relations" webpart from the list.
- Click the "Edit" button to configure the webpart.
- Provide a title for the webpart.
- Click the "Relation types" field to select which relations to add to the webpart. From here, you can select from the types of relations that are configured on the solution.
- Toggle the "Show inactive relations" checker to make the webpart hide or display inactive relations for the entity.
- Toggle the "Show relations in grouped list" checker to make the webpart show relations as a plain list or as a grouped list.
- Use the Hide options to hide delete, edit relation, and edit entity options from the pop-up when relations are selected in the webpart.
- Select which columns should be shown for each relation in the webpart. The checkboxes can be used to show or hide the columns, and the number selectors can be used to order the columns from left to right.
- Select a business module to add additional columns from. Only one business module can be selected. In this example, the webpart is showing relations between projects and organizers - in this case a company. Therefore, we use the "Companies" business module to be able to show additional columns from the company related to the project we are currently located on.
- Optionally select a MyTools button configured on the business module selected in pt. 10. This button will appear in the pop-up displayed when a relation is selected in the webpart, giving you easy access to functionality on the relation.
- Select which columns to add from the selected business module. In this example, we add the Site icon which allows us to go directly to the site of the related company, and the company ID.
- Use the checkers for the additional columns to show or hide them. Use the number selectors to order the columns from left to right.
- Click the "Republish" button. If this is the first time publishing this page, the button will simply be called "Publish".
The result is a webpart like this. Note that we have re-ordered the columns to show the site icon and the company ID as the 3rd and 4th columns.:
Note that sizing of columns are cached. This means that if you change the horizontal size of the columns by dragging, the new size is saved, and appears the same next time you visit the webpart. Resizing a column is shown in the image below.
Clicking the title of a relation opens a window displaying meta data from the related entity. In the following example, a relation has been created between a project and a contact person:
Note that the fields shown in the pop-up window are defined by the default view of the list of the related entity. If you wish to change the fields shown here, you will need to change the default view of the list.
6. Security trimming
As previously mentioned, security trimming refers to who can see relations between entities. The concept is illustrated in the image below:
In this example, there are two entities; a project and a company. Some relation exists between these two entities.
Person A only has permission to view information for the project, and persons C and D have permission to view only information about the company. Person B has permission to view information about both the project and the company. The relation between the project and the company is therefore only visible to Person B while invisible to persons A, C, and D.
Please note that you should only enable security trimming if you have configured some security settings on your solution. Also note that enabling security trimming has a minor impact on performance when loading relations.
Security trimming can be enabled from the Relations Module settings page:
Comments
0 comments
Article is closed for comments.