Today we'd like to introduce a couple of smaller additions and changes.

Default workspace form

You can now set a default form per workspace. This feature is only available when using a custom domain. Once your custom domain was fully set up, you can select a default form that is shown when visiting the domain.

You can still use the domain for other forms of a workspace by adding the identifier or slug. This is the previous behavior and will still work even when a default form is selected.

If you don't set a default form, the workspace logo is shown, with the Deftform logo as a fallback. That's how it has always been.

Custom ID parameter for responses

We recently introduced unique IDs. It is now possible to use the parameter ###UNIQUE_ID### anywhere field parameters are allowed. So the ID can then be used in respondent and admin emails. To learn more about these parameters, read this help article.

Read-only for input fields

We added a new option (toggle) to the "Short answer" fields that allows you to set a field to read-only. This should be used in combination with the previously mentioned field parameters, which will allow you to pre-fill fields via URL parameters.

Locale-based error message

There is an option to define a default error message for mandatory fields, though it is somewhat "hidden" in the workspace settings, leading to many of our customers not noticing it. Oddly enough, they have found the "Locale" option, which is just a couple of fields below.

The error message is now determined by the locale set in the workspace settings. By default, it is in English and reads, "This field is required." If the error message value is empty, users will see the translated value based on the selected locale.

Failed webhook attempts

We changed the way failed webhook events are treated. When a webhook fails, meaning we are unable to send the webhook to the specified endpoint, we will send an alert to the workspace owner.

We will attempt to deliver the webhook event three additional times, with a 4-hour interval between each attempt. If, after a total of 12 hours, the endpoint still fails to respond, we will stop sending the webhook.