LogoLogo
Connectors
Salesforce B2B Commerce App 2.1.0
Salesforce B2B Commerce App 2.1.0
  • Salesforce B2B Commerce App 2.1.0
  • Introduction
    • How it works
    • What's new in version 2.1.0
    • Requirements
  • Integrating the Digital River Salesforce B2B Commerce App
    • Step 1: Install the Digital River App for Salesforce B2B
    • Step 2: Create page labels
    • Step 3: Configure the Salesforce B2B Commerce App
    • Step 4: Add custom Salesforce B2B Commerce App fields to page layouts
    • Step 5: Enable email deliverability
    • Step 6: Import ECCN codes, tax groups, and tax types
    • Step 7. Update the Product Sync settings
    • Step 8: Set up Digital River fulfillments
    • Step 9: Set up webhooks
    • Step 10: Configure CC Admin settings
    • Step 11: Configure landed cost
    • Step 12: Schedule backend jobs
    • Step 13: Manage permission sets
    • Step 14: Configure the Salesforce B2B Commerce app logs
    • Step 15: Test the Digital River Salesforce B2B Commerce app integration
    • Step 16: Override the default App implementation
  • Support
  • Version number
  • Appendix
    • Fulfillment and cancellation flow
    • Issuing refunds
    • Managing regulatory fees
    • Managing subscriptions
    • Salesforce B2B Commerce App logs
    • Uploading tax certificates (US TEMS)
    • VAT invoices
Powered by GitBook
On this page
  • Step 10a: Create a service override for the Tax Calculation API class
  • Step 10b: Create configuration module for payment type
  • Step 10c: Create configuration metadata for Payment DR Module
  • Modules
  • Step 10d: Create configuration settings for a storefront
  • Modules
  • Step 10e: Refresh the Configuration Cache
  1. Integrating the Digital River Salesforce B2B Commerce App

Step 10: Configure CC Admin settings

Learn how to configure CC Admin settings.

PreviousStep 9: Set up webhooksNextStep 11: Configure landed cost

Last updated 4 years ago

Step 10a: Create a service override for the Tax Calculation API class

Salesforce B2B Commerce (CloudCraze) does not calculate taxes out-of-the-box (OOTB). Instead, it exposes a Tax Calculation webhook which you must override. This step will implement the new business-specific tax calculations by making a call to Digital River for tax calculations to override the Tax Calculation webhook.

To create a service override for the Tax Calculation API class:

  1. Go to CC Admin.

  2. Select Storefront from the Global Settings dropdown list.

  3. Click Tax under Integrations.

  4. Set the Tax Calculation API class to digitalriverv2.DRB2B_CartTaxCalculation as shown in the screenshot above.

  5. Click Save.

Step 10b: Create configuration module for payment type

You perform this step at the Global Settings level. The changes you make here apply to all your storefronts. To create a module for Digital River payment.

  1. Select the CC Admin tab.

  2. Select Configuration Modules.

  3. Click New in the Configuration Module pane. The Configuration Module dialog appears.

  4. Type Payment DR in the Name field and pmt_dr in the API Name field.

Step 10c: Create configuration metadata for Payment DR Module

Configure the following custom Salesforce B2B Commerce App pages in CC Admin. They will appear in the following storefront locations: Edit Page, New Page, Pay Page, and Proc. Note that you perform this step at the Global Settings-level. The changes you make here apply to all your storefronts.

The Payment DR module should pull in all payment types configured by Digital River.

To create configuration settings for the Payment DR configuration modules:

  1. Under Configuration Modules, click the Payment DR module.

  2. Repeat steps 2 and 3 to create configuration metadata for New Page, Pay Page, and Proc. After adding the configuration metadata to the Payment Module DR, the Configuration Module should look like this:

Modules

The following table lists the required settings for each field.

Module

Name

API Name

Description

Payment DR

Edit Page

edit

Edit page for Payment DR

Payment DR

New Page

new

