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

Forms

Showing 19 of 1560

CMS users can not access files uploaded through Episerver Forms

After upgrading Episerver Forms to fix the security vulnerability outlined in this blog post (https://world.optimizely.com/blogs/phu-nguyen/dates/2023/10/vulnerability-in-episerver-forms/') CMS users can no longer access uploaded files from the Fo...
about 1 month ago in Content Management / Forms 1

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...
7 months ago in Content Management / Forms 0

Forms should be able to show blocks on-page after a form submission

When configuring a Form in the CMS, the "Display message after form submission" rich text area allows blocks and other content items to be added. However when a Frontend user has submitted the form, the blocks will not render in the rich text area...
about 1 year ago in Content Management / Forms 0 Future consideration

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?
over 1 year ago in Content Management / Forms 0

Optimizely Forms show a blank page when creating new element

How to recreate the bug:1) Create a new Alloy project with CMS 12. 2) Install EPiServer.Forms nuget package. I used version 5.2.0 in my case. 3) Navigate to a content area and create a new Forms container block. Do not publish the block. 4) Create...
over 1 year 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...
almost 2 years ago in Content Management / Forms 0

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 ...
almost 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...
about 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...
about 2 years 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.
over 2 years ago in Content Management / Forms 0