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

To implement a custom Terms and Conditions checkbox at checkout in the Aura Commerce template, a developer should add a Desired Delivery Date input field during the checkout flow. The Desired Delivery Date input field allows the customer to enter a date when they want their order to be delivered. The developer can use the @api decorator to expose this field as a public property of the Lightning web component and bind it to the ccCheckoutOrder object. Thedeveloper can also use the @wire decorator to get the current cart object and use its properties, such as shipping address and shipping method, to calculate and display an estimated delivery date based on the desired delivery date. The developer can also add validation logic to ensure that the desired delivery date is valid and acceptable. Adding the Expected Delivery Date field to the order confirmation email is not a good solution, as it does not allow the customer to choose or see their delivery date before placing their order. Displaying the Expected Delivery Date on the order page with a Lightning web component is not a good solution either, as it does not allow the customer to enter or change their delivery date after placing their order. Configuring an email alert to the customerwhen the Expected Delivery Date changes is not a good solution either, as it does not provide a consistent or reliable way of informing the customer about their delivery date. Salesforce References: B2B CommerceDeveloper Guide: Checkout Flow, B2B Commerce Developer Guide: Checkout Order Object, Lightning Web Components Developer Guide: Communicate with Properties

For investigating errors during development, Salesforce recommends using the Streaming API Subscription Channel for Commerce Diagnostics Event Logging. This tool allows developers to subscribe to a real-time feed of system events, including errors, which can be crucial for diagnosing and resolving issues during development. The Streaming API provides a robust mechanism for monitoring and debugging by delivering secure, scalable, and customizable event notifications within Salesforce or through external systems. This is outlined in Salesforce documentation related to the Streaming API and its application in commerce diagnostics and event logging.

The format that the custom Salesforce field with the API name My_Field_Name__c is transformed onto by default in Salesforce B2B Commerce is myFieldName. This is done to follow the JavaScript naming convention and to avoid conflicts with thestandard Salesforce fields and relationships. The transformation rules are as follows:

Remove any namespace prefix from the field name, such as ccrz__ or cloudcraze__.

Remove any underscores from the field name and capitalize the first letter of each wordafter an underscore, such as MyFieldName.

Lowercase the first letter of the field name, such as myFieldName. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Query Transformation

When services use the ccServiceDao class to execute queries, variables are bound by string substitution. This means that the query string containsplaceholders for variables that are replaced by their values at runtime. For example, ccrz.ccServiceDao.getQuery('SELECT Id FROM Account WHERE Name = :name') will replace :name with the value of the name variable.

After deploying a new Lightning Web Component (LWC) to an org, the typical next step to use the component on a page involves navigating to that page, entering the edit mode (usually through AppBuilder or a similar interface), and then dragging the new component fromthe components palette onto the desired location on the page. This process is consistent with Salesforce's modular design approach, allowing for easy integration and configuration of components within the Salesforce ecosystem.

The cc_CallContext class is a utility class that provides access to various context level parameters, such as thecurrent storefront, user, cart, price list, currency, locale, and session. The class can be used internally within Salesforce B2B Commerce and in subscriber code to access these parameters. The current storefront is accessible via this class by using the getStorefront method, which returns a cc_Storefront__c object. The userLocale variable returns the current Locale for storefront, but it is not part of the cc_CallContext class. It is a global variable that can be accessed from any Visualforce page or component by using {!userLocale}. The Salesforce session is accessible via the getSession method, but it is not part of the cc_CallContext class either. It is a method of the cc_SessionUtil class, which is another utility class that provides methods for managing sessions. Salesforce References: [B2B Commerce Developer Guide: cc_CallContext Class], [B2B Commerce Developer Guide: cc_SessionUtil Class]