To handle changes on the combobox, the developer should replace < CHANGE EVENT > with {handleChange}. The handleChange is a function that is defined in the JavaScript file of the Lightning web component and is invoked when the value of the combobox changes. The developer can use this function to perform custom logic or actions based on the selected value of the combobox, such as updating other components or properties, calling Apex methods or services, or firing events. The developer can use the onchange attribute to bind the handleChange function to the combobox element in the HTML file of the Lightning web component. The onchange attribute is an HTML attribute that specifies a function to be executed when the value of an element changes. {event:handleChange} is not a valid way to handle changes on the combobox, as it is not a valid syntax for binding a function to an element. javascript:void(0);handleChange(); is not a valid way either, as it is not a valid syntax for binding a function to an element. {handleChange()} is not a valid way either, as it is not a valid syntax for binding a function to an element. Salesforce References: Lightning Web Components Developer Guide: Handle Events, Lightning Web Components Developer Guide: Communicate with Properties, Lightning Web Components Developer Guide: lightning-combobox

Two different types of services that Salesforce B2B Commerce APIs leverage are:

Logic services which are responsible for implementing business logic associated with entities. These services are defined in the logic classes, such as ccrz.ccLogicCart, ccrz.ccLogicOrder, or ccrz.ccLogicProduct. These classes provide methods for validating inputs, performing calculations, applying rules, or updating data for each entity.

Data services which are responsible for querying and transforming data from entities. These services are defined in the service classes, such as ccrz.ccServiceCart, ccrz.ccServiceOrder, or ccrz.ccServiceProduct. These classes provide methods for creating, reading, updating, and deleting data for each entity. Salesforce References:  B2B Commerce and D2C Commerce Developer Guide ,  Service Classes ,  Logic Classes

When implementing an Inventory clas s for checkout and indicating that inventory is available for all items and amounts in the cart, the correct step is to return sfdc_checkout.InventoryStatus.Status.SUCCESS . This indicates to the checkout process that the inventory check has passed and the items are available. Salesforce documentation on customizing inventory validation in the checkout process would detail the expected return types and values, ensuring that developers implement the inventory checks in a manner consistent with the platform's requirements.

Three actions that are applicable when modifying the number of steps required in the Salesforce Commerce Checkout flow are:

Perform a template override on the Checkout page. This action will allow you to change the structure and content of the Checkout page, such as adding or removing sections, widgets, or fields. For example, you can override the checkout.handlebars template and modify it according to your requirements.

Set the value of the configuration setting defined as CO.overrideFlow to TRUE. This setting will enable you to use your own custom checkout flow instead of the default one. You need to set this value to true before you can modify the checkout flow.

Set the value of the configuration setting defined as CO.useDef to TRUE. This setting w ill enable you to use a single-page checkout flow instead of a multi-step checkout flow. You need to set this value to true if you want to reduce the number of steps in the checkout flow to one. Salesforce References:  B2B Commerce and D2C Commerce Developer Guide ,  Checkout Flow

To fire a custom event called CustomEvent from the Lightning web component and propagate it up to the DOM, the developer must set two event settings: bubbles and composed. The bubbles setting determines whether the event bubbles up through the component’s ancestors in the DOM tree. The composed setting determines whether the event crosses the shadow boundary a nd reaches the light DOM. Setting both bubbles and composed to true allows the event to be handled by any element in the DOM that listens for it. The cancelable setting is not required for firing or propagating the event, as it only determines whether the event can be canceled by calling preventDefault() on it. Setting composed to false would prevent the event from reaching the light DOM and limit its propagation to the shadow DOM. Salesforce References:  Lightning Web Components Developer Guide: Create and Dispatch Events ,  Lightning Web Components Develo per Guide: Event Propagation

Similar to question 198, when custom code compares external prices with sales prices for cart items and finds them to be the same, the appropriate ret urn value should indicate a successful comparison (such as sfdc_checkout.IntegrationStatus.Status.SUCCESS ). This signifies that the external prices are aligned with the sales prices, and there are no conflicts.

