What’s new and changed in Funnelback SXC and Funnelback 16?
- New and enhanced features
- Client API access tokens
- Important changes
- What features have been retired?
Learn about the new features and important changes released in Funnelback SXC and Funnelback 16 and how they are different from the previous Funnelback 15.24 version. This document is updated frequently as a tool for users to compare features between the latest release of Funnelback SXC/Funnelback 16 and Funnelback 15.24.
A change log that provides detailed information on all the changes in Funnelback since v15.24 is also available.
Funnelback is now available as an integrated product in the Squiz experience cloud suite of products. Squiz experience cloud provides an integrated solution to one or more Squiz applications via a single interface.
This is the first step to provide much closer integration with other products within the Squiz product suite such as Squiz Matrix.
Funnelback SXC/Funnelback 16 includes a completely reimagined administration dashboard which focuses on simplifying the user experience of managing Funnelback and interacting with the analytics and reporting features.
The administration dashboard includes a completely redesigned process for the creation and management of new searches.
In Funnelback 15 and earlier the concept of collections and profiles was highly confusing for users and it encapsulated a number of different concepts and had a different meaning in different contexts.
In Funnelback SXC/Funnelback 16 these have been replaced with:
- Data sources
A data source is used to define a single content source such as a website (or set of websites); a YouTube channel or a database. These are roughly equivalent to a non-meta collection in v15 and earlier terminology.
- Search packages
A search package is used to package together one or more data sources into a combined data set that can be searched. These are roughly equivalent to a meta collection in v15 and earlier terminology. In v16 you can’t query a data source directly - the search interface must be set up by creating a results page which can only be defined on the search package.
- Results pages
A results page is used to define a search that a user will interact with. The results page includes the search templates, all of the configuration and reporting associated with a search that is provided to an end user. These are roughly equivalent to a service enabled profile in v15.24 and earlier terminology.
Plugin-based extensions provide Funnelback developers with a way of safely extending the functionality within Funnelback to provide reusable and upgradeable plugins that can be mixed and matched on search implementations.
Approved Funnelback extensions will be made available via a marketplace (similar to an app store).
The features superseded by plugins - Groovy document and Jsoup filters, hook scripts, custom workflow and custom gatherers are no longer available to be used in Funnelback SXC/Funnelback 16 and any existing implementations that are upgraded to Funnelback 16 must rewrite this custom code using the plugin framework.
The update scheduler, responsible for updating data sources and analytics has been greatly enhanced.
It enabled administrators to schedule an update to occur at a fixed time, or on a schedule and incorporates features that were previously only available when subscribing to hosted Funnelback SaaS offering.
Funnelback 16 introduces a new concept of a client, which groups together all of the search packages, data sources and results pages that belong to a specific customer or organisation.
This enables better management of these as well as the administration roles and users associated with that client.
Funnelback 16 now includes an upgrade utility that assists that automates many of the tasks required to upgrade a set of collections from Funnelback 15.
Many new administration APIs have been added to Funnelback SXC/Funnelback 16, including:
Management (creation, deletion) of results pages and search packages
Management (reading, editing) of gscopes and external metadata
Determining upgrade progress and status of data source updates
User independent API access tokens (associated with a client) are now supported. User-based access tokens should be updated to client tokens in most cases so that API integrations do not break when the user account that owns a token that is being used in the integraton is removed.
The data model has been streamlined in v16 reducing the overall size of the JSON response. As a result some elements have been removed or merged. The upgrade tool attempts to fix existing references within configuration but it may be necessary to make additional manual changes to imported configuration.
The addition of plugins in Funnelback SXC/Funnelback 16 enables the functionality provided by Groovy hook scripts, filters and custom gatherers; as well as workflow scripting to be performed in a safe and controlled manner.
As a result these are now considered deprecated and they should be replaced with plugins that perform the same functions.
Existing scripts cannot be used with the SXC. The scripts will still work in v16, but they can no longer be edited or accessed via the administration dashboard.