Hybris Features – 5.7 Series

Below is most entirely references from the hybris wiki, and reput together here.

Customer Ticketing System

The new Customer Ticketing System allows a customer to create, list and update support request tickets from a hybris Commerce Accelerator storefront – to connect customers with Cloud for Customer (or the hybris Customer Service Cockpit, or other 3rd party customer support system) Customer Support Agents.

In order to integrate the Customer Ticketing System, we:

  • Created a new Customer Ticketing System API
  • Created a new customerticketingstorefront AddOn for the Storefront accelerators
  • Implemented a customerticketingfacades Extension to support SAP Cloud for Customer, hybris Customer Service Cockpit and other 3rd party customer support system integrations

Single Sign-On Functionality

We introduced a new hybris Commerce samlsinglesignon Extension that uses an industry standard SAML 2.0 protocol to enable single sign-on functionality into the hybris Commerce – allowing cross-domain single sign-on functionality.

Assisted Service Module

The Assisted Service Module (ASM) provides one of the most important links in the integration, allowing a Customer Support Agent to login into a hybris Accelerator Storefront as the customer to prepare, then provide the customer with interactive sales and service support.  WCMS user restrictions enhance the customer sales and service support process by displaying more or less functionality and views to a Customer Support Agent.

In order to integrate the Assisted Service Module, we:

  • Integrated the ASM with SAP Cloud for Customer via a reference SAP Cloud Identity service, allowing single sign-on from SAP Cloud for Customer to SAP hybris Commerce (see above)
  • Implemented the capture and display of the Customer Support Agent’s details on the order details pages of the B2C Accelerator storefront, so that when a Customer Support Agent checks out a customer’s cart on their behalf, there is an audit trail of this for the customer or another Customer Support Agent or Manager
  • Implemented example restrictions, such as preventing an ‘asagentsales’ Assisted Service Agent user from checking out a customer’s cart on their behalf
  • Added additional Assisted Service Agent user groups (UN: asagentsales & asagentmanager (PW: 123456)) to easily use and demonstrate group related restrictions
  • Implemented ASM deep links within SAP Cloud for Customer (and the hybris Customer Service Cockpit) to deep-link directly into the ASM and Accelerator storefront, customer account or cart pages

Order Management Backoffice Perspective

  • Order Cancellation: This feature allows a Customer Service Representative (CSR) to cancel an entire order or part of an order. CSRs can select predefined reasons for the cancellation and also add comments.
  • Returns & Refunds: Customer Services Representatives can create return requests from previously fulfilled orders. CSRs can select predefined reasons for the return and add comments. When in store, CSRs can choose between manually refunding a customer or automatically refunding using the original payment method. This feature also includes a refund calculation where you can opt to refund the original amount of the return request, include delivery costs to the amount or manually override the amount to be refunded.
  • Fraud Reports: Set fraud criteria such as Black Lists and White Lists, Price Thresholds and let CSRs to accept or reject potential fraudulent orders.
  • Payment Transactions: View payments transactions and amounts authorized, captured or refunded.
  • Order Details Modification: CSRs can now change shipping methods and customers’ billing and shipping addresses.
Synchronization improvements

We have made several improvements to hybris-to-hybris sync that had its initial release in 5.6.

Improvements for configuration: Selecting a item type is sufficient to set up a new sync rule in the new Backoffice wizard. A suggested WHERE clause for catalog dependent types to be synchronized is generated automatically so that only items of the specified catalog version are synchronized. Attributes to be synchronized are defined within their own configuration item and get their ImpEx header definition generated automatically. Whole sets of sync rules can now be cloned to avoid starting from scratch especially for complex scenarios. For generating Data Hub schema XML we’ve added another wizard. Other new UI components allow to re-send a previously gathered change set to the Data Hub as well as completely resetting the change detection markers so that users can enforce re-synchronization if needed.

Among other issues fixed deletion via DataHub is working now and streaming data to the Data Hub has been speeded up by parallelizing that step.

The example configurations are now showing a ‘catalog publication’ and a ‘customer export with addresses’ scenario.

Solr 5 Support and running a standalone server

We provide a new solrserver extension that includes a standalone Solr server and manages automatic startup and shutdown with hybris. This keeps easy out-of-the-box search running for development and testing but enables an easier transition to production environments and support for the latest versions of Solr by not using embedded mode.

B2B Accelerator as AddOns to Core Commerce

The B2B Commerce Accelerator application is now delivered as an AddOn to the existing core commerce layer.

Being able to use the AddOn approach opens much more market value, allowing the generation of industry-specific accelerators with ease.

  • Facilitating the use of features and functionality as AddOns found within the core commerce layer allows for the B2B AddOn to tap into using them as needed by an implementation project.
  • Extracting and identifying B2B features and functionalities that can be moved to the core commerce layer opens up the possibility to have them used within other accelerators.

Benefits of B2B AddOn

The B2B AddOn was designed to house specific B2B Commerce functionality that can be seen through the accelerator. As the architectural redesign was planned certain features and functionality were identified that can be moved to the core commerce layer. Therefore, this approach resulted in the following benefits:

    • Multi-Dimensional Products functionality has been moved to the core layer thereby making it available to either a B2B or B2C implementation of the accelerator.
    • Accelerator Storefront Templates have been optimized so that common ones that existed within B2B and B2C have been defined as one.
    • Incorporate a Partial Responsive Capability with the B2B Accelerator due to the inheritance of certain storefront templates from B2C. Continued work to make B2B specific storefront template responsive is underway.
    • Other B2B Features and Functionalities will

Data Hub

The Data Hub 5.7 represents an important step in the evolution of the Data Hub. As of 5.7, Core+ has been forked to meet Data Hub specific persistence requirements. T he Data Hub team made significant changes to the persistence layer in order to improve performance, create better stability and provide a solid foundation for the professional edition. The Data Hub nows uses JPA and optimized SQL in the persistence layer. As a result of the changes, there has also been an increase in the overall performance especially with regard to the SAP HANA DB. The overall HANA performance has significantly improved and now the Data Hub performs better on this database engine than on other relational databases.

Simplified development by removing the requirement to use concrete subclasses for every Raw, Canonical and Target item created. The change is fully backward compatible so if the concrete subclasses are present, they will be used.

SpEL expression length increased from 255 characters to 1000 characters to enable the creation of more complex expressions.

UX Changes to add Manage Feeds and Manage Pools

Manage Pools:  The Manage Pools menu option allows you view and create pools.

For more information please see  Managing Feeds and Pools Using the Data Hub UI .

Manage Feeds:  The Manage Feeds menu option allows you view and create feeds for either the Global Pool or Named Pools.

For more information please see  Managing Feeds and Pools Using the Data Hub UI .