Schemes and workflows
A scheme is one use case or business process in ApplySG. It has its own forms, workflow, roles and permissions, and it runs independently of other schemes. A workflow is the path that a submission takes through a scheme, from the first state to the last. This page explains how the parts of a scheme fit together.
What a scheme contains
A scheme typically has one application form and its related child forms, such as claims, progress reports or change requests. Behind the forms, the scheme holds the people and rules that act on them.
| Part | What it is |
|---|---|
| Settings | The scheme’s type, name, dates and contacts. |
| Forms | The fields that applicants fill in, built from components. |
| States and edges | The stages of the workflow and the routes between them. |
| Roles and form roles | The responsibilities that people hold, linked to each form. |
| Permissions | Rules for who can view, edit, route or delete, at each state. |
| Automations | Actions that run when a submission is created, updated or moved. |
How a workflow moves a submission
A form combines the fields that collect data with the steps that process it. The components are the fields. The states and edges are the steps of the process and the routes between them. A state is one step. An edge is a transition from one state to another, and it can carry settings such as emails, logic and validation.
The diagram shows a simplified review workflow, drawn from the ApplySG Portal template. A submission starts in Draft and moves to Submitted when the applicant submits. It is checked out to a clerical officer, who routes it to a processing officer. The processing officer can return it to the applicant, which moves it to Pending Resubmission, or route it to an approving officer. The approving officer can move it to Approved. The labels on edges are the action names that officers see in the template.
A submission is created in the initial state. A user then performs a transit action by selecting an edge, and the submission moves to the state at the other end of the edge.
Who can do what
Three layers of permission decide what a person can do.
| Layer | What it controls |
|---|---|
| Scheme permissions | Who can configure the scheme and which parts. |
| Form permissions and edge permissions | What a form role can do with a submission in each state, and which routes it can take. |
| Component permissions | What a form role can do with each field in each state. |
A role must be linked to a form before it can act on that form. New roles and new states start with no component access.
Related content
- Tutorials: Set up your scheme, Build your workflow: roles, states and form permissions.
- How-To guides: Add and edit states, Add and edit edges.
- Reference: Scheme permissions, Workflow template behaviours.