68 Flow Steps Someone Else Wrote: Who Approves?

What Happens on Screen

This film has background music and on-screen captions, no voice-over. This is what it shows, in order.

1. 0:00

   Opening, the answer first: the panel shows the approval is a single Ask For Approval step, and the App Engine Admins group approves. On screen: “It traces the approvals and tells you who signs off”.

2. 0:08

   Title card: TorchTiger Engineer.

3. 0:10

   Workflow Studio, where Flow Designer flows are built, shows the flow “Application Intake Request V2”. On screen: “68 steps. Somebody else wrote it.”

4. 0:17

   The developer asks: “Walk me through what the flow Application Intake Request V2 does, and how it decides who approves.”

5. 0:24

   On screen: “Ask what it does”. The panel looks up the flow and traces its trigger, logic steps and actions. Personal data it detects in the records it reads is redacted before they are sent.

6. 0:34

   The answer: the approval is a single Ask For Approval step (step 49) on sc_request, the Request table. It doesn't approve against a named person.

7. 0:42

   The approver is the group looked up in step 3. On this instance that is the App Engine Admins group, so its current members approve. On screen: “It traces the approvals and tells you who signs off”.

8. 0:48

   The developer gives it a requirement: “I need it to escalate if nobody picks a permission type within 3 days. What exactly do I change?” On screen: “Now give it the requirement”.

9. 0:52

   The panel first pins down where in the flow the permission type is chosen.

10. 0:58

    It recommends a due date, cancel and re-ask pattern for the escalation. It says it can't safely make these edits through its write tools, because they would bypass the flow compiler.

11. 1:03

    It offers to prepare the supporting records instead. On screen: “It catches the trap first, then shows the safe path”.

12. 1:06

    End card: TorchTiger Engineer, Free Community Edition, torchtiger.com.