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)
Answer(s): 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.
A developer has a requirement to create a child FlexCard that contains all of its parent FlexCard's records In a Datable How should the developer configure the parent FlexCard's Node?
Answer(s): B
The Node field for the parent FlexCard should be set to {Records}, which is an array of all the records retrieved by the parent FlexCard data source. This will allow the child FlexCard to access the records and display them in a DataTable.
Which two in an integration Procedure or DataRaptor can execute a function like CONCAT or DATEDIFF?Choose 2 answers
Answer(s): A,D
A Set Values Action in a Value field and a Remote Action in an Additional Output value field can execute a function like CONCAT or DATEDIFF by using the syntax {{function(parameters)}}. For example, {{CONCAT(`Hello', `World')}} or {{DATEDIFF(`2021-01-01', `2021-01-31')}}.
An integration procedure contains a Remote Action element that calls a method of an APEX class. The method requires two fields are input: Account id and Product Id. The integration Procedure data JSON contains the following nodes:How should the Remote Action element be configured to pass the data correctly to the method?
Answer(s): A
Checking the Send Only Additional Input checkbox allows the Remote Action element to send only the key/value pairs specified in Additional input to the Apex method. The Additional input should have the same keys as the method parameters, and the values should be set to {{InputData.node}} for each node. For example, AccountId: {{InputData.AccountId}} and ProductId:{{InputData.Details.Products}}.
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.
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.
Post your Comments and Discuss Salesforce Plat-Dev-210 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Plat-Dev-210 content, but please register or login to continue.