ApplySG Portal template
The ApplySG Portal template is the generic starter configuration for applications such as support schemes and regulatory approvals. This page lists its form types, roles and states. It describes the ApplySG Generic Template. You can adapt the workflow by removing the states and roles that you do not need.
Portal capabilities
| Feature | What it does |
|---|---|
| Email OTP | Lets applicants sign in with an email address and a one-time password, without Singpass. Refer to Log in with email OTP. |
| Listings URL filtering | Filters the scheme listing page through URL parameters such as ?schemes[]=<RESOURCE_ID> or ?agencies[]=<AGENCY_CODE>. Refer to Filter the open listing by URL. |
For the sign-in methods, refer to Login methods.
Form types
| Form type | Kind |
|---|---|
| Application | Parent |
| Progress Report | Child |
You can add custom child form types. Refer to Manage form types.
The first submission in a lifecycle is the Request. Child submissions update the application data when they reach the Approved state, so the Application always holds the latest data.
Form roles
The template includes 12 predefined roles for each scheme. You can change them at any time.
| Form role | Can do |
|---|---|
| Clerical Officer (CO) | View submissions. Accept a submission from the unassigned pool. Return for edit. Reassign submissions. |
| Processing Officer (PO) | View submissions. Make a recommendation and upload letters to the applicant. Return for edit. Reassign submissions. |
| Supporting Officer (SO), optional | View submissions. Reassign submissions. |
| Approving Officer (AO) | View submissions. Approve a recommendation. Reassign submissions. |
| Viewer | View submissions. |
Approving Officers can have an approving limit on Application forms. If the limit is empty, the officer has no limit and can approve any amount. The list of eligible Approving Officers for routing depends on the submission’s approved amount.
States
States show where a submission is in the workflow. Applicants may see different state names from officers.
Application
| Applicant state | Backoffice state |
|---|---|
| Draft | Draft |
| Submitted | Submitted |
| Processing | Pending CO, PO, SO or AO |
| Approved | Approved |
| Rejected | Rejected |
| Pending Resubmission | Pending Resubmission |
| Closed | Closed |
| Cancelled | Cancelled |
Progress Report
| Applicant state | Backoffice state |
|---|---|
| Draft | Draft |
| Submitted | Submitted |
| Processing | Pending CO, PO, SO or AO |
| Approved | Approved |
| Rejected | Rejected |
| Pending Resubmission | Pending Resubmission |
| Cancelled | Cancelled |
Segregation of duties
Scheme owners who administer public schemes should separate duties. Evaluation and approval should be done by different officers, so a Processing Officer should not also be an Approving Officer. Officers who hold the Manage Permissions scheme permission should not also hold a processing role. Refer to Scheme permissions.
Constraints and limitations
| Constraint | Detail |
|---|---|
| Template | This page applies to the ApplySG Generic Template only. The portal also supports a starter template. |
| Custom child forms | Custom child form types are available. Refer to Manage form types. |
| Pre-built logic | Some states and edges carry pre-built logic. Refer to Workflow template behaviours. |
Related content
- ApplySG Portal backoffice: how officers process submissions.
- Dashboards: what the dashboards show.
