Sections in the article
Inriver is moving towards more incremental, smaller releases to better and faster accommodate our customers. With smaller, more frequent releases, Inriver will be able to increase the quality and transparency of the releases and identify and mitigate any erroneous behavior that may be caused by the release much faster.
NB! To receive notifications when new release notes are published, please ensure you follow this page by clicking the "follow" button above.
These improvements are available on the new media experience. If the new media experience has not yet been activated for your environment, please contact Inriver Support or your Customer Success Manager to start the process.
Improvements
“Save as new” is now available for transformations also on Resource entities
Media now lets you choose “Save as new” when applying Classic or AI transformations to a file from a Resource entity. Previously this option was hidden, so the original file always had to be overwritten, even when you wanted to keep both versions.
Because a Resource entity holds only one file, “Save as new” creates a new Resource entity for the transformed media asset. The original Resource and its file stay untouched.
Who benefits: Media Admins and content editors who want to produce transformed variants of an asset without losing the original.
A clearer upload prompt on the Media tab when an entity has no media yet
The Media tab now shows a large drag-and-drop upload area when an entity has no media. Before, it showed an empty “No resources found” list with a small upload box in the corner, which made the next step easy to miss.
The new area has an “Upload files” button and a short message that no media has been uploaded for the entity yet. It also states the 1 GB per-file limit. Once the first file is added, the tab returns to the usual asset list.
Who benefits: Content editors and Media Admins adding the first file to a Resource or other entity.
Deletion progress now shown in the Media Job Tracker
Deleting assets now reports its progress in the Media Job Tracker. Previously, a bulk delete simply refreshed the view with no confirmation, so users had to search for the assets to check whether they were gone.
When you delete multiple assets, the Media Job Tracker now shows how far the deletion has come and whether all items were removed successfully. This is most useful for large deletions of a hundred assets or more.
Who benefits: Media Admins and anyone managing large asset libraries, who can now see the outcome of a bulk delete.
Bug fixes
This release fixes issues in the new media experience, bringing it in line with classic Media behavior.
| # | Area | Fix |
| 1 | Upload | Field revision history is now recorded when media is uploaded, whether through Upload media, Media upload from an entity, or Save as new. Revisions for tracked fields such as ResourceFilename and ResourceFileId now appear in the Details tab, as expected in the Portal. |
| 2 | Upload | Uploading media no longer fails with “This SqlTransaction has completed; it is no longer usable” when a multi-value field has a long default expression. The evaluated result of the expression is now saved instead of the formula, matching the classic Portal upload. |
| 3 | Upload | When uploading media, the ResourceName field now includes the file extension (for example, “Feature-Image-30-1024x658.png”), matching the previous behavior. Previously the file extension was dropped, which could break existing mappings and validations. |
Comments
0 comments
Please sign in to leave a comment.