Queues
/
Forms and Buttons in Queues
Getting Started
Tutorials
Datasources
Functions
Spaces
Queues
Components
Self Hosted
Settings
REST API

Forms and Buttons in Queues

You can configure the following forms for each Queue:

  • Create/Update Task form: These forms are automatically generated and allow users to create/update Tasks.
  • Function Execution form(s): If you want to execute a function as part of a CTA, you’ll need to configure a form for it. 

Basics of Form Configuration

Enable the fields that you want to include in your form. Then, configure the value for each field.

Note:
Enabling a field doesn’t necessarily mean your user will see a form input for it. You can choose to have the user complete the field (in which case, when a user clicks a CTA button, a form will open and a form field will be displayed), or you can specify the value for the field using a data binding or template (in which case, no form field will be displayed to the user). See the next section for more details.

Also note that required fields must always be included in the form.

User completes field (opens form)

Choose this value type if you want to display a form field to your user. Then, select a component: Input, Text Area, Dropdown, Radio Button, or Tag Selector.

Then, add a form label. If you leave this blank, the actual field name will be used as the field label.

Next, configure the default value. Leave the default value blank if you don’t want the field to contain a value when the form is loaded. If you want the field to contain a default value, select the default value type. The available options will differ depending on the field type (e.g. UUID is only available for strings. And the current date and time is only available for timestamp and datetime. 

Below is an example where we’ve enabled the “email” field, set it as a form field that the user completes, and changed the field label to say “Email Address”. When the user loads the form, we want this email field to be pre-populated with an email address constructed using a template. Templates support Javascript Template Literals. Use the “Insert a variable” to choose from available variables”. 

In our example above, we’re concatenating the task’s “username” field’s data (e.g. jdoe) and “@example.com”. 

If you want to allow the user  to leave a field blank, check the box “Allow this field to be blank” and set how to treat blank values. You can either pass Null, an empty string, or not pass a value at all. 

Data binding

Choose this option to bind a field to available data. In this case, the user won’t see a form field. However, data will be passed through when the form is submitted.

In the example below, the email field is bound to the Task’s Field Value’s Email. In other words, if the user is working on task A and clicks on the CTA that executes this form, task A’s email will be passed through. In a similar manner, you can bind to a variety of data associated with a task (such as the assignee role_id or assignee user_id), a user (the email or role of the user who is completing the task), or Environment (the current environment name where the task is being completed).

Template

Choose this option to create a templated value. Similar to Bindings, the user won’t see a form field. Instead, the entire templated value will be passed through when the form is submitted. A template is a 

Templates support Javascript Template Literals. Use the “Insert a variable” to choose from available variables”. In our example below, we’re concatenating the task’s “username” field’s data (e.g. jdoe) and “@example.com”.