Fallback page for elements without detail presentation

As the administrator of a Relatics environment, you want users’ information needs to be satisfied as good as possible. At the same time, Relatics offers configuration flexibility so that in some cases, users may request a detail page of an element that doesn’t exist. Examples are detail pages of statuses, types, etc. In such a case, users are usually presented with an error message. This article explains how to configure Relatics to display a fallback page (similar to the ‘404’ page) instead of an error message.

Creating the presentation of the fallback page

Step 1 of setting up a fallback page is to create a presentation. This can be made in Workspace Studio under the Presentations menu item.

1 - Fallback Presentation - Create

After creating the presentation, it is important to configure Relatics such that the presentation is used to display elements that have no distinct presentation. To do so, on the Presents tab of the detail page of the presentation, select Element in the table Primarily presents one instance of:

2 - Fallback Presentation - Setting

You have now created a detail page that will be displayed in case an entity does not have its own detail page. The next step is to add content to this detail page.

Adding content to the presentation of the fallback page

Step 2 of setting up a fallback page is to add content to the presentation, such that the most relevant information is displayed in a generic fashion. I do so using three tables:

  1. A table that displays name, description and type;
  2. A table that displays all entities that are related through an outgoing relation;
  3. A table that displays all entities that are related through an incoming relation.

Query structure of the tables:

4 - Fallback Presentation - Query 1 7 - Fallback Presentation - Query Outgoing 6 - Fallback Presentation - Query Incoming
(1) (2) (3)

Table 1 has a query composed in accordance with (1). Typical for this query is that the second node in Join reads as follows: Parent.ConfigurationOfRef=Object.ID. This is how the type of an instance is to requested the type in Relatics.

5 - Fallback Presentation - Join 1

There are no particularities for the queries of tables 2 and 3. All queries can be viewed by downloading the RCS file at the end of this article and uploading it to a Relatics environment.

In additional to the three described tables it is generally advised to add a notice at the top of the detail page that makes it clear to the end user that a generic detail page is displayed. The content of this notice can be determined at will, and is easy to create with a Text Fragment.

Final result

After performing the steps above, the final result could look like this:

8 - Fallback Presentation - Result

About Frank Keizer

Relatics Portret-66

After finishing his studies Business Economics and Electric Engineering, Frank worked at an engineering company as a Systems Engineering Consultant. Nowadays he works at Relatics as a Business Information Consultant. Frank has a passion for implementing IT solutions that are optimized for end-user experience. Frank’s basic principles are: pragmatic use of Systems Engineering, optimizing for end-user experience and facilitating a learning organization.