A developer is trying to troubleshoot why a field is not displaying on the Product Detail Page. What should be typed in the Developer Tools Console in the browser to view the fields available for the Product Detail Page?
Correct Answer: C
Explanation:
To view the fields available for the Product Detail Page, the developer should type CCRZ.productDetailModel in the Developer Tools Console in the browser. This will display the product detail model object, which contains the product data and attributes that are rendered on the page. The other options are either not valid or not relevant for the Product Detail Page.
Question 2
A Developer created a custom field that a project wants to expose on a given page. How does the Developer ensure that the field is available to display on a given page?
Correct Answer: A
Explanation:
To ensure that a custom field is available to display on a given page, the Developer needs to override the Service Class that the page uses and update the Service Management in CCAdmin for the given storefront to use this new Service Class. The Service Class is responsible for retrieving and setting data for a given page. The Logic Class is responsible for implementing business logic and validation rules for a given page. Creating a new Service Class or Logic Class is not necessary, as overriding an existing one can achieve the same result. Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Service Classes, Logic Classes
Question 3
A configuration value, CO.NewOrder, is set to TRUE. What is one way of preventing anexisting payment page from being shown on the checkout payment page?
Correct Answer: B
Explanation:
This approach effectively removes the payment page from the list of allowed pages, ensuring it is not
displayed during the checkout process.
Reference: Salesforce B2B Commerce documentation on checkout process customization and
configuration settings, specifically focusing on payment page handling and the pmt.whitelist setting.
This approach effectively removes the payment page from the list of allowed pages, ensuring it is not displayed during the checkout process. Reference: Salesforce B2B Commerce documentation on checkout process customization and configuration settings, specifically focusing on payment page handling and the pmt.whitelist setting. The pmt.whitelist configuration setting in Salesforce B2B Commerce is used to manage the Visualforce pages that support all payment types on the storefront1. If you want to prevent an existing payment page from being shown on the checkout payment page, one way to do it is to remove the value matching the page name from the pmt.whitelist configuration setting. After doing this, you would need to rebuild and activate a new Configuration cache for the changes to take effect1. Please note that this information is based on the Salesforce B2B Commerce documentation and best practices1.
Demo Practice Mode
You are viewing only the questions marked as Demo.