Build and Publish a Process
Use this guide when you are building or revising a process.
Start with the workflow outcome
Before you touch the editor, answer:
- What business event starts this workflow?
- What data must be captured?
- What decisions or approvals must happen?
- What should happen at the end?
If you cannot answer those clearly, the build will drift.
Choose the right starting pattern
Nawfe supports multiple start styles in the product, including:
- manual starts
- schedules
- embedded forms
- webhooks
- email-based starts
Choose the simplest start that matches the business need.
Build the smallest complete version
For a first usable draft:
- define the trigger
- add the minimum required form data
- add the core actions or approvals
- review the end state
- remove anything ornamental
Use form design carefully
The form builder should make the workflow easier to run, not harder.
Use form fields that:
- support a real decision
- support reporting or audit needs
- prevent rework later in the process
Avoid fields that no one reads or uses.
If a field exists only because someone might want it one day, it usually should not be there yet.
A serious process does not need to feel like paperwork in a new outfit.
Publish with intent
Publishing is the line between design work and live behavior.
Before you publish:
- check the start path
- check required data
- check approvers and owners
- check any connected dependencies
- check that the workflow name will make sense to end users
After publishing
Once live, measure whether the process:
- reduces confusion
- lowers turnaround time
- improves handoffs
- increases compliance confidence
- makes status visible