Changelog

Have something to say?

Tell us how we could make the product more useful to you.

In Progress

Form Name should be decoupled from Form Title

If a user wants to create two variations of an onboarding form (e.g., a simplified and an extended version), they cannot distinguish between them effectively in their form list without also affecting the title that the customer sees. I don’t believe it’s a good practice to have the form rename affect the UI element that customers see and can inadvertently cause some issues.

Peter Kizik 6 days ago

💡 Feature Request

Need separate Time field in addition to Date field

I would like to suggest an addition of a separate Time field alongside the existing Date field. Rationale: While users currently have the option to fill out date and time in a single field, many service booking scenarios only require a start time after selecting a date. A separate Time field would improve user experience by providing a more intuitive and streamlined interface. This would align with common practices found on other booking sites, where the date is often prefilled and users can select time from a dropdown (ideally with possibility to restrict from-to). This change could ultimately reduce user errors and make the booking process more efficient. Improved User Experience: By providing a dedicated Time field, users can quickly select a time for their appointment or event without having to navigate a combined Date-Time picker. This segmentation simplifies the process and reduces potential confusion. Users who only need to specify a start time without reference to an end time will find separate fields more intuitive. Thank you for considering this enhancement!

Peter Kizik 14 days ago

1

💡 Feature Request

Completed

Custom validation error should supercede default error message

Currently, when a field is marked as "Required," the default error message ("This field is required") is displayed if the user submits the form without filling it out. I have implemented custom error messages for specific fields and conditions, but these messages do not appear when the default error message takes precedence. It would be beneficial to have the ability to display my custom validation messages while still keeping the "Required" flag enabled and thereby retaining the visual indication of the required field (such as the asterisk). Expected Behavior: When a required field fails validation due to custom conditions, the system should display the custom error message instead of the default "This field is required" message, all without requiring me to disable the "Required" flag. Use Case: This enhancement would allow for clearer, more informative feedback to users, improving form usability while still ensuring that they understand which fields are required. Steps to replicate: Create a text field and mark it as required. Go to Validation tab→select field → Add the field with condition “Is Not Empty” (essentially required) and add custom Error message. When the form is submitted default error message shows up instead of custom one.

Peter Kizik About 1 month ago

3

💡 Feature Request

Dynamic, Contextual Input Options

Problem Statement: Currently, input fields often have static, predefined options. This limits flexibility and user experience, especially when options depend on previous selections or dynamic data. Proposed Solution: Implement a feature that allows input fields to dynamically populate options based on: Admin-Defined Lists: Create and manage lists of options in the admin settings. Assign these lists to specific input fields. Example: A list of countries could be defined and assigned to a "Country" input field. API-Fetched Options: Allow input fields to fetch options from a specified API endpoint. The API endpoint can receive parameters based on previous input values. Example: When a user selects a "Country" from a list, the "City" input field can fetch city options for the selected country from an API. Use Cases: Contextual Filtering: A user selects a "State" from a dropdown. The "City" input field dynamically populates with cities from the selected state. Hierarchical Data: A user selects a "Country" from a dropdown. The "Region" input field populates with regions within the selected country. The "City" input field then populates with cities within the selected region.

User About 1 month ago

3

💡 Feature Request

Make form a quiz

Question-Based Input: Use questions to guide user input. Question Grading: Assign a grade to each question. Correct Answer Definition: Specify the correct answer(s) for closed-ended questions (e.g., single-select, multi-select). Rich Text Feedback: Provide detailed feedback using rich text formatting for: Correct answers Incorrect answers Open-ended questions requiring manual grading

User About 1 month ago

1

💡 Feature Request

Rejected

limit number of submissions based on sum of a number input

It would be very useful, if another option is added to limit the number of submissions: So for example, assume you want to use a form for event registration and there is a maximum number of participants for this event, but with a single form submission it is allowed to register up to e.g. three people. So maybe you use a scale block, with that the user can set this number. Then it would be nice, if the form gets closed, as soon the sum of all submitted scale input values reached the maximum number of participants.

cameo77 About 2 months ago

3

💡 Feature Request

Should be Required only if Unhidden

For fields which have Logic, if they are not shown, they should not be required. There must be an option to select both Hidden and Required, such that it is made to be Required only if it is Unhidden. This issue has occurred in many different forms over the years but I am just deciding it needs a bug report/feature request.

Pierce Mooney 2 months ago

3

💡 Feature Request

Export Individual Form Responses as CSV

Instead of forcing full CSV export of all historical responses, I would benefit from exporting 1 at a time. I propose being able to check a checkbox at the right side of the table, next to the Edit Form / delete icons, so when we click export as csv it only exports the checked one(s). There can be a “check all” box at top.

Pierce Mooney 2 months ago

💡 Feature Request

Planned

Form Submissions U.I. Improvement

We should be able to read each submitted field in OpnForm’s table easily. Currently, many users scroll very far to the right and open it in the Edit Form view or connect to 3rd party GSheets to get good table view. I propose that the table should not cut off the responses (text fields) every time the text is too long for the cell. There should be a button for WRAPAROUND so it can all fit in a cell which is a normal width. This ensures we can read the form responses without tons of sideways scrolling which is inefficient.

Pierce Mooney 2 months ago

1

💡 Feature Request