PLATFORM / PROCESS DESIGN
Make business processes explicit. Keep execution consistent.
A process definition describes how a business record moves through people, decisions and automated steps. WorkflowRight turns that definition into work that can be assigned, completed and operated over time.
- 01Start
- 02Manual task
- 03Exclusive decision
- 04Action / Timer
- 05Completion
01 / PROCESS DESIGNER
Describe the path from request to outcome
Begin with the business record and the event or person that starts the process. Place manual tasks where someone must review information or make a decision. Use exclusive decisions to choose a supported route based on business conditions, and structured actions to perform defined operations.
Timers represent a deliberate wait before execution continues. A visible process makes the handoffs understandable: which information is required, who acts next and how the instance reaches completion. This is a definition of operational responsibility, not just a drawing.
02 / PROCESS DESIGNER
Publish a definition that running work can rely on
Design changes are separate from published execution. Publication creates an immutable version, and each running instance stays associated with its published definition. A later edit does not silently replace the steps of work already in progress.
Task forms and their published versions belong in this review. Check the information people will see, the values they can provide and the decisions that use those values before publishing the process. Version preservation makes change something a process owner can reason about.
03 / PROCESS DESIGNER
Operate the process after publication
A manual task becomes work for authorized people, with assignments and candidate access handled through the work experience. Automated execution produces operational state and history. When a supported automated step fails, incidents and controlled retry behavior provide a route to investigation.
For evaluation, choose a process with a clear entry point and outcome. Walk through its normal route, a decision alternative and a wait or failure. Review the instance history alongside the work queue rather than judging only the design canvas.
- Identify the record and starting conditions.
- Review task responsibility and form versions.
- Check decision conditions and supported routing.
- Publish, execute and inspect the resulting work.
EVALUATE WITH YOUR BUSINESS CONTEXT
Bring a real process.
Review how it should operate.
Discuss the information, responsibilities and controls your organization needs.