OmniScript Developer Exam (WI22)

Question

A developer is troubleshooting an Integration Procedure with two elements: A Remote Action named FetchCart and a Response Action named ResponseCart. In Preview, what JSON node shows the data sent to the Response Action?

Answer 1

FetchCartDebug

Answer 2

ResponseCartDebug

Answer 3

ResponseCart

Answer 4

12.99,13.99

Answer 5

The row is deleted only in Version 3

Answer 6

The row is deleted In Versions 2 and 3 but will remain in Version 1

Answer 7

The row is deleted in Version 3 and Version 1

Answer 8

The row is deleted in all versions

Answer 9

The field is null 0 the Salesforce record.

Answer 10

{recordld} us misspelled in the Data Source Input Map.

Answer 11

There are no test parameters configured.

Answer 12

The fields have exceeded the maximum number allowed on the card.

Answer 13

%HTTPGetDetails:CaseData%

Answer 14

%DRXformCaseData: CaseData%

Answer 15

Answer 16

Answer 17

{Params.records}

Answer 18

{records{0}}

Answer 19

{recordId}

Answer 20

The new Integration Procedure will replace the existing one.

Answer 21

The new Integration Procedure will be used independently.

Answer 22

The new Integration Procedure is Chainable.

Answer 23

The new Integration Procedure uses a Cache Block.

Answer 24

Set the Timeout property on the HTTP Action in the Integration Procedure.

Answer 25

Configure a Remote action with timeout settings of 120000

Answer 26

Check the Chainable checkbox on the integration procedure Action in the OmniScript.

Answer 27

Check the Chain on Step Check on the HTTP Action in the Integration Procedure.

Answer 28

Check the Send Only Additional Input checkbox, and add the following/ value pairs to Additional: AccountId: %Accountd% ProductId: %Details:ProductId%

Answer 29

Check the DataRaptor Transform checkbox, and add the following Key/Value pairs to Output JSON Path: AccountId: %Accountd% ProductId: %Details:ProductId%

Answer 30

Add the following to Send JSON Path: AccountId: %Accountd%, ProductId: %Details:ProductId%

Answer 31

Set Return Only Additional Output to true, and add the following Key/Value pairs to Additional Input: AccountId: %Accountd% ProductId: %Details:ProductId%

Answer 32

SetValuesContactDetails should have been added to Additional input of DataRaptor Post Action in Integration Procedure

Answer 33

The Set values Action Keys should include the DataRaptor Post Action element name path, e,g LoadContactDetails, LastName

Answer 34

The DataRaptor Post Action in the integration procedure should have been executed before the Set Values Action

Answer 35

The valid field names should be added in the Domain object field in the DataRaptor

Answer 36

Use a Datatable element

Answer 37

Set the class’’ collapsible’’ on the block element

Answer 38

Set the collapsible property on the block element

Answer 39

Use a conditional FlexCard State

Answer 40

Navigate Action

Answer 41

DataRaptor Extract Action

Answer 42

Remote Action

Answer 43

Response Action

Answer 44

Relationship Query

Answer 45

Linked Mapping

Answer 46

Lookup Mapping

Answer 47

Lookup Key

Answer 48

A DataRaptor Load Action

Answer 49

A DataRaptor Extract Action

Answer 50

A Lookup Input Element

Answer 51

A DataRaptor Post Action

Answer 52

DataRaptor Transform

Answer 53

DataRaptor Extract

Answer 54

DataRaptor Load

Answer 55

DataRaptor Turbo Extract

Answer 56

DataRaptor Extract Action

Answer 57

REST API Action

Answer 58

Navigation Action

Answer 59

SOQL Action

Answer 60

HTTP Action

Answer 61

The new version of the FlexCard will be used in a new Console, and the current version of the FlexCard should remain unchanged.

Answer 62

Another team member is developing new action, fields and styling for the current version of the FlexCard.

Answer 63

The new and current versions will be displayed together on the same target.

Answer 64

All instances of the FlexCard must be updated with the changes.

Answer 65

HTTP Action

Answer 66

DataRaptor Post Action

Answer 67

Use a formula LIST(Contact), and add the output of the formula as the input in the Transform tab.

Answer 68

Set the Input JSON path as List(Contact) and the OutputJSON Path as Contact.

Answer 69

Set the Input JSON Path as Contact the out JSON Path as contact and output Data type as List.

Answer 70

Set the input JSON Path as Contact and the OutPut JSON Path as List (Contact)

Answer 71

Version Number 1

