Salesforce B2B-Commerce-Developer - Salesforce Accredited B2B Commerce Developer (SP25)

Two aspects that are applicable to PageIncludes are:

Standard Visualforce controls such as apex:form should not be used within a page include. This is because the page include is rendered inside an existing Visualforce page that already has a form element. Using another form element inside thepage include will cause conflicts and errors. Instead, the page include should use HTML elements or custom components that do not require a form element.

Page Includes can be configured as Body Includes Begin. This means that the page include will be rendered at the beginning of the body section of the page, before any other content or widgets. This can be useful for adding some custom content or functionality that applies to the whole page, such as a banner, a modal, or a script. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Page Includes

When including additional JavaScript files in a Lightning web component, a developer should keep in mind twoconsiderations: the files must be ES6 modules and must have names that are unique within the component’s folder and a module can export named functions or variables. The files must be ES6 modules because LWC uses ES6 modules as the standard for modular JavaScript code. The files must have names that are unique within the component’s folder because LWC uses the file name as the module identifier and does not allow duplicate identifiers. A module can export named functions or variables because LWC supports named exports, which allow a module to export multiple values with different names. Each additional file does not need a corresponding .js-meta.xml file, as this is only required for the main JavaScript file of the component. Additional JavaScript files should not be minified before deployment, as this is not necessary or recommended for LWC. Salesforce References: [Lightning Web Components Developer Guide: Include JavaScript Files], [Lightning Web Components Developer Guide: ES6 Modules]

 According to the B2B Commerce Developer Guide, the Order List Component (Aura) for B2B stores displays a list of orders that the user can view and reorder. The component filters the orders based on the current storefront and the current effective account. The current effective account is the account that the user is currently acting on behalf of, which can be different from the user’s ownaccount. The component does not show orders placed in other storefronts or related to other accounts, even if the user has access to them. Therefore, the correct answer is A. Orders placed in the current storefront and related to the current effective account. The other options are incorrect because they do not match the criteria of the component. References: B2B Commerce Developer Guide, Show the Order List Widget

The cookie that stores the effective account ID when effective account is enabled is apex__effacc. This cookie is set by the cc_hk_EffectiveAccount hook when a user switches to another account that they have access to. The cookie value is the ID of the effective account, which is used to determine the pricing, availability, and visibility of products and categories for that account. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Effective Account

To handle the subscription lifecycle of a message channel in a Lightning web component, the developer should implement the subscribe() and unsubscribe() methods from the lightning/messageService module. The subscribe() method returns a subscription object that representsthe connection to the message channel. The developer can use this object to unsubscribe from the message channel later. The unsubscribe() method takes a subscription object as a parameter and removes the listener from the message channel. The developer should call the unsubscribe() method when the component is disconnected from the DOM, such as in the disconnectedCallback() lifecycle hook, to avoid memory leaks and performance issues.

The other options are not correct because:

B. stopListener() is not a valid method for handling the subscription lifecycle of a message channel. There is no such method in the lightning/messageService module or the Lightning web component framework.

C. startListener() is not a valid method for handling the subscription lifecycle of a message channel. There is no such method in the lightning/messageService module or the Lightning web component framework.

References:

Subscribe and Unsubscribe from a Message Channel

Lifecycle Hooks

Use message channel in both direction

Three statements that are true about Global API versioning are:

Calling in with an API version set to lower than 1 will result in an exceptional case where the exception class ccrz.BelowMinAPIVersionException will be returned to callers. This exception indicates that the API version is not supported by the framework and the caller should use a higher API version.

The APIversion is scoped at the Class API level and NOT at the method level. This means that all the methods in a class will use the same API version that is specified by the caller. For example, if the caller passes an API version of 4 to ccrz.ccServiceProduct.getProducts(), then all the other methods in ccrz.ccServiceProduct will also use API version 4.

Calling in with an API version set to more than current maximum will result in exception case where the exception class ccrz.ExceedsMaxAPIVersionException will be returned to callers. This exception indicates that the API version is not supported by the framework and the caller should use a lower API version. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, API Versioning

QUESTIONNO: 68

Which three statements are true regarding event handling in the Salesforce B2B Commerce managed package? (3 answers)

A. Salesforce B2B Commerce relies on a series of Javascript click listener events.

B. Writing directly to your own custom BackboneJS Views and Models automatically integrates that data into the Salesforce B2B Commerce Backbone Views and Models.

C. Salesforce B2B Commerce relies on a central event channel for communication across various Salesforce B2B Commerce Backbone Views and Models called CCRZ.pubSub.

D. CCRZ.pubSub defines the following three functions which can be used for event handling: trigger, on, and once.

E. CCRZ.pubSub extends the Backbone.Events JavaScript object.

Answer: C,D,E

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 acallback 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 isa JavaScript framework that provides models, views, collections, and events for building single-page 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

A customer can create its ownrobots.txt file for three valid reasons:

The customer wants to reference multiple storefront sitemap indexes in a single robots.txt file. This can be useful if the customer has multiple storefronts under the same domain and wants to provide a single entrypoint for search engines to crawl their sitemaps.

The customer wants to reference a custom sitemap index. This can be useful if the customer has created their own sitemap index that contains custom sitemaps or sitemaps from other sources.

The customer’s store is not located at the root of their domain. This can be useful if the customer has their store under a subdirectory or a subdomain and wants to specify a different robots.txt file for their store than for their main domain. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Robots.txt File

In Lightning Web Components, wire adapters are used to retrieve and manipulate Salesforce data. Wire adapters abstract the underlying data access mechanism, providing a declarative way to access Salesforce data and metadata. Salesforce documentation on LWC andthe@wiredecorator details how wire adapters can be used to connect components to Salesforce data sources, including standard and custom objects, facilitating reactive data binding and efficient data retrieval.

The Product Detail Card component is a standard component that displays the product information and options on the product page. It includes the following elements1:

The product’s SKU

The product’s unit of measure

The product’s available inventory, or a generic availability message, if specified

The product’s shortdescription

The product’s price information

The product’s quantity selector

The product’s add to cart button

The product’s image gallery

To replace this component with custom components, a developer can use the following three components:

Product Fields Short component: This component displays the product’s short description, SKU, unit of measure, and price information. It also allows the developer to specify which fields to display and how to format them2.

Product Field Long component: This component displays the product’s long description, which can include rich text and images. It also allows the developer to specify which field to display and how to format it2.

Product Detail Image Gallery component: This component displays the product’s image gallery, which can include multiple images and thumbnails. It also allows the developer to specify the image field, the image size, and the image zoom option3.

These three components can be combined to create a custom product page that shows the product information and options in a different layout and style than the out-of-the-box Product Detail Card component. References: Configure Product Info and Options on the Product Detail Page, Product FieldsShort Component, Product Detail Image Gallery Component

 The connectedCallback is a lifecycle hook that is invoked when a Lightning web component is inserted into the DOM. It is used to perform any initialization tasks that depend on the component being rendered, such as fetching data, setting up event listeners, or creating timers. The connectedCallback can fire more than once, for example, when a component is moved or rerendered. The connectedCallback should not be used to change the state of a component, such as loading values or setting properties. Use getters and setters instead. The other options are incorrect because they do not describe the purpose of the connectedCallback. References: Lifecycle Hooks | Lightning Web Components Developer Guide, connectedCallback() in Lightning Web Component - Salesforce Diaries, Chapter 23: connnectedCallback() in Lightning Web Component