We’re thrilled to announce the new release of the REACT interface, packed with performance upgrades and usability enhancements that bring both speed and clarity to your ES. Headlining this release: status-based search now runs on Elasticsearch — making searches faster, more accurate, and highly scalable.
In earlier versions, filtering assets by status was a pain point — especially for systems with 100K+ assets. These queries were slow and could even crash the system under high load.
With version 1.6.0, that bottleneck is gone. We now allow you to replace the traditional status field with a metadata enumeration, backed by Elasticsearch. This reimagined system transforms status searches into facet searches, delivering:
To activate this feature:
If you want to preserve the status chip colors, ensure that your new metadata values exactly match the original status names. This can be automated with an API script.
Note: Don’t forget to lower the “Maximum Results All Data” value — since searches now span the entire dataset, there’s no gain in returning 5000 assets at once. Reducing this value improves responsiveness and reduces UI clutter.
If your statuses change dynamically, you’ll need to update your workflows to keep the metadata in sync (with Context.setMetadata(..)).
Contact the service team if you need help implementing this.
File Path and Last Modification Date are now available in table view — useful for tracking where assets live and when they were last updated.
The upload feature now honors the versioning regex expression, accurately reflecting revision activation and deactivation for volumes.
Version 1.6.0 introduces a massive performance boost with its metadata-based status search powered by Elasticsearch, while also refining the UI experience and ensuring greater clarity and flexibility for power users.
Upgrade today, and experience how much smoother large-scale asset management can be.
Have questions or need help configuring your interface ? Reach out to the service team — we’re here to help.
Back in April, we released Service Pack 4 (SP4), an essential update focused on long-term stability, enhanced security, and performance. SP4 included core component upgrades—Apache Tomcat v9.0.102, PostgreSQL v16.8, and Elasticsearch/Kibana v8.17.4—and also introduced over 20 fixes and 30 improvements to the React DAM interface (v1.5.5).
Search functionality was a major focus: the search algorithm received a significant speed boost, particularly when using production filters like status. Users can now combine logical operators such as AND, OR, and NOT to refine results—making it easy to search for, say, “PSD fruits excluding banana.”
Interface clarity also saw improvement. The confusing @ character in collection names (which clashed with user email addresses) was replaced by pipe separators, and collections now have dedicated shareable URLs for easy access (e.g., .../collection=my-collection).
Visual cues were added, too—such as a copyright icon for assets, linked directly to copyright information via plugin configuration.
You’ll also find improvements in organizing your workspace: folders and projects can now be added to Favorites, allowing one-click access to commonly used areas.
Administrators gained more control over profile-based restrictions, such as making Job Ticket Layouts view-only for selected user groups and configuring whether jobs and documents should be included in search results per profile.
On the download side, you can now create and save custom resolution presets, with defaults like Blog (144 dpi), Web (72 dpi), and Print (300 dpi).
The crop tool also received visual improvements, including zoomed-out previews and better feedback when image sizes don’t match selected ratios. A new “Keep Only Aspect Ratio” option gives users flexibility between proportional scaling and fixed dimensions.
And finally, the Virtual Book view lets you flip through assets as if browsing a catalog—a simple, engaging way to preview content directly within React.
These improvements collectively reflect our ongoing commitment to user feedback and interface refinement—making the DAM not just more powerful, but more enjoyable to use.