A consultant wants to proceed with a FlexCard canvas design that will display data from a legacy billing system. The legacy billing system is being extended to add a SOAP endpoint that will allow for the data to be retrieved in XML format. However, the endpoint is not ready yet. Which data source should the team use to make progress on the design?
Correct Answer: A
Question 82
How many levels deep can reusable OmniScripts be nested?
Correct Answer: D
Reusable OmniScripts are OmniScripts that can be embedded within other OmniScripts to create modular and reusable components. They can be nested up to unlimited levels deep, as long as there are no circular references or conflicts between the parent and child OmniScripts.
Question 83
A company needs to create a quoting process for its internal agents. During quoting the agent select a product that is passed to the Omniscript with product details including the unit price, and specifies the grade (A, B, C, D, E) size (Small, Medium, Large, X-Large). The process should use the grade and size to look up a discount factor, then multiply the unit price by that discount to retumn the quote. Which two tools should the to meet these Choose 2 answers
Correct Answer: C,D
The requirement involves creating a quoting process within an OmniScript where an agent selects a product (with a unit price), specifies grade and size, looks up a discount factor based on those inputs, and calculates the final quote. Two OmniStudio tools are needed to achieve this: Decision Matrix and DataRaptor Extract. Here's why C. Decision Matrix and D. DataRaptor Extract are the correct answers: * C. Decision Matrix: * Purpose: A Decision Matrix in OmniStudio is a tool used to look up values based on multiple input conditions, returning a result that can be used in calculations or processes. It's essentially a configurable lookup table stored as a Salesforce custom object (DecisionMatrixDefinition). * Application: In this scenario, the Decision Matrix is ideal for determining the discount factor based on the combination of grade (A, B, C, D, E) and size (Small, Medium, Large, X-Large). For example: * Grade A + Small = 0.9 (10% discount) * Grade B + Large = 0.85 (15% discount) * And so on for all 20 combinations (5 grades × 4 sizes). * Integration with OmniScript: The OmniScript can call the Decision Matrix via an Integration Procedure or directly reference it in a Calculation Action, passing Grade and Size as inputs and receiving the DiscountFactor as output. * Why It Fits: The requirement explicitly states "look up a discount factor," and Decision Matrix is purpose-built for such multi-variable lookups, making it more efficient than manual coding or other tools. * D. DataRaptor Extract: * Purpose: A DataRaptor Extract retrieves data from Salesforce objects and maps it into a JSON format usable by OmniScripts or other components. * Application: The product details, including the UnitPrice, are passed to the OmniScript when the agent selects a product. A DataRaptor Extract is needed to fetch this product data from a Salesforce object (e.g., Product2 or a custom object like QuoteLineItem__c) based on the selected product's ID. The extracted data (e.g., { "ProductId": "01t...", "UnitPrice": 100 }) is then available in the OmniScript's data JSON. * Role in Calculation: After the Decision Matrix provides the discount factor, the OmniScript can use a Calculation Action to multiply the UnitPrice (from the DataRaptor Extract) by the DiscountFactor (from the Decision Matrix) to compute the quote (e.g., 100 * 0.9 = 90). * Why It Fits: The process starts with product selection, and DataRaptor Extract is the standard OmniStudio tool for retrieving Salesforce data like unit price. * How They Work Together: * DataRaptor Extract: Fetches product details (e.g., UnitPrice) when the agent selects a product. * Decision Matrix: Looks up the discount factor based on Grade and Size inputs. * Calculation Action in OmniScript: Multiplies UnitPrice by DiscountFactor to return the quote. Now, let's examine why the other options are incorrect: * A. DataRaptor Transform: A DataRaptor Transform manipulates or reshapes data (e.g., converting JSON structures or applying formulas) but doesn't retrieve data from Salesforce or perform lookups like a Decision Matrix. While it could theoretically calculate the quote after data is fetched, it's not needed here since a Calculation Action within OmniScript can handle the multiplication, and it doesn't address the lookup requirement. * B. Expression Set: An Expression Set defines reusable formulas or conditions in OmniStudio, often used in Integration Procedures or Calculations. While it could compute the final quote (e.g., UnitPrice * DiscountFactor), it doesn't retrieve data or perform lookups based on grade and size. It's a supporting tool, not a primary solution for this requirement. References: * Salesforce OmniStudio Documentation: Decision Matrix Overview - Describes using Decision Matrices for multi-condition lookups. * Salesforce OmniStudio Developer Guide: DataRaptor Extract - Details retrieving Salesforce data for OmniScript use.
Question 84
What is the purpose of the "OmniStudio User" permission set license (PSL)?
Correct Answer: D
The OmniStudio User permission set license is used as the licensing entitlement that allows OmniStudio-related permission sets to be assigned to a user. A PSL does not automatically provision all OmniStudio tools, and it does not itself replace proper permission set assignments, object permissions, or field-level security. The actual access model still requires assigning the relevant OmniStudio permission sets according to the user's role. Option A is close but too broad; the more precise purpose in this context is that the PSL enables the assignment and use of OmniStudio-specific permission sets. Salesforce documentation and release notes describe OmniStudio permission set licenses and the relationship between OmniStudio User/Admin licensing and permission set assignment.
Question 85
A public sector agency wants to digitize a paper-based permit application. The process requires a citizen to step through several screens of questions, upload a PDF document, and sign the application digitally. Which OmniStudio tool serves this specific use case?
Correct Answer: B
OmniScript is the correct tool because the requirement is a guided, step-by-step digital interaction. The citizen must move through several screens, answer questions, upload supporting documentation, and complete an application process. Calculation Matrices are for rules-based calculations, not user-facing permit forms. Integration Procedures handle server-side orchestration and integrations, but they do not provide the guided UI experience. FlexCards are used to display contextual information and actions, not to run a multi-screen application journey. Salesforce specifically positions OmniScripts as guided processes for customers, partners, and internal users, and Salesforce Public Sector documentation describes OmniScripts as tools for dynamic application forms for licenses, permits, programs, and services. Salesforce also supports file upload elements within OmniScripts.
