Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

ADD FEEDBACK

My feedback: Forms

Showing 22 of 1837

Honeypot

There should be a honeypot field to prevent spam submissions without captcha.
about 3 years ago in Content Management / Forms 0 Future consideration

Limitation of number of sent forms

A customer, managed by Natalia Butor, needs to limit the number of sent forms. When googling I found a suggestion for using a criterion that uses the Forms API to count the number of sent forms. Then using a visitor group that hides the form when ...
over 2 years ago in Content Management / Forms 1

Async client side custom validators in Epiforms

Custom validators for Epiforms must currently return their validation result synchronously, this limits the kind of validation to simple string checking. In scenarios where a server must be consulted to check an input value it is often a better ex...
over 2 years ago in Content Management / Forms 0

Forms item field localization

ChoiceElementBlock and SelectionElementBlock property Items (type OptionList) Localized value is No by the default. Items is string field but it is not possible to localize those texts as default. This is lack in basic cms functionality and causes...
over 1 year ago in Content Management / Forms 0

Text area max lenght

Textarea element should have support for optional max length value. This would be helpful in preventing ddos attacks but also helpful in general.
about 3 years ago in Content Management / Forms 0

Missing autocomplete-attribute in Forms module

In the Forms module we are missing the possibility of setting the autocomplete-attribute, and therefore WCAG 1.3.5 is broken. Will this be fixed in a future update of Forms?
almost 2 years ago in Content Management / Forms 0

Allow form fields to be stored in a shared folder without breaking the mapping to Marketing Automation (i.e. Salesforce)

We want to maintain a list of shared form fields without breaking the mapping of the field into the Marketing Automation database (i.e. First name field mapped into Salesforce First name field). At the moment we have to set up fields like "First n...
over 2 years ago in Content Management / Forms 0

Form element creation behaves differently from block creation

When creating new form elements, edit UI does not ask to edit element’s fields. This is different from creating new blocks where UI also notifies about using some other name for the content than the default: “Consider renaming the content to somet...
almost 3 years ago in Content Management / Forms 0

Language translation of email contents in Episerver Forms

As a an editor I would like to translate the contents regarding "Send email after form submission" on the "Settings" tab in order to send e-mails with the correct language to end users, especially with regards to subject and message. This is not c...
over 3 years ago in Content Management / Forms 0

Improve selection field Epi forms

For the Epi forms it is possible to insert selection field. You can add as many options as you like. If I then want to change the order, I can only do so by using the hamburger menu to move the item up or down one place, see attachment. It would b...
over 3 years ago in Content Management / Forms 0