Skip to content

Bizzkit 21.54.0

Version 21.54.0
Release Date 28 Mar 2023
Download Bizzkit universal feed
SDKs Bizzkit nuget feed

Requirements

Requirement Minimum supported version Tested version(s) Requirement of
SQL Server SQL Server 2016 SQL Server 2017 All
Elastic 7.17.8 7.17.8, 7.17.9 DAM, Ecommerce Search, PIM
Redis 6 6 Ecommerce Search
Click for explanation...

SQL Server 2017 is the earliest version that is available as a docker image and so even though Bizzkit officially supports 2016, testing is done on 2017.

Elasticsearch is known to introduce breaking changes in minor releases and we therefore explicitly test the Bizzkit products with the two most recent releases. Other 7.17.x versions may work but are not tested explicitly.

Highlights

  • Completion of Pinning feature making it possible to pin products in Ecommerce Search via UI and search api Ecommerce Search product pinning

  • Completely new search & filter engine in PIM New PIM product filters

  • API endpoint to create predefined settings in DAM

Changes

CMS

Bug fixes

BCMS-840 URLDecoding of segmentations keys on public API endpoints

Friendly reminder that using segmentation IDs containing slashes is considered bad practice and IF used will only work when running CMS as a service. Also note that using characters that require URL encoding is strongly discouraged, since they can lead to confusion on whether the key is already encoded/decoded in certain situations, leading to double encoding/decoding accidents.

New features

BCMS-826 As a user I want to be able to navigate to ECommerceSearch via the product links in the top bar

Enhancements

BCMS-837 When navigating to DAM from CMS user session stays active, so the user does not have to login again

DAM

Bug fixes

BDAM-1150 Cache files which fail when running RebuildExpiredCachedFiles are not marked as failed

New features

BDAM-1030 Add API endpoint to create predefined settings

BDAM-966 As a customer I need filenames cached in order for the DAM SaaS offering to be usable

BDAM-1076 As a user I want to be able to navigate to ECommerceSearch via the product links in the top bar

Enhancements

BDAM-1099 Add support for Cache-Control header with 365 days expiry for images in cloud

BDAM-1075 Mediabank attempting to create cached files that apparently don't exist

  • Add cleanup-missing-original-files command to installer to be able to cleanup original files which are missing from disk
  • Fix: Better protection against failing builds of cached files, which could cause no new cached files to be built

Bug fixes

BECS-912 When deleting a range or term filter, the delete filter does not show old values

BECS-995 Repeatedly adding the same metrics results in 500 with db unique constraint exception

BECS-1221 Adding word associations from the Dashboard should put the terms in the correct place

BECS-1235 Multiword containing an ignored word throws error

New features

BECS-1121 As a user I must be able to delete a scope

BECS-1151 As a user I want to pin products to a context

Enhancements

BECS-1294 Remove number of SKU's from result limit calculation

BECS-1302 Improve accuracy of did-you-mean results

BECS-1346 Add missing vertical divider in "Compare" view

BECS-931 To improve security, segments should be aware of the hostname(s) of the webshop

BECS-1347 Publication Bar active on all pages

BECS-1423 BestFittingContextBoost MUST handle multiple split test ids

MAIL

New features

BMAIL-334 As a user I want to be able to navigate to ECommerceSearch via the product links in the top bar

PIM

Bug fixes

BPIM-2625 Adding an inline product extension frameset loads correct url

New features

BPIM-3139 As a user I want to be able to navigate to ECommerceSearch via the product links in the top bar

BPIM-1809 New search engine and more flexible product filters

Including:

  • Easier to find products either by free text search or by creating product filters

  • The user is guided through all possible options when working with product filters

  • New filter operators available which make it easier to filter

  • Logical grouping of filters available in advanced mode, which allows for more complex filter queries

  • Free text search doesn't require any configuration by default: all attributes are searchable

  • Easy to use boosting options for attributes, keeping the user in control of which attributes to search on

Warning

The new search engine limits the range of PDecimalX types to 18 significant digits (from 20), which means PDecimal1's range is now (-/+)99999999999999999.9 while PDecimal9's range is now (-/+)999999999.999999999.

Upgrade instructions

Note

In upgrade instructions, it is assumed that onprem installations use configuration files supplied by Bizzkit as is. If not, then placeholder changes must be merged manually.

Please refer to the CMS, DAM, and MAIL configuration files for reference.

CMS

Optional: In order to add a navigation link to EcommerceSearch in the top bar, add the ECommerceSearchUIUrl placeholder in the ContentManagement.Elements.dll-Placeholder.config file:

<add name="ECommerceSearchUIUrl" value="" />

DAM

This version of DAM contains a database migration. After upgrading, you should verify that database has version 21.16.0 (eg. under Settings -> General Information).

Optional: In order to add a navigation link to EcommerceSearch in the top bar, add the ECommerceSearchUIUrl placeholder in the MediaBank.Elements.dll-Placeholder.config file:

<add name="ECommerceSearchUIUrl" value="" />

MAIL

Optional: In order to add a navigation link to EcommerceSearch in the top bar, add the ECommerceSearchUIUrl placeholder in the MailOffice.Elements.dll-Placeholder.config file:

<add name="ECommerceSearchUIUrl" value="" />

PIM

Danger

This release does not support rolling upgrades.

If database contains any data that exceeds the new PDecimalX range, migration will fail and roll back any changes.

This means:

  • Do not upgrade if existing data exceeds the new PDecimalX range
  • Do not allow users to be working in PIM during the upgrade
  • Do create a backup of the database before upgrading (migration is irreversible)

Before upgrading

Due to the large number of possible PDecimalX values in PIM, it is recommended to verify before starting the migration, that no values are present in the database which would fail the migration check.

To help with this, a collection of SQL scripts have been included in the 21.54.0 release assets file.

The scripts are as follows:

  • verify_attribute_collection_item_values.sql
  • verify_attribute_value_ranges.sql
  • verify_global_list_items.sql
  • verify_product_validator_rules.sql
  • verify_selected_units.sql
  • lookup_owners_of_attribute_collection.sql

Warning

The scripts are all written targeting the 'dbo' schema. If the solution being upgraded uses an alternative schema, please manually update the scripts with the alternative schema.

For the majority of the verify_x scripts the results should be sufficient to locate the offending value within the running PIM and handle it accordingly.

For the verify_attribute_collection_item_values.sql script however, the result values will be harder to interpret. For this purpose an auxiliary script is included, lookup_owners_of_attribute_collection.sql, which allows the user to provide a number of AttributeCollectionIds, as are returned from verify_attribute_collection_item_values.sql, and resolve those to the entity in PIM where the illegal attribue value is assigned.

Once the result of running each script is empty, it is safe to proceed with the upgrade.

After upgrading

Verify that database schema and content has version 21.35.0.7 (eg. under System Administration -> General Information) which means that database has been successfully migrated.

The product index engine has been rebuilt completely and the old Elastic index is not compatible with the new engine, so a new one must be created:

  1. Set a name for the new index in the Bizzkit.PIM.Console.exe-appSettings.config file (use a different name to avoid overwriting old index in case a manual rollback is needed):

    <add key="productIndex.index" value=""/>
    
  2. Run the consolidate-configtables command in the PIM console in order to save the setting

  3. Run the consolidate-pim command in the PIM console which implictly creates a new index

Optional: In order to add a navigation link to EcommerceSearch in the top bar, add the search.uiUrl setting in the Bizzkit.PIM.Console.exe-appSettings.config file:

<add key="search.uiUrl" value=""/>

Next, run the consolidate-configtables command in the PIM console in order to save the setting.