Workflow/Process Automation

Question 1

Workflow Rules (Order)

Answer 1

-Before Triggers
-Validation Rules
-Duplicate Rules
-After Triggers
-Assignment Rules
-Auto Response Rules
-Workflow Rules
-Escalation Rules
-Entitlement Rules
-Update Parent Rollup Summary
-Save Records

Barbie’s Vagina Duplicates After Assholes Automatically Windup Eating Everything in the U S

Question 2

Action Types Workflow Rules

Answer 2

-Field Updates
-Task Creation
-Email Alert
-Outbound Messages

Fast Tigers Eat Oranges

Question 3

Schedule-Triggered Flow

Answer 3

-Can be configured to start on a specified date/time (once, daily, weekly)

Question 4

Process Builder

Answer 4

-cannot be used to invoke autolaunched flows in scheduled intervals or timings
-executes whenever records get created or edited
-outbound messages can’t be sent
-controls order of different actions but can’t launch a process depending on another process

Question 5

Flow (go with it)

Answer 5

-not bound to any one object
-can look up, create, update and delete records for multiple objects
-can provide screens to guide users through your business process (aka the actors – they want center stage, want you to see them work)
-build flows using Flow Builder (point and click tool)
-can automatically submit records for approval
-you cannot move Flows between objects or delete a Flow.

Question 6

Workflow

Answer 6

-main container for set of workflow instructions and has two components
1. Criteria: what must be true of record for workflow rule to execute associated actions ; always tied to one object
2. Actions: what to do when record meets criteria
-hard workers –> behind the scene (aka the stage hands)

Question 6

Workflow

Answer 6

-main container for set of workflow instructions and has two components
1. Criteria: what must be true of record for workflow rule to execute associated actions ; always tied to one object
2. Actions: what to do when record meets criteria
-hard workers –> behind the scene (aka the stage hands)
-time-dependent workflow actions cannot be added to an active workflow rule ; needs to be deactivated first

Question 7

Record triggered flow

Answer 7

-entry condition requirements can be specified either as :
1. combo of field value comparisons (ALL conditions are met, ANY condition is met, custom conditions logic is met) or
2. formula evaluation (ex: formula evaluates to true)
NOT both at the same time
-support scheduled paths that can be configured to be run at a scheduled time (it’s a little path that kicks in if record is (ex:) 10 days old and then can fire off an email because of this)

Question 8

Governor Limits

Answer 8

Examples:
-total number of SOQL Queries per Transaction
-total number of DML Statements issues per Transaction

Question 9

Types of Flows

Answer 9

1. Screen Flow
2. Schedule-Triggered Flow
3. Autolaunched Flow (No Trigger)
4. Record-Triggered Flow
5. Platform Event-Triggered Flow

Question 10

Debug

Answer 10

-enables you to enter values for input variables and will display debug details
-buttons : run, debug, deactivate, save as, save
-admin can skip starting condition requirements
-“run flow as another user”
-“run flow as if record is” to run flow as if record is created or updated
-can enable rollback
-fault connector - where we want the flow to go if there’s an error

Question 11

Flow Error Process

Answer 11

-sends email to Admin with link to Flow Builder
-no email sent when:
-flow installed as part of a managed package
-failure occurs after flow interview is paused, then resumed at least once
-error is handled because the element that encounters the error is connected to a fault connector
-failure occurs during apex test method
-flow is a standard flow
-value of flow’s metadata field status is Draft, or InvalidDraft

Question 12

System Context

Answer 12

-either system context or user context for flows
-can run system :
1. without sharing : ignores all security perms
2. with sharing : enforces record level access on flow

Question 13

Flow Elements Tab

Answer 13

1. Interactions : screen, action, subflow
2. Logic : decisions, assignments, loops
3. Data : create, update, delete

Question 14

Interactions Elements

Answer 14

1. Screen: allows you to present screen to the user. Displays info from data your Flow is working on, or can be used to collect info from the user
2. Action: allows you to pass data through to a pre-existing standard or custom action such as Send Email, a Quick Create, or custom Apex action
3. Sub-flow: allows users to call a Flow from within a Flow. Makes maintenance easier as you only need to update your logic once, if implemented effectively

Question 15

Logic Elements

Answer 15

1. Decisions: allow you to split your Flow depending on data that’s being sent through it
2. Assignments: allow you to give a value to a variable
3. Loops: allows you to handle multiple variables at once using collections

Collection Sort: sort items in a collection
Pause Element: pauses the flow

Question 16

Data Elements

Answer 16

Create
Update
Get
Delete

Question 17

Resources

Answer 17

1. Variables
   -used to store data in flow
   -text, number, record, dates, currency, boolean, picklists
   -collection variables can hold multiple variables for multiple records that are same data type
2. Collections
   -group, or ‘list’ of variables stored together
   -allow you to process multiple records at once, or ‘bulkify’ your Flows
3. Formulae
   -display dynamic value depending on other values within Flow
   -if you need to calculate a future date based on when Flow was run, Formula will be helpful
   -if you need to calculate and set a currency based on interest rate, Formula can be used
4. Choices
   -used within screen elements to display an option to user