eForms allow you to gather responses from your staff and external parties and build documents based on this information. This can be a mix of one-off questions (such as whether there is parking available onsite) and dynamic (such as tests on individual items in a location).

This article explains how to set up an eForm with both types of data.

In this example, we want to get this result:

This is made up of these parts:

· The top group has one-off data, such as the name of the customer and whether it is a re-test.

· The second group is for one type of test, of which there may be one or more results.

· The third group is a different type of test, of which there may be one or more results.

· The fourth group is a set of one-off questions.

· The final group is for a signature (which could be the customer, sub-contractor, supplier or employee.

So that Zigaflow knows which data goes where, we need to label the groups. The first section doesn’t need a group name, and it is also a mix of header fields (i.e. the customer name) and eForm questions (such as whether it is a re-test). The signature group doesn’t need a group name.

The group name needs to be set here on the eForm edit:

And in the corresponding group in the PDF, with the prefix {SectionGroup….}. e.g.

In the previous image, you can see all the Section Group names.

Where a section has data repeating by column and not by row (as in this example), add the variable {FieldsInColumns}.

To prevent the column headers from repeating, use the variable {AllSections}.

The structure of this should mirror the PDF template.

This is the first question, so it corresponds to the FormeFieldAnswer1, FormeFieldAnswer2, etc.

Next, add the section that will be repeated more than once on the form. You can only have one repeatable section. Note the ticked ‘Recipient Can Duplicate’.

End-User View

Setting the section in this way means the end-user can add multiple instances of the section, i.e. multiple inspections:

PDF

Each question is referenced by the ordinal, for example, SectionFieldAnswer1, SectionFieldAnswer2, etc. The section prefix distinguishes it from the FieldAnswer1 in the once-only question/answers.

These can be put anywhere in the table.

Without this, Zigaflow will render all the fields in a row-based list, e.g.:

Front Office

VOL001 Main HVAC plant

Roof Mounted Handling Unit

Etc.

This tells Zigaflow to only show the table header once.

This tells Zigaflow to put all the sections with this group name into the same table.

It needs to correspond with this in the edit form:

The highlighted tick box designates this.

Sequence

1. Create an eForm (don't use a pre-build at this stage).

2. Delete unwanted fields and add in the ones you want.

3. Preview the eForm and fill in the answers.

4. Create the document template.

5. Upload the document template (in the Settings -> Document Templates -> eForms) and preview against the eForm.

6. If you need to edit the eForm, make a copy and edit the new one.

7. When you are happy with the eForm and PDF template, click on the ‘Create Pre-Prebuild’ button on the eForm.

8. Upload the PDF template and add it to the pre-build. This will be used when an new eForms are created from the pre-build.