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.
Which three statements are true about Global API versioning? (3 answers)
Three statements that are true about Global API versioning are:
Calling in with an API version set to lower than 1 will result in an exceptional case where the exception class ccrz.BelowMinAPIVersionException will be returned to callers. This exception indicates that the API version is not supported by the framework and the caller should use a higher API version.
The API version is scoped at the Class API level and NOT at the method level. This means that all the methods in a class will use the same API version that is specified by the caller. For example, if the caller passes an API version of 4 to ccrz.ccServiceProduct.getProducts(), then all the other methods in ccrz.ccServiceProduct will also use API version 4.
Calling in with an API version set to more than current maximum will result in exception case where the exception class ccrz.ExceedsMaxAPIVersionException will be returned to callers. This exception indicates that the API version is not supported by the framework and the caller should use a lower API version. Salesforce Reference:B2B Commerce and D2C Commerce Developer Guide,API Versioning
Which handlebars helper expression is used in Salesforce B2B Commerce pages and
components to toggle the display of a block of markup?
The handlebars helper expression that is used in Salesforce B2B Commerce pages and components to toggle the display of a block of markup is {{#ifConfig 'Field__c'}} ... {{/ifConfig}}. This expression will evaluate the value of the configuration setting with the API name Field__c and render the block of markup if the value is true, or skip it if the value is false. For example,{{#ifConfig 'CO.showMiniCart'}}
Frank Adams
12 days agoReference Implementations Rodriguez
23 days agoDavid Allen
1 month agoReference Implementations Perez
2 months agoData Management Johnson
2 months agoAmy Rivera
2 months agoSusan Evans
2 months agoElizabeth Anderson
2 months agoDennis Torres
2 months agoMark Nguyen
2 months agoHarold Flores
2 months agoLashawnda
3 months agoGalen
3 months agoMalcom
3 months agoKandis
4 months agoDoyle
4 months agoKattie
4 months agoTarra
4 months agoAlana
5 months agoOlen
5 months agoDenae
5 months agoTeresita
5 months agoShannan
6 months agoDong
6 months agoBreana
6 months agoRicarda
6 months agoEthan
7 months agoMatt
7 months agoPansy
7 months agoBroderick
7 months agoJunita
8 months agoRasheeda
8 months agoSusana
8 months agoWillodean
8 months agoLeoma
9 months agoAlisha
9 months agoRickie
9 months agoGlendora
9 months agoHoward
9 months agoCiara
10 months agoBrice
10 months agoLeonora
12 months 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
1 year agoMargot
1 year agoStephania
1 year agoLeatha
1 year agoBernadine
1 year agoArlette
1 year 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