Custom confirmation message

[almet]

No description provided.

[sahildua2305]

This is a great idea! After a quick look, I can see it needs to be added in formbuilder/components/RecordCreated.js. Do you have any suggestions about where do we ask for this custom confirmation message input from the creator of the form?

[rlecellier]

I think that we need a form configuration page.
It will be available from the form save's confirmation screen (where we display both url and admin url) and from the admin page.

[sahildua2305]

Yes, that's what I have been thinking as well @rlecellier. Thanks for the reply.

[almet]

As usual for such choices, the best way to act is to ask to UX people. @Natouille @QuentinRoy, where do you think we should ask for a custom confirmation message?

[DirtyF]

@almet a Settings view would be the easy place to customize your form (you also spoke about background, colors, and such, custom message could belong there)

[almet]

In terms of flow, I would actually display a "change your confirmation message" screen when clicking on "submit the form", rather than having the user click on a "settings" view (or maybe this screen could be the settings view, in which different actions would be displayed ?)

[Natouille]

@almet it's always great to have a confirmation that your form was sell sent and delivered. It should be a page after the creation of the form. It will invite the creator to fill the options that will help the UX for the end users (but of course, they wil be optionnal). It's a better way than a settings button that could be ignore by the form creators.

[DirtyF]

@almet I agree, settings are just like hamburger icons, a lazy way to hide useful informations. But you also should be able to access this customization later.

[rlecellier]

Could we use the admin view as a form save confirmation page ?
I would regroup form information and settings:

• urls
• settings
• results

It could be two parts, information and results.
Each editable informations have a "edit" button that display the edit form.
Each part have a toggle button. Informations are hide by default when coming from admin url, display by default when coming from form save.
Also, we can add a message like "please take some time to configure your form" when coming from save form.

[almet]

I think results should still be in a different page.

Each editable informations have a "edit" button that display the edit form.

I'm not sure what you're refering to. Can you elaborate? If you're thinking about e.g the confirmation message, I believe we could have it in an input instead, and update the information as soon as the user changes it (with a small check to tell it's been updated).

If possible, I would reduce the distinction between "when coming from screen A" and "when coming from screen B", and always display the same thing, so the user knows where to find the information.

Also, we can add a message like "please take some time to configure your form" when coming from save form.
+1

[DirtyF]

Question: Could the confirmation message be treated like an editable field you add at the end of the form?

I was thinking we could create a special type of field, like "Success message"

• If it's added it replaces the default message.
• It's in the user flow and optional.
• it's easy to edit at creation or modification.

[sahildua2305]

I like your idea @DirtyF!

To make things simpler, we should just add another entry just like description at the end (just about the Submit your form button). It's optional to change it just like title or description of the form. This will give a better overview of the flexibility to the end user.

[almet]

I personally prefer to have this feature implemented as part of the confirmation page. To me fields are, well, fields! And we shouldn't tie them to other contexts, especially because they would mean adding a lot of logic just for them: if it's not present then fallback to another message, if it's present there should be only one, etc.

[sahildua2305]

As a user, when I'm thinking of creating a form these are the things I will have in mind to edit besides the form fields / questions -

• Form Title
• Form Description (providing more information about the form to the users)
• Form Confirmation Text (providing information about next steps to the users who submit the forms to keep them engaged or whatever the purpose I have)

According to me, if we're keeping one thing separate than the other two, we're breaking the flow in which user thinks. Or may be it's just me who's a weird user. I'm up for further discussion over this.

[DirtyF]

Interface should abstract complexity, not the other way around ;)

[almet]

Interface should abstract complexity, not the other way around ;)

I surely agree with this :-) We probably think in different ways about what's the simplicity is.

Let me try to propose a slight change to the approach you're proposing: let's add a "confirmation message" at the end of the form, which appears only when one or more fields have been added. It should be editable the same way the title and the description are editable.

Would that work for you?

[sahildua2305]

@almet yes, that'd be good as well! 👍

[rlecellier]

I dont like this confirmation message in the builder interface.
It's a different page that'll be dislay after the form being submited. i feel it confusing to have this "confirm message" field about a secondary page in the same interface.

I think we should keep 3 steps

1. Build your form : title, description, fields.
2. Customise your form: confirmation page, style, background, end date, max submit, etc ...
3. Access your form: user, results, settings