... a contemporary perspective on how to integrate B2C Commerce and the Salesforce Customer 360 Platform to power frictionless customer experiences in the B2C domain.
Changing the way includes are working in the b2c-crm-sync enablement framework, in order to allow extend the solution with another cartridge that needs to use the same framework model and would just define a new set of API in the b2ccrm-sync.config.json.
The main difference is that instead of allowing only int-b2ccrmsync includes we allow, cartridge path includes, hence we can put on top of the b2c-crm-sync additional capability cartridges that could provide additional functionality while using the same framework and template defined by b2c-crm-sync.
Changing the way includes are working in the b2c-crm-sync enablement framework, in order to allow extend the solution with another cartridge that needs to use the same framework model and would just define a new set of API in the
b2ccrm-sync.config.json.
Changing the way includes works in:
The main difference is that instead of allowing only int-b2ccrmsync includes we allow, cartridge path includes, hence we can put on top of the b2c-crm-sync additional capability cartridges that could provide additional functionality while using the same framework and template defined by b2c-crm-sync.
FYI: https://github.com/SalesforceCommerceCloud/b2c-crm-sync/pull/62 is a "fix" for this PR, in order to exclude "0.9.0 noise" in it.