Answer 72

Version Number 2

Answer 73

Version Number 3

Answer 74

Version Number 4

Answer 75

Use a Remote Action that calls the XMLStreamReader class

Answer 76

Use a Remote Action that calls the XMLStreamWriter class

Answer 77

Use a DataRaptor Transform to convert JSON to XML

Answer 78

Use a DataRaptor Extract and check the XML checkbox on the Output JSON Path.

Answer 79

Image1

Image:

22a (binary/octet-stream)

Answer 80

Image2

Image:

22b (binary/octet-stream)

Answer 81

Image3

Image:

22c (binary/octet-stream)

Answer 82

Image4

Image:

22d (binary/octet-stream)

Answer 83

In the Setup Panel, {recordId} is misspelled in the Data Source Input Map.

Answer 84

The field name in the FlexCard state does not match the DataRaptor Extract’s Output JSON Path name.

Answer 85

In the FlexCard state, the Field type for the field does not match the type in the Salesforce record.

Answer 86

There are No test Data test Parameters configured.

Answer 87

In the DataRaptor Output tab, select the Output Data Type of that field to Integer.

Answer 88

In the DataRaptor Output tab, enter the default value as 0 on the field.

Answer 89

In the DataRaptor Extract tab, set the Input Data Type field to Integer.

Answer 90

In the DataRaptor Formula tab, define a formula using the function TOINTEGER and use the formula as output.

Answer 91

Use two separate Calculation Steps with the Conditional Step property selected: use the ISTRUE(isCustomer) and NOT (ISTRUE) (isCustomer) functions in the Condition syntax.

Answer 92

Use two separate Calculation Steps with the Conditional Step property selected: reference just the isCustomer variable in the Conditional syntax (no comparison necessary)

Answer 93

Use two separate Calculation Steps with the Conditional Step property selected: compare the isCustomer variable directly to the literal true and false values in the Condition syntax.

Answer 94

Use a single Calculation Steps with IF statement directly in the formula definition to reference the isCustome variable and conditionally perform the appropriate calculation.

Answer 95

Go to the Lightning Console and reload the page to test.

Answer 96

Go to the PREVIEW tab In OmniScript to test.

Answer 97

Deactivate the card and layout, and go to the PREVIEW tab for the card to test.

Answer 98

Add a key/value pair in the DataRaptor to test it.

Answer 99

"Step1": { "Block1": { "Text1": "Text", "Block2": { "Telephone1": "1234567890", "Checkbox1": false } }, "Block3": { "Multi-select1": "Value A; Value B" } }

Answer 100

"Step1": { "Block1": { "Text1": "Text", "Telephone1": "1234567890", "Block2": { "Checkbox1": false } }, "Block3": { "Multi-select1": "ValueA;ValueB" } }

Answer 101

"Step1": { "Block1": { "Text1": "Text", "Telephone1": "1234567890" }, "Block2": { "Checkbox1": false, "Block3": { "Multi-select1": "Value A;value B" } } }

Answer 102

"Step1": { "Block1": { "Text1": "Text" }, "Block2": { "Telephone1": "1234567890", "Checkbox1": false, "Block3": { "Multi-select1": "Value A;Value B" } } }

Answer 103

Lookup Mode is not selected in the properties of the Type A Head Block.

Answer 104

Use Data JSON is not selected in the properties of the Type Ahead Block.

Answer 105

FirstName, LastName, and BirthDate are not placed inside the Type ahead Block.

Answer 106

The Typeahead key is not in the correct format

Answer 107

{ "Contact": { "Name" : "Leone Tomlin", "CellPhone" : "(2321) 177-66100" }, "CaseSubject" : "Cannot track your order", "CaseNumber" : "00021554" }, { "Contact": { "Name" : "Leone Tomlin", "CellPhone" : "(2321) 177-66100" }, "CaseSubject" : "Billing status", "CaseNumber" : "00021553" } }

Answer 108

{ "Case" : [ { "CaseSubject": "Cannot track your order", "CaseNumber": "00021554" }, { "CaseSubject": "Billing status", "CaseNumber": "00021553" } ], "ContactName" : "Leone Tomlin", "ContactCellPhone" : "(2321) 177-66100" }

Answer 109

{ "BlkCase" : [ { "CaseSubject": "Cannot track your order", "CaseNumber": "00021554" }, { "CaseSubject": "Billing status", "CaseNumber": "00021553" } ], "ContactName" : "Leone Tomlin", "ContactCellPhone" : "(2321) 177-66100" }

