Building a form for your users to fill in
Each section within an event type contains the individual fields that a user will fill in
To create a form for your users to fill in you'll first of all need to create an event type. Within the event type you can then create a section which is where you'll build the individual fields that the user will complete. When editing the section you will see a series of options at the bottom of the page which is where you can choose which type of field you'd like to add to the form.
Type | Description |
|---|---|
Text | Allows you to add a heading or some descriptive text to the form. A heading is helpful to break up the form into different areas and descriptive text helps you to convey information to people which may be relevant to this particular form. |
Blueprint | Allows you to select from an existing blueprint in the system to show on the form. |
Relation | Allows you to choose from an existing relation in the system to display within the form. Relations are used to link users together in a hierarchy structure. If the user filling in the form already has an element of the selected relation applied then they will only be able to select from elements that are beneath theirs in the hierarchy whilst completing this form. The element of the relation selected whilst completing this form will be applied between the date occurred and the end date of the event. The same relation can only be used once per event type section. |
Custom field | This is probably what you'll use most often. This allows you to select from most common field types; free text, discrete, date etc. |
Role | Allows you to select an existing role in the system which has been marked as user dependent. When this form is completed the person filling it in will be able to choose anyone in the system that has this role. This is useful for linking users together and similar to relations will be applied between the date occurred and end date of the event |
Embedded report | Allows you to select from any published report in the system. When the event is completed this report will generate information and display the output within the form itself. The person creating the event will need the permission to be able to run reports in order to be able to see this data. |
Embedded goal | Allows you to apply goals to your users, or allow them to set themselves their own goals. |
Signature | Places a signature box on the form which users can draw into. If on a desktop they can use their mouse to input a signature. |
Showing fields dependent on selections elsewhere
It is often useful to only display a field on a form when the user has answered a different question. For example, if in one field you asked the question Do you have any concerns? then if the user answers yes you may want to display a text box asking why.
Using this example you may decide to add a discrete custom field to ask the question.
Then you create the subsequent free text custom field which will used to ask the user for more information if they answer yes.
Within the settings for this free text custom field there are options for you to choose when it should be displayed. Only show this field when the user fills in will allow you to select from any of the other entry fields within this section. By using this and the subsequent And the following value(s) will enable you to choose exactly when this field should be shown to the user filling in the form.