Customers can be redirected to a URL specified by the vendor.

Keyword redirects can be easily configured using the Backoffice administration perspective.

Keywords make Solr searches more efficient.

Keywords specify synonyms that redirect to standard catalog terms.

The flexible search query returns a null value.

The flexible search query returns “PinkCandle”.

The flexible search query returns an SQL exception.

The flexible search query returns an empty list.

A type access right on the Product type for the user group

A search restriction on the UserGroup type

A search restriction on the Product type for the user group

A type access right on the UserGroup type

Redefine the default CMSComponentController alias

Create a JSP named(componentTypeCode) jsp

Implement a renderer in the cmsComponentRenderer Registery

Create a controller in the cmsComponentControllerRegistry

Delete a build that is no longer needed

View the history of the past deployments of a selected build

Deploy a successful build to a certain environment

Rebuild a successful build to do a performance test

A webhook requires an integration object as notification payload and consumed destination as the webhook…

A webhook uses the optional filter attribute to control which consumed destination will received notifications

A webhook can be configured to send notifications when an item is created, updated or deleted.

A webhook guarantees the At Least Once(ALO) principal and concurrent events are not completely discarded.

In the customPromotion-backoffice-config.xml file

In the customPromotion-spring.xml file

In the customPromotion-beans.xml file

In the customPromotion-items.xml file

Spring beans of backoffice web context

Context configuration object definition

Virtual socket definition

Widget connection

Create a JSP named [componentTypeCode].jsp that pulls data from a [ComponentTypeCode]Data

object.

Configure a custom controller bean and redefine the DefaultCMSComponentController alias to

point to it.

Configure a renderer in the cmsComponentRendererRegistry that doesn’t need to use a data

object or a view.

Create a controller for this component and register it in the cmsComponentControllerRegistry

Disable the autostart for the default instance. Enable the autostart for the cloud instance. Set the

cloud instance mode to true.

Disable the autostart for the cloud instance. Enable the autostart for the default instance. Set the

default instance mode to cloud.

Disable the autostart for the default instance. Enable the autostart for the cloud instance. Set the

cloud instance mode to cloud.

Disable the autostart for the cloud instance. Enable the autostart for the default instance. Set the

cloud instance mode to true.

Synchronize the category page in the Backoffice Administration Cockpit

Run a Solr indexer operation in the Backoffice Administration Cockpit

Synchronize the involved product in the Backoffice Product Cockpit directly

Re-import the price using ImpEx

Trigger the experience calculation for certain URL patterns.

Trigger the experience calculation after a defined number of requests.

Trigger the experience calculation when the customer logs in.

Trigger the experience calculation when the customer adds a product to the cart.

Trigger the experience calculation when the customer is promoted to a reward-level status.

IndexerStrategy

IndexerQueryContext

IndexerListener

IndexerService

After the order has been fraud checked

After the order has been completely sourced

At the first stage of the fulfillment process

After the payment has been processed

One-to-many relations are stored in the links table.

One-to-many relations are binary objects.

One-to-many relations are stored in a column.

Many-to-many relations are deployed as a table.

A list of Content Catalogs providing the pages, slots, and other CMSItems shown to Customers

A list of Product Catalogs providing the product info shown to Customers

A list of customers associated with the BaseStore.

A list of warehouses that support the delivery

A list of points of service that represent local branches

Use feature descriptor values if the values of the new feature are limited to a selection.

Create an empty classification unit even if the new feature doesn’t have a unit.

Use a feature descriptor to represent the name of the new feature and assign it to the product.

Create a classifying category with an attribute assignment model and assign it to the product.

Use the hot folder functionality by creating a file in the configured hot file.

Use the Backoffice Business Process section.

Invoke the appropriate method of the BusinessProcessService from a script in the hybris

Administration Console (hAC) scripting console.

Invoke the appropriate method of the BusinessProcessService from Java code

Overload the existing method of CommerceCartService by adding the new parameter.

Add a new property to CommerceCartParameter in a beans.xml file.

Extend the default strategy called by the method to handle the new parameter.

Extend the default implementation of the method to handle the new parameter.

To store the configuration of the rule engine

To provide the data as facts in rule conditions and actions

To persist the results of the rule evaluation

To eliminate unnecessary data provided by complex objects

Define the process in BPMN format.

Define the actions as Spring beans.

Create actions in Java code.

Define actions as new item types.

Define the process in XML format.