Two ways that a developer should configure taxes in B2B Commerce for Ursa Major are: configure a tax engine using third-party software and configure tax rates and rules for each state in Salesforce B2B Commerce. Configuring a tax engine using third-party software allows the developer to integrate with an external tax service provider that can calculate and apply accurate and up-to-date tax rates and rules for different states and jurisdictions. The developer can use the sfdc_checkout.TaxCalculations interface or the RegisteredExternalService object to connect to the third-party tax service provider’s API or service. Configuring tax rates and rules for each state in Salesforce B2B Commerce allows the developer to implement their own custom tax calculation logic using Apex code. The developer can use custom objects, such as TaxRate__c and TaxRule__c, to store and manage tax rates and rules for different states and products. The developer can also use the sfdc_checkout.TaxCalculations interface to define how to retrieve and apply tax rates and rules for a cart or an order. Using a different pricebook for each state is not a good way to configure taxes in B2B Commerce, as it can create complexity and inconsistency in pricing and discounting logic. Using the Salesforce out-of-the-box tax calculator is not a good way either, as it does not support complex or dynamic tax scenarios that may vary by state or jurisdiction. Salesforce References: [B2B Commerce Developer Guide: Tax Integration], [B2B Commerce Developer Guide: Tax Calculations Interface] , [B2B Commerce Developer Guide: TaxRate Object], [B2B Commerce Developer Guide: TaxRule Object]

Two guidelines for logging that are used within the core Salesforce B2B Commerce product are:

The close method of ccrz.ccLog must be called at the end of the remote action. This method will flush the log messages to the browser console or to a custom object, depending on the logging mode. If this method is not called, the log messages may not be displayed or saved properly.

No calls to ccrz.ccLog can be made before cc_CallContext.initRemoteContext is executed. This method will initialize the call context object, which contains in formation such as the current user, cart, storefront, and configuration settings. These information are required for logging, so calling ccrz.ccLog before initializing the call context will result in an error. Salesforce References:  B2B Commerce and D2C Commerce Developer Guide ,  Logging

In general best practices for tax implementation in systems like Salesforce B2B Commerce, previous tax entries are usually preserved or saved before any recalculation is performed. This ensures that there is a record of the original tax calculations before an y modifications, which can be crucial for auditing, historical data integrity, and in case the new tax calculation needs to be rolled back for any reason.

 A developer needs to make a call to a long running web service which is critical to finalizing their checkout process. The developer should consider the following items in their implementation:

A new CORS entry may need to be created in Setup. CORS stands for Cross-Origin Resource Sharing, which is a mechanism that allows web bro wsers to make requests to servers on different domains. If the web service is hosted on a different domain than the B2B Commerce site, the developer may need to add a CORS entry in Setup to allow the browser to access the web service.  This entry specifies the origin, path, and method of the request, as well as any headers or cookies that are allowed 1 .

A new Named Credential may need to be created in Setup. A Named Credential is a type of metadata that stores the URL and authentication settings of a web service. By using a Named Credential, the developer can avoid hardcoding the web service URL and credentials in their code, and instead reference the Named Credential by name.  This makes the code more sec ure and easier to maintain 2 .

An Apex method returning a Continuation will need to be created. A Continuation is a special type of Apex object that allows the developer to make asynchronous calls to long running web services. By using a Continuation, the developer can avoid blocking the main thread and improve the user experience.  A Continuation method must return a Continuation object, specify the web service URL and parameters, and register a callback method that handles the response 3 .

Option D and Option E are incorrect because they are not relevant to the scenario. Option D suggests that the developer should broker the requests to the web service, which means to use an intermediary se rvice that manages the requests and responses. This may be useful for some scenarios, but it is not required for making a call to a long running web service. Option E suggests that the developer should create a new Remote Site in Setup, which is a way to w hitelist the domains that can be accessed from Apex code.  However, this is not necessary if the developer uses a Named Credential, which automatically h andles the Remote Site setting 2 .  References:

Set Up CORS

Named Credentials

Continuat ion Class