Hybris 6.x features


Let’s discuss some of the important Hybris 6.x features introduced recently


SmartEdit(6.0)


This is one of the important features which enhances the business users experience with respect to content management.

We have WCMS to manage the Hybris UI(creating new page, component , edit content etc) but SmartEdit has come up with lot of additional features to make the CMS changes in a more robust and rapid way.

Business or non-technical users can easily make use of this feature to create new page, drag and drop components, moving the components to different positions within a page.

And most of all, we can preview all these changes in the same way how end customer could see in the site.

Business team (sales and marketing team) doesn’t need to rely on developers for quick UI changes as SmartEdit feature allows this in a much simpler way.

In 6.1 This feature has further enhanced with new features like Image Upload, Personalization.

In 6.3, This feature has further enhanced with features like synchronizaing of page and content slot,support of product carousal component etc.

In 6.4, This feature has further enhanced with features like Page cloning, permission based content editing.
When a user logs into SmartEdit, the user’s permissions are verified and only the content catalog versions that the user has permission to view and/or edit are displayed in the Sites landing page


CS cockpit in Back office (6.0)


This feature has moved cs cockpit into the Back office.

With this, They have integrated other Customer support related tools such as Customer ticketing system, Assisted Service Module(ASM).

It provides a single place for customer service agents, managers and Administrators to access different views according to their business requirements.


Distributed impex (6.0)


This is one of the much-awaited feature as it basically deals with large data set to import using impex.

We know that currently impex takes more time to import large data sets and this problem has been addressed in this feature.

The main logic of distributed impex is to  split impex import work into several batches of configured size and get them processed
 
by whole cluster.


Example:
If we have 10000 product records to be imported then we can define batch size as say 1000.

Then 10000/1000 = 10 batches will be created.

Each batch size is 1000 records.

And each batch will be running in the available node within the cluster and thus makes the import process faster.

In traditional impex import, impex runs in a single node so it takes considerable amount of time.

So, In case of distributed impex, we can use all the nodes within the cluster unlike using single node in traditional way.

Concept is named as Distributed impex as the impex tasks will be distributed across several nodes.

The most important benefit over here is, it uses one Transaction to run all the lines of batch and only one query will be executed for all the lines of batch.

There is no change in the syntax and other options of impex.


Promotion and Rule engine (6.0)


This feature has made the promotions and campaign management much simpler.

We can create lot of complex promotions by setting rules based on the requirement in Rule engine.

This feature has provided lot of promotion templates using which required promotion can be created by business users without much involvement of technical team.

This feature has introduced Rule builder which provides set of predefined conditions and actions which can be combined as per our need of custom promotion.

Example:
Condition: Cart total > 3000
Action: Fixed discount on cart

Also, Custom promotions can be created using Drools and Rule aware objects.

This new promotion and Rule engine feature has deprecated the jalo layer for writing custom promotions (earlier Jalo layer is used to write custom promotion logic)

Other existing features of promotions like assigning priority and providing promotions message to display on storefront are still intact.

This promotion engine feature is included as part of the Back office.


In 6.1 , This feature has further enhanced with Coupons management

In 6.3 , Voucher module has been deprecated and hence it is advised to use coupons instead of Voucher module.

In 6.5 , They have introduced Drools 7.0 and also provided promotion planning to activate promotions within a specified period of time.


Datahub


The Datahub is an existing feature in old version of Hybris and in latest version, they have improved its performance by introducing cache canonical items and cache target items.

It has also provided basic authentication for datahub URLs using Spring security mechanism.

In 6.3 Datahub, Hybris provides Out of the box support for clustering which helps in graceful handling of any failover.


Search and Navigation (6.2)


This feature is related to Solr search and Solr is now supporting in Cloud also to improve the scalability of searching.

In 6.3 they have introduced Search Query template using which we can improve the search results available to customers.

Example

We can configure search query to sort the result or group the result or we can specify the page size etc.

This feature can be used for keyword search and autocompleting suggestions


In 6.5 , They have also introduced Search term highlighting feature so that search terms in the result will be highlighted in the storefront


Backoffice Product content management (6.4)


This feature has introduced product cockpit functionality with some additional features in the Back-office framework.

This has introduced 2 perspectives in Backoffice PCM

1) Products Search and Browse View

In this view, We can search the product based on some keyword and we can also select facets to filter the result further.
We can also edit the product content and synchronize the same

2) Assortment View

In this view, we can Browse catalogs, categories and drag and drop the products from one category to another category.

In 6.5, they have also introduced collaboration center to manage the workflow to communicate more effectively within different set of business users responsible to handle product data.

So in BackOffice PCM, we can create workflow by attaching products and send them for review or to edit some changes etc.

And assign each task of workflow to specific employee so that they can do their part of work and complete the task.


Integrations


In addition to all the above feature Hybris has introduced several integrations like

Yaas integration with Hybris commerce using Datahub.

Marketing integration

Cloud for Customer Integration

SAP digital payment integration

OMS integration with SAP HANA and also multiple backend system
With this feature,Order Management for SAP Hybris Commerce can be done with a mix of SAP S/4HANA and SAP ERP systems.

About the Author

Karibasappa G C (KB)
Founder of javainsimpleway.com
I love Java and open source technologies and very much passionate about software development.
I like to share my knowledge with others especially on technology 🙂
I have given all the examples as simple as possible to understand for the beginners.
All the code posted on my blog is developed,compiled and tested in my development environment.
If you find any mistakes or bugs, Please drop an email to kb.knowledge.sharing@gmail.com

Connect with me on Facebook for more updates

Share this article on