What’s new in Hume 2.17?

We are proud to announce the release of Hume version 2.17. This release introduces new functionality in both Hume Core and Orchestra.

Hume is an enterprise-level graph analytics solution that allows you to easily convert multiple distributed data sources into a single, connected source of truth: the knowledge graph.

Hume 2.17 introduces:

• Create, edit and delete data with Hume Graph Editing.
• Dynamically hide and show items on the visualisation canvas using Hume Filters.
• Enable and disable Orchestra components; designing and debugging workflows has never been easier.
• Track changes and restore previous versions of your Orchestra workflows.
• And many more!

Create, Edit and Delete Data with Hume Graph Editing

Hume 2.17.0 introduces a new key functionality: Graph Editing. The feature allows for user- and machine-driven graph editing capabilities. Graph Editing allows you to:

• Create, Edit and Delete Data - Hume Graph Editing lets you make changes to data in the database directly from Hume, through visualisations or via API. You can create new nodes and relationships, or edit and delete existing data.
• Review Changes Before Publishing - Saved changes can be reviewed before publishing. Visual cues help you distinguish staged changes with highlighting to show newly created, edited and deleted items.
• Conflict Detection and Resolution - Hume Graph Editing will alert you to changes made to your staged items. If another user publishes changes to an item you are currently editing or have previously edited, Hume will alert you to the conflict.
• Configure Graph Editing Scope - It is possible to configure Graph Editing forms which allow managers to define attribute visibility and editing possibilities.

Hide and Show Items Using Hume Filters

Hume 2.17.0 welcomes the first iteration of the graph filtering functionality. Filters allow you to dynamically hide and show items on the visualisation canvas and allow you to:

• Display items on the canvas by category: Items can be filtered according to node class/relationship type, or attribute value.
• Select items based on filter categories: Make a selection of all, some or none of the attribute and class values on the canvas with the use of the category selection button.
• Integrate seamlessly with other visualisation tools: Filters are compatible with grouping as well as geospatial and temporal analysis.

Other Hume Improvements

• Define a Global Style Rule: A new option in Styles allows you to set a global style for node classes or relationships, which then affects all entities of that type.
• View LARGE_TEXT Excerpts in the Properties Panel: Long text excerpts are now visible in the properties panel. A new properties option allows administrators to define how long the excerpt can be.

Track Changes and Restore Previous Versions of Orchestra Workflows

Hume 2.17 introduces Orchestra Workflow History. Changes to your workflow version can be made with a simple click of a button. With workflow history you can:

• Track Workflow Changes: Changes made to components, links and workflow status appear in the Orchestra History panel.
• Restore Previous State: Restore a previous version of your Orchestra workflow without losing any of your changes.
• Name Versions: Name your workflow history entries for ease of use.

Enable and Disable Components in Orchestra Workflows

Orchestra components can now be disabled and re-enabled within workflows. Disabled components act as a pass-through element and keep their configurations. Enabling and disabling components is particularly useful when designing and debugging workflows.

Other Orchestra Improvements

• Neo4j 5 Compatibility: All Hume modules are now compatible with Neo4j 5.
• Orchestra Clustering: Orchestra can now make use of multiple instances for failover scenarios.
• Python 3 Support (Experimental): We have extended Orchestra capabilities to include Python 3 support. This feature is still considered experimental.
• Orchestra Performance Improvements: In this release we have made numerous improvements in CPU and memory utilisation during workflows.