What is the difference between a form and a workflow?+
A form collects structured information; a workflow defines what happens next. Connecting them turns a submission into assigned tasks, decisions and a recorded outcome rather than leaving someone to coordinate the response manually.
What should a business form include?+
Include the information needed to understand the submission and decide the next step. Use clear questions, helpful instructions and relevant attachments, and avoid asking for information that has no purpose in the process. An incident report, request or review form should collect the details its process needs.
How should a workflow handle decisions and missing information?+
Give each decision a clear owner and an explicit route for each outcome. Include a way to request more information, so an incomplete submission can return for clarification instead of becoming an unresolved task.
Who should own a form and its workflow?+
The process owner should be responsible for the questions, routing and intended outcome. Individual tasks also need named assignees and clear instructions, so responsibility remains visible as work moves between people.
How should changes to an active workflow be managed?+
Review changes in a draft and check the tasks, assignees and decision routes before publishing. Keep a record of which version each execution uses. Apollo keeps existing executions on their original version when a revised workflow is published.