What's New in the Digital Hive 2025.1 Release
This articles details the new product features, enhancements, and resolved issues, that were included as part of the Digital Hive 2025.1 release.
Prerequisites
To move to this release, this must be a new installation, or you must have an existing Digital Hive 2.x installation. You can install over any fix level releases that were previously applied to Digital Hive.
New Features & Enhancements
Allowlist for upload file types
Organizations want to limit the exposure users have to possibly malicious files. In order to support that agenda, Digital Hive can restrict certain files from being uploaded to the Digital Hive application. When a user tries to upload a file type that is not part of the default allowed list, a json file for example, the user will receive this error message: Something went wrong: 1 files failed to upload. Invalid file type for upload.
By default, these are the supported file types that are allowed to be uploaded to the Digital Hive file system:
pdfdoc/docxxls/xlsxppt/pptxpnggifjpegjpgsvgtxtrtf
If a new file type is desired, or some existing ones need to be removed, the allowed file list can be modified by an Administrator.
- Launch the Control Center as an Administrator
- Go to Content -> Connectors
- Click on Advanced...
- Click on Advanced System Settings
- In the Advanced System Settings dialog, locate the Allowed file types for upload field
- To add an item, add a comma (,) to the last object and then add the new file type. In this example, .json was used
- To remove an item, delete the file type, including the period (.) and the comma (,) if necessary
- Press UPDATE to apply the settings
Now when the user tries to upload the .json file that previously failed, the file will now successfully be uploaded.

When a file type is removed from the list, the update prevents all future uploads of that file type. Existing files with that extension will NOT be deleted from the application.
Uploaded Content inherits parent folder permissions
When new content is added to a Digital Hive folder, it will now automatically assume the permissions of the parent folder.
Recursively set folder/file permissions
To facilitate better management of content security policies within the Digital Hive folder structure, it is now possible to make changes to the permissions of a folder and then push those changes to all objects contained within that folder.

Ability to override default description coming from the content system
Most Business Intelligence and/or Content Systems provide the ability to add a description to a report or artifact. These descriptions are visible by users through Digital Hive.
In some scenarios, the descriptions may contain errors, or not be descriptive enough for end users. To modify the description, it could be done in the source system, which may not be easily accomplished. Digital Hive provides privileged users with the ability to override the description from the source system.

Descriptions that are added or modified through Digital Hive do NOT alter the description in the source system. Changes in Digital Hive are persisted in Digital Hive and are independent of the source content system.

Only users that have the Set Custom Values or Manage Metadata Catalog capabilities granted as part of their profile can override the descriptions.
To modify the description of an object within Digital Hive:
- Open the Properties of an object
- Press the pencil icon that is related to the Description field

- Type in the new Description
- Press the checkmark to apply the update
Once the Description field has been updated, it will be immediately visible.

Custom descriptions can also be leveraged to provide multilingual descriptions for different locales.
In this release, multilingual support has been added for global tags, interests, custom field names, and descriptions. Similar to text fields and other Hive properties, multilingual support has been expanded to other widget types. Here is an example of creating a new global content Tag and then applying a French translation.
Notice that as part of the tag creation dialog, there is now a multilingual option, currently set to the system locale of EN (US). Clicking on that button will present a list of all available locales. Select French and then provide the appropriate string.
When viewing the Tag while in an English locale versus viewing with a French locale selected:
Similar to the Tags, it is also possible to adjust the locale strings for Custom Fields: titles, descriptions, and the display names.

Do not change the Values that have been set, these must remain in their original state. Only the Display Names need to be changed to reflect multiple locales.
When a user with a French locale is within Digital Hive, the extended metadata properties of an object would reflect the correct locale strings for the Custom Field Title and Display Name. Note that the custom description on the object, used in the previous feature example has also been translated.

Personal tags are still single locale based because there's no need to enter multiple languages for a tag only the user creating the tag can see.
Multilingual Link URLs
It is now possible to designate different click action URL's based on locale. For example, if there is a requirement to for users to be able to access an external website, but it is desirable to have the user open a language specific page, the different URL's can be configured within Digital Hive.
A Link widget is added to a Hive page, the Click Action is set to Open URL and then a destination URL, relevant to the current locale, is specified.
To specify a unique URL for a different locale, click on the EN (US) button, select the new locale (French in this example), and enter the locale specific URL. When a user with the French locale is using Digital Hive, the Link widget will direct the user to correct locale specific URL.

