File Picker Form Element

Type: String

Name in Properties Panel: Accessible Description

Name to Use in Expressions: accessibleDescription

An accessible version of the description of the element. The accesible description is not visible on the page; it is hidden.

You can use the Accessible Description property to provide a description that can be used by assistive technologies, such as screen readers.

Type: String

Name in Properties Panel: Button Label

Name to Use in Expressions: prompt

The text that appears on the button that the user clicks to select a file. The default text is Add File.

You can format the button's label using Markdown.

Type: String

Name in Properties Panel: Description

Name to Use in Expressions: description

A description of the element. The description appears below the element's title.

You can use the Description property to describe what the element represents or to provide instructions to the user about how to use the element.

You can format the description using Markdown.

Type: String

The element's ID, which is used in other form elements and activities to access the element's properties, including the user's input. The ID must be unique across all elements in the form.

You cannot set the value of the Element ID property in an expression—you can only use the value that you configured for it. To use the Element ID property in an expression:

${Display Form ID}.state.{Element ID}.{property name}

For example:

Type: Boolean

Name in Properties Panel: Enabled

Name to Use in Expressions: enabled

Indicates whether the File Picker element is enabled in the running workflow. When a File Picker element is enabled, the user can select files. When a File Picker element is disabled, the user can see the File Picker element, but cannot interact with it. Disabled elements appear dimmed or shaded in the running workflow.

By default, File Picker elements are enabled. To disable a File Picker element, clear the Enabled checkbox. You may want to change the property's value at run time depending on the user's input in a previous form element.

To access the enabled property in an expression:

For example:

Type: String | MarkdownRef

Indicates whether an error occurred in the element.

We recommend using the Set Form Element Error and Clear Form Element Error activities to work with errors in form elements.

Type: String

Name in Properties Panel: File Types

Name to Use in Expressions: fileTypes

The types of files that the user can select. Use commas to separate the file types. If you leave the File Types property blank, the user can select any type of file.

You can specify either file extensions or MIME types, for example:

• .xml - Accepts XML files

• .png, .jpg, .jpeg - Accepts PNG, JPG, and JPEG files

• image/png - Accepts files with the image/png MIME type

• image/* - Accepts files with an image/* MIME type

• * - Accepts all file types

To access the fileTypes property in an expression:

For example:

Type: Number

The maximum number of files that the user can select. If you do not specify the maximum, the user will be able to select 3 files.

Type: Boolean

Name in Properties Panel: Required

Name to Use in Expressions: require

The Required checkbox is intended as a quick way to do simple validation without having to add a validate event. When you add a validate event, the Required check is not performed even if the checkbox is selected. To force the Required check to be performed when a validate event is configured, add a Propagate Form Event activity anywhere within the event's subworkflow.

Indicates whether the user must select a file. When the File Picker element is required, the user cannot submit the form until at least one file is selected. .

By default, File Pickers are not required. To require a File Picker , select the Required checkbox.

To access the require property in an expression:

For example:

Type: String

Indicates the name of the style that will be applied to the element.

To access the styleName property in an expression:

For example:

Type: String

Name in Properties Panel: Title

Name to Use in Expressions: title

The element's title, which appears at the top of the element. You may want to change the title to describe what the element represents in your workflow.

You can format the title using Markdown.

Type: String

Name in Properties Panel: Title Location

Name to Use in Expressions: titleLocation

Specifies whether the element's title appears above (default) or beside the element.

The value must be either "above" or "beside".

Type: String

Name in Properties Panel: Tooltip

Name to Use in Expressions: tooltip

A message that displays when the user hovers the mouse pointer over the File Picker. You may want to use the tooltip to provide help to the user.

Type: String

The variety of form element. File Picker elements are type "FilePicker".

Use the type property to find out the variety of a form element in a form with many elements. Loop through ${Display Form ID}.state, comparing each element to the known form types and performing some action on the elements that meet your type criteria.

To access the type property in an expression:

${Display Form ID}.state.{Element ID}.type

For example:

Type: FilesRef

An object of type FilesRef that represents the selected file or files. The object has a files property that is the collection of files.

To access the collection in an expression:

${Display Form ID}.state.{Element ID}.value.files

For example:

$form1.state.filePicker1.value.files

The load event fires when the element finishes loading.

You can use the load event to set one or more of the element's properties at run time. For example, you could set the element's initial value.

The change event fires when the user adds a file.

You can use the change event to create dependencies between form elements. For example, you could configure a change subworkflow that enables or disables other form elements depending on the user's selection.

The change event fires every time the user adds a file. This means that the change subworkflow can run multiple times. Because of this, you should make sure that the change subworkflow is not computationally intensive or long running.