Bizzkit 23.4.0

Requirements

Changes

BIZZKIT

New features

BCPS-1154 Docker compose setup for solution partners, academy and demo

CMS

Enhancements

BCMS-1015 Improve segmentation endpoint compliance with Bizzkit REST API Standards

Endpoints related to segmentations, still in preview, have received some changes:

• POST /_/segmentations
  • Was always a PUT /_/segmentations, 23.2.0 release notes were simply not updated.
• DELETE /_/segmentations/{id}
  • Is now: DELETE /_/segmentations/{segmentationKey}
• POST /_/segmentation-permissions/by-user-and-key/{segmentationKey}
  • Is now: POST /_/segmentations/{segmentationKey}/permissions
• DELETE /_/segmentation-permissions/by-user-and-key/{segmentationKey}
  • Is now: POST /_/segmentations/{segmentationKey}/permissions/delete-by-user
• POST /_/segmentation-permissions
  • Is now: POST /_/segmentations/{segmentationKey}/permissions/by-user
• POST /_/segmentation-permissions/keys/{segmentationKey}
  • Is now: GET /_/segmentations/{segmentationKey}/permissions

BCMS-676 As a product owner I need REST based implementation of the Reverse API method BeforeMenuItemDeletedMethodV1Base in order to not rely as heavily on the customer solution

The payload of the PATCH /{segmentation-key}/menu-items/{menuItemId} endpoint now takes an additional (optional) deleteLock property:

1
2
3
4

"deletionLock": {
  "isLocked": true,
  "reason": "Delete reason"
}

Instead of requesting permission to delete a menu item in the reverse api, CMS now uses the deletionLock property on the menu item itself to determine whether a menu item can be deleted.

Note that this change is only active if the FEATURE_FLAGS_CMS__ENABLE_REVERSE_API flag is set to false and the beforeMenuItemDeleted setting is set to true in the cms configuration file.

BCMS-677 As a product owner I need REST based implementation of the Reverse API method BeforeMenuItemMovedMethodV1Base in order to not rely as heavily on the customer solution

The payload of the PATCH /{segmentation-key}/menu-items/{menuItemId} endpoint now takes an additional (optional) movementLock property:

1
2
3
4

"movementLock": {
  "isLocked": true,
  "reason": "Move reason"
}

Instead of requesting permission to move a menu item in the reverse api, CMS now uses the movementLock property on the menu item itself to determine whether a menu item can be moved.

Note that this change is only active if the FEATURE_FLAGS_CMS__ENABLE_REVERSE_API flag is set to false and the beforeMenuItemMoved setting is set to true in the cms configuration file.

BCMS-864 As a product owner I need a CRUD REST API for Content Block Placeholders instead of a mix of config and reverse APIs

BCMS-865 As a product owner I need a CRUD REST API for the data associated with Searcher and validator link types

BCMS-1006 Move segmentation sync job to API project

The segmentation synchronization job has been moved to the API application. The job is triggered as the API starts, and runs once every minute. The environment variable FEATURE_FLAGS_CMS__ENABLE_REVERSE_API=true must be set and available to the application at startup in order for segmentations and permissions to be properly synchronized. The synchronization is required for all projects that still depend on the Reverse SDK.

It's also important to note that the admin role needs ViewSystemConfiguration permissions in the Users application. This is so the synchronization job is able to know which machine clients exist and grant them the appropriate permissions in the CMS.

BCMS-1029 Show meaningful error message when starting up CMS with no segmentations/permissions for any segmentations

DAM

Other

BDAM-1008 Add ability for DAM to set Permissions based on Role via API

BDAM-1210 Do not include appsettings.Development.json in release package

BDAM-1211 Rebuild missing cache files job has been refactored such that it no longer crashes when using a shared folder as storage

BDAM-1213 Enable DAM to switch exif extractor

ECOMMERCE SEARCH

Enhancements

BECS-1489 Added endpoint for deleting content in bulk

BECS-1634 Added language support for Czech, Hungarian, Polish, Portuguese, Romanian

BECS-1643 Content is now also filtered by scope configurations

BECS-1647 It is now possible to specify the default number of content search results on a scope

PIM

Bug fixes

BPIM-3515 Searching for global list item

Other

BPIM-3514 Overall dashboard UI Improvements

BPIM-3517 Upgrade Material UI to v5.13.3 (latest)

BPIM-3456 'Any of' filtering now supports up to 65.536 terms

Upgrade instructions

None