Fields & Field Types

Freeform uses its own set of fields and field types. Using a predefined set of fields also gives us the control to more easily account for how each form field should be displayed in Composer's live preview, and provides a smoother experience.

WARNING

There is currently a limit (around 130+) on the number of Freeform fields for each install of Craft, due to the MySQL column limit, since all fields are stored in a single table. However, Freeform fields can be used across all forms, and even be relabelled for each form.

Overview

Fields are global and available to all forms, but they can also be overwritten per form. This allows you to save time reusing existing fields when making other forms, but also gives you flexibility to make adjustments to them when needed. So to clarify, you can create fields with labels and options that are common to all forms, but also override those on each form. For example, if you have a field named Cell Phone, on the form level, you can rename the field name to Mobile Phone, or if you have a Checkbox Group field with options: Option 1, Option 2, and Option 3, you could override it to just have 2 options with values of Option A and Option B. When the fields are edited at global level (in main Fields area of Freeform control panel), your customizations per form will NOT be lost.

Fields can be created and managed in the main field creation area (Freeform > Fields > New Field) and can also be created directly within the Composer interface as well. Fields created here are available globally as well (they do not just exist for that form).

Composer - Quick Create Fields

Select, Multiple Select, Checkbox Group and Radio Group fields can also be automatically populated with select Craft Elements or Pre-defined list options.

All fieldtypes conveniently include the ability to set attributes for their labels, inputs, errors and instructions directly inside the Composer property editor. This allows you to keep your hands clean of being inside formatting templates and specify one-off exceptions for fields such as readonly and autocomplete="off", etc.

  • To use single attributes like novalidate, just enter the attribute in the Attribute column and leave the Value column empty.
  • You can use anything inside the Form and Field objects as well, e.g.:
    • {{ field.id }} to access Field ID.
    • {{ form.handle }} to access form handle.

Composer - Field Attributes Editor

Important Notes:

  • All field properties can be overwritten at form level inside Composer, including the field Handle.
  • Once a field is created, you cannot change the field type after.
  • Freeform will load fields of Hidden type at the beginning of the form, regardless of where they are placed in Composer layout.
  • When needing to use {} for attributes in Regex fields (such as pattern), you will need to specify them differently, as Freeform is built to allow Twig rendering and it'll choke. So for example, if you need to use [0-9]{4,5}, change it to:
[0-9]{{ '{' }}4,5{{ '}' }}
1

Fields Create a Field

Basic Field Types

The following field types are available (see below for additional Pro Field Types):

Text

A simple input field.

  • Can be marked as required.
  • Can contain default text and/or placeholder.
  • Can set maxlength property.
  • Field specific properties for templating:
    • placeholder

Textarea

A simple multi-line input field.

  • Specify the number of rows the textarea should have.
  • Can be marked as required.
  • Can contain default text and/or placeholder.
  • Can set maxlength property.
  • Field specific properties for templating:
    • placeholder

Email

An input field that is flagged in Freeform to expect an email address value as well as possibility for receiving email notifications.

  • In the Property Editor (right column) in Composer, select a notification template if you want the email entered for this field to receive an email notification.
    • Users/groups need to have permissions access for Email Notifications to create new formatting templates.
  • To allow sending of email notifications to more than 1 email address (e.g. in the case of a "tell-a-friend" type form), you will need to add multiple input fields, each with the input name email[]. This approach would require that you code this part manually however.
  • Required field type if you wish for your users to receive an email notification.
  • Required field type if you're using with a Mailing List API integration.
  • Can be marked as required.
  • Can contain default text and/or placeholder.
  • Field specific properties for templating:
    • placeholder
    • notificationId
      • The database ID of the assigned Email Notification Template.

Number

A number type input field that is validated to contain numbers only, based on several configuration options.

  • Choose if validation should allow negative numbers.
  • Optionally set Min/Max values.
    • Both are optional, you can have both, just one or neither.
  • Optionally set Min/Max character length.
    • Both are optional, you can have both, just one or neither.
  • Set the number of decimals allowed.
  • Can be marked as required.
  • Can contain default text and/or placeholder.
  • Field specific properties for templating:
    • placeholder
    • minLength
    • maxLength
    • minValue
    • maxValue
    • decimalCount
    • allowNegative (e.g. false)

Hidden

A hidden field.

  • Can only include text strings at this time (no variables allowed).
    • If you need you pass a value to your hidden field dynamically, you can do so with the overrideValues parameter. Ex: overrideValues: { myFieldname: myvalue }
  • Cannot be marked as required.
  • Freeform will load fields of this type at the beginning of the form, regardless of where they are placed in Composer layout.

