Bloomreach Accelerator: B2C Commerce Release Notes - Bloomreach Experience - Open Source CMS

This article covers a Hippo CMS version 13. There's an updated version available that covers our most recent release.

06-12-2019

Bloomreach Accelerator: B2C Commerce Release Notes

This Bloomreach Experience Manager feature requires a standard or premium license. Please contact Bloomreach for more information.

Project status

Solution version Bloomreach Experience Manager version
2.x  13.x
1.x 12.x

Release Notes (2.x)

2.4.1

Bug

  • [ACCEL-622] - Support "Add to Cart" button feature in brSM decorated Product Detail Page
  • [ACCEL-643] - CTOrderRepositoryImpl instantiates CTCartRepositoryImpl directly instead of injected via Spring
  • [ACCEL-666] - Failing unit test when trying to set up a visitor context without an existing HstRequestContext
  • [ACCEL-688] - Connector component path variables field is ignored while interacting with commerce backends

Improvement

  • [ACCEL-541] - Ability to display Campaigns
  • [ACCEL-695] - Make BRItemModel#getResource() public for extensibility

2.4.0

Bug

  • [DXPFORC-462] - [ElasticPath Connector] ElasticPath cart repository doesn't encode the product code when adding product to cart
  • [DXPFORC-464] - Autosuggest product items renders links to incorrect product detail pages
  • [DXPFORC-469] - Personalization command doesn't parse the product id correctly

Improvement

  • [DXPFORC-461] - CartProductListCommand may cause infinite redirect if not used correctly.

2.3.0

Upgrading to Starter Store 2.3.0? See the following Upgrading Notes.

Bug

  • [DXPFORC-393] - Multiple issues with special characters in filters
  • [DXPFORC-403] - Inconsistency between Category Highlight Component items added and supported
  • [DXPFORC-404] - Replace the category view using treeview option (without description) in the external document modal window
  • [DXPFORC-405] - Product displayed on PLP from brSM should be overriden by the product decorator
  • [DXPFORC-416] - EPCategoryRepositoryImpl#findOne returns one with a wrong ID
  • [DXPFORC-420] - moreLikeThis and justForYou show no results
  • [DXPFORC-421] - It’s not possible to use 2 different brSM accounts on 2 different channels
  • [DXPFORC-424] - [commercetools Connector] An ID of the external category is displayed instead of the name in the document
  • [DXPFORC-425] - brSM ProductRepository doesn't return the same product ID or Code of ElasticPath
  • [DXPFORC-432] - Product Grid (Search): Customized description is applied to other products
  • [DXPFORC-451] - Product Component is not displaying the product

Task

  • [DXPFORC-431] - Upgrade brXM to v13.3.0 in 2.3 branch

Improvement

  • [DXPFORC-423] - Improve commercetools Category repository in order to provide a hierarchical data while retrieving categories
  • [DXPFORC-426] - Improve ElasticPath Category repository in order to provide a hierarchical data while retrieving categories
  • [DXPFORC-438] - Hide brSM from connector dropdown in Product Detail Page document

2.2.0

Bug

  • [DXPFORC-147] - Multiple facets not working
  • [DXPFORC-310] - Wrong parameters when using relevance variations
  • [DXPFORC-339] - Cart Commands warning logs brSM category page
  • [DXPFORC-346] - Search doesn't return results in 'related external category'
  • [DXPFORC-363] - 4 out of 5 templates in Categories Menu component doesn't work
  • [DXPFORC-367] - Title/Description of category is not populated into Category Highlight if the document title is blank
  • [DXPFORC-369] - Title/Description of product is not populated into Product Highlight if the document title is blank

New Feature

  • [DXPFORC-135] - Add request reset password functionality to SDK

Story

Task

  • [DXPFORC-334] - Upgrade to brXM 13.2.0 in starter store and boot

Improvement

  • [DXPFORC-303] - [Let brSM Integration use SDK] Implement the rest repositories using SDK other than Category/Product Repositories
  • [DXPFORC-304] - [Let brSM Integration use SDK] Implement product repository
  • [DXPFORC-340] - Introduce ItemModel#getReferenceId()
  • [DXPFORC-366] - Change label of the blank field in the connector drop-down list in channel settings

2.1.0

Bug

  • [DXPFORC-234] - starterstore-category.ftl blows up
  • [DXPFORC-257] - CustomerForm has confusing (new)RepeatedPassword properties
  • [DXPFORC-280] - ElasticPath Connector Module dependency should only in cms-dependencies
  • [DXPFORC-281] - SimpleCartForm.getEntries() can throw NPE
  • [DXPFORC-282] - Setting VisitorContext must be done regardless of visitor specific access token
  • [DXPFORC-294] - Jackson binding error in customer page
  • [DXPFORC-311] - Product Grid fails in 2.1 snapshot
  • [DXPFORC-312] - Category menu doesn't show up in 2.1 snapshot
  • [DXPFORC-318] - Fix Change Password functionality to work in CommerceTools
  • [DXPFORC-331] - Products are not added to the cart if the cartId cookie is empty
  • [DXPFORC-336] - Raw CRISP Resource objects cannot be put as model for JSON serialization through Page Model JSON API

New Feature

  • [DXPFORC-305] - Implement brSM category repository
  • [DXPFORC-316] - Support anonymous cart in CommerceTools connector

Story

Task

  • [DXPFORC-191] - Update templates to use pixel integration properly in v13
  • [DXPFORC-259] - Align one of the stacks between SM and EP
  • [DXPFORC-287] - Branch release/2.1
  • [DXPFORC-315] - Use 13.1.1 in starterstore and boot

Improvement

  • [DXPFORC-146] - Document should enrich instead of replace CommerceBackend content
  • [DXPFORC-197] - More detailed error messages
  • [DXPFORC-267] - Redirect from product add to cart page after login not working
  • [DXPFORC-313] - Utility to find and return a specific Connector SDK repository if exists

2.0.0

New Features

  • Compliant with brXM v13.1
  • New Commerce Connector SDK API introduced.
  • New built-in ElasticPath Commerce Connector Module.

Release Notes (1.x)

1.0.0

New Features

  • Initial release, compliant with v12.6
  • Built-in Commercetools integration.

 

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?