What’s new in Hume 2.24?

We are proud to announce the release of Hume version 2.24.

GraphAware Hume is an intelligence analysis solution. It represents your world as a network of interconnected entities, builds a single view of your siloed intelligence holdings, and brings powerful, user-friendly, machine-assisted link analysis capabilities to end users.

Hume 2.24 introduces:

Action Boards

All intelligence, unified on one board. 2.24 introduces the capability of creating customisable dashboards with Action Boards. Users can view graphs, maps, tables, HTML elements and charts on a board. In addition, they allow users to have a unified view of information from within the graph and from external sources. This capability allows users to integrate documents from external sources or view information that may only be allowed to query on the fly.

Action Boards can display a wide range of data and can be used for various use cases. They can display all information about a single entity (such as a person’s profile), allowing analysts to easily see all important information on a single subject in one place, without looking for it in Visualisations. Alternatively, Action Boards can display information related to a specific use case, such as an investigation overview showing the main entities related to the investigation or the latest changes made to related entities, etc.

Improved Usability of Visual Queries

Version 2.24 continues to bring significant improvements to the usability of the Advanced Expand feature and query builder interface. Making this powerful tool more intuitive is crucial for unlocking its full potential to end users.

Input Case Transformers

Neo4j text operators are case-sensitive, and often values in the database are stored in a certain case. To avoid users having to memorise the exact case of the value in the database, it is now possible to configure the Input Transformer. The Input Transformer allows you to configure a mask for attributes which will turn all of the user’s inputs into the chosen case. Therefore, if a user enters “John Smith” into an Advanced Expand filter or in Graph Editing, and a capital case input transformer has been applied on the name attribute, the query will return results for “JOHN SMITH”.

Hide Attributes from Search and Advanced Expand Filters

It is now possible to exclude attributes from the Advanced Expand filters and Fine-Grained Search. Often, computed attributes or item IDs are not relevant or available for searching. They can now be configured as non-searchable, thus making sure that they cannot be selected by users.

Expanded Action Capabilities

In this release, we continue expanding the capabilities of Actions with several new action types.

Utility Scope

2.24.0 introduces a new action scope called Utility. Actions with this scope are only visible to users with admin or action creation privileges and are hidden from end users without these permissions. The Utility scope is intended to be used as a scope for programmatic actions which are not meant to be run manually by the end user. These actions can be run from Action boards, URLs (such as a temporary visualisation URL), GraphQL API, and can only be run from the side panel if the user has the appropriate permissions.

Utility actions can be used with:

• Action boards - some actions used in board templates may not make sense outside of action boards.
• Temporary Visualisation URLs - temporary visualisation setup actions that should not be visible to end users.
• GraphQL API - some actions which can be run from the GraphQL API are not meant for a visualisation but are instead just data queries.

HTML Return Type

The HTML return type is a dedicated HTML action which renders dynamic HTML content. It disregards the Allow HTML Rendering Knowledge Graph setting, but respects the URL security settings.

The HTML setting allows for various use cases, especially when paired with Action Boards, and can return information from internal or external sources. For example, HTML actions can be used in an action board which creates a profile view of a single person. The organisation’s security rules may prevent users from having stored images of the person. The HTML action can return an image from an external source and display it in Hume, letting users have a complete view of all information on the person in question.

Action developers can benefit from the power and flexibility of HTML and CSS styles to create ad-hoc representations of the action data.

Pattern Scope & Return Type (Beta)

In this release we are introducing the pattern action scope and return type. This feature is currently in beta.

The pattern scope allows users to run actions from the Advanced Expand panel, while the pattern return type allows actions to dynamically generate a pattern and open the Advanced Expand panel with it.

The pattern action scope and return type allow for several use cases such as saving Advanced Expand patterns, loading saved patterns, and creating a new alert from a visual Advanced Expand query.

Other Improvements

• Custom URL Schemes - It is possible to configure schemes other than http/s as clickable for URL attributes. This allows admins to configure alternate schemes such as ftp, mailto, or custom application schemes for Hume to render as clickable links.

• Orchestra HTTP Components - It is now possible to specify which HTTP error codes produce a failure in Orchestra HTTP components. Errors which do not produce a failure will produce a message with an empty HTTP response and error code header. Thus, such errors returned by external APIs cannot stop the workflow.

A detailed description of changes is available in the Hume 2.24 release notes in the documentation portal.