This feature is available for widgets that support a click action: Link, Button, Image, and Icon.
A lot of organizations leverage ratings and comments as a way to guide users to valuable and relevant content. Unfortunately, sometimes user comments can be inappropriate or not relevant to the content in question. Administrators can now delete undesired comments. Examining the properties of an item, Administrators will now see a trash can icon which will delete the corresponding comment.
One of the features within Digital Hive is the ability to create metadata tags that can be applied to content. These tags make searching easier and can also be used to categorize content or to drive visual cues that can be applied to objects.
It is now possible to export these tags, which includes the tag definition (including any multilingual locale translations that may exist) as well as the content to which the tags have been applied. This is a great feature for backing up the tagging that has occurred, or for moving tags from one Digital Hive installation to another.
To export/import the tags:
- Log into Digital Hive as an Administrator
- Launch the Control Center
- Expand Content and select Connectors
- Press the Advanced... link
- There will be two options there to either import or export the global metadata tags
Allow recursive setting of Custom Field values
In a previous version of Digital Hive, the ability to recursively set Custom Field values was introduced for users that were granted the Manage Metadata Catalog capability. In most organizations, there are non-administrator users that are responsible for assigning custom metadata values, so now in this release, users who have been granted the "Set Custom Field Values" capability, can also recursively set values.
Support for PowerBI Report Server
A new Connector for PowerBI Report Server was added to the growing list of supported content providers. PowerBI Report Server is an on premises version of Microsoft Power BI which requires different connectivity parameters as different API endpoints are leveraged.
'Lens' feature renamed to Unified Filters
To better align with market naming conventions, and to provide additional clarity for Hive authors, the existing Lens feature, which allows users to filter content across different analytics platforms, has been renamed to Unified Filters. The name change does not modify or invalidate any existing functionality that has previously been deployed.
Hide Unified Filters from filter Panel
In some scenarios, it is desirable to hardcode a value for a Unified Filter (previously Lens Filter) where users should not be able to modify the filter. For example, using a high level Sales report, the requirement is to have a unique Hive page for each product category. Although users would be able to edit filters for different dimensions, it is required that each page be bound to a specific product category. This could be accomplished by creating alternate versions of the report, one for each product category, which introduces additional burden on the report team, adds yet more content to an already taxed system, and can take some time to complete ... or a Unified Filter could be applied in Digital Hive.
Within the Unified Filter definition, there is now an option to hide the filter from the control panel. This essentially hardcodes the value defined in the Unified Filter and doesn't allow users to change it.
Selectively display Properties or Navigation Side Panel in Content Pop-up
Some Hive designs require simplicity, not only from an appearance perspective, but from a functionality standpoint. Some new options to promote simplicity allow authors to disable the side panels when users view content in the content viewer pop-up.
On the left hand side of the content viewer pop-up are navigation links to other related content. On the right hand-side, users can scroll across to gain access to different elements of metadata pertaining to the object. On the Catalog. and search page, as well as the File explorer, Content lane, Icon, Button, and Link widgets, either or both of these side panels can be enabled or disabled. Deselecting the checkboxes in the Content Launching section of the Properties, will hide both side panels.
Set the default value for a Date Custom Fields to today's date
Custom Fields are a great way to add consistent metadata fields and values to content across multiple content systems. There quite a few scenarios where date fields are required, and typically the date that needs to be supplied is today's date. For example, Content Reviewed Date, Certification Date, etc. In these scenarios, it is possible to set the default date to today's date. If metadata for an historical event is required, the user can still set that date. This is a convenience enhancement but also helps to ensure data quality and accuracy.
With these settings, when a user modifies the Custom Fields on an object, the date field will already be populated with today's date.
Author as a search facet
In addition to all of the different facets (filters) that can be applied to refine the search results within Digital Hive, this release now introduces the ability to filter the results by Author. Selecting one or more of these values will filter the search results to all content that has been authored by the selected user(s) (more specifically, the author that is listed as the latest user to edit the content).
The value for Author comes from the underlying source system. For example, here is what it looks like in the information flyout.

