Force Academy '19: I fell in love with clicks AND code - here's what I learned in relationship therapy

#ForceAcademyLA
I fell in love with
clicks AND code
… here’s what I learned
in relationship therapy

#ForceAcademyLA
Thank you Sponsors!
A big shout out to our sponsors, without them these events would
not be possible:

#ForceAcademyLA#ForceAcademyLA
Hello!
Daniel Stange
Technical Architect
DIA die.interaktiven
Frankfurt (DE) User Group Leader
Found Salesforce boring in the dark ages -
Changed my mind.
You can find me at:
@stangomat
linkedin.com/in/danielstange/
Blog: blog.danielstange.de

• Happy (Solo) Days
• Relationship <3
• Crisis!
• Reconciliation
Agenda

#ForceAcademyLA
“Do not swear by the moon,
for she changes constantly.
then your love would also change.”

#ForceAcademyLA
Solo Admin,
flyin’ solo
1.
HAPPY
DAYS

DEMO
Our session
scenario: Just a plain
org with some basic
“clicks not code”
automations
Place your screenshot here

#ForceAcademyLA
Wouldn‘t it be nice
if it never rained?

Which scenarios
were tested?
There aren‘t any issues, right?
How was it tested?
For which scale
was it built?
Operation Types
Data Volume

#ForceAcademyLA
Admin <3 Dev
kinda…
2.
RELATIONSHIP

• Apex Developers
• AppExchange Packages
• Integrations & Data Loads
• ... and even yourself (yes, that‘s right)
Who‘s in the game?

Scenarios?
Again...
Tests?
Scale? Operations?
Data Volume?
Single record, positive tests from the UI with
an Admin user...

DEMO
A new requirement!
And alas – it needs
some code!

#ForceAcademyLA
“Thus with a kiss I die”

#ForceAcademyLA
„Just don‘t send these
kinds of emails!“
3.
CRISIS

DEMO
Turns out that
declarative and code
don’t live side by
side harmonically…
But why?
And What can we
do?

• „it‘s nothing personal“ indeed:
Exceptions pop up as they happen
• Team up
• Keep documentation (of the system AND of
incidents)
Cope with Anger & Frustration

LIMITS
Bring the attention of your audience over a
key concept using icons or illustrations

#ForceAcademyLA
Everyone shares the same set of limits
Even workflow rules consume governor
limits.
Database interactions, rows...
And CPU time!
KNOW ABOUT THE LIMITS

ORDER
There’s an order to everything that
happens after you saved a record to the
database

Know the „Order of Execution“ by heart
Þ Core explanation for most common problems
Þ Logic may not run (or run more than once)
Þ Data may have changed
Þ Inspect the operation flow in the dev console
using the „Analysis Perspective“

„Order of Execution“ at a glance

RECURSION
Re-Entry into previously executed logic
is sometimes crucial – and sometimes
terribly dangerous

Operations can (and will) run in circles
Recursion is the #1 villain... Really.
Use the recursion flags
for Workflows and
process Builder with care
Map out your operations

SPREAD
A Change in Data can trigger a chain
reaction as it fires logic far away from the
starting point

Operations tend to spread out
Plan automations carefully if they are going to touch
related objects and keep documentation / maps.

The Usual Suspects...
• Rollup Summaries
• Cross Object Workflow Updates
• Implicit Rollups
• (Task to LastActivityDate on Account and WhoId / WhatID)
• DLRS / Rollup Helper

DEMO
Supposedly simple
operations can
consume a massive
amount of your
limits

#ForceAcademyLA
They lived happily
Ever after
4.
RECONCILIATION

CHOOSE
WISELY
Know when to build code,
know when to save the effort

• Avoid PB / Flow for bulk operations
• Use the advantage of the „before“ context in
Triggers
• Use „update records“ action with care if
writing up or down
• Minimize the number of automation types
and stick with one
Rule of thumb: Least complex tool
to do the job

BE
SPECIFIC
For every automation, check for the
conditions to really run the automation

• Leverage entry criteria
• Leverage action criteria in Process Builder
• Check for Changed Fields before running
your logic
Filter for exact scenarios

USE
GATES
Filter away everything
that should not happen

• Use hidden fields to start or bypass
workflows, flows and process builder nodes
Flow Control in Declarative Logic

Static variables to keep track of
• Operation Entry Point
• Executed Units
• Processed Record Ids
• Units to execute (or not)
Advanced stuff: Enterprise Patterns / Unit of
Work
Flow Control in Apex Triggers

DEMO
Use clear entry
conditions and
prevent re-entry

ALLOW
BYPASSES
Once you control your automations, build
ways to bypass your logic

Bypasses let you decide which logic to run next.
• Exceptions from Validations
• Deliberately bypass logic
KNOW WHAT YOU‘RE DOING:
Data Inconsistency Ahead!
Bypasses to manipulate the flow

DEMO
Use a Custom
Permission to
Bypass Validations

DEMO
Use Handler
bypasses in Triggers

The Work Horse:
Kevin O‘Hara‘s Framework:
github.com/kevinohara80/sfdc-trigger-framework
Lightweight & Modern:
MyTriggers: github.com/appero-com/MyTriggers
Full Circle:
Force DI: github.com/afawcett/force-di
Trigger Handler Progression

TEST,
TEST,
TEST… volume, integrations, expected outcome,

DEMO
Example of a test
data insert, update
extract and delete
job.

Thank Y u!
Any questions?
You can find me at:
@stangomat
Daniel.Stange@die-interaktiven.de
linkedin.com/in/danielstange/
Blog post / source code to come
blog.danielstange.de and github.com/dstdia

Force Academy '19: I fell in love with clicks AND code - here's what I learned in relationship therapy

More Related Content

What's hot

Similar to Force Academy '19: I fell in love with clicks AND code - here's what I learned in relationship therapy

Recently uploaded

Force Academy '19: I fell in love with clicks AND code - here's what I learned in relationship therapy