Answer 110

{ "Case" : [ { "CaseSubject": "Cannot track your order", "CaseNumber": "00021554" }, { "CaseSubject": "Billing status", "CaseNumber": "00021553" } ], "Contact" : { "Name" : "Leone Tomlin", "CellPhone" : "(2321) 177-66100" } }

Answer 111

Check the Enable Cancel checkbox in the Setup tab under Cancel Options.

Answer 112

Add a navigation Action inside each step and set the Component name to ‘’Cancel’’

Answer 113

Add a navigation Action outside each step and set the Element Name to ‘’Cancel’’

Answer 114

Add a navigation Action inside each step and set the Element Name to ‘’Cancel’’

Answer 115

DocuSign Envelope Action

Answer 116

PDF Action

Answer 117

DocuSign Signature Action

Answer 118

Email Action

Answer 119

Define a formula with the Filter function

Answer 120

Use a Custom Output Type when creating the DataRaptor

Answer 121

Use the LIMIT filter on the Extract definition

Answer 122

Set the Limit Property on the Action that calls the DataRaptor Extract

Answer 123

As an OS Action

Answer 124

As a Custom Action

Answer 125

As an OmniStudio Action

Answer 126

As a Lightning Action

Answer 127

A SOQL Query

Answer 128

A DataRaptor Load

Answer 129

A DataRaptor Extract

Answer 130

A DataRaptor Transform

Answer 131

Add the FlexCard’s API name to FlexCard Player component

Answer 132

Set the Target property in publish Options to Community Page'’

Answer 133

Configure the Component visibility in the custom Component

Answer 134

Set the Developer property in Card Configuration to ‘’Community’’

Answer 135

Script configuration

Answer 136

Community logs

Answer 137

DataRaptor configuration

Answer 138

Action Debugger

Answer 139

Create a Postprocessor apex class to calculate the sum

Answer 140

Add an Aggregation Step as SUM (BasePrice)

Answer 141

Add A Calculation Step as SUM (BasePrice)

Answer 142

Create a Preprocessor class to calculate the sum. It must be included in the calculation output

Answer 143

The first state with the true conditions sequence closest to the top of the FlexCard canvas will display

Answer 144

The first state with true nested condition, regardless of sequence in the FlexCard canvas, will display

Answer 145

The state sequenced first in the FlexCard canvas will display

Answer 146

The first state with a true AND condition, regardless of sequence in the FlexCard canvas, will display

Answer 147

BlockX.BlockY.ActionZ

Answer 148

ActionZ:BlockY:BlockX

Answer 149

ActionZ.BlockY.BlockX

Answer 150

BlockX:BlockY:ActionZ

Answer 151

Use a List Action to merge the array elements together.

Answer 152

Use a Calculation Action to call a Calculation Procedure.

Answer 153

Use a Set Values Element inside a Loop Block.

Answer 154

Use a Matrix Action to call a Calculation Matrix.

Answer 155

Define an extraction step for the Contact object and set the Extract JSON Path to Contact:Account.Name

Answer 156

Define extraction steps for the Contact and the Account objects, and set the Extract JSON Path to Contact.Account.Name

Answer 157

Define extraction steps for the Contact and the Account objects, and set the Extract JSON Path to Account.Name

Answer 158

Define an extraction step for the Account object, and set the Extract JSON Path to Account:Contact.Name

Answer 159

Check the Lookup property when mapping the fields.

Answer 160

Add Link to RecordType object in the Contact Object with the id field of RecordType object.

Answer 161

Select RecordType in the Lookup object list. DeveloperName in the lookup Field list, and ID in the Lookup Requested Field list.

Answer 162

Select RecordType in the Lookup Object list. ID in the Lookup Field list, and DeveloperName in the Lookup requested Field list.

Answer 163

In Procedure Configuration, in a Tracking Custom Data value field.

Answer 164

In a Remote Action, in a Remote Options value field.

Answer 165

In a Remote Action, in an Additional Output value field.

Answer 166

In a Response Action, in an Additional input value field.

Answer 167

Update the ContextId value to specify an id from the Production org.

Answer 168

Add a Show/Hide condition on the Set Values element.

Answer 169

Delete or Deactivate the Set Values element.

Answer 170

Deactivate the contextId key/value pair.

Answer 171

To %%Details:Customer|0:ID%%

Answer 172

To %%Details:Customer|n:ID%

Answer 173

To %Details:Customer|1:ID%

Answer 174

To $Details:Customer|0:ID$

