Explanation:

Three statements that are true regarding event handling in the Salesforce B2B Commerce managed package are:

Salesforce B2B Commerce relies on a central event channel for communication across various Salesforce B2B Commerce Backbone Views and Models called CCRZ.pubSub. This object allows different components to publish or subscribe to events without being coupled with each other. For example, CCRZ.pubSub.trigger(‘cartChange’) will publish an event named cartChange that can be subscribed by any component that needs to react to it.

CCRZ.pubSub defines the following three functions which can be used for event handling: trigger, on, and once. The trigger function is used to publish an event with a name and optional arguments. The on function is used to subscribe to an event with a name and a callback function. The once function is similar to on, but it will only execute the callback function once for each event.

CCRZ.pubSub extends the Backbone.Events JavaScript object. This object provides methods for managing events in Backbone.js, which is a JavaScript framework that provides models, views, collections, and events for building singlepage applications. CCRZ.pubSub inherits all the methods and properties of Backbone.Events and adds some custom ones.

Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Events, PubSub Class

Explanation:

Two things that happen with the cart during tax implementation are that new entries are written to the cart and previous entries are deleted from the cart. A tax implementation is an integration that calculates and applies tax rates and amounts to a cart or an order based on various factors, such as product type, price, quantity, location, and tax rules. A tax implementation can use either an external tax service provider or custom Apex code to perform the tax calculation. When a tax implementation is invoked for a cart, it writes new entries to the cart with a type of Charge and a charge type of Tax. These entries represent the tax amounts and adjustments that are applied to the cart. Before writing new entries to the cart, the tax implementation deletes any existing entries with a type of Charge and a charge type of Tax from the cart. This ensures that the tax calculation is accurate and up-to-date based on the current state of the cart and avoids any conflicts or inconsistencies with previous tax entries. Previous entries are not copied to another object or modified with the new tax calculation, as these are not valid actions for handling existing tax entries.

Salesforce References: B2B Commerce Developer Guide: Tax Integration, B2B Commerce Developer Guide: Tax Calculation Flow

Explanation:

The recommended method for increasing the number of required autocomplete characters that are typed before autocomplete works is to override the autoComplete.search_input.minLength value in the CCRZ.uiProperties file. This file contains various properties that control the behavior and appearance of the user interface components. The autoComplete.search_input.minLength property specifies the minimum number of characters that must be entered before the autocomplete feature is triggered.

The default value is 3, but it can be changed to any desired value by overriding it in the CCRZ.uiProperties file.

Salesforce References: B2B Commerce and D2C Commerce Developer Guide, UI Properties

Explanation:

To investigate a suspected bug in a checkout flow, comparing previous versions of the flow with the current one can help identify changes that might have introduced the bug. Additionally, Salesforce provides debugging capabilities within the Flow Builder, where a developer can select the debug option, provide input values known to trigger the issue, and execute the flow to observe its behavior, aiding in pinpointing the source of the problem.

Explanation:

Three pages that should be enabled for the Guest user profile for a storefront to have anonymous checkout are:

CCPaymentInfo: This page allows the guest user to enter their payment information, such as credit card number, expiration date, and security code. The page also displays the order summary and total amount.

CheckoutNew: This page allows the guest user to enter their shipping and billing information, such as name, address, phone number, and email. The page also displays the cart items and shipping options.

OrderConfirmation: This page displays the confirmation message and order number after the guest user places their order. The page also provides a link to view the order details or print the invoice.

Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Anonymous Checkout