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?
Answer : D
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
What is the purpose of Step elements in an OmniScript?
Answer : A
Step elements (A) -- The Step element is used in OmniScripts to break down the script into multiple pages or sections. This helps organize the user flow and enhances the user experience by making long processes more manageable.
B . Groups elements that extract data -- This is not correct; data extraction is handled by DataRaptors or Integration Procedures.
C . Enables the use of repeatable blocks -- This is incorrect; Repeat Blocks allow users to dynamically add multiple sets of input fields, not Steps.
D . Allows the user to input data -- While Steps may contain input fields, their primary purpose is to organize the script into multiple pages, not to handle input directly.
Comprehensive and Detailed In-Depth Why not the other options?? Salesforce OmniStudio Reference:
OmniScript Step Elements
Service agents must confirm customer contact information in the first step of a payment OmniScript. Contact information includes name, telephone number, mobile number, and email. None of the contact information on first step is required.
On the last step, after taking payment, the agent can optionally email the receipt to the customer. If the customer says yes, the agent selects a checkbox. If the agent selects the box but the email address field is empty, the process must require the user to return to the first step and enter the customer's email address.
What should the consultant recommend to meet this requirement?
Answer : A
The consultant should recommend adding a Set Errors element to meet this requirement. A Set Errors element can display an error message and prevent the OmniScript from proceeding if certain conditions are not met. The consultant can use a Set Errors element to check if the email address field is empty when the agent selects the checkbox to email the receipt.If it is empty, the Set Errors element can show an error message and direct the user to return to the first step and enter the customer's email address
A company implements an integration procedure that is invoked from an OmniScript. The integration procedure includes a recommend to improve performance and address users concerns
Which feature should the consultant recommend to improve performance and address users concerns?
Answer : C
The two actions that the consultant should recommend to the project team are replace existing APEX using DataRaptors and HTTPActions, and implement FlexCards and OmniScripts for the front-end. Replacing existing APEX using DataRaptors and HTTPActions would reduce implementation time, as these tools are declarative and do not require coding. Implementing FlexCards and OmniScripts for the front-end would ensure end-user processes are as simple as possible, as these tools provide guided interactions and contextual data. Creating new LWC templates for branding and styling would increase implementation time, as this would require coding and testing. Using existing APEX classes as data sources would not ensure optimal UX, as this would limit the flexibility and scalability of the solution.
A business is creating an agent console with FlexCards to provide a 360 view of their customers. The business wants the following information displayed:
* Account information including account name, phone, and website
* Active opportunities related to the account
* Active contracts related to the account
* The ability to view and renew contracts
An Integration Procedure will be used to retrieve Account, Opportunity, and Contract data.
How should the consultant design the FlexCards to meet these requirements?
Answer : A
The consultant should design the FlexCards using a Parent FlexCard with multiple Child and Card Actions to meet these requirements. A Parent FlexCard is a FlexCard that can display data and actions in a card format, and also contain one or more Child FlexCards. The consultant can use a Parent FlexCard to display the account information, including account name, phone, and website. A Child FlexCard is a FlexCard that can display data and actions in a card format within a Parent FlexCard. The consultant can use multiple Child FlexCards to display the active opportunities and contracts related to the account. A Card Action is a button or a link that can invoke an OmniScript or an Integration Procedure from a FlexCard.The consultant can use multiple Card Actions to enable the user to view and renew contracts
When a customer calls to add a new primary contact to their account, call center agents need to complete a I contact form. The agent enters the new contact information using an OmniScript and then needs to generate PDF with the contact information pre-filled that can be shared with the customer.
Which OmniStudio tool should the consultant recommend to generate the pre-filled PDF'
Answer : C
The OmniStudio tool that the consultant should recommend to generate the pre-filled PDF is DataRaptor. A DataRaptor is a tool that can read, transform, and write data from Salesforce objects or JSON objects. A DataRaptor Load can write data to a PDF template using a PDF mapping file, and generate a PDF document with the contact information pre-filled.The PDF document can be stored as an attachment or a content document in Salesforce
When designing OmniStudio solutions, what are two reasons that explain why Integration Procedures are recommended as the first choice of data sources for FlexCards and OmniScripts?
Choose 2 answers
Answer : A, C
The two reasons that explain why Integration Procedures are recommended as the first choice of data sources for FlexCards and OmniScripts are: they future-proof your front-end design and they combine multiple actions into a single server call. An Integration Procedure can abstract the data source from the front-end design, making it easier to change or update the data source without affecting the FlexCard or OmniScript.An Integration Procedure can also execute multiple DataRaptor actions, such as Extract, Transform, and Load, and also invoke REST or SOAP services in one call, reducing the number of requests and processing time