As a convenient way for an administrator to get an asset's UUID, it now displays in the UI as one of the attributes when viewing an asset in the Digital asset table.

New REST API endpoints enable programmatic management and interaction with folders. This enhancement aligns folder-related REST operations with existing UI capabilities, improving automation and integration potential. Most endpoints for POST, PUT, and Delete were previously available, but were refactored to accommodate folder-related actions. This release includes the addition of new endpoints were added for GET search and download:

Previously, the Drive screen only supported a grid view, limiting the amount of visible information per asset and number of assets displayed. Users needed to open asset previews or access the Version management tab to see more details. Now you can switch between Grid view and List view in the Drive screen. The new List view displays assets and folders in a table layout with extended details, offering improved information visibility without requiring additional clicks.

The file size limit for document previews was increased from 5MB to 20MB. Additionally, parts of the document can be previewed without waiting for the entire file to load.

The documentation now includes instructions for encoding special characters in REST calls. See the Developer Guide > REST overview section for details.

Performance was improved:

Usability improvements:

The TIBCO EBX® Digital Asset Manager Add-on no longer supports previews for Word 2003 DOC files. The add-on continues to support preview functionality for Word 2007 and newer DOCX files.

Previously, retrieving an asset's current version via the Java API always returned the version marked as current in the Drive. This behavior has changed. The API now returns the version that is current in the context of the specified dataset, which may differ from the Drive's current version.

Updated Apache POI and related libraries (poi, poi-ooxml, poi-ooxml-full, poi-scratchpad) to version 5.4.1.

Updated docx4j-JAXB-ReferenceImpl and docx4j-export-fo to version 11.5.2.

Updated Azure libraries:

Updated pdfbox, pdfbox-tools, fontbox, preflight, and xmpbox to version 3.0.5.

Updated batik-all to version 1.18.

Updated xmlgraphics-commons to version 2.10.

Digital assets are accessible via URL without having to log into EBX®.

File names containing Chinese characters are incorrectly encoded.

In the Digital asset table, users can still delete assets that belong to other users, even when they do not have permission to do so.

The Manage digital assets screen is not accessible via IFrame.

Only one table archive should be imported when multiple files are required.

After a media type field is set to Hidden in all views and the data model is published, it is no longer possible to upload or edit assets in that field. This issue occurs even after permissions are set back to Visible in all views and the model is re-published.

The add-on is not stable when deployed on a WebLogic application server. Fatal errors can occur when trying to use the add-on's services. The root cause is under investigation.

When uploading assest from a Connector, the add-on is not able to recognize duplicate assets that were uploaded (not using the add-on) to an externally managed server.

It is possible that some DOCX file previews might not generate when Microsoft Word is not installed. This is due to missing font files.

If the Cancel button is clicked during a delete operation on 100 or more assets, the operation is not cancelled and assets are still deleted.

When attempting to delete assets from 2 Drives in the same operation and one of the Drive's has an authentication issue, the displayed result states that all deletions failed. However, some assets are still deleted and the asset thumbnails in the UI display a File not found error.

In certain cases the add-on is not able to preview DOCX files. This can occur when the file contains invalid characters, or unsupported elements, such as charts, floating tables, or other complex elements.

In instances where PPTX files contain complex shapes, the add-on cannot generate a preview. This is due to a third-party technical limitation.

The first time a large file is previewed, users might experience a delay while the preview is generated.

Searching for assets in the media-type field using quick search is not supported. However, when previewing some file types, such as PDFs, you can search for text within the file.

The configuration is not updated for the supported file extensions after users access the Digital Asset Manager widget.

Document previews cannot display Vietnamese text.

When accessing assets in an external Drive, error messages may display when selecting all assets. This can be the result of access limitations put in place by the third-party tool.

Thumbnails of some uploaded SVG files do not display correctly.

Previews of PPT, PPTX, DOC and DOCX files cannot display charts due to a limitation of the library used to generate the preview.