Date Picker Form Element

Type: String

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 get or 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:

$form1.state.datePicker1.visible

Type: Boolean

Name in Properties Panel: Enabled

Name to Use in Expressions: enabled

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

By default, date pickers are enabled. To disable a date picker initially, 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:

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

For example:

$form1.state.datePicker1.enabled

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: Boolean

Name in Properties Panel: Required

Name to Use in Expressions: require

Indicates whether the user must select a date in the date picker. When the date is required, the user cannot submit the form until a date appears in the date box.

By default, date pickers are not required. To require a date picker, select the Required checkbox.

The Required checkbox is intended as a quick way to do simple validation without having to add a validate event. If you add a validate event to a form element, selecting the Required checkbox will not have any effect. In this case, you must make the validate event check whether the user entered a value.

To access the require property in an expression:

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

For example:

$form1.state.datePicker1.require

Type: String

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

To access the styleName property in an expression:

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

For example:

$form1.state.datePicker1.styleName

Type: String

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. Descriptive titles make forms easier to understand.

You can format the title using Markdown.

Type: String

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

Type: String

The variety of form element. Date pickers are type "DatePicker".

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:

$form1.state.datePicker1.type

Type: DateTimeRef

The currently selected date.

To access the value property in an expression:

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

For example:

$form1.state.datePicker1.value

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 date picker's initial value.

The change event fires when the user selects a date.

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's selection changes. This means that the date picker's change subworkflow can run multiple times. Because of this, you should make sure that the change subworkflow is not computationally intensive or long running.