Process Automation & Logic: Declarative Features 2

Question 1

<blank> can be invoked from Process Builder to add custom functionality to a process.
</blank>

Answer 1

Apex code

Question 2

An Apex action can be created and added to the process to invoke Apex code. True or False?

Answer 2

True

Question 3

<blank> with appropriate annotation can be used to invoke the methods in an Apex class.
</blank>

Answer 3

Invocable methods

Question 4

An Apex action is defined with an <blank> and <blank> for adding Apex code functionality to a process.</blank></blank>

Answer 4

Action Name, Apex Class

Question 5

The <blank> annotation is used in Apex classes to identify methods that can be run as invocable actions. Invocable methods must be static and either public or global.</blank>

Answer 5

@InvocableMethod

Question 6

What is a limitation to having an invocable method in an apex class?

Answer 6

Only a single method in an Apex class can have the @InvocableMethod annotation, and other annotations cannot be used with it.

Question 7

What is a limitation of an invocable method itself?

Answer 7

An invocable method can have at most one input parameter, and the @InvocableVariable annotation can be used to identify class variables used as input or output parameter.

Question 8

Annotation attributes <blank> and <blank> are supported by invocable methods and variables.</blank></blank>

Answer 8

‘label‘, ’description‘

Question 9

Invocable variables also support the <blank> modifier which specifies whether the variable is required and adds a prompt in the UI.</blank>

Answer 9

‘required‘

Question 10

An Apex method can be invoked from a process using the <blank>.</blank>

Answer 10

Apex action type

Question 11

Apex code can be called from a flow using one of two flow elements:

Answer 11

Apex Plug-in and Call Apex.

Question 12

The <blank> interface or the @InvocableMethod annotation can be used to invoke Apex from a flow.</blank>

Answer 12

Process.Plugin

Question 13

Bulk operations are supported by @InvocableMethod annotation but not Process.Plugin interface. True or False?

Answer 13

True

Question 14

Classes that implement the Process.Plugin interface will only be available to flows. True or False?

Answer 14

True

Question 15

Classes with the @InvocableMethod annotation will be available to <blank></blank>

Answer 15

flows, processes, and the REST API.

Question 16

Values can be passed into Apex-defined variables when a flow is launched from a <blank></blank>

Answer 16

Subflow element, a Visualforce page, or as an action.

Question 17

If a screen flow executes an invocable method that performs a callout, the <blank> attribute can be added to the annotation. This enables the screen flow to avoid callout errors when the flow also executes DML operations.</blank>

Answer 17

callout=true

Question 18

What does the Process.Plugin Interface do?

Answer 18

The built-in Process.Plugin interface allows one to process data and pass it to a flow.

Question 19

The interface exposes the Apex class as a <blank> that accepts input values and returns output back to the flow.</blank>

Answer 19

service

Question 20

What are the unsupported data types of the Process.Plugin interface?

Answer 20

Blob, Collection, sObject, and Time data types are not supported by Process.Plugin.

Question 21

The Process.Plugin Interface supports what 3 top level classes?

Answer 21

Process.PluginRequest Class
Process.PluginResult Class
Process.PluginDescribeResult Class

Question 22

What does the Process.PluginRequest Class do?

Answer 22

Passes input parameters to the flow

Question 23

What does the Process.PluginResult Class do?

Answer 23

Returns output parameters from the class

Question 24

What does the Process.PluginDescribeResult Class do?

Answer 24

Passes input parameters from the flow to the class

Question 25

Salesforce recommends using @InvocableMethod annotation instead of the Process.Plugin interface, True or False?

Answer 25

True

Question 26

An Apex class that implements the Process.Plugin interface can be used as an action in a flow. True or False?

Answer 26

True

Question 27

How can a flow be called from Apex Code?

Answer 27

A flow can be called from Apex code using the Flow.Interview system class.

Question 28

The method of the Flow.Interview class can be used to launch an autolaunched flow or user provisioning flow from Apex.

Answer 28

start

Question 29

The getVariableValue method can be used to return the value of the specified flow variable. True or False?

Answer 29

True

Question 30

Does the start method have a return type?

Answer 30

The start method does not have a return type while the getVariableValue method has the return type of Object.

Question 31

In order for Apex code to successfully call a flow, the status of the flow must be .

Answer 31

active

Question 32

How can a flow be called from apex dynamically?

Answer 32

A flow can be called from Apex dynamically. Meaning, the flow is not fixed or hardcoded in Apex, which allows the flow to invoke to be determined only at run-time.

Question 33

Invocable methods and invocable variables support generic and data types.

Answer 33

sObject, List

Question 34

Support for enables an Apex action to be reused across multiple types of objects.

Answer 34

sObject data types

Question 35

When an Apex class is used as an input or output parameter for an invocable method, the class member variables that need to be available to the method should be annotated with

Answer 35

@InvocableVariable

Question 36

A flow can be referenced in Apex by defining the flow using the syntax.

Answer 36

Flow.Interview.flowName

Question 37

A flow interview can also be created dynamically at run-time using a method.

Answer 37

Flow.Interview

Question 38

The method of the Interview class can be used to start a flow from Apex dynamically.

Answer 38

createInterview()