Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

Elastic Path 7.4.1 Release Notes

Elastic Path 7.4.1 Release Notes

Release highlights

B2B Support for Elastic Path Account Manager

Create organizational models and accounts for your B2B customers

  • The Account Manager allows Seller Organizations to create and manage commerce accounts for Buyer Organizations
  • Model and create the divisional structure for corporate accounts to accommodate the desired accounting and commerce processes
  • Provides buyer organizations with account and management tools to meet business requirements
  • Easy integration with the rest of the e-commerce ecosystem

Assign purchasers to shop on behalf of their organizations

  • Seller Organization will be able to add associates and grant them authority to purchase on behalf of their Organization's divisions

Customize price lists at the Organizational and the Divisional level

  • For B2B, every buyer organization can establish specific pricing depends on contract agreements, initial negotiations, or initial terms and conditions
  • The Elastic Path account management module provides the ability to establish customized price lists at the Buyer Organization, or at the Divisional level
For more information on the Elastic Path Account Management system, see the new B2B menu:
  • Account Management Overview Guide
  • Elastic Path Account Management User Guide
  • Account Management API Documentation
  • Deployment Guide
  • Configuration Guide

Improved configuration management

Multiple configuration management changes were made to provide a better starting point for project teams and to simplify CloudOps management of operations configuration. Duplication of configuration between Commerce and CloudOps was eliminated to provide greater clarity on configuration responsibilities.

System Requirements and Compatibility

Elastic Path Commerce 7.4.1 is compatible with the following Elastic Path releases:

Elastic Path component Versions Location Git branch or file name
Elastic Path CloudOps for AWS See CloudOps for AWS compatability matrix release/3.N.x where N is the minor version number
Elastic Path CloudOps for Azure See 1.1.x or later, CloudOps for Azure compatability matrix release/1.N.x where N is the minor version number
Elastic Path Commerce Demo Package 7.4.1
Elastic Path Commerce for Adobe 1.7 Internal release available upon request.

New in This Release

Improved configuration management

  • Enabled run-time overrides of operations managed settings The following settings still need to be defined in Elastic Path Commerce, but can be overridden at run-time using Java system properties. Elastic Path CloudOps now injects these properties into Docker containers using environment variables.
    Tip: In your local development environment it is no longer necessary to rebuild the database to change these properties.
    System Property Maven Property Description
    -Dep.asset.location ep.local.asset.path Overrides COMMERCE/SYSTEM/ASSETS/assetLocation system setting.
    -Dep.changesets.enabled ep.changesets.enabled Overrides COMMERCE/SYSTEM/CHANGESETS/enable system setting. Overrides the default value of the COMMERCE/SYSTEM/SEARCH/searchHost system setting. n/a Overrides the master context value of the COMMERCE/SYSTEM/SEARCH/searchHost system setting. Overrides COMMERCE/SYSTEM/EMAIL/mailHost system setting.
    -Dep.smtp.port ep.smtp.port Overrides COMMERCE/SYSTEM/EMAIL/mailPort system setting.
    -Dep.smtp.scheme ep.smtp.scheme Overrides COMMERCE/SYSTEM/EMAIL/smtpScheme system setting.
    -Dep.smtp.username ep.smtp.username Overrides COMMERCE/SYSTEM/EMAIL/emailAuthenticationUser system setting.
    -Dep.smtp.password ep.smtp.password Overrides COMMERCE/SYSTEM/EMAIL/emailAuthenticationPassword system setting.
  • Removed run-time settings from files. Operations managed settings (see above) were removed from files for non-development environments.
  • Added new sample environments. The following sample environments were added to the extensions/database/ext-data module. The environmont names match the standard environments that are used by Elastic Path Cloud Commerce.
    Environment Purpose Notes
    ci Used for automated system tests in the CI (Continuous Integration) pipeline
    local-perf Used for local developer performance testing where additional data and longer cache timeouts are needed. By default this environment includes SNAPITUP data and has a 60 minute cache timeout. See maven/settings.xml for instructions on how to activate this environment.
    perf Used for performance testing in a single instance environement. Higher volume performance testing requires a larger scale environment and can use either the author-live environment or a dedicated performance test environment.
    qa Used for manual QA testing
    stage-author Author environment for final staging and testing of changes before pushing to production.
    stage-live Live environment for final staging and testing of changes before pushing to production.
  • Removed or deprecated non-standard environments. The following environments were removed or deprecated:
    • dev was renamed to dev-deprecated. Project teams that wish to continue using this environment should rename it back to dev when upgrading.
    • sample-prod was removed. Production environments should be modeled on stage-author and stage-live instead.
  • Moved additional configuration files to the default environment to reduce duplication. Configuration files that were duplicated across multiple environments were moved to the default environment. These include:
    • cache/ehcache-5-seconds.xml
    • cache/ehcache-60-minutes.xml
    • configured to use cache/ehcache-5-seconds.xml by default.
  • Added for use by the Data Populatation Docker container. The Data Population Docker entrypoint script substitutes placeholders in the environments/default/ with values from environment variables.
  • Added support for creating Azure Database for MySQL. The data.population.username.short property was added to to support creation of Azure Database for MySQL.
  • Fixed -Preset-conf and -Pupdate-conf commands. These commands now copy files from the default environment.
  • Removed property from Import/Export configuration. The Import/Export tool did not use the property as previously documented, but used the value from the settings framework instead.

Core Commerce

  • Added support for import and export of search facet configuration. For more information, see Facets Import/Export.


  • Added the -DenableTrustedSubjectHeaderMode Java system property to support switching between OAuth2 authentication and Trusted Subject Header Mode authentication when starting Cortex. For more information, see the Cortex Authentication section.

Upgrade Notes

The Upgrading Elastic Path Guide provides general instructions on upgrading Elastic Path projects. The upgrade instruction specific to 7.4.1 release are listed in the following sections:

Database Changes

The following changes were made to the database. For more information, see core-changelog.7.2.0_gdpr_query_optimization.xml in the commerce-engine/liquibase module.

  1. A TCUSTOMERCONSENTHISTORY table was added, and all historical rows move from TCUSTOMERCONSENT to TCUSTOMERCONSENTHISTORY.
Warning: Deploying to a production environment requires a planned system outage. This is not a backward compatible change.

Configuration Management Upgrade Notes

The extensive changes to configuration management described above are expected to result in merge conflicts in the extensions/database/ext-data module when upgrading. The following general considerations should help guide the upgrade process.

  1. It is strongly recommended that projects using CloudOps for AWS upgrade to version 3.2.x to take advantage of the improvements to configuration management. See the CloudOps release notes for more information.
  2. It is a best practice to move default files to the environments/default/files/conf directory.
  3. There is no requirement to change existing environment names to conform to the standard names introduced in this release.
  4. When finished resolving merge conflicts, you should compare the previous configuration with the upgraded configuration to make sure that all essential configuration elements have been preserved.

Bug fixes

Core Commerce

  • Resolved issue with slow performance retrieving GDPR customer consent information from a large TCUSTOMERCONSENT table.

Documentation Changes

For more information about the updates in this release, see the following sections:

Elastic Path CloudOps for Azure 1.0

  • Elastic Path for Azure Overview
  • Elastic Path for Azure Deployment Guide

Elastic Path Account Management

  • Account Management Overview Guide
  • Elastic Path Account Management User Guide
  • Elastic Path Account Management API Documentation
  • Elastic Path Deployment Guide
  • B2B Organization-based Pricing Guide
React Reference Storefront Developer Guide See also: