Form property types

Replaces the default Done button label on tasks with the value of the Name from property field.

The button completes the task and sets its value to true.

This form type only works for user tasks that have no additional forms.

Only accepts boolean: true or false (not case sensitive).

Replaces the default Submit button on a form with the value of the Name from property field.

The button submits the whole form and sets its value to true.

Allows users to select one or more values from a predefined list.

You define the values in the Form values section by entering the Id and the Name for each check-box item.

dynamicCheckbox

Same as checkbox.

You define the values as a map in a variable by providing the Id and the Name for each check-box item: [<Id1>:"<Name1>",<Id2>:"<Name2>",...]. You call the variable in the Form values section by entering dynamicValuesExpression as the Id and the variable as the Name: ${<variable_name>}.

Allows users to select the date or the date and the time form a calendar. Accepts timestamp values in long format.

You define the format in the Form values section by entering dateTimeType as the Id and date or datetime as the Name for each check-box item.

Allows users to select one value from a predefined drop-down list.

You define the values in the Form values section by entering the Id and the Name for each list item.

dynamicEnum

Same as enum.

You define the values as a map in a variable by providing the Id and the Name for each list item: [<Id1>:"<Name1>",<Id2>:"<Name2>",...]. You call the variable in the Form values section by entering dynamicValuesExpression as the Id and the variable as the Name: ${<variable_name>}.

Creates a temporary file and stores the UUID in the variable of the workflow, so that the user can import or attach a file later on in the workflow.

Saves whole numbers. Decimal values are not accepted, they will be truncated to whole numbers.

If you want to enter numbers with decimals, use a string type.

Allows users to enter simple text.

This form type:

• Can hold a maximum of 4,000 characters. If the value could exceed this number, use the textarea form type.
• Is the same as string, except that it has a larger text box, with the same height as text area.

Allows users to select one value from a predefined list.

You define the values in the Form values section by entering the Id and the Name for each list item.

dynamicRadiobox

Same as radiobox.

You define the values as a map in a variable by providing the Id and the Name for each list item: [<Id1>:"<Name1>",<Id2>:"<Name2>",...]. You call the variable in the Form values section by entering dynamicValuesExpression as the Id and the variable as the Name: ${<variable_name>}.

Allows users to enter simple text.

This form type can hold a maximum of 4,000 characters. If the value could exceed this number, use the textarea form type.

Replaces the default View task button label on tasks with the value of the Name from property field.

The button opens the task dialog box and sets its value to true.

This form type only works for user tasks that have additional forms.

Only allows assets as input.

Checks whether the assets that are entered exist.

Only allows communities as input.

Checks whether the communities that are entered exist.

Only allows groups as input.

Checks whether the groups that are entered exist.

Only allows roles as input.

Checks whether the roles that are entered exist.

Displays two side by side input boxes in which users can specify a role and an optional community.

Checks whether the roles and communities that are entered exist.

Only allows users as input.

Checks whether the users that are entered exist.

User accounts that have been disabled are also included in the drop-down list.

Only allows domains as input.

Checks whether the domains that are entered exist.