How Can We Help?
< All Topics
Print

What are the Audio Widget Properties

Audio Widget

Using the Audio feature, your forms can capture audio. To add an audio widget in your workflow, you can simply drag the widget from the left panel and drop it to the middle screen.

For example, the Audio widget can be added to your workflow for ‘customer feedback,’ where instead of typing the entire feedback, you can just record the customer’s voice. While filling out the workflow, the audio can be either recorded live or an audio file can be browsed and selected.

Audio Widget—Properties

Label

You can change the name of the ‘Audio’ using a label. It is ‘Audio’ by default. On the right panel, go to the label section and you can type the required text that you want. The same name will appear on the workflow. For example—you might create audio for ‘Customer Feedback’ in your workflow.

Required

You can use this property to make ‘Audio’ mandatory to be filled. Some fields in your workflow might be mandatory, while some might not be. For example, ‘Audio’ can be set to ‘Yes’ in the required property when you want to make the field mandatory. So, while filling out a workflow, the user will have to compulsorily capture or choose an audio file, without which the workflow wouldn’t be submitted.

Unique Identifier

Every field will have a unique identifier. No two unique identifiers for fields will be the same. Please note that the ‘Unique Identifier’ property is just for reference purposes only. The user need not have to do anything to this property, it can be referred to when there are fields created with the same names. When you create two fields with the same names, it might get confusing when you are setting a condition and you wouldn’t know which field is which.

For example—if you have created a field ‘address’ – and set a visibility condition to it saying the ‘address’ field will be only visible if you have entered the ‘Phone number.’ But if there are two fields that say ‘Phone Number’ – it will be difficult to set a visibility condition since both the fields have the same name. Both of these fields ‘Phone Number’ will have different unique identifiers. You can check the unique identifier and then set the condition accordingly.

Visibility Conditions

Visibility Condition in the property for the ‘Audio’ is used to specify a condition. If you apply any visibility condition, it implies that the ‘Audio’ field will only be visible if it satisfies the condition that you have set. Visibility condition can be set by specifying the condition – you can do that by clicking ‘condition not specified.’

For example—you might create an audio field ‘Customer Feedback’ which will be only visible if the user chooses the ‘Yes’ option in the earlier choice list ‘Did you record an audio for customer feedback?’

Validity Conditions

Validity Condition in the property for the ‘Audio’ is used to specify a condition. If you set any validity condition, it implies that the ‘Audio’ will only be valid if it satisfies the condition that you have set. Validity condition can be set by specifying the condition – you can do that by clicking ‘condition not specified.’

For example—You might create an audio field ‘Customer Feedback’ which will be only valid if the user enters ‘Yes’ in the earlier choice field ‘Did you record customer feedback?’ Otherwise, it would be invalid and show an error message.

Validations can help you control the type of input during the filling of a workflow by the user.

You can also customize an error message that you want to display by typing the message in ‘Validity Error Message.’ This message will be displayed when the validity condition does not match with the given input. The error message could be “The audio is only for recording customer feedback.”

Table of Contents