The combination of one or more Forms and Templates to create a functional application that can be used by a User to produce tailored Documents. You build Applications using ZumeForms.
Content within a Template that is either inserted, left in or removed from an assembled Document, depending on the answers to questions on a Form or to other Data values. Conditional Content is usually surrounded by ‘IF’ statements that run when the Template is passed through the Document Assembly Engine.
Answers and values entered on a Form in response to questions, and other information gathered from other sources (for example, Google’s mapping database or a CRM system), that is used in an Application.
A tailored Document made by the Document Assembly Engine by combining Data gathered from Forms (and other sources) with Templates.
Document Assembly Engine
The part of the Platform that takes Data from Forms (and data from other sources) and combines the Data with one or more Templates, to produce a tailored Document.
The act of embedding a Form within another website page so that it looks like the Form forms an integral part of the website hosted by the Publisher of the Form.
This is a unique name or identifier for a Field on a Form.
The Field Name on a Form must match the Mergefield name in your Template.
A webform designed using ZumeForms Form Designer.
The part of the ZumeForms application used to design and publish Forms.
An element that you drag onto a Form to gather Data, perform actions or to adjust the layout of your Form. There are many different types of Fields, including text Fields, yes/no Fields, HTML editor Fields.
A person who designs and then Publishes a Form using ZumeForms. (A Form Publisher is sometimes referred to as the Form’s ‘owner’.)
Form Scripts are short pieces of code that you can incorporate into your Forms to make them do things that are outside the built-in functionality of the ZumeForms designer.
Form Script Extensions
HTML5 is a markup language used for structuring and presenting content on the internet. It is the fifth and current version of the HTML standard.
The process of connecting the ZumeForms platform to another platform, service or application. This generally relates to the ability for ZumeForms to pull Data from another application (for example, a CRM system), or to push Data and Documents to another application (for example, file storage). The most common form of web-based integration is via a ReST API.
A Mergefield is a field that is inserted into a Template into which Data in merged by the Document Assembly Engine.
A list of structured content that is assembled into a Document by the Document Assembly Engine based on a selection made by the User when filling in the Form.
The value selected by the Document Assembly Engine from a Merge-Text List is dependent on the value selected by the User from a number of options presented by a multi-choice Field on a Form.
For example, the Form may give the User the option of selecting between ‘Mr’ and ‘Mrs’. If the User selects ‘Mr’ then the first element of the Merge-Text List will be assembled into the Document, in this case ‘he’. Whereas if the User selected ‘Mrs’ then the second element of the Merge-Text list would be assembled into the Document, in this case ‘she’.
Merge-Text Lists can be used to create sophisticated personalised Documents.
A Form with a number of pages, with each page representing a single-page Form.
The act of changing the status of a Form so that it can be accessed by a user over the internet.
A Record contains all of the Data and Documents that Users have entered and produced from running a single instance of an Application.
A Section of a Form that has the Repeat property turned on, so that a User can enter multiple rows into the Section. A Repeat Section is similar to a table with rows – with Form Fields in each row.
REST stands for ‘Representational State Transfer’. (It is sometimes spelled “ReST”.) It relies on a stateless, client-server, cacheable communications protocol — and in virtually all cases, the HTTP protocol is used. REST is an architecture style for designing networked applications.
A REST API defines a set of functions which can perform requests and receive responses via HTTP protocol such as GET and POST.
The tool used to put ‘business logic’ into your Applications. Based on certain Conditions being met (or not met), the Rules Builder will then perform various Actions. For example, making Fields and Sections on a Form appear and disappear.
The act of saving a draft (or published Form) so that changes will not be lost when you close the Form Designer. The Data entered in a Form is saved when the User clicks the Save button (if it is visible)
A section of a Form. A Section can contain a group of Fields. A Section can be a simple single Section, or it can be made into a ‘Repeat Section’ by changing the Repeat property of the Section.
A ‘payment gatway’ for collecting money in an Application on the internet. You can use Stripe.com in your Applications to charge Users for accessing Forms and producing Documents.
When a User clicks the ‘Submit’ button on a Form the Data entered on the Form is saved to the Record. This may also fire-off other actions, such as document assembly or re-directions, etc.
A document, usually in Microsoft Word format, that is used to produce a tailored document when processed through the Document Assembly Engine.
Some Applications involve more than one Template.
A person accessing a published Form to produce a tailored document on the internet.