Core 7.1.10 Release Notes

April 15, 2024
This build focused on urgent bug fixes, and associated performance improvements for asset processing, the download panel, and package sorting.

Performance and Experience Improvements

• Processing and performance improvements for packages created during upload workflow, from package replication, and for adding files to existing packages. Files should appear more quickly without having to continuously refresh.

• Processing improvements for PDFs and compressed file types (.zip, .tar, etc.) on upload.

• Improved UI performance and logic improvements for downloads. These improvements also addressed several bugs, the fixes for which are listed in the bugs section below.

• Added scrolling to User Role rules. Roles with many rules can now be scrolled through for easier navigation.

• Improved messaging for “empty packages” when processing / package creation takes longer than a few moments.

• Updated the sort order logic within packages to address several issues. This is the first of several forthcoming sort fixes that will be addressed in packages and asset groups. Specific usability “bugs” related to this solution are listed in the bugs section below.

Bug Fixes and Technical Updates

Downloading

FIXED: Standard users who have permission from the Sender to download a source file from a package (via Recipient Settings or Download WITHOUT Watermark). Users were reporting they could either download only proxies or could download the source file the first time, but only proxies thereafter. This also addresses the PSD source download bug.

• Send package to standard user with Recipient Settings:

  • Standard user recipient – In the download panel, select Download WITHOUT Watermark, and then choose Source if not already highlighted.
  • Select the Download button.

• Send package to Standard user with Download WITHOUT Watermark selected, and choose Source

  • Standard user recipient – In the download panel, select Download button.

• Downloaded file should download as the unwatermarked original file.

FIXED: Standard users who have permissions to download Source and Proxy, and who have been sent a package with Recipient Settings don’t have Source as a download option on Download WITHOUT Watermark.

UPDATED: Standard users with the Change Watermark permission when receiving packages went via Download WITH Watermark were previously given the option to Download WITHOUT Watermark on High and Low Res proxies. This has been updated to remove the Download WITHOUT Watermark option.

UPDATED: Direct Download page redirects user to download interface instead of giving message “Download Note Found”.

UPDATED: When a package is open in the asset viewer and a package is also open in the package panel on the right, selecting the download button in the top bar downloads the package in the asset viewer, and selecting the download button at the bottom of the package panel downloads that package.

Watermarking

FIXED: Watermarking a file with a group on download was downloading only the watermarked file of the user who downloaded it.

• Admin user or user with Change Watermark permission, select an asset to download.
• Apply a Group watermark.
• Download it.
• The asset should download respectively for each member of the group, and apply that users watermark to the asset.

Packages

FIXED: Large packages were showing black screens on assets after sorting by something other than Upload Date and then selecting “Load all files”.

• Open a package containing 100+ assets.
• Sort by Name.
• Load all files.
• Open an asset in the package.
• Contents should be visible, if they are a playable or viewable file type.

FIXED: Package sort order – When moving between the package view to a file view and then back to the package view, the group sort order will no longer jump to a different sort display.

UPDATED: Package sort order – When adding a new file to a package that hasn’t been sent and then changing the sort position order prior to sending, the package should now retain the sort order for the recipient user(s). This use case has been fixed, however, adding several more files and ongoing changes to the sort order may still cause sort order or duplicate file issues. Please contact support in this case to alert for ongoing issues as we hone in on solving the problem / root cause.

Tagging / Categorization

FIXED: Not all assets are updating to the correct project name when a production tag value is updated/renamed.

FIXED: When updating tags / metadata on files, the page doesn’t refresh and show the updates.

General

IMPROVED: Duplicate files appearing in asset groups in File Search and Packages.

• This has been fixed for most use cases. There are intermittent occurrences when the user continuously changes the sort view and moves back and forth between File Search and Package View and an asset group where this still occurs.