A developer creates a new FlexCardto display customer data and actions, such as updating billing information and changing the contact for the customer account. The FlexCard contains 10 fields and 5 actions. During testing, several fields display with the correct data, but one of the fieldsshows only the label. What could cause this?
A. The fields have exceeded the maximum number allowed on the card.
B. The field is null 0 the Salesforce record.
C. {recordld} us misspelled in the Data Source Input Map.
D. There are no test parameters configured.
Explanation:
When a FlexCard field binding evaluates to null (or empty), the card renders the field’s label but no value. All other configured fields display correctly simply because they contain non-null data; the lone field in question shows only its label precisely because its corresponding record field has no value. Neither a mapping typo nor hitting a field-count limit produces this “label-only” behavior—those errors typically prevent the entire field from rendering or throw a debug error. Ensuring the record’s data source supplies a non-null value (or providing a default) will make the field’s value appear.
In a calculation procedure, what is required for the output of a calculation step to be used in an aggregation step?
A. It must be included in constants.
B. It must bea matrixlookup step.
C. It must be a calculation step.
D. It must be included in the calculation output.
Explanation:
Aggregation Steps in OmniStudio Calculation Procedures can only operate on variables that are exposed in the procedure’s output JSON. When you configure a Calculation Step, you must check Include in Calculation Output for that step’s output variable. This flags the engine to emit the result into the procedure’s output payload, making it available for subsequent aggregation functions (e.g., Sum(MyValue)). If you omit a variable from the output, the aggregation step cannot “see” it and will either error out or return zero. Ensuring every variable you plan to aggregate is included in the calculation output is required for correct aggregation.
Which two of these options can a developer use to retrieve data from a Salesforce object? Choose 2 answers
A. A DataRaptor Load Action
B. A DataRaptor Extract Action
C. A Lookup Input Element
D. A DataRapt or Post Action
Explanation:
Developers have two primary methods for retrieving data from Salesforce objects within Omnistudio implementations. The DataRaptor Extract Action (Option B) serves as a powerful query tool that executes SOQL or SOSL queries to extract records and their fields from specified objects, returning the data in a structured JSON format for use in FlexCards or OmniScripts. The Lookup Input Element (Option C) provides an interactive interface that allows end-users to search for and select records from standard or custom objects, automatically retrieving all associated field data for the selected record. These methods differ fundamentally from DataRaptor Load (Option A) which is designed for data manipulation operations like inserts/updates, and DataRaptor Post (Option D) which handles outbound integrations rather than data retrieval. The Extract Action offers programmatic control for backend data access, while the Lookup Element provides user-driven record selection functionality.
The OmniScript must retrieve device details stored in the Assetobject and then call an external system to send troubleshooting commands via REST API to the device. Which two OmniScript element should the developer use to configure this functionality?
A. DataRaptor Extract Action
B. REST API Action
C. Navigation Action
D. SOQL Action
E. HTTP Action
Explanation:
To retrieve device details from the Asset object, you should use a DataRaptor Extract Action in your OmniScript. This element lets you declaratively query one or more Salesforce objects—like Asset—apply filters, and map field values into your script’s JSON context without writing Apex. Once you have the device information, you need to send troubleshooting commands to an external system via REST. For that, the HTTP Action element is ideal: it supports full HTTP methods (GET, POST, PUT, etc.), headers, authentication, and request/response mappings directly within the OmniScript. Combining these two action elements keeps your integration fully declarative, leverages Salesforce’s governor-limits–aware engine, and avoids custom code. Other elements—like SOQL Action or REST API Action—are either redundant or serve different use cases, whereas DataRaptor Extract and HTTP Action are explicitly designed for Salesforce data retrieval and external API callouts respectively.
Reference:
Salesforce OmniScript Action Elements
A developerneedsto use the CONTIF function to process data entered by the user in an OmniScript. The output of the function needs to be displayed to the user immediately in the current step. Based on best practice, what element should the developer use this function in?
A. A Calculation Action element
B. A SetValues element
C. A formula element
D. A Range element
Explanation:
A formula element allows the developer to define formulas using functions and operators to manipulate data in an OmniScript. The output of the formula element can be displayed to the user immediately in the current step using a display element. The CONTIF function counts how many times a value appears in a list1. A Calculation Action element executes a calculation procedure and returns the output as a JSON object. A Set Values element assigns values to variables or fields in an OmniScript. A Range element defines a range of values for a variable or field in an OmniScript1. Based on best practice, a formula element is the most suitable element to use the CONTIF function in this scenario.
An integration Procedure uses an HTTP action to makea REST API call. The response from the REST API must be converted into a specific XML structure before sending it as an input to another external wen service. How should the developer configure the Integration Procedure to meet this requirement?
A. Use aRemote Action that calls the XMLStreamReader class
B. Use a Remote Action that calls the XMLStreamWriter class
C. Use a DataRaptor Transform to convert JSON to XML
D. Use a DataRaptor Extract and check the XML checkbox on the Output JSON Path.
Explanation:
After your HTTP Action returns JSON, you can declaratively reshape it into the exact XML schema required by your downstream service by dropping a DataRaptor Transform Action into your Integration Procedure. The Transform maps JSON input nodes to output nodes (including attributes and nested elements), and its output format can be configured as XML. This avoids writing Apex parser or writer classes, leverages built‐in tooling for maintenance, and executes within the same transaction. By pointing your Response Action’s Send JSON Path at the Transform element, the system emits well‐formed XML for the next HTTP or Remote Action.
Reference:
Integration Procedure Data Mapper Transform Action
What should a developer's first step be when troubleshooting whether a DataRaptor Extract is retrieving data?
A. Go to the Lightning Console and reload the page to test.
B. Go to the PREVIEW tab In OmniScript to test.
C. Deactivate the card andlayout, andgo to the PREVIEW tab for the card to test.
D. Add a key/value pair in the DataRaptor to test it.
Explanation:
The PREVIEW tab in OmniScript allows developers to simulate and debug DataRaptor Extract actions without affecting live environments. By previewing, they can verify if the correct data is being retrieved before deployment. Option A (Lightning Console) is inefficient for initial troubleshooting. Option C (deactivating cards) is unnecessary for basic validation. Option D (adding key/value pairs) modifies the DataRaptor prematurely. The PREVIEW tab (B) provides immediate feedback, making it the best first step to confirm data retrieval issues.
A developer needs to display the following information together on oneFlexCard:
* Account name, address, phone number, website
* Primary contact first name, contact name, address, phone number, email
The account information must always be visible, and the contact information should only be visible as needed by the user.
What approach should the developer use to display the contact information on the card?
A. Use aData tableelement
B. Set the class’’ collapsible’’ on the block element
C. Set the collapsible property on the block element
D. Use a conditional FlexCard State
Explanation:
FlexCards let you group fields into Block elements and make those blocks user-expandable by enabling their Collapsible property. In this scenario, you’d place the contact fields inside a Block with Collapsible = true, so the Account block remains fully visible while users can click to expand or collapse the contact details on demand. This declarative setting requires no custom CSS or extra states and cleanly separates always-visible account data from optionally visible contact information.
Reference:
FlexCard Block Element Properties
When launching an OmniScript from an action on a FlexCard, the OmniScript displays, but no Salesforce data is populated:
Which two errors could cause this behavior?
(Choose 2 answers)
A. The Id Field for Actions in the FlexCard is blank.
B. There is no active version of the Data Raptor Extract.
C. There isnonactive version of the OmniScript
D. In the DataRaptor Extract Action, the Input Parameters Filter Value is misspelled.
Explanation:
The Id Field for Actions in the FlexCard specifies which field from the FlexCard data source will be used as the record ID for the OmniScript. If this field is blank, the OmniScript will not receive any record ID and will not be able to retrieve any Salesforce data. In the DataRaptor Extract Action, the Input Parameters Filter Value determines how to filter the data based on the record ID. If this value is misspelled, the DataRaptor Extract will not be able to match the record ID and will not return any data.
A developer creates an Integration Procedure with a Set Values and a DataRaptor Extract Action that requires AccountId as a key. When the developer previews the Integration Procedure, thedeveloper enters the AccountId correctly and execute the Preview. The developer sees the data extract by the DataRaptor in the Debug Log, but the response is empty. What is the likely cause of this issue?
A. The DataRaptor Action did not have the add response Ro Response JSON property set to true.
B. The Response cannot be previewed directly.
C. A Response Action was not added to the integration Procedure.
D. The AccountId used for the preview is invalid.
Explanation:
According to the OmniStudio Developer Guide, “To return a response from an Integration Procedure, add a Response action as the last action in your Integration Procedure.” Therefore, the correct answer is C.
A developer needs to configure a DataRaptor to retrieve data from a singleobject. Thestructure of the output data does not need to be changed. Following best practices, which type of DataRaptor should the developer use?
A. DataRaptor Transform
B. DataRaptor Extract
C. DataRaptor Load
D. DataRaptor Turbo Extract
Explanation:
A DataRaptor Turbo Extract is a simplified version of a DataRaptor Extract that can retrieve data from a single object without changing the structure of the output data. It is suitable for this scenario because the developer does not need to transform or load the data
A developer needs tocreateDataRaptor to retrieve the name of an account for a contact. Following best practices, how should a developer configure the extraction steps?
A. Define an extraction step for the Contact object and set the Extract JSON Path to Contact Account.Name
B. Define extraction steps for the Contact and the Account objects, and set the Extract JSON Path to Contact Account.Name
C. Define extraction steps for the Contact and the Account objects, and set the Extract 3SON Path to Account.Name
D. Define an extractionstep for the Account object, and set the Extract JSON Path to AccountContact.Name
Explanation:
A DataRaptor Extract can retrieve data from multiple objects using extraction steps and JSON paths. However, if the data is from a single object, only one extraction step is needed. The Extract JSON Path can use dot notation to access related fields from that object, such as Contact.Account.Name.
| Page 2 out of 10 Pages |
| Previous |