Process Start Form

The process start form tab within process model properties can be configured to show a form to a user when starting the process. Data collected on the start form must be saved into process parameters.

Configuring the Process Start Form Tab

Besides some key differences, configuring a process start form is identical to configuring the Forms tab of an attended node or smart service. In this section we will talk about those key differences. If you want to learn how to use the Select an interface, Create Interface, or Write an expression options, please read the Ways of Setting up Forms section of the Forms Tab page.

Process Parameters

The process technically has not started while a user is filling out a start form. It only starts after the user submits the form. Because of this, there is no concept of an activity class parameter, which is only available when there is an active node or smart service. Process parameters are simply process variables with the Parameter checkbox selected.

By defining a process variable as a parameter, you are allowing the value to be provided to the process before kicking off the processes start event. Take a look at the process history below and notice that the variable change occurred before the start event was activated.

If you want to collect data from a process start form, you must use process parameters. In fact, process parameters are the only options available as values for rule inputs in the grid displayed on the Process start Form tab.

Cannot Save a Draft of In-Progress Tasks

On attended nodes, such as a user input task there is a checkbox at the bottom of the forms tab. This feature allows users to save a draft of their progress and come back to the form later. Since no activities have started yet, this option is not available on start forms.

Other Considerations

Offline Mobile Start Forms

Offline Mobile forms must be configured as a start form. To make an action available to users when they are offline, refer to Configuring a Start Form for Offline Use

Start Form vs. Chained User Input Task

A start form that is used as an action or related action will appear immediately after clicking on that particular action.

This behavior can be mimicked by activity-chaining the Start Event to the first attended task (such as a User Input task) and then configuring that task to the process initiator. This way, you can map the fields of a form to a single variable using a custom data type.

Generally speaking, process models that require a user interaction first should be configured with a process start form. Activity-chained tasks are useful when something needs to happen between kicking off the process and the user seeing the form.

Save As Application Action

The interface designer has a feature to save the interface as a report or application action. This provides an easy way of starting your process model development when you are designing your forms as a first step. When this feature is used, it will:

  1. Create a Process Model.
  2. Create a process parameter for every rule input.
  3. Use that interface as a process start form.
  4. Map the rule inputs to process parameters.


One of the page types that can be configured in a Site is an Action. Only process models that have a start form will appear as an available action.

See Also

To learn more about configuring process variable, please see the Configuring Process Variables

To try and build a process start form for yourself, use the Process Model Tutorial to help you walk though creating one.