In which three ways should useful debugging information in Salesforce B2B Commerce implementation be garnered? (3 answers) A) Enabling the logging token via

In which three ways should useful debugging information in Salesforce B2B Commerce implementation be garnered? (3 answers) A) Enabling the logging token via
A . Admin andsubsequently inspecting the logs via the browser console.
B . Logging a case with Salesforce support to enable advanced debugging options.
C . Enabling debugging options for the current user and visually inspecting the Salesforce debug logs.
D . Placing a System.debug() statement anywhere in the class being debugged.
E . Logging into the community as a system administrator to identify any potential permissions or Visualforce exceptions.

Answer: A,C,E

Explanation:

Useful debugging information in Salesforce B2B Commerce implementation can be garnered in three ways:

Enabling the logging token via Admin and subsequently inspecting the logs via the browser console. This will enable logging messages and errors to the browser console, which can be viewed by opening the Developer Tools in the browser. The logging token can be enabled by setting the value of CO.logToken to true in CCAdmin.

Enabling debugging options for the current user and visually inspecting the Salesforce debug logs. This will enable logging messages and errors to the Salesforce debug logs, which can be viewed by opening the Debug Logs page in Salesforce Setup. The debugging options can be enabled by creating a Debug Level and a Trace Flag for the current user in Salesforce Setup.

Logging into the community as a system administrator to identify any potential permissions or Visualforce exceptions. This will allow viewing any errors or warnings that may occur on the community pages due to insufficient permissions or Visualforce issues. The system administrator can also access CCAdmin and other tools from within the community.

Salesforce Reference: B2B Commerce and D2C Commerce Developer Guide, Logging, Debug Your Code