Reusable Workflow Recipes
Business problem
Section titled “Business problem”A reusable recipe should explain a business need before asking someone to configure a workflow.
Result
Section titled “Result”A documented, reproducible workflow with verified actions, known inputs and outputs, and acceptance checks.
Workflow diagram
Section titled “Workflow diagram”Each specific recipe includes a textual diagram. Its stages express business intent until the real action sequence is confirmed.
Actions used
Section titled “Actions used”Use the exact catalog names only after implementation review. Link to verified action references.
1Record the approved context
Define the account, site, library, access owner, and Drive ID map.
2Choose and test the available actions
Check input formats, output mapping, permission requirements, and behavior on repeated runs.
3Record the accepted outcome
Compare the test result with the expected business result and document failure handling.
Example values
Section titled “Example values”Use fictional names and non-sensitive test resources. Do not use real customer data or secret values as examples.
Final outcome
Section titled “Final outcome”A recipe becomes a tested procedure only after its action sequence and observed results are recorded for a known product version.