What Is the Difference Between a Start Task and a Standard Task?

Two types of human task activities can be used in a process: a start task or a standard task. In short, a start task is used only when a task form is the first activity in a process. A standard task is used for every other type of form.

This topic provides the complete list of differences between a start task and a standard task.

Start Task

Use a Start Task activity only if this is the first activity in your process. If you have other activities before the form, use the eForms Standard Task or External Forms Standard Task.

• A start task is a form that starts a process.

  A start task is sometimes referred to as a "submit step" or "submit form."

• A start task must be the first activity in a process. If a system activity starts the process, the process can not include a start task.
• A start task uses either a eForms Standard Task activity or a eForms Start Task activity.
• The default participant is set to Process Initiator.
  • If permission groups are enabled, only the members of the App Initiators permission group can start the app.
  • If permission groups are not enabled for the app, any user with the Initiate A Process access right can start the app.
• Start Task can be saved as a draft and edited before it is submitted.

  For more information, refer to, (External) Save Multiple Drafts For Submit eForm.

• The Auto Complete activity property is always set to True. This means the first time a task is entered at runtime, it is automatically marked as Completed.
• The Submit Step activity property is always set to True. This means that the activity starts the process.

Standard Task

Use a Standard Task activity only if you do not want the form to start the process. If you want your form to start the process, use the Start Task (eForms) activity or Start Task (External Forms) activity.

• A standard task is used for tasks that occur after the process has started.

  This means that any form that is not the first activity in a process must use a standard task activity.

• A standard task can use either a eForms Standard Task activity or a External Forms Standard Task activity.
• Any participant who has permissions as a runtime app user for the app can be configured as a participant for a standard task. There is no default participant.
• The Auto Complete activity property is set to False by default. This means the first time a task is entered at runtime, it is not automatically marked as Completed.
• The Submit Step activity property is always set to False. This means that the activity can not start the process.
• A standard task can not be saved as a draft.