Glossary

This glossary defines the terms that ApplySG documentation uses in a product-specific way. Each entry is short and links to the page that explains the concept. Terms are in alphabetical order.

Actor

A person or a system that takes part in a submission’s workflow, such as an officer or an integrator. Form roles list the actors who are involved in a form’s workflow.

Applicant

A person or organisation that submits an application on a portal. Refer to Applicant roles.

Child form

A form whose submissions relate to a parent submission, such as a claim or a progress report. Refer to Parent and child forms.

Component

One field or content block on a form, such as a text field or a date. Refer to Add components to a form.

Configurator

A backoffice user who builds and maintains a scheme: its settings, forms, workflow, roles and automations.

Edge

A route that a submission takes from one state to another in a workflow. Refer to Add and edit edges.

Form role

A scheme role that you link to one form, so that the role can act on that form. Refer to Add form roles.

Integrator

A system that acts on a user’s behalf through the ApplySG APIs. Integrators can hold only the View and Invite scheme permissions. Refer to Scheme permissions.

Lifecycle

The configured set of forms, workflow, roles and permissions of a scheme. The term appears in role codes, in scheme permissions and in the API. Refer to Schemes and workflows.

Parent form

The first form type in a scheme, such as an application. Child forms relate to it. Refer to Parent and child forms.

Request

The first submission in a lifecycle, the parent submission. Child submissions can update it, so applicants and officers always see the latest data in one place. This is a product term, not an everyday request.

Role

A responsibility that people or systems hold in a scheme’s workflow, such as processing officer. Refer to Manage scheme roles.

Scheme

One use case or business process, with its own workflow, configuration and permissions. A scheme usually has one application form and its related child forms. Refer to Schemes and workflows.

State

One stage that a submission goes through in a workflow, from start to end. Refer to Add and edit states.

Stub account

A test account that lets you sign in to the staging applicant portal. Stub accounts work in staging only. Refer to Create a stub applicant account.

Submission

One application or form entry that is created on a scheme. A submission moves through the states of its workflow.

Version

A duplicate of a parent form and its child forms, with their configuration. Only the latest published version accepts new submissions. Refer to Form versions.

Workflow

The states of a form, the edges between them and the roles that act on them. It sets how a submission is processed. Refer to Schemes and workflows.