Case story · Automation

One field. Three writers.

How a mid-sized B2B company took a field with several writers down to one.

Download the PDFAll case stories
Flow
Writes the field
Workflow Rule
Writes the field
Apex trigger
Writes the field
Field
Discount
Value on the record
?
The last one to run wins
Three automations, one field
Nobody can say which value is right

The situation

A mid-sized B2B company had years of automation. A Flow, an old Workflow Rule and an Apex trigger all wrote the same field.

The last one to run won, so nobody could say which value was right.

How we work

One field. One owner.

1
Map it
Every automation that writes the field
2
Find the overlap
Where two or more collide
3
Decide one owner
One writer for each field
4
Change safely
Retire the rest in tested steps

You keep the map and the findings either way.

What changed

One writer
Several writers, now one

From our client work

Try it this week

Check your fields.

Pick a field people argue about. List everything that writes it.

Flows
Count them
+
Old rules
Count them
+
Code
Count them

More than one writer? Name one owner.

The Org Review

We untangle automation, old rules and code. Quote-to-cash is our specialty.
$3,500
USD, from, fixed fee
  • Agreed before work starts
  • You keep the findings either way
Talk to usDownload the PDF