The Release Notes for Assets Server contain information about the new features, changes, fixed issues, known issues and upgrade instructions for each release of WoodWing Assets Server.
The versions are sorted by version number in descending order. Use the Navigation block to the right of the page to quickly navigate to the information of a released version.
Assets Server 6.53.2
Assets Server version: 6.53.2.772
Release date: 4 September 2020
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.
- 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.
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.
|
Notes:
|
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:
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
New features
The following feature has been added in this release of Assets Server:
- Licensing: API licenses with super user permissions. It is now possible to combine an API license with a super user role. This makes it possible to automate tasks for which a regular API user does not have sufficient permissions. Users with such a role can access all files, metadata fields and admin endpoints, and can log in to concurrent sessions of the same user. For more information, see Controlling user access to clients and client features in Assets Server.
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-14940 Metadata report: Paragraphs in the Description field are generated as separate records.
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:
Note: Some screenshots in the product documentation may still show Elvis products. This will be updated over the coming weeks.
Assets Server 6.48.1
Assets Server version: 6.48.1.695
Release date: 19 May 2020
New features
No features have been added in this release of Assets Server.
Changes
Assets Server 6.48 is based on Elvis Server 6.47 and is technically the same. Apart from re-branding it by changing logos and product name references at various places, no changes have been made.
Note: The re-branding applies to Assets and Assets Agent. References to Elvis are still present in Assets Server, the Management Console, the installer, folder names, configuration options, APIs, and so on. These will be updated in a future release.
Fixed issues
The following issues have been fixed in this release of Assets Server:
LVS-14861 Webhooks with a trigger on specific Metadata Queries include more assets than expected.
LVS-14875 Prevent reindex of Asset index block node startup during upgrade.
LVS-14944 Missing necessary library for SAML / ADFS integration.
LVS-14957 Make sceSystemId available in metadata field permission configuration.
LVS-14958 Removing assets fails when 'enabledUsageLogActions' excludes REMOVE.
LVS-14972 When uploading an XML asset, the structure and content of the file is changed.
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.
Downloads
The download files for this release of Assets Server can be found in the Release announcement.
Documentation
Documentation for Assets Server is available on Help Center:
Note: Some screenshots in the product documentation may still show Elvis products. This will be updated over the coming weeks.
Versions 6.47 and older
For versions 6.47 and older, see the Elvis 6 Release Notes.
Comments
Do you have corrections or additional information about this article? Leave a comment!
Do you have a question about what is described in this article? Please contact support here.
0 comments
Please sign in to leave a comment.