Inwhich three different ways can a theme be enabled in
Salesforce B2B Commerce? (3 answers)
A theme can be enabled in Salesforce B2B Commerce in three different ways:
A Storefront setting: The theme can be specified in the Storefront Configuration settings in CCAdmin. This will apply the theme to all users who access the storefront.
An Account Group field value: The theme can be specified in the Theme field of an Account Group record in Salesforce. This will apply the theme to all users who belong to that account group.
Dynamically through a hook: The theme can be specified dynamically by extending the cc_hk_theme hook. This hook allows changing the theme based on various factors, such as the user, cart, product, or storefront. For example, the hook can apply a different theme for a specific product category or for a specific user segment.
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?
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
Universal Containers (UC) is ready to build a tax provider class using the interfaces available in the Buyer Experience SDK. When creating a tax provider, what are three things that a developer should consider first?
When creating a tax provider, three things that a developer should consider first are: steps to complete in the tax service, how to handle results, and what to implement. Steps to complete in the tax service are the actions that the developer needs to perform to connect to and use the third-party tax service provider's API or service. These steps may include authentication, authorization, request formatting, response parsing, error handling, and logging. How to handle results are the actions that the developer needs to perform to process and apply the tax calculation results from the tax service to the cart or order. These actions may include creating or updating cart items with type of Charge and charge type of Tax, applying tax adjustments or exemptions, and displaying tax amounts and details on the storefront. What to implement are the methods that the developer needs to define in their custom Apex class that implements the sfdc_checkout.TaxCalculations interface. The interface provides methods for customizing the tax calculation logic for a cart or an order, such as getTaxRatesAndRules, applyTaxAmountsAndAdjustments, and handleTaxErrorsAndExceptions. Whether to use JSON or XML is not something that the developer should consider first, as it is not a critical or relevant factor for creating a tax provider. It may depend on the format that the tax service provider supports or prefers, but it does not affect the overall functionality or performance of the tax integration. What events to fire in the Lightning web component is not something that the developer should consider first either, as it is not related to creating a tax provider. It may be an optional feature that the developer can add to enhance the user interface or user experience of their storefront, but it does not affect the core logic or functionality of the tax integration. Salesforce Reference:B2B Commerce Developer Guide: Tax Integration, [B2B Commerce Developer Guide: Tax Calculations Interface]
What interface must a developer implement to override Tax in Checkout?
To override tax in checkout, a developer must implement the sfdc_checkout.TaxCalculations interface. The sfdc_checkout.TaxCalculations interface is an Apex interface that provides methods for customizing the tax calculation logic for a cart or an order. The interface allows the developer to define how to retrieve tax rates and rules, how to apply tax amounts and adjustments, and how to handle tax errors and exceptions. The developer can use the sfdc_checkout.TaxCalculations interface to integrate with a third-party tax service provider or to implement their own tax calculation logic. The other interfaces do not exist or are not related to tax calculation. Salesforce Reference:B2B Commerce Developer Guide: Tax Integration,B2B Commerce Developer Guide: Tax Calculations Interface
Although Salesforce B2B Commerce and Salesforce recommend against using
"without sharing classes" whenever possible, sometimes it is unavoidable. Which three
items will open up a major security hole? (3 answers)
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.
Cynthia Stewart
26 days agoReference Implementations Brown
1 month agoFrank Adams
2 months agoReference Implementations Rodriguez
2 months agoData Management Jackson
29 days agoDavid Allen
3 months agoReference Implementations Perez
3 months agoData Management Johnson
3 months agoAmy Rivera
4 months agoSusan Evans
3 months agoElizabeth Anderson
3 months agoDennis Torres
4 months agoMark Nguyen
3 months agoHarold Flores
4 months agoLashawnda
4 months agoGalen
5 months agoMalcom
5 months agoKandis
5 months agoDoyle
5 months agoKattie
6 months agoTarra
6 months agoAlana
6 months agoOlen
6 months agoDenae
7 months agoTeresita
7 months agoShannan
7 months agoDong
7 months agoBreana
8 months agoRicarda
8 months agoEthan
8 months agoMatt
8 months agoPansy
9 months agoBroderick
9 months agoJunita
9 months agoRasheeda
9 months agoSusana
10 months agoWillodean
10 months agoLeoma
10 months agoAlisha
10 months agoRickie
11 months agoGlendora
11 months agoHoward
11 months agoCiara
11 months agoBrice
11 months agoLeonora
1 year agoPok
1 year agoBrynn
1 year agoLetha
1 year agoPenney
1 year agoJettie
1 year agoYasuko
1 year agoDominic
1 year agoShelton
1 year agoVicki
2 years agoMargot
2 years agoStephania
2 years agoLeatha
2 years agoBernadine
2 years agoArlette
2 years agoCharlene
2 years agoBettina
2 years agoEmilio
2 years agoRanee
2 years agoTegan
2 years agoKenneth
2 years agoSamira
2 years agoMiesha
2 years agoElza
2 years agoAshton
2 years agoSheldon
2 years agoTien
2 years agoFreeman
2 years agoCorinne
2 years agoSuzan
2 years agoAn
2 years agoTamesha
2 years agoHarrison
2 years agoEllsworth
2 years agoPhyliss
2 years agoErnest
2 years agoMargarett
2 years agoTruman
2 years agoLetha
2 years agoLinwood
2 years ago