You can configure the following forms for each Queue:
Enable the fields that you want to include in your form. Then, configure the value for each field.
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.
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.
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).
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