Salesforce OmniStudio Consultant Practice Exams
Last updated on Oct 22,2026- Exam Code: OmniStudio Consultant
- Exam Name: Salesforce Certified OmniStudio Consultant Exam
- Certification Provider: Salesforce
- Latest update: Oct 22,2026
Question #111
A company needs to create an OmniScript with three steps.
• Step 1
• Step 2
• Step 3
Enter customer details
Select a product
Display a price retrieved from a REST API
The product’s price should automatically display in Step 3.
What should the consultant add to the design of the OmniScript to meet these requirements?
- A . DataRaptor Post Action between Step 2 and Step 3
- B . Integration Procedure Action between Step 2 and Step 3
- C . DataRaptor Post Action inside Step 2
- D . Integration Procedure Action inside Step 3
Correct Answer: D
D
Explanation:
The consultant should add an Integration Procedure Action inside Step 3 to meet the requirements. An Integration Procedure Action can execute an Integration Procedure that invokes a REST API and retrieves the product price. The Integration Procedure Action can be configured to run automatically when Step 3 is loaded, and display the price in a field or label element
D
Explanation:
The consultant should add an Integration Procedure Action inside Step 3 to meet the requirements. An Integration Procedure Action can execute an Integration Procedure that invokes a REST API and retrieves the product price. The Integration Procedure Action can be configured to run automatically when Step 3 is loaded, and display the price in a field or label element
Question #112
A business requires a solution to generate an event {platform event) using account information. All the event information is related to the customer and is stored in Salesforce.
Using an Integration Procedure, which two actions are necessary to design this solution? Choose 2 answers
- A . HTTP
- B . Response
- C . DataRaptor Post
- D . DataRaptor Extract
Correct Answer: C,D
C,D
Explanation:
The two actions that are necessary to design this solution using an Integration Procedure are DataRaptor Post and DataRaptor Extract. A DataRaptor Post is an action that can write data to a Salesforce object or invoke a Salesforce API. The consultant can use a DataRaptor Post action to create an event (platform event) using account information. A DataRaptor Extract is an action that can retrieve data from a Salesforce object or invoke a Salesforce API. The consultant can use a DataRaptor Extract action to get the account information from Salesforce
C,D
Explanation:
The two actions that are necessary to design this solution using an Integration Procedure are DataRaptor Post and DataRaptor Extract. A DataRaptor Post is an action that can write data to a Salesforce object or invoke a Salesforce API. The consultant can use a DataRaptor Post action to create an event (platform event) using account information. A DataRaptor Extract is an action that can retrieve data from a Salesforce object or invoke a Salesforce API. The consultant can use a DataRaptor Extract action to get the account information from Salesforce
Question #113
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
- A . Data Mapper Transform
- B . Expression Set
- C . Decision Matrix
- D . Data Mapper Extract
Correct Answer: C,D
C,D
Explanation:
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:
C,D
Explanation:
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:
Question #114
A company needs to create some boundaries for their sales teams regarding the minimum and maximum discounts that can be applied to their orders. The discount thresholds are set using adjustments such as 5%, 10%, 15%, 20%, 25%, and 30%. The minimum adjustment and the maximum adjustment are determined by their region and their customer lifetime score.
Which two OmniStudio tools should the consultant recommend to meet these requirements’ Choose 2 answers
- A . OmniStudio Action
- B . Calculation Procedure
- C . Calculation Matrix
- D . DataRaptor Transform
Correct Answer: B,C
B,C
Explanation:
The two OmniStudio tools that should be recommended to meet these requirements are Calculation Procedure and Calculation Matrix. Calculation Procedure allows the designer to define a multi-step calculation process that can use data from various sources. Calculation Matrix allows the designer to define a table of values that can be used as inputs or outputs for calculations. In this case, a Calculation Matrix can be used to store the discount thresholds based on region and customer lifetime score, and a Calculation Procedure can be used to apply them to the orders. OmniStudio Action is not needed for this scenario, as there is no interaction involved. DataRaptor Transform is not suitable for this scenario, as it is used to transform data from one format to another.
B,C
Explanation:
The two OmniStudio tools that should be recommended to meet these requirements are Calculation Procedure and Calculation Matrix. Calculation Procedure allows the designer to define a multi-step calculation process that can use data from various sources. Calculation Matrix allows the designer to define a table of values that can be used as inputs or outputs for calculations. In this case, a Calculation Matrix can be used to store the discount thresholds based on region and customer lifetime score, and a Calculation Procedure can be used to apply them to the orders. OmniStudio Action is not needed for this scenario, as there is no interaction involved. DataRaptor Transform is not suitable for this scenario, as it is used to transform data from one format to another.
Question #115
A company has a requirement to create a 360° view of their customers using FlexCards. At this company, customer data is stored in Salesforce but also in external legacy systems. A consultant reviews the use cases needed and recommends a FlexCard canvas that contains 5 child FlexCards inside the state of the parent FlexCard.
How many different data sources can be configured using FlexCards in this scenario?
- A . 2
- B . 6
- C . 5
- D . 1
Correct Answer: D
D
Explanation:
The number of different data sources that can be configured using FlexCards in this scenario is 6. A FlexCard can have one data source per state, and a state can have multiple child FlexCards, each with its own data source. Therefore, the parent FlexCard can have one data source for its state, and each of the 5 child FlexCards can have a different data source, making a total of 6 data sources
D
Explanation:
The number of different data sources that can be configured using FlexCards in this scenario is 6. A FlexCard can have one data source per state, and a state can have multiple child FlexCards, each with its own data source. Therefore, the parent FlexCard can have one data source for its state, and each of the 5 child FlexCards can have a different data source, making a total of 6 data sources
Question #116
A company needs to create a quoting process for its internal agents. During quoting, the agent selects a product that is passed to the OmniScript with product details including the unit price, and specifies the grade (A, B, C, D, E) and 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 return the quote.
Which two tools should be used to meet these requirements? Choose 2 answers
- A . DataRaptor Transform
- B . Expression Set
- C . Decision Matrix
- D . DataRaptor Extract
Correct Answer: C,D
C,D
Explanation:
Comprehensive and Detailed In-Depth 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:
C,D
Explanation:
Comprehensive and Detailed In-Depth 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:
Question #117
Topic: Salesforce API
You want to display Chatter feeds, users, groups, and followers, especially in mobile applications. Also, you want to provide programmatic access to files, recommendations, topics, notifications, and Data.com purchasing.
Which of the following option should you use to do this?
- A . Streaming API
- B . REST API
- C . Tooling API
- D . Chatter REST AP!
- E . Chatter SOAP API
Correct Answer: D
D
Explanation:
The requirement involves displaying Chatter-related data (feeds, users, groups, followers) in mobile applications and providing programmatic access to additional features like files, recommendations, topics, notifications, and Data.com purchasing. The Chatter REST API is the most suitable Salesforce API for this purpose, making D the correct answer.
Here’s why
D. Chatter REST API is the correct answer:
Chatter REST API Overview: The Chatter REST API is a specialized subset of the Salesforce REST API, optimized for social collaboration features. It provides access to Chatter-specific functionality (e.g., feeds, posts, comments, groups, users, followers) and extends to related features like files (Chatter Files), recommendations, topics, notifications, and even Data.com purchasing integrations. Meeting the Requirements:
Chatter Feeds, Users, Groups, Followers: The Chatter REST API offers endpoints like /chatter/feeds, /chatter/users, /chatter/groups, and /chatter/users/{id}/followers to retrieve and display this data in a mobile app.
Files: Use /chatter/files or /connect/files endpoints to access and manage Chatter Files.
Recommendations: Access Chatter recommendations via /connect/recommendations.
Topics: Manage topics with /connect/topics.
Notifications: Handle notifications via /connect/notifications.
Data.com Purchasing: The API supports Data.com-related calls (e.g., purchasing contact data) through specific endpoints like /connect/datacom.
Mobile Optimization: The REST-based architecture of the Chatter REST API is lightweight, uses JSON (or XML), and is ideal for mobile applications due to its stateless, HTTP-based design, aligning with the requirement’s emphasis on mobile use.
Programmatic Access: It provides full CRUD (create, read, update, delete) capabilities for Chatter data and related features, meeting the need for programmatic control.
Now, let’s examine why the other options are incorrect:
D
Explanation:
The requirement involves displaying Chatter-related data (feeds, users, groups, followers) in mobile applications and providing programmatic access to additional features like files, recommendations, topics, notifications, and Data.com purchasing. The Chatter REST API is the most suitable Salesforce API for this purpose, making D the correct answer.
Here’s why
D. Chatter REST API is the correct answer:
Chatter REST API Overview: The Chatter REST API is a specialized subset of the Salesforce REST API, optimized for social collaboration features. It provides access to Chatter-specific functionality (e.g., feeds, posts, comments, groups, users, followers) and extends to related features like files (Chatter Files), recommendations, topics, notifications, and even Data.com purchasing integrations. Meeting the Requirements:
Chatter Feeds, Users, Groups, Followers: The Chatter REST API offers endpoints like /chatter/feeds, /chatter/users, /chatter/groups, and /chatter/users/{id}/followers to retrieve and display this data in a mobile app.
Files: Use /chatter/files or /connect/files endpoints to access and manage Chatter Files.
Recommendations: Access Chatter recommendations via /connect/recommendations.
Topics: Manage topics with /connect/topics.
Notifications: Handle notifications via /connect/notifications.
Data.com Purchasing: The API supports Data.com-related calls (e.g., purchasing contact data) through specific endpoints like /connect/datacom.
Mobile Optimization: The REST-based architecture of the Chatter REST API is lightweight, uses JSON (or XML), and is ideal for mobile applications due to its stateless, HTTP-based design, aligning with the requirement’s emphasis on mobile use.
Programmatic Access: It provides full CRUD (create, read, update, delete) capabilities for Chatter data and related features, meeting the need for programmatic control.
Now, let’s examine why the other options are incorrect:
Question #118
A consultant is tasked with migrating Calculation Matrices and Procedures as Decision Matrices and Expression Sets respectively.
What is a key consideration when migrating Calculation Matrices and Procedures?
- A . Procedures can be migrated without considerations.
- B . Matrices can be migrated with minimal considerations.
- C . Matrices can be migrated without considerations.
- D . Looping procedures cannot be migrated as expression sets.
Correct Answer: D
D
Explanation:
The task involves migrating legacy Calculation Matrices to Decision Matrices and Calculation Procedures to Expression Sets in OmniStudio. A key consideration arises from the differences in functionality between these tools, particularly with looping logic, making D the correct answer.
Here’s why
D. Looping procedures cannot be migrated as Expression Sets is the correct answer:
Migration Context:
Calculation Matrices → Decision Matrices: Calculation Matrices (from older Vlocity tools) are lookup tables that map inputs to outputs. They migrate to Decision Matrices in OmniStudio, which serve the same purpose (e.g., returning a discount based on inputs) and are generally straightforward to convert, as both are data-driven tables stored as Salesforce metadata.
Calculation Procedures → Expression Sets: Calculation Procedures are sequential, logic-driven processes that can include formulas, conditions, and loops. They migrate to Expression Sets in OmniStudio, which are collections of reusable expressions (formulas or conditions) executed in a specific order.
Key Consideration C Looping:
Calculation Procedures: These legacy procedures support looping logic, such as iterating over a list of items (e.g., processing multiple line items in a quote to calculate totals).
Expression Sets: Expression Sets in OmniStudio are designed for linear, non-iterative calculations. They execute a series of expressions (e.g., Total = Price * Quantity) but do not natively support looping constructs like “for each” or “while” loops. Looping requires an Integration Procedure or custom Apex in OmniStudio, not Expression Sets.
Impact: If a Calculation Procedure includes looping (e.g., summing values across a JSON array), it cannot be directly migrated to an Expression Set without rearchitecting the logic. The consultant must consider alternative tools (e.g., an Integration Procedure with a Loop Block) to handle such cases.
Why It’s Key: Failing to account for looping can break the migrated process, as Expression Sets lack this capability. Identifying and addressing looping logic upfront is critical to ensure functional equivalence post-migration.
Now, let’s examine why the other options are incorrect:
D
Explanation:
The task involves migrating legacy Calculation Matrices to Decision Matrices and Calculation Procedures to Expression Sets in OmniStudio. A key consideration arises from the differences in functionality between these tools, particularly with looping logic, making D the correct answer.
Here’s why
D. Looping procedures cannot be migrated as Expression Sets is the correct answer:
Migration Context:
Calculation Matrices → Decision Matrices: Calculation Matrices (from older Vlocity tools) are lookup tables that map inputs to outputs. They migrate to Decision Matrices in OmniStudio, which serve the same purpose (e.g., returning a discount based on inputs) and are generally straightforward to convert, as both are data-driven tables stored as Salesforce metadata.
Calculation Procedures → Expression Sets: Calculation Procedures are sequential, logic-driven processes that can include formulas, conditions, and loops. They migrate to Expression Sets in OmniStudio, which are collections of reusable expressions (formulas or conditions) executed in a specific order.
Key Consideration C Looping:
Calculation Procedures: These legacy procedures support looping logic, such as iterating over a list of items (e.g., processing multiple line items in a quote to calculate totals).
Expression Sets: Expression Sets in OmniStudio are designed for linear, non-iterative calculations. They execute a series of expressions (e.g., Total = Price * Quantity) but do not natively support looping constructs like “for each” or “while” loops. Looping requires an Integration Procedure or custom Apex in OmniStudio, not Expression Sets.
Impact: If a Calculation Procedure includes looping (e.g., summing values across a JSON array), it cannot be directly migrated to an Expression Set without rearchitecting the logic. The consultant must consider alternative tools (e.g., an Integration Procedure with a Loop Block) to handle such cases.
Why It’s Key: Failing to account for looping can break the migrated process, as Expression Sets lack this capability. Identifying and addressing looping logic upfront is critical to ensure functional equivalence post-migration.
Now, let’s examine why the other options are incorrect:
Question #119
A consultant is working with a client who wants to display specific account information on a Flexcard. The client wants to include account status, priority level, creation date, and company logo. They also want to include actions such as closing a case, opening a new case, or creating a task.
What is the best approach for the consultant to meet the client’s requirements?
- A . Use Omniscripts to ,,, script that display .. required information
- B . Use the Flexeard Designer to create a Flexcard, adding the necessary fields and actions.
- C . Use Integration Procedures to integrate the necessary data
- D . Use Data Mappers to transfer and transform the necessary data.
Correct Answer: B
B
Explanation:
FlexCards (B) C FlexCards are the best choice because they are designed to display account-related information such as status, priority level, creation date, and company logo while also allowing the inclusion of actions (e.g., closing a case, opening a new case, creating a task).
FlexCards provide a user-friendly UI with clickable actions that can trigger OmniScripts or Integration Procedures to process user interactions.
B
Explanation:
FlexCards (B) C FlexCards are the best choice because they are designed to display account-related information such as status, priority level, creation date, and company logo while also allowing the inclusion of actions (e.g., closing a case, opening a new case, creating a task).
FlexCards provide a user-friendly UI with clickable actions that can trigger OmniScripts or Integration Procedures to process user interactions.
Question #120
A business wants to create a FlexCard for mobile plans to add to their Customer 360° console application.
The FlexCard needs to include the following actions:
• Start a process to retrieve plan consumption data
• Create a new case
• Open a promotions web page
• Change the SIM card
which combination should the consultant use in designing the solution?
- A . Custom Event and Redirect URL
- B . OmniScript and Navigate
- C . Event, Navigate and Card
- D . Flyout and OmniScript
Correct Answer: B
B
Explanation:
The combination that the consultant should use in designing the solution is OmniScript and Navigate. An OmniScript is a tool that can design customer interactions using elements and actions. The consultant can use an OmniScript to display the mobile plans for the Customer 360° console application. A Navigate action is a button or a link that can redirect the user to another web page or URL. The consultant can use Navigate actions to add the following actions to the FlexCard: start a process to retrieve plan consumption data, create a new case, open a promotions web page, and change the SIM card
B
Explanation:
The combination that the consultant should use in designing the solution is OmniScript and Navigate. An OmniScript is a tool that can design customer interactions using elements and actions. The consultant can use an OmniScript to display the mobile plans for the Customer 360° console application. A Navigate action is a button or a link that can redirect the user to another web page or URL. The consultant can use Navigate actions to add the following actions to the FlexCard: start a process to retrieve plan consumption data, create a new case, open a promotions web page, and change the SIM card