Release notes
14.4.2
Improvements
-
Provided clarification on configuring
server.defaultRoute
andkibana.defaultAppId
settings. -
Added an option to enforce text parsing for specific columns when importing from a CSV file. This resolves the issue where leading zeros were removed, even when columns were mapped as text or keyword.
-
Added the ability to install plugins from URLs with self-signed or invalid SSL certificates.
Bug fixes
-
Fixed an issue where the field selection was enabled for EIDs when creating or editing a relation.
-
Fixed an issue where it was not possible to delete a dashboard after removing visualizations.
-
Fixed an issue in Global Search where searching for multiple words did not work correctly for keyword fields.
-
Fixed an issue where the relations tab was not rendered for more than 100 relations.
-
Fixed an issue where filters could not be renamed when using the DSL query editor.
-
Fixed an issue where it was impossible to sort a list of visualizations by their type and the pagination was broken.
-
Fixed an issue that prevented saving
visualization:tileMap:WMSdefaults
in Advanced Settings in certain cases due to an incorrect validation. -
Fixed an issue where no visualizations were displayed on the dashboard page after deleting a visualization.
-
Fixed an issue where expansion options would not be saved with the saved graph.
-
Fixed an issue where edges would overlap with node labels and bullet points.
-
Fixed a validation issue where the usage of
siren:joinTaskTimeout
was disabled. -
Fixed an issue where invalid complex join filters caused an endless migration loop.
-
Fixed an issue where the timebar in the Graph Browser would not reset when the graph selection was changed.
-
Fixed an issue where switching to map mode in the Graph Browser shrank the icon size of group nodes.
-
Fixed an issue where a dashboard filter applied from a record table that inherited data from a parent search did not display the filter label.
-
Fixed an issue where the exported nodes with i2 would not have the associated
dateTime
fields even if set on the mapping.
Security fixes
-
Upgraded NodeJS to version 20.18.0. For more information, see: https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md#20.18.0
-
Enhanced validation for Investigate Access Control APIs to mitigate the risk of Regular Expression Denial of Service (ReDoS) attacks.
14.4.1
New features
-
Added the SirenAPI methods
dataModelEntity.getIcon()
anddataModelEntity.getColor()
to extract the icon and color of aDataModelEntity
instance. For more information, see dataModelEntity.getIcon() and dataModelEntity.getColor().
Improvements
-
Improved the robustness and clarity of UI messages when custom dynamic filter types are removed.
Bug fixes
-
Fixed an issue where text box graph elements were shown in the Graph Browser table as extra rows.
-
Fixed an issue where the selection table filter would not consider edited values.
-
Fixed an issue where temporary dashboard filters were lost after switching dataspace.
-
Fixed an issue where local nodes were incorrectly included in the count. Now, only document nodes are counted as intended.
-
Fixed an issue where the total hit count was inaccurately displayed after adding a new record to the document table.
-
Fixed an issue where icons would not show up in the visualizations list.
-
Fixed an issue where deleting a relation in the data model would cause an error.
14.4.0
New features
-
Added a new UI-ACL-context to allow administrators to hide the global search input box.
-
You can now boost newer records in search results. You can configure the boost by time period in the data model and enable and disable the boost in the dynamic filters panel. For more information, see Boosting by record recency.
Graph Browser
-
Added the ability to copy and paste nodes, edges, and groups between graphs. For more information, see Copying and pasting.
-
Added the ability to select and style group edges.
Improvements
-
When cloning a dataspace, Sentinl watchers are no longer cloned by default.
-
The dynamic filters panel in Siren Search now opens by default at the start of each new session.
-
Introduced a new simple
api/health
endpoint to monitor Investigate process. For more information, see The Health API. -
The headers of Data Model tabs with errors will now be highlighted.
-
In the Graph Browser the Expand by Relations modal will no longer appear if there are no available relations for the selected nodes.
Breaking changes
-
Investigate no longer supports upgrading or importing backups from versions earlier than 13.2.0. If you have Investigate data from versions earlier than this, please upgrade to 14.3.x before upgrading to 14.4.0 or later.
-
The
createNotifier
service has been removed. If you are a developer and wrote a custom plugin using that service, you must update your plugin to use theNotifier
class instead. To do that, import theNotifier
class:import { Notifier } from 'ui/notify/notifier';
and use it in your code in the same way you used the createNotifier service:
const notifier = new Notifier({ location: 'Context' });
-
The
VisVisTypeProvider
factory has been removed. If you are a developer and wrote a custom plugin using that function to access theVisType
class, you must update your plugin to import theVisType
class directly instead:import { VisType } from 'ui/vis/vis_type';
-
Signatures of following internal methods changed and now require a mandatory id parameter:
SpyModesRegistryProvider.register(spy) -> SpyModesRegistryProvider.register(spy, id) VisTypesRegistryProvider.register(vis) -> VisTypesRegistryProvider.register(vis, id) SavedObjectRegistryProvider.register(obj) -> SavedObjectRegistryProvider.register(obj, id) RegistryFieldFormatsProvider.register(formatter) -> RegistryFieldFormatsProvider.register(formatter, id) savedObjectManagementRegistry.register(section) -> savedObjectManagementRegistry.register(section, id) ManagementSection.register(section) -> ManagementSection.register(section, id)
Third-party plugins must release a compatible version if they use any of the above methods.
-
Jira Integration Update:
-
Jira is now supported using the new
jira.js
plugin, which replaces thejira_connector
. -
The following parameters are no longer supported:
-
jira_connector.strictSSL
-
jira_connector.rejectUnauthorized
-
jira_connector.basic_auth.base64
-
-
-
The logging for Investigate has been rewritten using the Pino library. While the human-readable output remains the same, the JSON output format has changed and may impact tools that process Investigate logs in JSON format.
-
Graph browser Text Box feature is no longer beta.
-
gForce layout for Graph Browser is now deprecated and will be removed in an upcoming release.
Bug fixes
-
Fixed an issue where the sidebar global list failed to display the unsaved status of graphs after reloading the page.
-
Fixed an issue where dashboards were removed from their groups after Investigate was upgraded.
-
Fixed an issue where dataspaces could not be properly cloned when the source dataspace did not have metadata objects.
-
Fixed an issue where resetting dynamic filters did not clear error message for date ranges.
-
Fixed an issue where the "Topic Clustering" visualization showed the wrong count when a text was entered into the dashboard search bar.
-
Fixed an issue that prevented selection from the "Sort on" dropdown for top hit aggregation in the "Metric" visualization.
-
Fixed an issue where the Jira plugin failed to export when a record table on the dashboard had NLP tags.
-
Fixed an issue that prevented dynamic filters from being applied when there was a text filter using an input mask.
-
Fixed an issue where changes to the Graph Browser side panels state could not be saved.
Graph Browser
-
Fixed an issue where arrow keys would not work in the edit label text box.
-
Fixed an issue where aggregated relations configured with a metric could result in an invisible edge on the graph.
-
Fixed an issue where edge counts would throw an error for documents with more than 200 values in join fields for older federate versions.
-
Fixed an issue where, in certain situations, exporting to image would return a zero byte image. From now if the underlying hardware does not support the default resolution, a lower resolution image will be generated.
-
Fixed an issue where lenses would not be applied when going from the search app to a saved graph.
Security fixes
-
Upgraded Node.js to version 20.17.0. For more information, see https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md#20.17.0.
-
Upgraded dompurify library to v3.1.6.