Not logged in

The Form Editor

Every event must have an input form to populate the results list.
An input forms consist of form elements: text lines and input controls. Text lines are just for decoration and explaining things on the input form (the only place where they are visible). Input controls request interaction of the user (subscriber), like filling in their name fields or to select a choice. Labels for these controls appear later as column headings on the results list.

The form editor enables you to add or edit text and controls to your form, to delete them or drag them around on your form or to change their behavior.


When you add or edit a form element, an edit box will appear on the place where you want to add the element. Every control has a set of attributes.
Each input control must have a unique label. This label is used as column heading in the result list.


Hiding input controls on the input form

You can hide an input control on the input form for users by using the checkbox 'Hide when not logged in'

Unchecked:Everybody will see this control and can therefore use it.

Checked:You will only see this control when you are logged in.
Reasons why you want to do this, could be that you want to add some information later to a subscription, like payment status or just a remark.

Hiding Fields on the result page

Each control has three options for the subscription list:
Always Show:As it implies, this column will always be visible for everybody

Show when logged in:Only you as the registrar or the power-user of the event can see the result. Use this option for sensitive information like emails, or just to de-clutter the subscription list to keep it simple for the user

Never show:Nobody will see this column, even when logged in or as a Power User.
Use this option for including for example an invisible sort field like rank

Form Editor: Text Line

Text lines are only visible on the input form, and are for decoration and explanations only.

You can set the font size, the bold attribute and the alignment.


Form Editor: Text Box

Text boxes are used for short inputs like names, numbers or email addresses.


Type Use Icon
Anything Use for alphanumeric input like names etc.
Numeric Only numbers allowed
Email only valid formatted email addresses allowed
Date The user will be presented with a date selector
Link A valid URL. On the result list this will be a
clickable link.
Image Users will be able to upload an image. On the result list this will be a thumbnail that when clicked will show the image in a viewer.
File Users will be able to upload a file.

Form Editor: Text Area

Text areas are used for longer textual inputs, up to 2000 characters.

Form Editor: Drop Down

Use drop-down boxes for choices (up to 30)

You can allow for multiple choices as well (hold control key down when selecting):

Advanced: you can specify value-prompt pairs as follows (for single-choice dropdown boxes):
{10} I donate ten dollars
{20} I donate twenty dollars

In this way, the result can be evaluated to something numeric, which allows it to be used as a payment control or used in a formula which calculates results.

More Advanced

You can specify a textbox from another event of yours. The dropdown box will then automatically be populated with unique values from the results of that field.

Example: you have an event (database) of places you have visited with fields year, country, city

You also want to store some pictures from your trip in a new database, so you create an event 'mypics' where you want to store the picture, location and some caption.

Now if you create a dropdown with a field 'The country' (the field name doesn't matter) and let it point to country in the other database, your dropdown list will be populated with all the cities you visited.

Note that this is dynamic: if you add a country later, the dropdown will automatically reflect this.

There is no real limit of how many options you can have (the 30 limit doesn't apply here), but it should not be more than a couple of hundred, because download time and workability

Form Editor: Radio Buttons

Use radio buttons boxes for choices (up to 10)
None of your business

Advanced: you can specify value-prompt pairs as follows:

{10} I donate ten dollars
{20} I donate twenty dollars

I donate ten dollars
I donate twenty dollars

In this way, the result can be evaluated to something numeric, which allows it to be used as a payment control or used in a formula which calculates results.

Form Editor: Country Selector

A country selector is drop-down control pre-populated with countries of the world.


Form Editor: Rich Text Editor


Use this control if you want to allow for rich (formatted) text. You can have up to 4 Rich Text input controls on your form. In general it's not a good idea to have a Rich Text input on your form if the input form is for the general public because it allows for giant font sizes, but it might come to use if you or your power user are the only ones submitting.

Form Editor: Formula

String formula

A formula is used to replace field values to make a compound object.

The result of formula can only be shown on the result list. Any label name between brackets {} will be replaced by the value in the database.

Let's say you have a field 'Telephone number' but you don't want to repeat the country and area prefixes for every entry, because they are all the same. You can then insert a formula with the following content:

31-382-{telephone number}

Now it can be desirable not to show 31-382- as well when a record doesn't have a telephone number. Then simply place everything between square brackets, and when a value between the inner brackets {} is not found, everything between and including the square brackets is not shown: [31-382-{telephone number}]

telephone number 12345 will be shown as 31-382-12345
Telephone number 'blank' will be shown as 'blank'.

Other example: an event with two fields: 'short name' and 'full link'.

Formula with a field name of 'link': [<a href='{full link}'>{short name}>/a>]

For the result list, hide the fields 'short name' and 'full link' and only show 'link'

short name: google
full link:

result for 'link': <a href=''>google</a> which is a clickable link.

Numeric Formula

Numeric formulas can also be used as a checkout-control on the input form.

Numeric formulas start with an equal sign: ''=''

All fields used in the formula should evaluate to a numeric value or blank (evaluates to 0)

Numeric formulas can refer to other numeric formulas but should not be recursive.

Assume you have a drop down box with hotel prices, populated with the following options:
My Hotel:
{35} Hill Town Hotel
{50} Sharedon Hotel

And you have a check box to include breakfast when checked (5 US$)

You can then calculate the total price as follows:

={My Hotel} + 5 * {Include Breakfast}

Empty fields always evaluate to 0. Check boxes evaluate to 1 when checked and zero when not checked.

Days between to calendar dates are evaluated depending on the 'Date Range' setting in 'Event Options'

Date range: Hotel type, check in - check out

A: 10 April (start date)
B: 11 April (end date)

B - A = 1 day (only one night occupancy)

Date Range: Per day

A: 10 April 2013 (start date)
B: 11 April (end date)

B - A = 2 days (two days usage of an asset)

Form Editor: Booking Control

A bookings control is a special input mechanism which checks availability against a set of assets (hotel rooms, motor bikes etc).
To use it you have to create at least 2 events total, one for the assets, one for the bookings (which has this booking control on it)

Example for the Assets Table: An event with at least two fields:
A text-box for unique IDs and a drop-down control for types filled with value-prompt pairs (example: {75}Superior Room)

After inserting some values, the assets table (event) could look something like this:

Room No Type
101 {50}Standard
103 {50}Standard
105 {50}Standard
102 {75}Superior
104 {75)Superior
106 {75}Superior

The Bookings events should have the bookings control on it, together with fields for other information, like name and email.

The Bookings Control searches the available assets based on what the user selects. For example if only an end date is given, then the control shows only types and quantities available for that date. If a quantity is given, it will only show types and dates for which this quantity is available etc.

The final value of a Bookings Control is a number: the price of the booking.

Adding a Booking Control will add a new tab to the menu: bookings, which is a time graph of assets and dates.

The Bookings Control will add 5 fields to the result list: total price, start date, end date, quantity, type and an IDs field with allocated IDs field for that booking.