Scope includes Workflows and Process Builders
Why the need to review Flows?
There is currently > 250 active flows in the Jarvis Org
Here are some high level stats:
Area | ||
|---|---|---|
| 1 | TAP | 131 (18) |
| 2 | WB | 60 ( |
| 3 | Hogwarts | 45 |
| 4 | ASOP | 13 |
| 5 | All | 250 |
Real life examples:
Add link to tickets if that is easy
How are we approaching this challenge/technical debt?
We will work to build a consensus about what the problem is and the need to take action to address it.
We will standardize and simplify and reduce the number of flows across the Org
Best practices to consider:
2-3 Flows per Object. No More
Guiding principles:
Link to the page Yeng has created
Troubleshooting of Flows:
USYD Error Log for the recent Flows