What’s new in Hume 2.15?

Danica Stankovic Dimitrios Stamatis

by Danica Stankovic & Dimitrios Stamatis
· 3 min read

We are proud to announce the release of Hume version 2.15. This release introduces several new Hume features, as well as Orchestra features and Amazon SQS support.

In Hume 2.15 you can:

  • Set user session expiration for added security.
  • Edit and delete styles created by other users.
  • Added Amazon Simple Queue Service (SQS) support.
  • Read and modify Orchestra workflow context from within components.
  • And many more improvements!

Define User Session Expiration

Now you can set session expiration settings in Hume. With the new Hume admin settings, you can define the length of time before a user is logged out due to inactivity, as well as whether and when a warning notification should be displayed to the user informing them that they will be logged out. Users are considered active if they perform mouse movements (including scrolling) or keystrokes in Hume.

Overwrite and Delete Other User’s Styles

In this release, we are introducing a new set of permissions that grant users the ability to change other users’ styles. Previously, users could modify a style created by another user and save it as a new style. Now, when assigned the new permissions, users can overwrite and save another user’s style or delete the style in question. By default, EXPLORER sub-roles do not have these permissions assigned, while MANAGER And ADMINISTRATOR sub-roles do.

Amazon Simple Queue Service (SQS) Support

With this release, we introduce support for the popular Amazon Simple Queue Service. Now you will be able to connect to your Amazon SQS from within Hume. Using our newly crafted components (SQS Consumer & SQS Producer) you can read and store data directly to your Amazon Simple Queue Service.

Orchestra Workflow Context State

Workflows now benefit from a global contextual state that can be updated/queried and reacted upon using specific Orchestra components. We have also created a new component called “On Context Value Change” (available under the Monitor group) which can be used specifically to monitor workflow state changes.

Various Improvements

Improved TABLE Actions

Results for actions with the return type TABLE have now been improved. Now, the result window displays all columns in the results and allows for horizontal scrolling if there are many columns. In addition, columns are displayed alphabetically, and HTML rendering is allowed if enabled in the knowledge graph settings.

Improved Colour Picker

We have improved the colour picker, which is available in the schema and in visualisation styles, to be more accessible to users with accessibility limitations. The colour picker palette now supports the 508 standard and a contrast ratio is displayed for each colour value. The contrast ratio displays an X symbol if the ratio falls below the 3.1:1 contrast ratio (graphical elements). In addition, the colour palette now has more space between values to make it easier to distinguish them. Finally, hex colour codes, and icon names can be copied to the clipboard to make it easier to use them elsewhere.

Hume API (Beta)

In this version, we have added API support for Styles and Grouping Strategies. Alerting support has also been added but remains experimental in this release.

Orchestra Improvements

Neo4j Writer Cypher Query

The Cypher Query can now be specified directly into the Neo4j Writer component, easing workflows when there is only one branch writing to Neo4j.

Message Timestamp Display

You can now see at what time a message was processed in the component message view.

Show Workflow Elapsed Time

The Orchestra UI now shows how long a workflow has been running for.

Further sources of knowledge

If you’re interested in learning more about how graphs and Hume deliver high value solutions…

Read our blog to find out how you can Optimise Logistic Chains with Hume.

Learn more about Data-driven Orchestration with Graphs.

Or read this introductory blog to Understand the Power of Graph Visualisation.

Share this blog post: