Step 14: Override the default App implementation
Learn how to override the default App implementation.
Last updated
Learn how to override the default App implementation.
Last updated
Each Salesforce B2B Commerce (CloudCraze) implementation comes with its own business requirements and unique challenges. While OOTB (Out of the Box) App for Salesforce B2B Commerce can solve some of these challenges with specific configurations, sometimes the business requirements cannot be fulfilled in a configurable manner. That is, the solution requires code. To address these challenges, we provide extension points within the App. These extension points are called by the core app code and allow you to meet specific business requirements for each implementation.
The current version of the App provides an extension point for setting the Ship From Address (Warehouse location) based on the client’s business requirement.
Extension for Ship from Address: digitalriverv2.DRB2B_ShipFromAddressInterface. The digitalriverv2.DRB2B_ShipFromAddressInterface extension is used to extend the App's ShipFromAddress functionality.
global Map getShipFromAddressMap(). This method is called when posting the user and cart information to Digital River to get the tax value. Out of the box, the App uses the Ship From Address values configured in the General Config tab of the Salesforce B2B Commerce App.
Inputs: None
Output:
Map<String, String>: This contains addressLine1
, addressLine2
, city
, stateCode
, countryCode, and postalCode
.
Implementing an extension is a two-step process. To override the default App implementation:
Extend the Salesforce B2B Commerce App extension point. That is, implement the interface digitalriverv2.DRB2B_ShipFromAddressInterface
and provide the implementation for the method getShipFromAddressMap()
. See example 1.
Configure the App to use this extension class as follows:
Go to the digitalriverv2__DR_Connector_Extension_Configuration__mdt metadata type.
Click Manage DR Connector Extension Configurations.
Open the Ship From Address metadata record.
Update the Extension Class field with the previously created Custom Class name.