B2B-Commerce-Developer Exam Dumps - B2B Commerce for Developers Accredited Professional (AP-202)

To update the checkout process so that buyers can purchase with one of the below payment types:

• Credit Card
• Purchase Order
• Contract Now & Pay Later Additionally, show only Purchase Order and Contract Now & Pay Later if a custom checkbox field on the account is checked, a developer should create a custom Lightning web component for the checkout flow that has all the options available. Within that component, pulldata from the account to determine which options to show. Creating a custom Lightning web component for the checkout flow allows the developer to define custom logic and user interface for processing payments using different payment types. The developer can use Apex methods or third-party APIs to integrate with payment service providers or payment gateways and handle payment authorization, capture, void, and refund. The developer can also use @wire or @api decorators to get data from the account object and use its properties, such as the custom checkbox field, to determine which payment options to show or hide based on business logic. Creating a custom Lightning web component that can be used with the standard payment component is not a valid way to meet this requirement, as it does not allow the developer to replace or modify the standard payment component’s logic or user interface. Modifying the standard payment component settings in the checkout screen flow and adding the new payment method is not a valid way either, as it does not allow the developer to add custom payment types or conditional logic based on account data. Adding a new payment gateway through the reference implementation steps so the payment shows up on the checkout payment screen is not a valid way either, as it does not allow the developer to add multiple payment options or conditional logic based on account data. Salesforce References: B2B Commerce Developer Guide: Payment Integration, B2B Commerce Developer Guide: Payment Component, B2B Commerce Developer Guide: Checkout Subflow

The handlebars helper function that is used on Salesforce B2B Commerce pages and components for formatting price values is formatPrice. This function will format a numeric value as a price according to the currency settings and locale of the storefront. For example, {{formatPrice price}} will format the price value as $1,234.56 for US dollars or €1.234,56 for euros. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Handlebars Helpers

If a developer leaves debug mode turned on in an environment, the user will begin getting JavaScript limit exceptions. Debug mode is a setting that enables more detailed logging and error reporting for Lightning web components. However, it also increases the size and complexity of the JavaScript code that is delivered to the browser, which can cause performance issues and JavaScript limit exceptions. The JavaScript limit exceptions are errors that occur when the browser reaches its maximum capacity for executing JavaScript code, such as memory heap size or script execution time. The performance of the org will not become slower each day, as debug mode only affects the client-side performance, not the server-side performance. The org will not turn off debug mode after 72 hours, as debug mode is a persistent setting that can only be changed manually by an administrator. A banner will not be displayed to the userindicating that the org is in debug mode, as debug mode is a transparent setting that does not affect the user interface. Salesforce References: Lightning Web Components Developer Guide: Debug Your Code, Lightning Web Components Developer Guide: JavaScript Limit Exceptions

To debug a flow with detailed tracing of a single input, including watching all variable changes as the checkout process is executed, the developer should enable "Show execution details" (inline) within the Flow Debugger. This feature allows developers to see a step-by-step execution of the flow, including the values of variables at each step. This is crucial for understanding how data is being passed through the flow and for identifying any issues. Salesforce documentation on debugging flows provides more information on this feature:Salesforce Flow Debugging Documentation.

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.

• The correct answer is A and C. To use a sophisticated pricing engine hosted as a service outside the org, the developer must make a call to the service and implement the sfdc_checkout.PriceCalculations interface12. The sfdc_checkout.PriceCalculations interface is a standard interface that defines the methods for calculating prices for a cart or an order1. The developer can use this interface to override the default pricing logic and integrate with an external pricing service12. The developer must also make a call to the external service using Apex REST or SOAP callouts3 and handle the response data accordingly.
• Use External Objects and Implement the sfdc_checkout.CartPriceCalculations are not the correct answers. External objects are a way to access data from external data sources in real time, but they are not suitable for integrating with a pricing service that requires dynamic calculations . The sfdc_checkout.CartPriceCalculations interface is a deprecated interface that was used for calculating prices for a cart only1. It has been replaced by the sfdc_checkout.PriceCalculations interface, which supports both carts and orders1. References:
• B2B Commerce on Lightning Experience Developer Guide
• B2B Commerce and D2C Commerce Developer Guide
• Salesforce Accredited B2B Commerce Developer
• sfdc_checkout.PriceCalculations Interface
• Integrate with Lightning B2B Commerce
• Apex REST Callouts
• [Apex Web Services and Callouts]
• [Work with External Data Sources]
• [Access External Data With Salesforce Connect]

Three ways to implement custom post Order processing are:

• Extend cc_hk_invoice to handle custom business logic post Order processing. This hook allows modifying the invoice data or performing additional actions after an Order is placed. For example, the hook can send an email notification or update a custom field on the invoice record.
• Use cc_hk_Order.placeTarget to define a new Order Confirmation page which executes additional business logic. This hook allows specifying a custom Visualforce page that will be displayed after an Order is placed. The custom page can include additional business logic or user interface elements.
• Use Process Builder to implement business processes that execute when an Order record is created. Process Builder is a tool that allows creating workflows and actions based on criteria and conditions. For example, Process Builder can create a task, send an email, or update a record when an Order record is created. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Hooks, Process Builder

A valid way of referencing the global cc_api_CartExtension apex class via subscriber code is to use ccrz.cc_api_CartExtension. This is the name of the class that is defined in the cloudcraze managed package. The class is global, so it can be accessed by subscriber code. The other options are either invalid or incorrect. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, API Classes