Release Notes for Assets Server

New features

No features have been added in this release of Assets Server.

Changes

The following changes have been made in this release of Assets Server:

Scheduled plug-ins: resetting a blocked plug-in. When a server with jobRunnerEnabled=true set is unexpectedly shut down or loses connection to the cluster, a Scheduled plug-in that was running at that time might still have status Scheduled assigned when the server is restarted. While in that state, the plug-in is locked.

Resetting the plug-in so that it can be run again can now be done by clicking Reset plugin. The plug-in is then re-scheduled for next execution according to its configuration, any locks are removed and the plug-in can be run again manually or by schedule.

The Reset Plugin button in the Management Console

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-15662 Scheduled plug-in is not re-scheduled on another node if a node which it currently executes on disconnects.

LVS-15679 Storage engine pattern is case sensitive where it should be case insensitive.

LVS-15704 Studio integration: Metadata in Studio is not always updated for metadata synchronized from master to Production Zone.

LVS-15714 Studio integration: Archived layouts and shadow objects do not show 'Contains' and 'Contained by' relations for items archived after October 2020.

LVS-15726 Studio integration: Unable to clear 'Keyword' metadata from Studio for files linked to Assets.

LVS-15740 Management Console: When creating a new rule and only entering a name, the Permissions tab is enabled.

LVS-15754 Plug-ins: the scheduledScriptsEnabled cluster setting is not working correctly.

LVS-15788 API: Parameter filterQuery is ignored on Move API calls.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Note: When making use of multi-tiered storage, an additional upgrading step may have to be performed. See the article about upgrading for more details.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

The following changes to the documentation have been made in this release of Assets Server:

Upgrading Assets Server - updated
Scheduling tasks in Assets Server with Schedule plug-ins - updated

Assets Server 6.63.1

Assets Server version: 6.63.1.902

Release date: 30 March 2021

New features

The following has been added in this release of Assets Server:

Action plug-ins: adding an Action plug-in to the context menu of a folder. Action plug-ins can now be added as a command to the context menu of a folder.

For internal plug-ins this is done by configuring the following menuAssignment parameter:

folderContextMenu

For external plug-ins this is done by enabling the 'Folder context menu' option on the External action plug-ins page in the Management Console.

Note: Users need to have the 'Action plug-ins' permission assigned (ROLE_ACTION_PLUGINS) to see the menu command.

Changes

The following changes have been made in this release of Assets Server:

Permissions. Rules are now created separately for files, Collections, and folders. This makes it possible to more finely control permissions, down to individual assets in the system. For example: it is now possible to lock specific folders, or allow to move a file without allowing to move the folder that the file is in.

Setting up Rules in the Management Console

Figure: The Rules window in the Management Console is now split into Rules for files, Collections, and folders.

In addition, when browsing to a folder while setting up a Rule, a new folder can now be created directly from within the Folder browser, and a Folder path field can be used to manually set a path, including by the use of the asterisk wildcard for easily setting up a Rule that matches multiple folders.

Example: Assume that the following folder structure exists with the same structure except for one folder:

/My Brand/Production/2020/Images/

/My Brand/Production/2021/Images/

The repeating folder can then be replaced by an asterisk:

