The latest version of HCL Commerce, v9.1.6, will be out shortly. One of the features introduced is the new version of Customer Service Representative (CSR) capability. This is the first phase of CSR capability that we are adding to HCL Commerce, and this phase is focused on a functional replacement of the CSR capability from the Aurora storefront (also known to some of our customers as Buy On Behalf). While this is mainly a functional replacement, with the same CSR use cases as were in the Aurora store, there’s a big difference architecturally with the new implementation. In Aurora, the CSR capability was embedded into the storefront .jsps, meaning that for any of our customers who didn’t start with the Aurora store as the base, they needed to spend the time and money to re-implement our CSR capability into their storefront. There was no way to just “drop” the capability into the store, as it was spread across multiple .jsp pages. It had to be re-coded across all of those .jsps. That changes with the new implementation. It’s done in REACT, to match the rest of the storefront, but it’s not actually coded into the Emerald/Sapphire sample SPA (single page application). Instead, it is a separate SPA, informally called a mini-SPA by our development team. This mini-SPA renders the CSR tool which allows a CSR to log in, find customers, find orders, and other such operations. When it comes time for the CSR to make modifications to the customer’s information, they can press the button to view it in the store. The storefront launches, with the CSR logged in on behalf of the customer they have selected. Under the covers, what’s happening is that the CSR mini-SPA is passing the login information to the URL of the chosen storefront. As...

We want to provide our customers with the tools that they can easily customize to meet the needs of their business. Read this interesting blog to know more.