...... configure Additional input to send exactly the same data? Assume that the develop checkedSend Only Additional input.
A)
B)
C)
D)
Correct : D
Option D is the correct way to configure Additional input to send exactly the same data as Input Data. The Additional input should have the same key/value pairs as Input Data, and the value should be set to {{InputData.key}} for each key. This will pass the value of Input Data for each key to Additional input.
Start a Discussions
Refer to the exhibit.
A developer has configured an integration Procedure element with SEND/RESPONSETRANFORMATIONS as shown.
Alternatively, how could the developer configure Additional input to send exactly the same data? Assume that the developer checked Send Only Additional input.
A)
B)
C)
Correct : C
Option C is the correct way to configure Additional input to send exactly the same data as Input Data. The Additional input should have a key/value pair for each field in Input Data, and the value should be set to {{InputData.field}} for each field. This will pass the value of Input Data for each field to Additional input.
Start a Discussions
A developer is building an OmniScript and needs to retrieve data from Salesforce and from an on-premises billing database.
Which two OmniScript elements could retrieve this data?
Choose 2 answers
Correct : B, C
According to theOmniScript Action Elementspage, a DataRaptor Extract Action can be used to ''get data from one or more Salesforce records'' and an HTTP Action can be used to ''get, save, or delete data through a web application programming interface (API)''.
Start a Discussions
A)
B)
Correct : B
The correct answer is Option B, which shows a FlexCard with a header, a body, and a footer. The header contains the title and the icon of the FlexCard. The body contains a Data table element that displays the records from the parent FlexCard. The footer contains a navigation Action that invokes an OmniScript. Option A is incorrect because it shows a FlexCard with only a header and a body, and no footer.
Start a Discussions
A customer sets up to LWC Omniscripts, one embedded into another. Account is set in a Set Values element in the parent Omniscript.
The AccountId set in the parent Omniscript is used to another Set Values element ContextAccountid in the embedded OmniScript. The embedded Omniscript is activated.
While previewing the OmniScript flow from the parent, it is found that Account is set correctly in the parent OmniScript. However. ContextAccountId in the embedded OmniScript is not set with the AccountId from parent Omniscript. On previewing the embedded OmniScript individually, it is found that ContextAccountId is set correctly.
What is the reason for this? Refer to the exhibit below.
Correct : B
The LWC PubSub Message flag in the Set Values action of the parent OmniScript enables the parent OmniScript to send data to the embedded OmniScript using a custom event. If this flag is not set, the data will not be passed to the embedded OmniScript.
Start a Discussions