Predefined quality gates

Use the predefined completeness checks and quality gates of censhare dedicated solutions to create a quality gate sequence for your product, media and content assets.

Context

Completeness checks are the base components of Quality gates. Quality gates can be combined into a Quality gate sequence.

Introduction

The quality management of product data is essential in a PIM system. Quality gates help you to achieve the required level of data completeness. We recommend that you define Quality gates for the different domains of your PIM system.

A Quality gate contains one or more completeness checks. A completeness check verifies a single property, relation, or file of an asset. The output of a completeness check is a Boolean expression that can be true or false. If true, the asset passes the respective completeness check. If false, the asset fails the completion check.

The basic usage of a completeness check verifies whether one of the following exits:

an asset property (for example a product feature)
an asset relation (for example a main content relation)
an asset file (for example a file in an Image asset)

Additionally, the check can include any attribute of the target. For example, a completeness check for localized content can verify, whether the related content asset has a certain language attribute. The completeness check for the main picture can verify, whether the related image has a certain MIME type.

For these basic usages, completeness checks are defined in an XPath expression. For more complex completeness checks an XSL query and transformation can be added.

To add Quality gates to Product assets, you must assign the Quality gates to a Quality gate sequence. The Quality gate sequence applies the assigned Quality gates in the defined order. A Quality gate in the sequence can only be achieved if all predecessor Quality gates are achieved as well.

The censhare standard solution contains the preconfigured Product Quality gate sequence. This Quality gate sequence is prepared for Product assets. Assign your Quality gates to this Quality gate sequence to use them in your PIM system.

Predefined completeness checks

The censhare standard solution contains the following predefined Completeness checks on Products:

Completeness check	Usage
Check child task completion	Checks if the Tasks assigned to a Product are completed (only if a Task is assigned to a Product).
Check EAN (product)	Checks if a Product has an EAN.
Check retail price (product)	Checks if a Product has a retail price.
Check feature story child	Checks if a Product has an assigned Feature story.
Check text block child	Checks if a Product has an assigned Text block asset.
Check main content child	Checks if a Product has an assigned Main content asset.
Check main content child localized	Checks if a Product at least two assigned Main content assets and that the target assets have language attributes DE and EN.
Check main picture child	Checks if a Product has an assigned Main picture asset.

You can use any of the above Completeness checks as is. Some checks require customization. For example, customize the Check main content child localized for other languages:

The predefined standard check has the following XPath expression:

count(child_asset_rel[@key='user.main-content.']) ge 2 and (for $x in child_asset_rel[@key='user.main-content.'] return cs:get-asset($x/@child_asset)/@language) = ('de', 'en')

CODE

To check if three Main content assets with the languages English, French, and Italian exist, use the following XPath expression:

count(child_asset_rel[@key='user.main-content.']) ge 3 and (for $x in child_asset_rel[@key='user.main-content.'] return cs:get-asset($x/@child_asset)/@language) = ('en', 'fr', 'it' )

CODE