Answer 175

Answer A

Image:

46d (binary/octet-stream)

Answer 176

Answer B

Image:

46a (binary/octet-stream)

Answer 177

Answer C

Image:

46c (binary/octet-stream)

Answer 178

Answer D

Image:

46b (binary/octet-stream)

Answer 179

Copy the Input JSON from the DataRaptor Action Debug node.

Answer 180

Build the Input JSON node by node in an editor.

Answer 181

Copy the Input JSON from the OmniScript {Data} modal.

Answer 182

Build the Input JSON node by node m the DataRaptor Designer.

Answer 183

The DataRaptor Action did not have the add response To Response JSON property set to true.

Answer 184

The Response cannot be previewed directly.

Answer 185

A Response Action was not added to the integration Procedure.

Answer 186

The AccountId used for the preview is invalid.

Answer 187

{postalcode}

Answer 188

{Parent.postalcode}

Answer 189

{Records.postalcode}

Answer 190

{Params.postalcode}

Answer 191

Show element if true

Answer 192

Disable read only if true

Answer 193

Set element to optional if false

Answer 194

Set element to require if true

Answer 195

It populates data in PDF and DocuSign format

Answer 196

It is easier to configure

Answer 197

It has better performance at runtime

Answer 198

It supports complex field mappings

Answer 199

Rich text Area

Answer 200

Text Block

Answer 201

Edit Block

Answer 202

The API url is not allowed in Salesforce.

Answer 203

The Omniscript has no active version.

Answer 204

The Integration Procedure Preview Input Parameters do not match the JSON sent from the OmniScript.

Answer 205

The JSON sent from the Integration Procedure Action does not match any of the Original Input for the Integration Procedure.

Answer 206

The Id Field for Actions in the FlexCard is blank.

Answer 207

There is no active version of the Data Raptor Extract.

Answer 208

There is no active version of the OmniScript.

Answer 209

In the DataRaptor Extract Action, the Input Parameters Filter Value is misspelled.

Answer 210

Use an Edit Block element configured with Remote Actions.

Answer 211

Use an Edit Block element configured with SOQL statements.

Answer 212

Use an Input Block element and a DataRaptor Post Action element.

Answer 213

Use a Text Block element and a Remote Action element.

Answer 214

An OmniScript

Answer 215

An Integration Procedure

Answer 216

A DataRaptor

Answer 217

A Child FlexCard

Answer 218

The LWC PubSub Message flag in the Set Values action of the parent OmniScript has not been set.

Answer 219

The flag passData.JSON in the parent OmniScript in not configured correctly.

Answer 220

A developer failed to include a Navigate Action Element to pass data from the parent OmniScript.

Answer 221

Both parent and embedded OmniScripts have the same element name for the Set Values element.

Answer 222

Enable the record Looping feature on the data table elements

Answer 223

Select the Repeatable Mode property on the data table elements

Answer 224

Enable the Repeat Records feature on the FlexCard Setup tab

Answer 225

Disable the Repeat Record feature on the FlexCard setup tab

Answer 226

Populate the Lookup object and Lookup fields

Answer 227

Check the Upset key and is required for Upsert checkboxes on the Account id field

Answer 228

Check the Upsert key checkbox on the Account Status field

Answer 229

Check Overwrite Target for all Null input checkbox on the Account id field

Answer 230

HTTP Action

Answer 231

DataRaptor Post Action

	Erstellt von Julie Bulakh vor fast 2 Jahre

Nächster

OmniScript Developer Exam (WI22)

Beschreibung

Zusammenfassung der Ressource

Frage 1

Frage 2

Frage 3

Frage 4

Frage 5

Frage 6

Frage 7

Frage 8

Frage 9

Frage 10

Frage 11

Frage 12

Frage 13

Frage 14

Frage 15

Frage 16

Frage 17

Frage 18

Frage 19

Frage 20

Frage 21

Frage 22

Frage 23

Frage 24

Frage 25

Frage 26

Frage 27

Frage 28

Frage 29

Frage 30

Frage 31

Frage 32

Frage 33

Frage 34

Frage 35

Frage 36

Frage 37

Frage 38

Frage 39

Frage 40

Frage 41

Frage 42

Frage 43

Frage 44

Frage 45

Frage 46

Frage 47

Frage 48

Frage 49

Frage 50

Frage 51

Frage 52

Frage 53

Frage 54

Frage 55

Frage 56

Frage 57

Frage 58

Frage 59

Frage 60

ähnlicher Inhalt