Salesforce B2B-Commerce-Developer Exam With Confidence Using Practice Dumps

To retrieve metadata about a specific picklist, a developer should use the getPicklistValues wire adapter. The getPicklistValues wire adapter imports data from the @salesforce/ui-api module and returns an object that contains information such as the picklist’s label, value, default value, validity, and controlling field values. The getPicklistMetadataValues wire adapter does not exist. The getPicklistMetadata wire adapter does not exist either. The getPicklist wire adapter does not exist either. Salesforce References: [Lightning Web Components Developer Guide: getPicklistValues], [Lightning Web Components Developer Guide: Import User Interface API]

To reflect the price values stored in an external ERP during the checkout flow, the requirement can be satisfied by overriding the computePricingCart method in ccrz.cc_api_CartExtension and making the callout in this method. This method is responsible for computing the pricing for the cart and its line items. By overriding this method, the user can make a callout to the external ERP and update the pricing information accordingly. Salesforce References: B2B Commerce and D2C Commerce Developer Guide, Logic Classes, ccLogicCart Class

 To debug a flow and watch all the variables changing as the checkout process is executed, the developer needs to enable two features: show the details of what is executed and render flow in either Lightning Runtime or Lightning Experience. These features are available in the debug options in Flow Builder, and they allow the developer to see real-time details of the flow actions, inputs, outputs, and outcomes in a panel on the right. The developer can also set input variables, restart the flow, and convert the debug run to a test. Option A is incorrect because there is no such thing as a debug tog in Flow Builder. Option C is incorrect because running the latest version of each flow called by subflow elements is not a feature that the developer can enable or disable, but rather a default behavior of Flow Builder. References: Debug a Flow in Flow Builder, B2B Commerce Checkout Flow (Aura), B2B Commerce Checkout Flow Core Actions