/My Brand/Production/*/Images/

This also makes sure that any future folder such as 2022 is automatically captured by this rule.

For more information, see Controlling user access to folders and files in Assets Server.

The Folder browser

Figure: When setting up a Rule, the Folder Browser now has a New folder button at the top, and a Folder path field at the bottom.

Note about upgrading: When upgrading from a previous release, existing Rules are automatically split into these separate rules. Each Rule covers part of the Rule that existed previously.

After the upgrade, the permissions closely mimic the previous permission setup, allowing a smooth transition for users to the new permission system.

Verify the generated Rules, and tweak or remove them to match the user requirements.

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-15445 Permissions: Add wildcard support in folder selection for Rules.

LVS-15664 Studio integration: Empty values are not included when sending an update to Studio.

LVS-15665 Permanently locked folder cannot be unlocked.

SPA-2283 Make it possible to trigger Action plug-ins from the folder context menu.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

The following changes to the documentation have been made in this release of Assets Server:

Controlling user access to folders and files in Assets Server - updated
Upgrading Assets Server - updated
Assets Server action plug-ins setting - menuAssignments - updated

Assets Server 6.62.1

Assets Server version: 6.62.1.885

Release date: 9 March 2021

New features

The following has been added in this release of Assets Server.

Support for Windows Server 2019. Assets Server 6.62 has been tested with Windows Server 2019 and found to be compatible.

Changes

No changes have been made in this release of Assets Server.

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-11632 Processing: Adobe Illustrator files that are saved with 'Create PDF Compatible File' are up- and downloaded as PDFs instead of Illustrator files.

LVS-13474 When downloading .bmp images that have been rotated, the downloaded images are not rotated.

LVS-15497 'Unable to locate provider for protocol: smtp.:' error when sending out e-mails due to incorrect e-mail dependency.

LVS-15531 Processing (Linux): Previews of Illustrator files appear with a black background.

LVS-15544 'Unexpected service exception' error is logged when logging in or refreshing Assets.

LVS-15549 Processing: Add configuration property for the number of pages created for .xlsx previews (unoconvXlsProcessingMaxPageRange).

LVS-15567 Searching: Unexpected results when using a NOT operator in a search query.

LVS-15611 APIs: Configuring plug-ins with webaccess public set to 'false' still results in the plug-in being public.

LVS-15629 Security: API license types can be incorrectly disconnected when a super user connects without available license seats.

LVS-15634 Processing: XMP metadata structure of InDesign and Illustrator files are rewritten after import or metadata change.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

The following changes to the documentation have been made in this release of Assets Server:

Compatibility of Windows with WoodWing applications - updated
Compatibility of Assets Server - updated

Assets Server 6.61.1

Assets Server version: 6.61.1.868

Release date: 16 February 2021

New features

No features have been added in this release of Assets Server.

Changes

The following changes have been made in this release of Assets Server:

User role 'Super user' has been split into full access and admin access. The Super User role allows users full access to all client applications and all areas of the server. In environments where there is a split of responsibility between managing the environment and the functional setup, a similar role but with less access is useful.

To that purpose the super user role has now been split into two:

Full access to all admin functionality. This is the existing role which gives users full access to all parts of the system.
Access to Assets and admin functionalities. This is a new role which allows users full access to Assets, but limited access to the Management Console of Assets Server. Using this role requires a Pro or API license.

In combination with a Pro license:

This super user has full permissions in Assets.
This super user only has access to the following features in the Management Console of Assets Server:
Server status
Permissions assignment
Branding
Plug-in management (external plug-ins only)
Configuring external plug-ins
Cluster properties¹
Active users (viewing and removing them)
Setting up Webhooks, image synchronization, and single sign-on
Field info
Support tools

¹ To prevent users with this limited role from making breaking changes to the system or from making changes that require a server restart, the configuration options that they are allowed to change are defined in a newly introduced option security.dataAdminClusterProperties.

Features in the Management Console that these users do not have access to are:

Plug-in management (all plug-ins other than external plug-ins)
License management
Bulk import
Studio Server configuration and tenant registration
Tools for setting up HTTPS, index management, file store rescue, asset processing, Studio update, and manual upgrades

In combination with an API license:

An API admin user can perform the same tasks as a Pro admin user with the exception of the following:

Access to clients
Concurrent sessions

For more information, see Controlling user access to clients and client features in Assets Server.

The license and super user options in the Management Console

Watermarks: configuration added for scaling and transparency. The scaling and transparency for watermarks can now be configured by setting the following options in the cluster-config.properties.txt file:

watermarks.scaleFactor. One of the following values:
1. The watermark fits exactly within the image, touching at least 2 opposite sides of the image.
A number between 0 and 1. This leaves room around the watermark; lower values means a smaller watermark.
A number above 1. Part of the watermark will be rendered invisible outside of the image bounds. On Linux and Windows the watermark will still be centered, on macOS it will be placed on the left and/or top edge of the image.

watermarks.opacity. A number between 0 and 1. Applies only to processing on Linux or Windows.

In previous versions, a fixed scaling of 0.2 (20%) was used. Depending on the shape (square or non-square) of the image, the generated watermark could turn out to be very small or very large.

Example: For an image of 1000x1000 pixels the watermark would be within an area of 200x200 pixels in the center of the image: this is only 4% of the center area for square images with a square watermark. The covered area decreased with non-square watermarks, but increased with non-square images due to calculations based on the largest dimension.

By increasing the new watermarks.scaleFactor option, the watermark can be made to cover almost all of the image. To make the watermark more subtle when it becomes larger, it is now also possible to increase the transparency.

For more information, see Showing watermarks on images stored in Assets Server.

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-15503 Increase server side timeout while downloading a folder with a large number of files.

SPA-2268 Introduce new data admin role with reduced access to the Management Console.

SPA-2274 Add configuration options for scale and opacity of watermarks.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

The following changes to the documentation have been made in this release of Assets Server:

Showing watermarks on images stored in Assets Server - updated
Controlling user access to clients and client features in Assets Server - updated

Assets Server 6.60.2

Assets Server version: 6.60.2.851

Release date: 29 January 2021

Fixed issues

Fixed issues

The following issue has been fixed in this release of Assets Server:

LVS-15560 Studio Server related metadata fields are cleared for articles archived from Studio Server.

Details: A change in Assets Server 6.60 related to handling relations resulted in Studio Server placement information to be cleared unexpectedly for articles or files that are created via Studio without a placement relation to other objects.

This issue affects Assets Server 6.60 in combination with a Studio Server or Enterprise Server integration, and affects the following fields:

sceArticleId
sceArticleName
sceChannelId
sceChannelName
sceIssueId
sceIssueName
sceEditionId
sceEditionName
sceLayoutId
sceLayoutName
scePage

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Assets Server 6.60.1

Assets Server version: 6.60.1.847

Release date: 26 January 2021

New features

No features have been added in this release of Assets Server.

Changes

The following changes have been made in this release of Assets Server:

Indexing: stopping and continuing a re-index process. When an index is updated, the process can now also be paused and continued again. Use this when indexing takes a long time and it affects the performance of the client applications; pause it during working hours and resume it in between working hours.

For more information about re-indexing, see Updating the file index of Assets Server.

APIs: Parameter added to Search API for excluding thumbnails of Collections. When the results of a search performed with the Search API include Collections, an additional search is done to enrich each Collections with up to 4 thumbnails. Depending on the number of Collections found, this can have an impact on the performance of running the search. To exclude thumbnails from Collections, a new parameter named 'returnThumbnailHits' has been added to the Search API. When set to true (which is the default setting) or when it is not passed, Collections will show thumbnails; when set to false the thumbnails are excluded.

Linux Assets Server configuration. The wrapper.conf file for Linux instances has been split into a wrapper.conf file and a wrapper_custom.conf file. This makes automating installations easier and provides a clear separation for custom configurations.

When upgrading Assets Server, the installer will move custom settings starting with wrapper.java.additional.<number> from the wrapper.conf file to the wrapper_custom.conf file. Any further customizations need to be applied from the custom file.

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-14433 Processing: Incorrect preview generated for WCML files.

LVS-14824 Processing: Watermark is not positioned correctly when maxWidth and maxHeight are different.

LVS-15332 Metadata: Tooltip for the 'Description' field does not appear.

LVS-15430 Periodical renewal stops from being triggered.

LVS-15513 Enterprise Server: History gets polluted with Enterprise metadata changes when sceRelations is set.

LVS-15523 Sharing: E-mail notifications for a Shared Link are not translated.

LVS-15529 Log the usage stats when (bulk) removing files.

LVS-15533 Processing: Image containing both IDF0 and JFIF metadata results in incorrect resolution.

LVS-15548 SSO: 'Invalid username or password' message when trying to log in to Assets Server in InDesign.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

The following changes to the documentation have been made in this release of Assets Server:

Updating the file index of Assets Server - updated
Assets Server REST API - search - Updated
Setting up HTTPS in Assets Server - updated
Assets Server memory configuration - updated

Assets Server 6.59.1

Assets Server version: 6.59.1.837

Release date: 5 January 2021

New features

The following has been added in this release of Assets Server:

Plug-ins: Action plug-ins and panel plug-ins can now be hosted on an external system — such as Netlify, Amazon S3 with Cloudfront, or Surge — and linked to one or more Assets Server installations as external plug-ins.

Note: This is now the recommended way of making these plug-ins available for Assets Server, as opposed to placing them in the plugins folder as part of the Assets Server installation.

Creating a new external plug-in is done by making use of the Assets Client SDK which is hosted on NPM. Refer to the README of the SDK for installation and usage of the library.

Any existing internal plug-in can also be converted to an external plug-in.

For more information, see Working with external plug-ins in Assets Server.

Metadata: Restricting the synchronization of metadata fields by changes made in the original file only. When synchronizing metadata across file variations, the defined metadata fields can be changed in both the original file as well as in all its variants. For scenarios in which metadata fields that hold sensitive information (such as copyright information) may only be changed by specific departments, such changes should be prevented from being made in the file variants, and only be made in the original file. This is now possible by using the following option:

syncMasterOnlyMetadataFields

Any metadata field that is configured in this option can be edited in the original file but not in its variants; for users this field appears as read-only and API calls to update this field will fail.

For more information, see Synchronizing metadata across file variations in Assets Server.

Changes

No changes have been made in this release of Assets Server.

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-15404 APIs/Security: Reduce amount of unnecessary information exposed by the Welcome controller.

LVS-15438 Linux: Custom rendition preview is not applying correct width and height when image is rotated 90 degrees.

LVS-15447 Metadata: Synchronize image metadata only from master to variants.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

The following changes to the documentation have been made in this release of Assets Server:

Working with external plug-ins in Assets Server - new
Managing Assets Server - updated
Synchronizing metadata across file variations in Assets Server - updated

Assets Server 6.58.1

Assets Server version: 6.58.1.831

Release date: 16 December 2020

New features

The following has been added in this release of Assets Server:

Metadata: option added for ignoring the resolution metadata for EPS and AI files. When graphic files are imported, a preview is generated based on the values defined in defaultResolutionPixelsPerInch or fallbackResolutionPixelsPerInch. For EPS and AI files, this can result in a preview in an incorrect resolution. When this is the case, the preview generation can now be forced to use the resolution data that is stored in the metadata of the file itself. This is done through the useResolutionFromMetadata option in the Cluster Properties page in the Management Console:

useResolutionFromMetadata=true

Changes

The following change has been made in this release of Assets Server:

APIs: Duplicate IDs. The log generated by the API for scanning if files with a duplicate ID exist now also shows the duplicate IDs that have been found instead of only the number of duplicates.

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-15483 APIs: Duplicate ID tool should also show actual duplicate IDs.

LVS-15458 Processing: Remove requirement for external GraphicsMagick dependencies for raw image processing

LVS-15449 Studio integration: Empty custom date-time field is not parsed when uploading an image in Studio.

LVS-15428 Indexing: Handle possible duplicate IDs in the system during index updates.

LVS-15052 Metadata: Add configuration to ignore resolution metadata for EPS and AI files.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

No changes to the documentation have been made in this release of Assets Server.

Assets Server 6.57.1

Assets Server version: 6.57.1.823

Release date: 24 November 2020

New features

No features have been added in this release of Assets Server.

Changes

The following change has been made in this release of Assets Server:

Integration with Studio Server / Enterprise Server. The metadata selector field group 'Enterprise' has been renamed to 'Studio'. When the 'Enterprise' group is used in the custom-assetinfo.xml file, manually change this to Studio'.

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-15188 Searching: Date searches display incorrect results when start and/or end date is set to 00:00:00.

LVS-15309 File permissions on Linux are set to 'world writable'.

LVS-15355 Files in .orf format get incorrect MIME type assigned.

LVS-15372 Files are not sorted correctly when sorting by Relevance.

LVS-15403 Stack trace is displayed to end users.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

The following changes to the documentation have been made in this release of Assets Server:

Upgrading Assets Server - updated

Assets Server 6.56.1

Assets Server version: 6.56.1.812

Release date: 3 November 2020

New features

No features have been added in this release of Assets Server.

Changes

The following change has been made in this release of Assets Server:

Documentation: The Help link in the avatar of the Management Console has been updated to point towards the articles aimed at system administrators. This way, system administrators can quickly access the documentation about installing, configuring, and managing the system, while articles that are less relevant stay out of view.

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-14982 Security: Password is displayed in plain text when a HTTPS certificate upload error occurs.

LVS-15111 Processing: Different color quality for JPEG files on Linux compared to macOS processing and Photoshop.

LVS-15258 Exclude view/download counter updates from metadata update events.

LVS-15296 Metadata synchronization can cause a deadlock situation when updating many files at the same time.

LVS-15315 Index revision is not updated when running Asset Processing tool.

LVS-15343 Move of asset to another pattern match within the same storage engine results in missing asset.

LVS-15353 Management Console: Update the default links to the documentation on Help Center.

LVS-15359 Installer: Install EPEL repository before trying to install GraphicsMagick package on Linux.

LVS-14448 Layout can be checked out when Assets Agent is not connected and layout is part of multiple selected files.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

No changes to the documentation have been made in this release of Assets Server.

Assets Server 6.55.1

Assets Server version: 6.55.1.799

Release date: 15 October 2020

New features

The following features have been added in this release of Assets Server:

File formats. Support for the Canon CR3 file format has been added. For more information, see Supported file types in Assets Server.

Changes

No changes have been made in this release of Assets Server.

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-15295 Processing: defaultBackground 'transparency backdrop color' settings not applied on Linux.

LVS-15273 Prevent that an XML extension is added to unknown files during upload.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

The following changes to the documentation have been made in this release of Assets Server:

Supported file types in Assets Server - updated

Assets Server 6.54.1

Assets Server version: 6.54.1.791

Release date: 24 September 2020

New features

The following features have been added in this release of Assets Server:

Video processing: Define if a node should be used for processing videos. Processing videos can take quite some resources and time which may delay other tasks such as processing regular image files. In workflows in which many videos are processed, it may therefore be beneficial to dedicate one or more nodes for processing only videos. This can be done by using the videoProcessing option in the node-config.properties.txt file. Use one of the following settings:

yes. The node processes video and non-video files. Use this setting when videos are processed on occasion.
no. The node does not process videos. Use this setting when the video processing is offloaded to a dedicated node.
only. The node only processes videos. Use this setting when the node should be used as a dedicated node for video processing.

Note: The cluster needs to have at least one node that processes videos (setting 'yes' or 'only'), and at least one that processes non-videos (setting 'yes' or 'no').

Example: videoProcessing=yes

Synchronizing images. When an image has one or more variants, and the original image is changed, replaced, or updated in some way, it may be that some or all of its variants need to be synchronized with these changes.

For example: A low-resolution version of the image is replaced by a high-resolution image, or image specific metadata of the file such as width, height, color space, and so on is changed.

Updating the variants can now be done by using the Image Synchronization feature in the Management Console.

With it, a Source folder is defined as the location of the original image and a Target folder is defined as the location of the variants.

When the original image in the source folder is changed, the variants in the target folders are synchronized.

Variants that should not be changed (such as those that are archived) can be left out by not defining their folder as a target folder.

During synchronization, the file itself as well as specific image related metadata fields can be synchronized.

For more information, see Synchronizing images in Assets Server.

The Image Synchronization page

Changes

No changes have been made in this release of Assets Server.

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-15197 assetFileModified field is not updated after modifying assets in Collections.

LVS-15229 Allow nodes to not run video processing or video processing only.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

The following changes to the documentation have been made in this release of Assets Server:

Synchronizing images in Assets Server - new
Installing Assets Server - updated

Assets Server 6.53.2

Assets Server version: 6.53.2.772

Release date: 4 September 2020

Fixed issues

Fixed issues

The following issue has been fixed in this release of Assets Server:

HTTPS setup for WoodWing Assets

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Assets Server 6.53.1

Assets Server version: 6.53.1.768

Release date: 1 September 2020

New features

The following feature has been added in this release of Assets Server:

Video processing: configuration options for streaming videos. When a user previews a video, the original video will be streamed when possible so that the user experiences it in its maximum quality. A video file is considered to be streamable if all of the following criteria are met:
The format is mp4 or mov.
The codec is h264.
The size is no bigger than 1920 x 1080.

However, whether or not the original of the video is streamed depends on the 'Use original' permissions of the user: if the user only has rights to preview the video, a preview version of the video will be loaded instead.

Options for configuring video previews were already available in the Cluster properties:

ffmpeg.extraPreviewArgsHD
ffmpeg.extraPreviewArgsLD

By default a 10-minute preview is created.

However, when the video is mostly or always showing the original, there is less need to process a 10-minute (or longer) preview and you may want to adjust the preview generation to be less resource heavy for streamable videos.

To improve this, streamable video preview generation can now be configured separately via the following options:

ffmpeg.streamed.extraPreviewArgsLD
ffmpeg.streamed.extraPreviewArgsHD

By default they will follow the same values as the non-streamed configuration option, but can be configured by copying the value from those options and changing the necessary parts, for example by reducing the duration of the preview.

It is also possible to turn off streamable videos completely by setting the following configuration option to false:

ffmpeg.streamed.enabled

When doing so, the other ffmpeg.streamed configuration options are ignored and previews will be the same for all supported video types.

For more information, see the Management Console > Server configuration > Cluster properties and search for the options.

Changes

No changes have been made in this release of Assets Server.

Fixed issues

The following issues have been fixed in this release of Assets Server:

LVS-15087 Management Console: Metrics requests are repeatedly triggered when connection is slow.

LVS-15183 Processing: Allow different preview configuration for videos that can stream the original file.

LVS-15199 Import: Unknown extensions on files with application/zip as MIME type will not receive a .zip extension.

LVS-15217 Import: Files without extension but ending with dot are imported through API or bulk import as generic files.

LVS-15226 Creating a Metadata Report fails when selecting more then 900 assets.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

No changes to the documentation have been made in this release of Assets Server.

Assets Server 6.52.1

Assets Server version: 6.52.1.753

Release date: 11 August 2020

New features

The following features have been added in this release of Assets Server:

Metadata reports. It was already possible to create a metadata report, but this was based on selected files only. It is now also possible to base the report on all files that match the current folder, query, and filters.

When using the Metadata report API, this is done by using the 'q' parameter.

When using Assets, this is done by choosing the option 'All found files' in the Metadata report dialog.

The Metadata report dialog

Metadata: synchronizing file variations. One of the ways of creating a file is by making a copy of an existing file (either directly in Assets or via the integration with Studio).

This creates an exact copy of the original file, including the metadata field values.

When a copied file is updated by changing the values of its metadata fields, it may be that these changes also need to be made in the original file and all other copies of it. Think of metadata fields containing important context or legal information such as the description, tags, copyright details, usage rights information, and so on.

The process of synchronizing metadata fields across file variations can now be automated: when a field is updated for a file of which variations exist, the value of this field is automatically updated for all these file variations.

This is done by configuring the metadata fields that should be synchronized in the syncMetadataFields option of the cluster properties of Assets Server.

Then, when a field is updated for a file of which variations exist, the value of this field is automatically updated for all these file variations.

For more information, see Synchronizing metadata across file variations in Assets Server.

The syncMetadataFields option in the Management Console

Changes

The following change has been made in this release of Assets Server.

APIs. The following change has been made to the Metadata report API:

The 'q' parameter has been introduced. With it, a report can be created for any asset that matches the query.

Fixed issues

The following issue has been fixed in this release of Assets Server:

LVS-15172 Smart Mover: Fix support for checking in files.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

The following changes to the documentation have been made in this release of Assets Server:

Assets Server REST API - Metadata report - updated
Creating a Metadata report in Assets Server - updated
Working with metadata in Assets Server - updated
Synchronizing metadata across file variations in Assets Server - new

Note: Some screenshots in the product documentation may still show Enterprise products. This will be updated over the coming weeks.

Assets Server 6.51.1

Assets Server version: 6.51.1.741

Release date: 22 July 2020

New features

The following feature has been added in this release of Assets Server:

Disabling the download and view count. When users of Assets download or view a file, the counter that shows how many times that file has been downloaded or viewed is automatically increased.

When keeping track of these counts is not needed, updating them can now be disabled through the following option:

File: cluster properties
Option name: downloadViewCounterEnabled
Value: true or false
Requires Elvis Server restart: no

Example: downloadViewCounterEnabled=false

Changes

No changes have been made in this release of Assets Server.

Fixed issues

The following issue has been fixed in this release of Assets Server:

LVS-14933 Studio server test button on Management console fails to reach a working Studio URL.

LVS-14985 Removed or added permissions of a logged-in user are not directly applied.

LVS-15085 Metadata fields 'additionalModelInformation' and 'modelAge' missing in the default metadata set.

LVS-15099 Index asset revision fails when a taxonomy is added to the 'labels' metadata field.

LVS-15131 Auto-renaming option ignoreNumberPostfixOnCreate is not working when uploading files.

LVS-15136 Disable Download and View count updating.

LVS-15156 Search no longer working after removing a custom field or changing the data type.

Known issues

The following known issue exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

No changes to the documentation have been made in this release of Assets Server.

Note: Some screenshots in the product documentation may still show Elvis or Enterprise products. This will be updated over the coming weeks.

Assets Server 6.50.1

Assets Server version: 6.50.1.730

Release date: 30 June 2020

New features

The following feature has been added in this release of Assets Server:

Studio integration: searching for Digital articles based on their components: When a Digital article is archived or uploaded, the names of the default components that it contains are now stored in a new metadata property named 'Article Components'.

This property can be used for finding Digital articles containing a specific component, for example by adding the property to the Filter in Assets.

Filtering Digital articles based on the components they contain.

Notes:

Names of custom components are not stored.

The Article Components field for Digital articles that are already in the system can be updated by running the 're-extract metadata from files' option of the Asset processing tool.

Changes

The following change has been made in this release of Assets Server:

Management Console: All references to 'Elvis' have been replaced by 'Assets' and all references to 'Enterprise' have been changed to 'Studio'.

Fixed issues

The following issue has been fixed in this release of Assets Server:

LVS-14842 Processing: different quality in custom renditions between Linux and macOS processing tools.

LVS-14921 userQuery stats are not always populated and only simple queries are logged.

LVS-14926 Elvis action plug-in API - elvisContext.openSearch creates a clear search instead of performing a proper query.

LVS-14967 Processing: Slow performance experienced on moveGroup and moveBulk operations.

LVS-15002 Security: Pen test results show Medium vulnerability for Jquery 3.4.1 JavaScript component.

LVS-15016 No results in Brand portal filter for pure lower-cased metadata fields.

LVS-15027 Studio integration: Images are not always copied when copying slides from a slideshow from one Dossier or article to another.

LVS-15064 File size mismatches between index and FileSystem.

LVS-15086 Studio integration: Pinned Dossiers always attempt to log in to Content Station instead of Studio.

Known issues

The following known issues exists in this release of Assets Server:

Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.

Installing and upgrading

Clean installation: For information about installing Assets Server on a system on which it is not yet installed, see Installing Assets Server.
Upgrading an existing installation. For information about upgrading an existing installation of Assets Server, see Upgrading Assets Server.

Downloads

The download files for this release of Assets Server can be found in the Release announcement.

Documentation

The following changes to the documentation have been made in this release of Assets Server:

Archiving Digital articles to Assets Server - updated

Note: Some screenshots in the product documentation may still show Elvis or Enterprise products. This will be updated over the coming weeks.

Assets Server 6.49.1

Assets Server version: 6.49.1.707

Release date: 9 June 2020