Page tree
Skip to end of metadata
Go to start of metadata

Support for "OR" in IQL

IQL now supports "OR" which adds a lot of power to the Insight platform. This is an example of an IQL:

"Partner Level" = "Platinum" OR "Service Agreement" IS NOT EMPTY

VideoInsight 5.5 - Support for "OR" in IQL


Inheritance support for Import modules

The import module engine now supports configuration of inheritance structure. This means that you can point different parts of the source/data to different child object types by configuring an IQL.

Let's imagine that you have a CSV file with a lot of servers and one column in the CSV file is "Vendor". You can then create an inherit structure in Insight with "Server" as parent, and different child object types for each vendor like (Apple, Microsoft, Dell, etc). And by IQL point the source to the different object types by IQL:

Config for objectType "Apple"

objectType = Apple

Config for objectType "Microsoft"

objectType = Microsoft

etc etc

All data that's not configured for a child object type, will be added to the parent, but you have the possibility to configure a child object type with an empty IQL that will be the default child.

VideoInsight 5.5 - Inheritance support for import modules


Improved custom fields

We have improved all custom fields to support filtering on any attribute. The default is the "Label", but you can change or add any attribute to be available for search. We have also changed the custom fields to filter objects on "like" instead of "startsWith" as we have had up til today.

Example:

Filtering with "like" where any characters in the attribute to search will be in consideration:

Example:

We have selected "Label" and "Role" to filter on and in this case we find objects from the "Role" attribute.

Video: Insight 5.5 - Improved custom fields search


Improved Insight Attribute Filtering

We have improved filtering of referencing objects in Insight attributes to support "like" instead of "startsWith" as we have had up til today.


Restriction on reference usage

With the "OR" support and an improvement of the place holder support we can now support uses case like "IP Address management" or any relationship where you want more like a "check out" strategy. One use case is when you have a servers and IP Addresses, and you want to make sure that only one server can use the same IP Address. This is the IQL to configure for the "IP Address" attribute on the Server object type:

object not having inR() OR object having inR(Key = ${Key})

This will make sure that you only can select an "IP Address" that not have any inbound references except the one that is set to the specific server.


Improved placeholders support

For any placeholder we have improved it to support retrieving the id or label on placeholders representing objects. The pattern is ${placeholder.id} or ${placeholder.name}. This means that you are able to filter on f.ex Issue type names, users display name, etc. This is supported for both internal JIRA fields and custom fields.

This is an example of an IQL with placeholders:

Organisation = ${customfield_12345.name} AND "Issue Type Id" = ${issuetype.id} AND Description like ${summary}

Read more about this here: Insight with Placeholders#CustomField


IQL

We have added the IQL function "having user" that will give you objects that have users or groups that a specified user/s belongs to.

Examples:

"Group/s" having user("admin")
"Group/s" having user("currentUser()")
"Group/s" having user("currentReporter()")
"User/s" having user("admin")
....

We have deprecated some IQL functions:

  • connectedJiraIssues in favor for connectedTickets
  • jiraGroup is favor for group


Other fixes

  • Referenced fields supports filtering from different objects schemas than the parent field configured schema.
  • We have been working on decreasing the memory utilization, both from an Insight index perspective as well as during import synchronizations.
  • Placeholders in Jira transition screens are now fixed and supported.
  • Minor fixes

Before upgrading to Insight 5.5

Upgrade from Insight 4.x

We strongly recommend that you review all your import configurations after you have upgraded to Insight 5 from Insight 4. 

If your installation of Insight is configured with an Insight Discovery import you will have to do the following after you have installed Insight 5

  1. Download and install version 2.x of Insight Discovery from Marketplace
  2. Navigate to your Object Schema where your Insight Discovery import is configured and press Migrate Configuration
  3. Verify the migrated import configuration

If your installation of Insight is configured with a Tempo Account import you will have to do the following after you have installed Insight 5

  1. Download and install Insight Tempo Integration from Marketplace
  2. Navigate to your Object Schema where your Tempo import is configured and press Migrate Configuration
  3. Verify the migrated import configuration
  • No labels