ConfigPortal Release Notes

The following items on the list encompass breaking changes, features, and fixes that are relevant for the major release.

Patches for this major release

Patches are shown based on recency and will appear below as soon as they are issued.

Patch 25.2.24 on 19 Sep 2025

Patch 25.2.21 on 27 Aug 2025

Patch 25.2.20 on 20 Aug 2025

Patch 25.2.17 on 31 Jul 2025

Patch 25.2.16 on 31 Jul 2025

Patch 25.2.15 on 11 Jul 2025

Patch 25.2.14 on 11 Jul 2025

Release 25.2.14 on 09 Jul 2025

Dependencies and Component Updates

The following central components will be shipped in the noted version, along with relevant product and service dependencies:

General topics

Resource Tags

The use of resource tags in VidiCore and other Vidispine products makes it possible to restrict the usage a software component to certain functional areas or locations. The following functionality is implemented to support resource tags and multi site deployments:

• Resource tags can be registered in CP via a new API. Currently the following types of resource tags are supported:

  • Location

  • Purpose

• A new global configuration page “Resource Tags” shows all configured resource tags. Editing is currently not supported on this pages due to deployment reasons.

• A new toolkit “ResourceTags” is implemented to allow the selection of one or multiple resource tags in use case pages.

• Use case pages can be set to “resource-tag-aware” via a configuration flag on the page. This will enable the page to support multiple configuration sets for different resource tag combinations and show an overview list on the main page instead of a single entry.

• The configuration pages for storages, storages methods and storage groups use the new toolkit for the resource tag selection.

• The existing location API is replaced by resource tags of type “Location”. It is no longer possible to set values via the location API, while reading delivers the configured resource tags of type “Location”. On first startup, ConfigPortal automatically migrates existing location values to resource tags. The page for “Locations” is removed from the CP UI and replaced but the page “Resource Tags”.

• An API call is implemented to deliver also inherited resource tags based on the VidiCore inheritance approach.

Configuration of VidiCore Server Agents (VSAs)

For the product VidiCore, most of the VidiCore Server Agent settings can now be configured in ConfigPortal. Only settings relevant for the connection between the VSA and VidiCore still have to be set in the agent.conf file.

New VSA instances can be created in the CP UI. For each environment, each VSA instance can be selected as activated or deactivated. This allows to configure all required instances in CP but reduce the amount of redundant instances in test environments.

The VSA configuration properties can be selected from a dropdown, providing a tooltip text and a link to the VidiCore documenation. Environment-dependent values are marked with the well-known flag icon.

As usual, you should assume that ConfigPortal is the master of the configuration values and not change them in parallel in the VSA configuration file. Existing configurations can be imported from VidiCore into CP and then made editable if desired.

Selection of VSAs

In previous versions it was possible to select a VSA instance in different places in CP, e.g. in the storages configuration for so called VSA storages. This selection was loaded from the connected VidiCore instance in the active environment. This way of selection is kept optionally for backward-compatibility.

Alternatively it is now possible to select a VSA from the new VSA configuration.

The VSA selection was also changed to support a multi-selection of VSAs. This allows to create only one access method in CP with multiple VSAs, leading to multiple access methods in VidiCore for each of the selected VSAs. Configuration of multiple redundant VSAs for the same set of functions and configuration should be much more convenient now.

VidiCore Database Purging

In the section VidiCore Configuration for the product VidiCore, a new page was implemented. It allows to show and adapt the database purging settings for VidiCore for the following entities:

• Audit Trail

• Change Log

• Jobs

• Transfer Log

In contrast to most other settings in ConfigPortal, this data is not saved in CP, but set directly in the VidiCore instance connected to the current environment. Changing these values in a non-active environment is not possible.

VidiCore Storage Groups

ConfigPortal allows now to configure storage groups in VidiCore. Storage groups can be configured in the corresponding global configuration page.

In the storage configuration, one or more group(s) can be selected from a dropdown. The storage group overview also provides the “usage” feature to see which storage uses a group.

When importing storages from VidiCore, the existing storage groups are also imported.

Support VSA Storages for Export Location and Thumbnail Resources

VSA storages can now also be configured for export locations and thumbnail resources.

It is now also possible to configure multiple access methods for thumbnail resources.

Enhanced Naming Script Support for Storages and Export Locations

Storages and Export Locations now support the same configuration options for file naming scripts:

• No script: No script is set.

• Default script: The ConfigPortal default script is set.

• User defined script: The user can defined a script in a text box.

Toolkit enhancements

The following enhancements are done for the different toolkits:

• The new toolkit Time_StagingDependent allows to use environment-dependent time values in a use case page.

• A migration is implemented for switching from the standard toolkits for entering numbers or time values to the staging-dependent versions.

• The Metadata masked control toolkit return value for enum metadata as the default value.

• The Metadata Input toolkit resolves values to an enum’s value.

• The Multiple Workflow Selection allows now editing the workflow label and version when EnableMetadataEditing is set to false.

Other enhancements

New contact cache

A new database cache for contracts (workflows, rules, user tasks) is implemented. This will speed-up nearly all contract related operations and also reduce memory consumption heavily in some situations.

Enhanced logging for staging operations

When performing staging operations, ConfigPortal creates more log entries to allow more detailed analysis in the case that errors occur.

Enhancements for key/value data for metadata field and group definition

Key/value metadata fields for metadata are now displayed as multiline. It is also possible to add key/value metadata for VidiCore system metadata.

Support method type “VidiFlow” for Storage Accesses

A new storage method type “VidiFlow” was introduced allowing VidiFlow agents to access local storages which are handled as VSA storages by VidiCore. Supported protocol are FILE and the different cloud storage protocols.

CP Maintenance Mode

The maintenance mode feature in ConfigPortal is designed to ensure the integrity and availability of the Git repository during critical operations such as upgrades or maintenance. It provides both automatic and manual backup capabilities, allowing users to safeguard their repository data effectively. The following use cases are supported:

• Automatic backup of the Git repository when shutting down the CP POD

• Manual backup via API

• Restore the Git repository

• Set CP to maintenance mode (read-only state)

Display read-only state for contracts

CP now supports to properly display the state for workflows, rules and user tasks marked as read-only.

Changes for new metadata entries

The default sorting for new metadata is now case-insensitive.

The default setting for indexing in VidiCore is changed to false.

Lottie plugin error handling improvements

When the embedded Lottie preview window does not load an animation properly, CP reacts after a timeout and allows editing the configuration without the preview.

Fixes