Forms

#Design a form

1. Create a view of the type Form in the database.
2. Design form opens the editor:
   • title, description and the label of the submit button,
   • questions: order, hide, required, help text per question,
   • question type: short or long text, radio buttons instead of a list, a linear scale 1–10 for numbers,
   • confirmation text after submitting.
3. Save form.

Flowplan checks required fields and input types in the browser and on the server. Files properties allow uploads in the form.

#Share a form

Under Share form, switch the form on and copy the link.

• Members only: answering requires signing in; the answer carries the person's name.
• Anonymous: anyone with the link can answer, without an account and without a name.

Person and relation questions only exist in forms for members, because they would reveal members and records.

#Answers

Every answer is a normal record: it appears in all views and can be filtered, assigned and commented on.

#Customer portal

The customer portal turns a form into a service desk: whoever sends it can follow their request afterwards.

1. Under Share form, switch on the customer portal.
2. Choose which properties are visible in the portal – for example Status or a due date. A select property named “Status” is preselected when you switch it on. People, relations and files always stay internal.

After sending, the person sees a private link to their request. If they answered an e-mail question and e-mail is set up, the link also arrives by e-mail – in their language. The page shows the status, their answers and a conversation with the team.

The team replies in the record under Customer request. Replies go to the person by e-mail; when they write back, the people on the record, everyone who already replied and whoever created the database get a notification. Copy customer link passes the link on when there is no e-mail address.