Select

A select dropdown menu field.

  • Can specify labels (with values assumed) or labels and values (that differ).
    • To make the first option empty, use labels and values approach with first option having -- or Please select..., etc for the label, and leave option blank.
  • Can be automatically populated with select Craft Elements or Pre-defined list options.
  • Can be marked as required.
  • Can specify default option to be selected.
  • Field specific properties for templating:
    • options
      • An array of option objects with label and value properties.

Multiple Select

A multiple select field.

  • Can specify labels (with values assumed) or labels and values (that differ).
  • Can be automatically populated with select Craft Elements or Pre-defined list options.
  • Can be marked as required.
  • Can specify default option(s) to be selected.
  • Field specific properties for templating:
    • options
      • An array of option objects with label and value properties.

Checkbox

A single checkbox field.

  • Can be rendered vertically or horizontally.
  • Has a default value of Yes, which can be overwritten with any value you want. The front end however, will always display the value as 1, but upon submission, the value will be switched to the one you have set.
  • Can be marked as required, which would essentially require that this checkbox be checked.
  • Can be checked by default.

Checkbox Group

A group of checkboxes.

  • Can specify labels (with values assumed) or labels and values (that differ).
  • Can be automatically populated with select Craft Elements or Pre-defined list options.
  • Can be marked as required.
  • Can specify which (if any) options to be checked by default.
  • Field specific properties for templating:
    • options
      • An array of option objects with label and value properties.

Radio Group

A group of radio options.

  • Can specify labels (with values assumed) or labels and values (that differ).
  • Can be rendered vertically or horizontally.
  • Can be automatically populated with select Craft Elements or Pre-defined list options.
  • Can be marked as required.
  • Can specify which (if any) option to be selected by default.
  • Field specific properties for templating:
    • options
      • An array of option objects with label and value properties.

File Upload

A file upload field, using Craft Assets.

  • Can allow a single file or multiple files (applies multiple attribute to the single file upload input) to be uploaded.
    • Specify a number larger than 1 in the File Count setting to allow multiple files to be uploaded at the same time.
  • Must have an Asset Source location where the file will be uploaded to.
  • Does NOT work with Image Transforms.
  • Define maximum file size (in KB). Default is 2048 KB (2MB). Is subject to:
  • Select which file types can be uploaded.
    • Leaving all options unchecked will allow ALL file types.
  • In multi-page forms, if an earlier page contains file upload field(s), files will actually be uploaded before the form is officially submitted.
    • If the form is never completed, incomplete submissions are stored for 3hrs, and then are removed (along with the file(s)) after that.
  • Upload Location Subfolder (optional) - the subfolder path that files should be uploaded to. May contain form.handle or form.id variables as well.
  • Can be marked as required.
  • Field specific properties for templating:
    • fileKinds
      • An array of allowed file kinds, e.g. image, document, audio, etc.
    • maxFileSizeKB
      • The numeric representation of the upload limit in kilobytes.
    • fileCount
      • The maximum number of allowed files to be uploaded.
      • Specify a number larger than 1 to allow multiple files to be uploaded at the same time.

Dynamic Recipients

