Contents - What's in the release?

This release primarily focuses on a lot of bug fixes as a preparation to our Long term support release.

Fixes

AI Studio

Fixed an issue where

• Recommend bubble is not completely displayed and thumb-down button isn't aligned.

• There is a mis-configured link in the build-model step.

• Rejected feedback doesn't get marked as processed.

• Studio plugins in AI studio space fail.

• In the Feedback widget for incorrect classification, there is no option to select the correct class.

• View for configuring a Ground Truth is not rendered properly.

• Ground Truth: labeling of bigger documents triggers 414 error.

• List of documents overflows in the Ground Truth list view.

Cognitive Search

• Added a tooltip to see full name in communities.

• Search bar no longer overlaps tabs on communities screen.

• Fixed the import of Cognitive search project template.

• Improvements to PDF Highlighting of Query Matches.

• Upgrade Cognitive Search Template to support additional typeahead strategies.

• Change default sort order for cognitive search project template to: “By Relevance” from "By Time".

• Visual fixes around horizontal Scrolling and overflowing Search Bar community tabs.

• Highlights from global feed now has community display for all items instead of just the first item.

• Fixed an issue where Global Search Bar not taking right colours.

• Add a configurable option to disable number of items for communities if required. Turning this option will have a performance impact.

• Spacy NER cannot handle large text inputs which is used for content typeahead.

• Fixed an issue where Communities headline widget has a broken arrow shape.

• Fixed an issue where Favorite filters search is broken.

• Fixed an issue where community query displayed inside the breadcrumb instead of community name

• Added infinity scroll loading for communities.

• Added a Search option on communities list page to find a community.

• Sorted list of communities on communities list page is not case sensitive.

• Newsletter

  • Sending of newsletters does not fail when

    • There is no full name.

    • No communities are subscribed.

    • With additional_data error.

  • Update of scheduling frequency on project settings now reflects again in already scheduled newsletter tasks.

  • Triggering a sample email for testing purpose also gets populated with data.

  • Item links now redirect the user to a Squirro dashboard instead of the original source.

Translations

• We now also have support for French and Italian language in Squirro interface. Needs to be enabled in the configuration.

New Ingestion Pipeline Editor

The pipeline editor has been completely recreated. The new editor is more visual, and provides a much easier overview of the various pipelines in a project.

• In addition to that we have also laid down a lot of ground-work to allow for the re-running of pipeline workflows (for datasources running in the Frontend only) which allows for easier experimentation during the project setup process. For the more technical audience, this is enabled through the following underlying configurations. This will be included in the frontend in the upcoming releases.

  • We have added a new built-in pipeline step “Transform Input” which does the item fields and facets mapping. This was previously done in the dataloader itself but can now be handled in the pipeline itself. This step is controlled using the configuration option item_transformation_in_pipeline. It is disabled by default, and should be considered a beta feature for this release.

  • We have introduced a new processed directory in the Ingester to store the input data to this directory before performing pipeline steps. This enables us to keep a copy of the raw data to re-run the pipeline without fetching the data from the original source. This behavior is controlled by the configuration option keep_processed_data, which is also disabled by default.

  • We have also extend the Ingester to automatically remove the input data after a certain time period or disk space threshold to avoid disk over-filling. This is controlled by the configuration options days_to_retain_processed_batchesand hours_to_retain_processed_batches. This mechanism kicks in when the keep_processed_data is enabled.

• In addition, we now offer three different Pipeline Workflow presets designed for various use-cases.

Open

• We have also added the functionality to rename all of the steps in pipeline workflow to your liking.

• Pipelets which hint in their names that they perform Known Entity Extraction are now by default categorized in the “Relate” section of the Pipeline Editor.

Miscellaneous

• Projects names are visible again in the project sidebar.

• Adapt the SQ Dataloader behavior to not kill jobs automatically every 30 mins as long as we can fetch new data.

• Fixed an issue where user cannot change avatar picture because save button missing.

• Add animation for “Add feed sources” button on the feed dataloader plugin.

• Fixed an issue where Startup of topic service would fail to install saml2 plugin because of failing to install the pysaml2 dependency.

• Multiple Visual bug fixes around Cards widget and item detail view.

• Improve exception handing in the feed plugin.

• Scan endpoint now is not limited to 1000 entities per call/iteration.

• Fixed the creation of favorites on the dashboard.

Salesforce SDK

• Fonts are now downloaded from Salesforce instead of Squirro.

• Styles no longer bleed from Squirro to Salesforce.

• Fixed an issue where we were unable to open items.

Breaking Changes

• With the introduction of the new pipeline editor, the navigation structure in the Setup space has changed. To make room for the new pipeline editor to use the full width, all the options that were previously under the Enrich tab have now moved to the new AI Studio tab. Rerunning of enrichments will soon disappear from there and then move into the new pipeline editor properly. As a result, any custom studio plugins under these sections have to be re-uploaded to either one of the existing sections or to a new section called “AI Studio”. This Can be achieved by specifying the ”location”: “dss” in the studio_plugin.json file.

• Pipeline steps which are part of existing Pipeline workflows should continue function normally given that the included migration script was executed successfully. In case that something is not correct with an existing step of a workflow (e.g., no configuration options for a Pipelet when it should have), please remove the faulty step and add it again to the workflow. Then it should work as expected.

Fresh Installation Instructions

Please follow the regular installation steps

Upgrade Instructions