Forms and questions

Adding a form to a status

1. 1Click the Forms & Actions tab to configure the status page.
2. 2Drag the Form action from Available Actions into the blank box.
3. 3Drag questions from the sidebar on the left into the form. A form can hold as many as you need.
4. 4Click Add Panel to split a long form into sections.

Once the form exists, four settings shape how it behaves:

• Read Only makes the form display data without accepting changes
• Multi Step Form splits a panelled form across several pages, which is worth doing as soon as a form starts to feel long
• Heading Content adds a title above the form
• Visible to controls which user types see it at all, such as internal users or client contacts

Visibility Rules go further and hide questions until other questions have been answered. Add a question, optionally pin it to a specific answer, and the hidden content appears only once that answer is given. You can chain more than one.

Creating a custom question

SwiftCase ships with default questions such as First Name and Email. When you need something specific to your process, create your own.

1. 1On the Forms & Actions tab, drag a Form into the blank box.
2. 2In the Questions sidebar on the left, click Create Question.
3. 3Give the question a name and choose a Type. The type decides what the field looks like and what it will accept.
4. 4Optionally add a Mapped Name. If an inbound API request uses a different field name, put that name here and SwiftCase will match it to this question.
5. 5Optionally add a Default Answer to pre-populate the field.
6. 6Click Save. The question is now searchable in the sidebar and can be dragged into any form.

Question types

The type you choose is the cheapest validation you will ever get. A date field cannot receive a typo that a text field would swallow.

Using answers in emails and documents

Answers are not stuck in the form. Both the email template editor and the document template editor have an Insert Task Information Tag button, which opens lists of user, question, task and file tags to drop into your content.

A tag is replaced with the real value at the moment the email or document is produced, so one template serves every case. This is what makes it reasonable for a laboratory to run fifty-two document templates across its workflows rather than fifty-two thousand documents.