As the value comes from the source content systems, the format of the user name is controlled by those systems. If the format of user names varies from system to system, for example, email address in one platform and user name in another, the list in Digital Hive will show both. Although in theory they point to the same user, the values are unique and treated as such.
Define Search context
Search is a very powerful capability within Digital Hive as it allows users to locate content across multiple systems with one search operation. The challenge that users face is that if they've taken the time to navigate within the Folder Browser to a specific location and then search, the matching results from all content systems are returned.
In this new release, it is now possible to change the search context from 'everywhere' to current folder which will use the current folder as the starting point, and then search for content within that folder and sub-folders.
Set Hive favorites
As Digital Hive grows across an organization, more Hives are created. To help users quickly navigate to their preferred Hives, they can now 'pin a Hive' to their Hive selector menu. Much like marking certain Reports and Dashboards as favorites, Hives can be pinned to the top of the menu.
Here is a Hive selector that contains more than 4 Hives.
To get to the desired Hive, Marketing, the user could either scroll through the list, or refine the results by typing in the Hive name.
Hovering over the Marketing Hive, a pin is displayed.
Pressing this pin will place the Hive at the top of the menu in future sessions. Notice how the 'pin' overrides the alphabetical display of the Hive names.
Track when users download artifacts
To help monitor how users are interacting with content, Digital Hive no provides the ability to determine what content is being downloaded, when it was downloaded, and by whom. Auditing download activities is part of the core platform so nothing needs to be enabled/disabled for this feature. Audit records for user download activities can be found in the theia_audit_ui_interactions view and the operation name would be Download Artifact.
In this example, the user MK3\u000001 downloaded two Sharepoint Online artifacts on January 20th, one PDF and one HTML page.
Customize the details and actions available on an artifact
When users browse and interact with content within Digital Hive, there is a lot of detail and functionality that they are exposed to. Based on certain requirements, it may be desirable to suppress some detail and/or disable some functionality. The following thumbnail contains a title (Dashboard), information text (that it is a View from the Tableau HWT connector), adornments (5 star rating), actions (ability to favorite and the vertical three dots that provide different actions a user can take on the object), visual cues (that the object is new and that the content is certified), and a more info flyout button (the i button in the header that provides users with additional context, like location).

This new feature allows Digital Hive authors to control what information/functionality is available to the end users. The control can be applied to either the Content Lane objects or the objects within a File Explorer widget. The view can also be customized on the Search and/or Catalog page types.
Within the Properties panel, the following section will be visible which shows all the details that will be visible to the users. To alter the items, click on the X to delete them from the list or click on the drop down arrow to expose the full checklist of items.
Deselecting visual cues, information text, and actions, will result in the following display for users.
Launch Tableau Workbooks
In previous releases, Tableau workbooks were treated like folders, because they contain various views within. Users would be able to drill into the workbook to see the individual views within. That functionality still exists, but what's been added is the ability for a user to go to the object actions and launch the workbook either in a new or current browser tab.
Connector cards now show a currently indexing indicator
Resolved Issues
- Enabling multiline in Custom Fields does not show the
static values
- Inability to change the system credential when SSO credential is being used
- Tableau filters resetting to ‘all’ when a view is
embedded
- Encrypt app client/secrets for Cloud based
connectors
- Easy Hive page navigation in the Designer
- Size limitation for imported Hives
- Unable to see currently re-indexing status
- Can't save roles when the name is really long
- Screenshot this page feature for Hive thumbnail fails
- Obfuscate Qlik Sense Root and Client passwords
- Reduce the verbosity of Tomcat error messages
- No translations for the default system preferences
- Include a notices.txt file as part of the installation files for third party libraries
- SAML assertion groups aren't being included in a user's profile
- Minor improvements to the Hive import menu
- Remove the unified filters 'writeback' to prevent looping of filters
- Unable to delete flyout multilingual strings
- Lose Custom Fields metadata when there are a lot of fields and the show more isn't expanded while editing
- Update installer check for MS Visual C++ runtime to look for 2015+ instead of 2013
- Double scrollbar is visible in certain connector settings screens
- Installer does not update the selection if an incorrect value is selected and then modified
- Execution parameters are not working for Tableau views
- Default Progresql settings improved