VisualForce page leveraged for saving new Drop-in payment information via the My Account page

Payment DR

Pay Page

pay

VisualForce page for rendering the Payment DR on the Checkout page

Payment DR

Proc

proc

Payment processor for backend processing

Step 10d: Create configuration settings for a storefront

If you want custom Salesforce B2B Commerce App pages to show up in your storefront, you must configure them in CC Admin for them. Note that you perform this step at the storefront level. The changes you make here apply to a specific storefront. If you have more than one storefront, you should repeat this step for each storefront.

To create or update a store's configuration settings:

  1. Repeat steps 1 through 6 for each additional storefront.

Modules

The following table lists the DR Configuration Settings that need to be configured for each storefront:

Module

Configuration

Page

Value

Body Includes Begin

Enabled

Order View

TRUE

Body Includes Begin

Enabled

Order Confirmation

TRUE

Body Includes Begin

Enabled

Check Out

TRUE

Body Includes Begin

Page Include Name

Order VIew

digitalriverv2__DRB2B_OrderConfirmation

Body Includes Begin

Page Include Name

Order Confirmation

digitalriverv2__DRB2B_OrderConfirmation

Body Includes Begin

Page Include Name

Check Out

digitalriverv2__DRB2B_OrderReview

Body Includes End

Enabled

My Account

TRUE

Body Includes End

Enabled

Check Out

TRUE

Body Includes End

Page Include Name

My Account

digitalriverv2__DRB2B_MyAccount

Body Includes End

Page Include Name

Check Out

digitalriverv2__DRB2B_PaymentProcessor_Checkout

Checkout

Payment Types

all

dr

Checkout

Use Default

Check Out

TRUE

My Account

Use Default

My Account

FALSE

My Account

Override Flow

My Account

TRUE

My Wallet

Payments

all

dr

Order Review

Show Total Surcharge

all

TRUE

Order Review

Show Surcharge

all

TRUE

Payment

White List

all

cc_pmt_PO_New,cc_pmt_PO_Pay, digitalriverv2__DRB2B_Payment_DR

Payment DR

New Page

all

digitalriverv2__DRB2B_MyWallet_Payment_DR

Payment DR

Proc

all

digitalriverv2.DRB2B_CCPaymentProcessor

Payment DR

Edit Page

all

digitalriverv2__DRB2B_MyWallet_Payment_DR

Payment DR

Pay Page

Check Out

digitalriverv2__DRB2B_Payment_DR

Step 10e: Refresh the Configuration Cache

CC Admin configurations are cached. Refresh the configuration cache to ensure you can see the latest configuration changes made to the storefront. To refresh the configuration cache:

  1. Click Build New.

  2. Click Activate under the Status column for the new configuration identifier and deactivate any previous configurations.

  3. Locate the previous cache and click Deactivate.

  4. To verify your changes, clear the browser cache and test the storefront pages.

Click New to create the Edit Page configuration metadata for the configuration module.

Use the information associated with the to complete the Edit Page configuration metadata. Note: Don’t select the Externally Safe check box.

From CC Admin, click Global Settings in the upper-right corner and select your storefront (for example, DefaultStore). Note: After selecting the storefront, the select box will still display Global Settings. However, the left navigation pane will display <storefront name>SETTINGS and the options associated with the store.

Click Configuration Settings under <storefront name> SETTINGS.

Select the module name (for example, Body Includes Begin from) from the Module dropdown list.

To create a new page setting for the module, click New. The New Page Setting dialog appears.

Complete the fields using the information from the table and click Create. The new module appears in the Configure Settings list and displays Delete in the ACTION column, and the name of the storefront appears in the STOREFRONT column.

Repeat steps 3 through 5 for each additional row in the table.

Click Global Settings to return to the Global Settings page.

Click Configuration Cache Management under GLOBAL SETTINGS.

Click Refresh List. You may have to click the Refresh link several times before the build completes. When complete, a new configuration identifier appears under the CONFIG ID column.

Modules
Modules
module
Modules