A special field, displayable as a Select, Radio or Checkbox Group that contains protected email addresses and labels for each.

  • Can be switched to Radio or Checkbox options at form level inside Composer.
  • Can be rendered vertically or horizontally.
  • Can be automatically populated with select Craft Element options. 3.2.3+
  • Specify labels and email address values.
    • Emails are never parsed in source code (they're replaced with 0, 1, 2, etc).
      • NOTE: When parsing this field semi-manually, be sure to use loop.index0 to generate numeric values of options instead of fieldName.value.
    • To make the first option empty, specify -- or Please select..., etc for the label, and leave option blank.
  • In the Property Editor (right column) in Composer, select a notification template you want the selected recipient for this field to receive.
    • Users/groups need to have permissions access for Email Notifications to create new formatting templates.
  • Can be marked as required.
  • Can specify default option to be selected.
  • Can specify 1 or more recipient options at a time (when using as Checkboxes).
  • Multiple email addresses can be specified for each option, separated by commas.
  • Can include more than 1 of this field type in your forms, allowing for multiple sets of recipients to be notified.
  • Field specific properties for templating:
    • showAsRadio
      • A boolean value. If true the dynamic recipients field should be rendered as radio buttons instead of a select field.
    • showAsCheckboxes
      • A boolean value. If true the dynamic recipients field should be rendered as checkboxes instead of a select field.
    • notificationId
      • The database ID of the assigned Email Notification Template.
    • NOTE: When parsing this field semi-manually, be sure to use loop.index0 to generate numeric values of options instead of fieldName.value.

Pro Field Types

The following extra field types are available with Freeform Pro:

Date & Time Pro

A complex date and/or time field. Can be used as Date only, Time only, or both. Many configuration and validation options available as well:

  • Set a default value.
    • Can use now, today, 5 days ago, 2017-01-01 20:00:00, etc, which will format the default value according to the chosen format as a localized value.
  • Select if the field should use the default Freeform datepicker.
    • Can include your own manually in the template if you wish.
  • Generate a placeholder from your date format settings showing the accepted format.
    • Can include your own placeholder if you wish.
  • Date Order - the formatting order you'd like. Options are:
    • Year month day
    • Month day year
    • Day month year
  • Select if the year should be displayed/validated as 4 digits.
  • Select if the day and month numbers should have a leading 0 for single digit values (e.g. August will display as 08 instead of 8).
  • Date separator - the character used between each year, month, day value:
    • None
    • Space ()
    • /
    • -
    • .
  • Select if time and datepicker should use 24 hour clock.
  • Clock separator - the character used to separate hours and minutes:
    • None
    • Space ()
    • :
    • -
    • .
  • Choose if placeholder should separate AM/PM with a space (for 12hr clock).
  • Select the Min and Max dates for the date picker and validation (optional). Use static dates (e.g. 2018-11-01, 2018-11-30) or relative date strings (e.g. -10 days, +3 months).
  • Can be marked as required.
  • Freeform will automatically insert javascript in the footer of the page for this fieldtype. If you prefer to have this load inside the <form></form> tags (for purposes of caching, etc), you can adjust the Freeform Javascript Insertion Location setting.
  • For localization reference:
  • The Flatpickr date picker will automatically localize according to the locale set for your site. Locales available are only 2-letter codes like fr, de, etc. In the event you're using a locale like fr-CA or es-US, etc, Freeform will just look at the first 2 letters and use that as the locale.
  • To translate the formatting syntax error message, be sure to translate the following strings:
    • "{value}" does not conform to "{format}" format.
    • To translate the {format} rendered value to match the current locale, be sure to also translate whatever the rendered string is in the error message. For example, if you're using fr locale, and wish to have the default English DD/MM/YYYY show up as JJ/MM/AAAA, create a static translation for this manually.
  • Field specific properties for templating:
    • initialValue
    • dateTimeType (e.g. both)
    • generatePlaceholder (e.g. true)
    • dateOrder (e.g. ymd)
    • date4DigitYear (e.g. true)
    • dateLeadingZero (e.g. true)
    • dateSeparator (e.g. /)
    • clock24h (e.g. false)
    • clockSeparator (e.g. :)
    • clockAMPMSeparate (e.g. true)
    • useDatepicker (e.g. true)
    • minDate (e.g. five weeks ago)
    • maxDate (e.g. 2024-12-31)

Date & Time fieldtype

Phone Pro

A tel type input field that is validated to contain phone numbers only, based on a configured pattern.

  • Set pattern to desired format, where 0 is a digit between 0 and 9, e.g:
    • (000) 000-0000
    • +0 0000 000000
    • Check off Use JS validation checkbox to have Freeform include JS in the form that validates the format and auto-inserts the extra characters like (, -, + etc).
  • Can be marked as required.
  • Can contain default text and/or placeholder.
  • Field specific properties for templating:
    • placeholder
    • pattern

Phone fieldtype

Table Pro 3.5.0+

A field that allows you to collect and handle repeating data.

Table fieldtype

Form Rendering

Here's how you can use field.render for an automated approach to render your Table field inside your formatting templates:

{{ field.render({
   class: "table",
   addButtonLabel: "Add +",
   addButtonClass: "btn btn-sm btn-primary",
   removeButtonLabel: "x",
   removeButtonClass: "btn btn-sm btn-danger",
   tableTextInputClass: "form-control",
   tableSelectInputClass: "form-control",
   tableCheckboxInputClass: "form-check-input"
}) }}
1
2
3
4
5
6
7
8
9
10

For manual rendering of the Table field inside your form for full customizability, your code might look something like this:

<table class="table">
    <thead>
    <tr>
    {% for column in field.tableLayout %}
        <th>{{ column.label }}</th>
    {% endfor %}
    </tr>
    </thead>
    <tbody>
    {% if field.value is empty %}
        <tr>
		{% for index, column in field.tableLayout %}
			{% set colName = field.handle ~ "[0][" ~ index ~ "]" %}
			<td>
			{% switch column.type|default("text") %}
				{% case "select" %}
					<select name="{{ colName }}">
					{% for option in column.value|default("")|split(";") %}
						<option value="{{ option }}">{{ option }}</option>
					{% endfor %}
					</select>
				{% case "checkbox" %}
					<input type="checkbox" name="{{ colName }}" value="{{ column.value|default("Yes") }}" />
				{% default %}
					<input type="text" name="{{ colName }}" value="{{ column.value|default("") }}" />
			{% endswitch %}
			</td>
		{% endfor %}
        </tr>
    {% else %}
        {% for rowIndex, row in field.value %}
            <tr>
			{% for index, column in field.tableLayout %}
				{% set colName = field.handle ~ "[" ~ rowIndex ~ "][" ~ index ~ "]" %}
				{% set colValue = row[index]|default("") %}
				<td>
					{% switch column.type|default("text") %}
					{% case "select" %}
						<select name="{{ colName }}">
						{% for option in colValue|default("")|split(";") %}
							<option value="{{ option }}"{{ option == colValue ? " selected" }}>{{ option }}</option>
						{% endfor %}
						</select>
					{% case "checkbox" %}
						<input type="checkbox" name="{{ colName }}" value="{{ column.value|default("Yes") }}" {{ colValue ? "checked" }} />
					{% default %}
						<input type="text" name="{{ colName }}" value="{{ colValue }}" />
					{% endswitch %}
				</td>
			{% endfor %}
            </tr>
        {% endfor %}
    {% endif %}
    </tbody>
</table>
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

Submission Data

How to render a Table field's data inside Submission object:

<table class="table">
    <thead>
        <tr>
        {% for column in field.tableLayout %}
            <th>{{ column.label|default("-") }}</th>
        {% endfor %}
        </tr>
    </thead>
    <tbody>
    {% for row in submission[field.handle].value %}
        <tr>
        {% for index, column in field.tableLayout %}
            <td>{{ row[index] }}</td>
        {% endfor %}
        </tr>
    {% endfor %}
    </tbody>
</table>
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

A complete example might look like:

{% for field in submission %}
    <td>
	{% if field.type == "table" %}
		<table class="table">
			<thead>
				<tr>
				{% for column in field.tableLayout %}
					<th>{{ column.label|default("-") }}</th>
				{% endfor %}
				</tr>
			</thead>
			<tbody>
			{% for row in submission[field.handle].value %}
				<tr>
				{% for index, column in field.tableLayout %}
					<td>{{ row[index] }}</td>
				{% endfor %}
				</tr>
			{% endfor %}
			</tbody>
		</table>
	{% else %}
		{{ submission[field.handle] }}
	{% endif %}
    </td>
{% endfor %}
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

Rating Pro

A special field that allows for star ratings using Freeform's built in CSS.

  • Set a default star rating value (based on Maximum Number of Stars configuration option)
  • Set the maximum number of stars allowed.
  • Select an "Unselected" display color.
  • Select a "Hover" display color.
  • Select a "Selected" display color.
  • Can be marked as required.
  • Field specific properties for templating:
    • colorIdle (e.g. #ddd)
    • colorHover (e.g. gold)
    • colorSelected (e.g. #f70)
    • maxValue (e.g. 5)

To manually render a Rating field to use your own styles, your code might look something like this:

{% for i in 1..field.maxValue %}
	<label for="rating-{{ i }}">whatever {{ i }}</label>
	<input type="radio" id="rating-{{ i }}" value="{{ i }}" name="{{ field.handle }}">
{% endfor %}
1
2
3
4

Rating fieldtype

Opinion Scale Pro

A special field that allows for flexible opinion scoring using Freeform's built in CSS.

  • Set entire scale and option labels and values
  • Set a default opinion value
  • Set the legend (optional).
  • Can be marked as required.
  • Field specific properties for templating:
    • scales
    • legends

To manually render an Opinion Scale field to use your own styles, your code might look something like this:

{% set field = form.get("opinionScale") %}

<div style="border: 1px dashed gray; padding: 5px;">
	{% if field.scales %}
		<ul>
			{% for index, scale in field.scales %}
				<li>
					<input type="radio" name="{{ field.handle }}"
							value="{{ scale.value }}"
							id="{{ field.idAttribute }}-{{ index }}"
							{{ field.value == scale.value ? "checked" }}
					/>
					<label for="{{ field.idAttribute }}-{{ index }}">
						{{ scale.label }}
					</label>
				</li>
			{% endfor %}
		</ul>
	{% endif %}
	{% if field.legends %}
		<ul>
			{% for legend in field.legends %}
				<li>{{ legend.legend }}</li>
			{% endfor %}
		</ul>
	{% endif %}
</div>
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

Signature Pro 3.4.0+

A field that allows users to handwrite signatures inside your form.

  • Set the dimensions of the field writing/drawing area.
  • Set whether a Clear button is shown or not (resets the writing pad area).
  • Can be marked as required.
  • This field also has some special considerations:
    • Signatures are stored as an image datapoint value.
    • Signatures can be downloaded as JPG or PNG files (from control panel).
    • Signatures are excluded from regular exports and the allFields loop in email notification templates (since it would just hold an image datapoint value string).
    • Signatures can be edited when the form is in edit mode.
    • The Clear button can be styled inside Composer with Input attributes area inside the property editor.
    • The Signature field, due to it's complexness, cannot easily be manually generated in a form, and is best done with render helpers, e.g. field.render.
    • There's currently no way to make the signature pad area "responsive" (like setting it to 100% width), as this would be quite difficult to account for with the need to display the signature image in various places, etc.

Signature fieldtype

Invisible Pro 3.5.0+

A field that allows you to collect hidden data in form submissions without a hidden field being present in the template source code. You might typically use this in conjunction with the overrideValues parameter to set a dynamic value into the field. It can also be given a hard coded value inside the Property Editor in the CP Composer interface while building your form.

Regex

An input field that is validated based on the specified regex pattern (e.g. /^[a-zA-Z0-9]*$/).

  • Set error message a user will see if an incorrect value is supplied.
    • Any occurrences of {{pattern}} will be replaced with specified regex pattern inside the error message, if any are found.
  • Can be marked as required.
  • Can contain default text and/or placeholder.
  • Field specific properties for templating:
    • placeholder
    • pattern
    • message

Regex fieldtype

Website Pro

A url type input field that checks to see if the URL specified has valid syntax (http://, https://, ftp://, etc).

  • Can be marked as required.
  • Can contain default text and/or placeholder.
  • Field specific properties for templating:
    • placeholder

Website fieldtype

Special Fields

Special fields are ones that either every form needs (such as Submit button), ones that assist in setting up form behaviors (such as Confirm and Password), and ones that aid in the layout and content of forms (such as the HTML block). None of these fields store any submission data in the database. The following special fields are available to use:

Submit

  • Settings allow you to edit the button label.
  • You may adjust the positioning of the submit button:
    • Aligned to Left
    • Aligned to Center
    • Aligned to Right
  • When using with multi-page forms, Freeform will detect when you're on a page after first page, and provide you with additional options:
    • It will include a Previous button by default, allowing the user to go back to previous pages in the form.
      • Previous button can be disabled.
    • Positioning options now include:
      • Apart at Left and Right
      • Together at Left
      • Together at Center
      • Together at Right
  • You may include 1 per page in your form.
  • Field specific properties for templating:
    • labelNext
      • A label for the Next button. Submit by default.
    • labelPrev
      • A label for the Previous button. Previous by default.
    • disablePrev
      • A boolean value. If true the Previous button should not be rendered.

HTML

  • Property Editor will load an HTML area for you to type or paste your code into.
  • Layout column will live parse your HTML.
  • All HTML is allowed here.
  • You can include as many of these in your form as you wish.

Rich Text Pro

  • Property Editor will load a Rich Text area for you to type into and style as necessary.
  • Layout column will live parse your content.
  • You can include as many of these in your form as you wish.

Confirm Pro

Allows you to force a user to enter a matching value for another field, including Password special field (e.g. "Confirm Email Address").

  • Select a target field to compare with.
  • Can be marked as required.
  • Can contain default text and/or placeholder.

Password Pro

Allows you to collect a password from a submitter, but NOT store the value in the database.

  • Useful for creating a user registration form (using the Element Connections feature) and in other very specific use-cases where you're passing the password off somewhere else.
  • Collected data is not stored in Freeform anywhere, nor is it included in the Submission object or allFields variable in email notifications.
  • When using with Users Element Connections feature, the password will be passed off to Craft's Users member account feature.
  • Can be marked as required.
  • Can contain default text and/or placeholder.

reCAPTCHA v2 Checkbox

  • Built in support for reCAPTCHA v2 Checkbox.
  • See reCAPTCHA documentation for more information.
  • reCAPTCHA v2 Checkbox fields will render automatically like the rest of your fields in your form, but if you're building a form manually, you'd call it like this (using the Hash value for reCAPTCHA field in Property Editor of Composer):
{% set form = craft.freeform.form("composerForm") %}
{% set recaptcha = form.get("JDGnlp8vB") %}
{{ recaptcha.renderInput }}
1
2
3
  • If you're loading an entire form via AJAX, you'll need to load the reCAPTCHA JS yourself, since it's considered insecure otherwise and the browser blocks it. You should add this script tag anywhere on your page, preferably the footer:
<script type="text/javascript" src="https://www.google.com/recaptcha/api.js?render=explicit"></script>
1

Populating Fields with Elements & Predefined Options

Inside Composer (only), basic field types with options have the ability to be automatically fed options from Craft Elements or Predefined Options. This allows you to quickly build forms by having fields auto-generated.

Available Fields

The following field types can be auto-populated:

Available Craft Elements

The following Craft Elements can be fed to the above field types:

  • Craft Entries
    • Target sections or all sections.
    • Option Label and Option Value choices:
      • ID
      • Title
      • Slug
      • URI
      • Fields (simple values)
  • Craft Users
    • Target user groups or all groups.
    • Option Label and Option Value choices:
      • ID
      • Username
      • Email
      • First Name
      • Last Name
      • Full Name
      • Fields (simple values)
  • Craft Categories
    • Target category groups or all groups.
    • Option Label and Option Value choices:
      • ID
      • Title
      • Slug
      • URI
      • Fields (simple values)
  • Craft Tags
    • Target tag groups or all groups.
    • Option Label and Option Value choices:
      • ID
      • Title
      • Slug
      • URI
      • Fields (simple values)
  • Craft Assets
    • Target asset groups or all groups.
    • Option Label and Option Value choices:
      • Filename
      • ID
      • Fields (simple values)

Element Feeders

Available Predefined Options

The following Freeform predefined options can be fed to the above field types:

  • States
    • Official USA States
    • Option Label and Option Value choices:
      • Full
      • Abbreviated (upper case 2 letters)
  • States & Territories
    • Official USA States and territories
    • Option Label and Option Value choices:
      • Full
      • Abbreviated (upper case 2 letters)
  • Canadian Provinces
    • Provinces - English
      • Canadian Provinces and territories in English
    • Provinces - French
      • Canadian Provinces and territories in French
    • Provinces - Bilingual
      • Bilingual list of Canadian Provinces and territories
      • Option Label and Option Value choices:
        • Full
        • Abbreviated (upper case 2 letters)
  • Countries
    • All world countries
    • Option Label and Option Value choices:
      • Full
      • Abbreviated (upper case 2 letters)
  • Languages
    • All world languages
    • Option Label and Option Value choices:
      • Full
      • Abbreviated (lower case 2 letters)
  • Numbers (range)
    • A custom range of numbers
    • Range Start and Range End
      • E.g. 60 - 65 would return list: 60, 61, 62, 63, 64, 65
  • Years (range)
    • A custom range of years
    • Range Start - number of years in PAST from current year
    • Range End - number of years in FUTURE from current year
      • E.g. 5 (start) - 0 (end) would return list: 2018, 2017, 2016, 2015, 2014, 2013
    • Sort Direction:
      • Ascending
      • Descending
  • Months
    • All 12 months of the year.
    • Option Label and Option Value choices:
      • Full, e.g. September
      • Abbreviated (Capitalized 3 letters), e.g. Sep
      • Single Number, e.g. 9
      • 2-digit Number, e.g. 09
  • Days
    • List of days 1 to 31.
    • Option Label and Option Value choices:
      • Single Number, e.g. 3
      • 2-digit Number, e.g. 03
  • Days of Week
    • List of all days of week.
    • Option Label and Option Value choices:
      • Full, e.g. Thursday
      • Abbreviated (Capitalized 3 letters), e.g. Thu
      • Single Number, e.g. 4

Predefined Feeders



Icons made by srip from www.flaticon.com is licensed by CC 3.0 BY.

Last Updated: 11/15/2019, 12:04:37 PM