Salesforce Certified B2B Commerce Developer Practice Test - Questions Answers, Page 4

To persist payment information data in the Checkout flow for Salesforce B2B Commerce version 4.2 and beyond, the project needs to trigger the processPayment event and pass in the payment information object as an argument. This event will invoke the processPayment method of the ccServicePayment class, which will validate and process the payment information and return a payment result object. The payment result object will contain the status and details of the payment transaction.

The REST APIs in Salesforce B2B Commerce support pass-through parameter handling by passing parameters through the service handlers. This means that any parameters that are not recognized by the REST API framework will be passed to the service handler class that implements the API logic. The service handler class can then use these parameters for custom logic or validation.

A price group can be dynamically set by extending the cc_hk_pricing hook. This hook allows modifying the price group based on various factors, such as the user, cart, product, or storefront. For example, the hook can apply a different price group for a specific product category or for a specific user segment.

A theme can be enabled in Salesforce B2B Commerce in three different ways:

A Storefront setting: The theme can be specified in the Storefront Configuration settings in CCAdmin. This will apply the theme to all users who access the storefront.

An Account Group field value: The theme can be specified in the Theme field of an Account Group record in Salesforce. This will apply the theme to all users who belong to that account group.

Dynamically through a hook: The theme can be specified dynamically by extending the cc_hk_theme hook. This hook allows changing the theme based on various factors, such as the user, cart, product, or storefront. For example, the hook can apply a different theme for a specific product category or for a specific user segment.

Salesforce B2B Commerce API sizing blocks can support multiple API sizing requests in three ways:

When different entities are specified in the method invocation. For example,ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_M, ccrz.ccAPI.SZ_L)will use the SZ_M sizing block for the product entity and the SZ_L sizing block for the related entities.

SZ_ASSC is used. This flag indicates that the associated entities should use the same sizing block as the primary entity. For example,ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_M, ccrz.ccAPI.SZ_ASSC)will use the SZ_M sizing block for both the product entity and the related entities.

SZ_ASSC is not used. This flag indicates that the associated entities should use the default sizing block, which is SZ_M, unless otherwise specified. For example,ccrz.ccServiceProduct.getProducts(ccrz.ccAPI.SZ_M)will use the SZ_M sizing block for the product entity and the SZ_M sizing block for the related entities. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Data Sizing Conventions

Useful debugging information in Salesforce B2B Commerce implementation can be garnered in three ways:

Enabling the logging token via Admin and subsequently inspecting the logs via the browser console. This will enable logging messages and errors to the browser console, which can be viewed by opening the Developer Tools in the browser. The logging token can be enabled by setting the value of CO.logToken to true in CCAdmin.

Enabling debugging options for the current user and visually inspecting the Salesforce debug logs. This will enable logging messages and errors to the Salesforce debug logs, which can be viewed by opening the Debug Logs page in Salesforce Setup. The debugging options can be enabled by creating a Debug Level and a Trace Flag for the current user in Salesforce Setup.

Logging into the community as a system administrator to identify any potential permissions or Visualforce exceptions. This will allow viewing any errors or warnings that may occur on the community pages due to insufficient permissions or Visualforce issues. The system administrator can also access CCAdmin and other tools from within the community. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Logging, Debug Your Code

To enable a new payment type for the Checkout flow, three possible configuration metadata descriptors are needed:

*.pay: This descriptor defines the payment type name, label, description, icon, and handler class. For example,CO.pmts.CreditCard.paydefines the payment type for credit card payments.

*.Edit: This descriptor defines the Visualforce page that is used to edit or update an existing payment of this type. For example,CO.pmts.CreditCard.Editdefines the page that allows editing a credit card payment.

*.New: This descriptor defines the Visualforce page that is used to create a new payment of this type. For example,CO.pmts.CreditCard.Newdefines the page that allows creating a new credit card payment. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Payment Configuration Settings

The Global API Data-Sizing convention flag that prevents an API request from propagating to further requests when provided as a Boolean parameter with a value of true is ccrz.ccAPI.SZ_ASSC. This flag indicates that only one API request should be executed with the specified sizing block, and any subsequent requests should use their own default sizing blocks. For example,ccrz.ccServiceCart.getCart(ccrz.ccAPI.SZ_L,true)will use the SZ_L sizing block for retrieving the cart data, but any other requests that are triggered by this method will use their own default sizing blocks. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Data Sizing Conventions

The default Global API Data-Sizing convention flag that is used by the API's unless otherwise specified is CCRZ.ccAPI.SZ_M. This flag indicates that the medium sizing block should be used for retrieving data, which includes the most commonly used fields and related entities. For example,ccrz.ccServiceProduct.getProducts()will use the SZ_M sizing block by default, unless another sizing block is specified as a parameter. Salesforce

Reference:B2B Commerce and D2C Commerce Developer Guide,Data Sizing Conventions