February 2025 Releases

Users can now preview configuration files, including metadata-mappings.cfg, xml-index.cfg, and site_profiles.cfg through WebDav and the configuration file manager.

The configuration is displayed in raw format, and users can copy it between different instances or resources.

This minor improvement removes the often cumbersome, time-consuming, and error-prone approach of manually entering the configuration information using the dedicated Administration UI.

The original maximum timeout that could be set for crawl requests to a web page was 30 seconds. Pages that exceeded the 30 second crawl timeout would not be processed during an update.

The maximum timeout that can be set for crawl requests (crawler.request_timeout) was increased to two minutes (120 seconds). If the crawl request timeout configuration is set to the maximum value, then web pages that take over 30 seconds will now be processed

In Preview mode, users encountered an issue where the total segment count was not visible when selecting multiple segments, particularly when the longest priority segment had a lengthy name.

This limitation has been addressed by displaying the total segment count in Preview mode, even when the highest priority segment is selected with a long name.

Previously, the File Store UI did not support uploads larger than 50 MB while the API handled up to 100 MB.

This change brings the UI up to API feature parity, offering a more convenient way to manage files through the UI.

Quick options in components initially supported enum properties. This release has expanded quick options properties to support boolean types. This minor improvement helps component developers create more flexible components that meet organizational needs.

The push data source and filter classes ignored the filter.class configuration key. This key was required for each MODIFY request sent to the push API. The lack of the configuration key caused unexpected behavior between data sources depending on the type.

The change implemented applies the filter.classes configuration key value for push data sources if no filter query option is provided with the push API request.

The StringDocumentFilter generated an illegal character error when processing a URL set by the plugin, which caused errors while updating the data source with plugins applied.

The plugin framework tool can now handle special characters such as | in the start URLs. A raw string is first converted to a Java URL object and then encoded into a Java URI object while ensuring special characters are accepted by URL and not URI.

If a user did not have the correct permission to modify configuration keys in an attempt to update it, instead of the relevant error message the UI was displaying [object] [object].

The error handling under these circumstances was improved so that the user either receives useful feedback about the invalid value of the configuration key or the lack of permissions they hold to modify the key.

The push system attempted to clean up all data sources running as query processors but failed because the document data and delete lists were missing. When setting the push optimization features, the “prepare Funnelback for upgrade” feature failed.

Push optimization features were adjusted to skip cleaning up data sources in SLAVE mode when preparing to run an upgrade. These adjustments allow the optimization features to iterate past the skippable collections and complete the process.

If the display of a key depended on the value of another key with a parameter, only the first key value with a parameter would be taken into account, instead of any that fulfilled the condition. Adding the next key with a wildcard that fulfilled the dependent key condition would not display the dependent key form to provide its value.

The fix displays the dependent key form if any key with a parameter fulfills the condition instead of only the first key value. Users are now able to provide plugin configuration details.

The following types of transient errors were causing OAuth to unexpectedly fail, triggered fatal errors, and ultimately prevented users from continuing with the authentication flow:

Users experiencing these transient errors would see an ungraceful failure in the authentication process and would need to manually restart their attempt.

OAuth authentication has been updated to automatically retry the process in the event of transient errors. Instead of immediately triggering a fatal error, the system now attempts multiple retries before stopping authentication completely.

This change significantly reduces the likelihood of failures and ensures a smoother experience.

When an asset was published or set to live, a bug with how version history event listeners were loaded caused minor version history entries (for example, 0.x.0) to not be recorded. This issue caused inconsistencies between the documented versioning rules and the stored version history, making it difficult for users to track version changes.

The event listeners are loaded before proceeding deep into the HIPO execution path. Customers can now reliably track minor version history updates made to assets.

A blank content page triggers an issue where the reload button appears clickable but does nothing, leading to user confusion.

The logic for the reload button was modified to perform its intended function even when there is no content to be reloaded. With these changes, the reload button now correctly performs a reload action and animates upon click.

When configuring a CDP event with an Authorized condition, the Events UI did not protect against selecting unsupported rule types or typing string values when the condition required boolean values.

To fix this problem, the Authorized event condition now automatically fills the correct values, which are read-only and set to equals true. Users can now configure Authorized event conditions that behave as expected.

Fixed a RangeError: Maximum call stack size exceeded console error when navigating to a locked workspace using the Tenant Admin UI.

Fixed an issue where some threads were missing on the Execution page after applying specific filters.

Fixed an issue in the Implement tab where changes to the shutdown timeout for a flow did not apply without refreshing the page.

REST assets had code that only functioned if they were running within a web request with "Append Query String" enabled. If REST assets were used through a scheduled task, the task would fail to run and cause a cron deadlock.

REST assets have been updated to assume an empty query string when running without a web request. REST assets with "Append Query String" enabled can be run from scheduled tasks.

Mirror and asset syncing operations only searched for asset IDs in specific patterns to avoid treating random numbers as asset IDs. Designs that specified a Menu Normal Design Area with a root_node asset ID configured directly in the parse file would be erroneously excluded from the search and break the imported design because they failed to migrate.

Mirror was updated to match asset IDs in Menu Normal Design Area root_nodes, which allows them to migrate correctly with Mirror or asset syncing.

Functionality to update access within Advanced Forms was only passing updated access requirements and not the user’s name, which accidentally overrides the name with "undefined". Any reporting or viewing of users will show "undefined undefined" as the author’s name.

With this release the full name of the user is updated in Advanced Forms each time their access is updated. Full names of users are correctly showing up in reports.