In practice it’s usually necessary to leave a few spare fields outside the form groups, or ‘cheat’ by adding a group with a name such as ‘Miscellaneous’ or ‘Additional information’, as in the example above. In a sense, defining forms and grouping their fields is a data modelling exercise that complements the workflow’s process modelling component.ĭon’t worry if you can’t fit all of the fields into a well-named group. The ‘vacancy’ is an example of what’s called a ‘domain entity’ in data modelling-a coherent group of data that corresponds to a higher-level concept. In the same way that the form builder lets you reuse an existing form, you can also select a form group to copy it from another form. In our example, we recognise that a job vacancy is a ‘thing’, which helps us understand the purpose of the fields in the ‘Vacancy’ form group.Īs well as adding structure to the form, a named form group is also a reusable collection of fields. This is also why form groups are so powerful: good form group names reduce a complex form into a smaller number of recognisable sections. The hardest thing about creating a form group is choosing a good name. You can also add a form group description that provides guidance for people completing forms. To do this, select or drag the Form Group control In the form builder, and then drag fields onto the form group. The following version of the same form splits it into four fields: Team, Vacancy, Recruitment process and Additional information. Each section has a title, and an optional description. In Process Governance, you can use ‘form groups’ to split a large form into sections. The ‘team’ fields belong together, as do the ‘vacancy’ fields. The first few fields are about which part of the company-which team-has the vacancy, and the next few fields are about the vacancy itself. If you look at the long job vacancy form carefully, you might notice that there are several groups of fields. The solution to these problems is to identify fields that belong together, and group them. Long forms like this are harder to understand, harder to fill in correctly, and harder to maintain. This form now has too many fields to take in at a glance. What used to be a small form ends up with many more fields. One way for a workflow to become more complex is when it handles more complex data. Processes can be complex in different ways, and workflow automation usually adds complexity as the workflow evolves. Almost all forms start simple, with less than ten fields, in the same way that there was probably originally a spreadsheet with less than ten columns. Workflows typically use forms like this to collect information, and present this information for review or approval. How forms become complexĪ workflow for creating a new job vacancy to be published on the company site typically starts with a form that captures the vacancy details. This article shows you how Process Governance uses ‘form groups’ to address this kind of complexity. In complex scenarios you can end up with long forms that are hard to use and maintain. PHP Version: 5.3.29 (should be 5.Forms and data collection form an important part of many workflows. Web form builder ver: 2.5 5437 / PHP Version: 5.3.29.įormBuilder version: Web Form Builder (Windows), build The host company has been involved already and claims they have no 'blocks', and system appears ok to work. The site is hosted off Google, but we are using Google email. I hope I have simply overlooked a config detail, perhaps someone can assist in spotting it.

Connection parameters for a SMTP server that supports secure connections, such as

Connection parameters for a plain SMTP server Use this if the server needs authentication: Does the remote SMTP server need authentication? data (minus the specific email and pass): Your form could not be submitted for the following reason(s): To possibly save time, here is the question anyway:

Coffeecup web form builder manual