Salesforce B2B-Commerce-Developer - Salesforce Accredited B2B Commerce Developer Certification Exam

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.

The ccrz.ccUtil.defVal (Map<String.Object> mp, String key, Object ob) method will return the value in
the given Map if found or a default value in the event that the Map is null, empty, or an object is not
found for that key. This method is useful for providing fallback values for configuration settings or
input parameters that may be missing or invalid. Salesforce Reference: B2B Commerce and D2C
Commerce Developer Guide, ccUtil Class

The ccUtil apex class provides two methods to check the input or return data of the Global API’s:
ccrz.ccUtil.isNotEmpty(Map<String, Object>) and ccrz.ccUtil.isEmpty(Map<String, Object>). These
methods return true if the map is not null and contains at least one entry, or if the map is null or
empty, respectively. Similarly, ccrz.ccUtil.isNotEmpty(List<Object>) and
ccrz.ccUtil.isEmpty(List<Object>) return true if the list is not null and contains at least one element,
or if the list is null or empty, respectively. These methods are useful for validating the input
parameters or the output results of the Global API’s.

Executing dynamic SOQL inside a without sharing class with a bind variable from
PageReference.getParameters(), PageReference.getCookies(), or cc_RemoteActionContext class will
open up a major security hole because these sources of input are not sanitized and can be
manipulated by malicious users to inject SOQL queries that bypass the sharing rules and access data
that they are not supposed to see. For example, a user can modify the URL parameters or cookies to
include a SOQL query that returns sensitive data from the database. To prevent this, it is
recommended to use static SOQL or escape the bind variables before executing dynamic SOQL.