Search in all information in the workspace

Because Relatics works in a consistent way, end users become quickly accustomed and it allows them to find information at the place where they expect it. In some cases, it is difficult for end users to find information. This is the case when they don’t know what type of information (e.g. requirements, system objects, activities) they are looking for. The solution is to create a generic search query for end users, in which the power of parameters and constraint queries are combined. In this article, I explain how you can configure this yourself in Relatics.

Configure a query that searches in all instances

In Relatics it is possible to create a query that searches in all instances. This means, searching in all instances of all types that are part of the information model of the project. Below you can find an example of a query that I like to apply:

01_relatics_search_query

The root element uses four constraint queries that I will further explain below.

The Constraint Query Non_System_Instance enables that all instances appear in the search result that are part of the information model as configured by the project. This excludes all system instances. You can achieve this with the following constraint:

Example Constraint: Only show instances that are part of the project information model

Object.IsSystem = 0 and Object.InformationLevel = ‘Instance’

With the Constraint Query Name_Description, the parameter ‘Search’ is applied to the attributes ‘Name’ and ‘Description’. These are commonly used attributes in the visualization. Of course, you can configure yourself in which attributes to search. Example of a constraint:

Example Constraint: Search in the attributes ‘Name’ and ‘Description’

Object.Name Like @Search or Object.Description Like @Search

The Constraint Query Property_Value searches in a similar way in the attribute ‘Value’ of all the properties. Again, this is a frequently used attribute. Example:

Example Constraint: Search in the attribute ‘Value’ of a property

Object.Value Like @Search

The Constraint Query MiddleElement is used to exclude Middle Element constructions. I chose this, because Middle Elements often don’t contain important information. Usually, a Middle Element also doesn’t have a detail page. Of course, you are free to apply this or any other restriction.

The end result

When an end user enters a search term, all instances are displayed in the table on the left-hand side. An additional column ‘Type Name’ provides more context to the user about the found information. By clicking on an instance, the end user can find the details on the right-hand side. This is really an ideal and accessible way for an end user to find information when the context is unknown.

02_relatics_search_results

About Kris de Waal

Relatics Portret-120

After graduating in Business Administration with a specialization in Business Information Management, Kris joined Relatics as a Business Information Consultant. He is eager to learn about new concepts, technologies, IT systems and apply the knowledge in his daily work. In addition, Kris loves to work on new ideas and innovations to get more out of Relatics.