about us      downloads      documentation      contact      home 
 products
 antHR
 workflow studio
 technical toolkits
 content entry
 workflow
 security
 hierarchy
 concepts
 how tos
 reference
 FAQs
previous: Create  next: Configuring fields further

How to: Defining content definitions - Add fields

  Step 1 : Summary
  Step 2 : Create
  Step 3 : Add fields
  Step 4 : Configuring fields further
  Step 5 : Repeats and groups

Add fields which define the content structure - (page 3 of 5)

Level: basic

A content definition contains a collection of fields. These fields define:
  Field name: name of the field, displayed in the left hand hierarchy;
  Label: Label to display when editing this field;
  Hint: help text to display when editing;
  Displayer: Name of the displayer used to edit this field;
  Converter: Name of the converter to validate this field, and to convert it to database types;
  Validation error: error to display if the value entered in the field fails validation;
  Default value: default value for the field;
  Required: determines whether the value is required or can be left blank;
  Database column name: Name of the database column to save this value in. See here for more details;
In this step we will add a number of fields, and then test the resulting form. First, right click in the Left hand box called "Fields". On the context menu select "New field ...". A new field name appears in the "Fields" box. Rename this field to "MyFirstField".
Now change the label in the right hand "Details" box to "My first". Click "Test" to see the form. Change the converter type to "date", and test again. You will notice that the field is now a date selector rather than a edit field. The "input" displayer automatically changes type based on the converter.

Add a few more fields of different types and converters. Of course you might get strange results matching an int converter with a user displayer!
Test frequently to see how the fields work.


 

Did you find this article helpful? Comments on this page are welcome and can only help us improve the quality of our documentation.
© Ant Organisation Ltd, 2003