Forms in Sheep are built from a hierarchy: questions at the bottom, which can be grouped into a section, sections are added to a form template, and templates are finally made public inside a sheep form.
To construct a form you must start at the bottom and work up:
Define your questions
Group questions into sections (you must have at least one)
The Sheep Forms (templates, sections and questions) define the reusable form that a user will complete. The answers a user provides are stored in a form_response. A form response will have a reference to the form it is referring to and the contact that is completing the form.
The user has completed and submitted their form. Further user edits are not possible.
withdrawn
The user has asked to withdraw their submission.
accepted
The response has been accepted (e.g. an application to join) or simply closed/complete.
rejected
The response was not accepted.
Status fields are configurable but certain statuses are required to exist. As a form response changes state, Sheep trigger events are created which can be connected through actions to deliver automation (e.g. sending an email when a form moves to accepted).
The standard core API can be used to create, update and delete form responses. Deleting a form response will not delete any associated attachments or score sheets.
Forms can be scored (marked) directly or scored by a separate score sheet. Separate score sheets are only recommended if multiple independent scores are required.
Users can be assigned/pinned to a form response. What the assignment means will depend on the context and wider configuration. User assignments can be used in conjunction with permissions to control access to certain form responses.