2.3. Custom (User Defined) Fields

Table of Contents

2.3.1. Formula Fields
2.3.2. Adding custom fields

Depending on your industry and business practices you may need to enter additional information for projects and tasks. Such fields cannot be provided as part of Celoxis. For example, a company may have a policy to take an advance on a project from the client or a building contractor may want to know whether they only need to supply the drawings for building a house or whether they are also responsible for the construction. Celoxis provides the ability to create such fields. They are called Custom Fields as they are customized by you. There is no limit to the number of fields you can have.

Custom fields can be attached to projects, tasks, workflow processes and workflow state transititons. Project custom fields are specific to project categories. This allows greater flexibility in that different types of projects may have different fields. Project fields can also be shared across categories. This increases reusability, maintains uniformity and reduces maintainance. Workflow custom fields can be shared across applications.

Custom fields can be created of different types. Say you wanted to have a field called "Advance received?" for a project and users were expected to enter Yes or No. It is possible that sometimes users may enter "yes" or "no" (notice the lower case "y" and "n"). Now, if you wanted to a report to see the projects for which you have received advance, and you searched for the word Yes, you would not see the projects for which users had entered yes. Similarly if you wanted to have a "Advance Received On" which is supposed to be a date, users may enter it in different styles like Jan 10, 2009, 10/1/2009 or 10 Jan 2009. Having specific field types instead of a single plain text field ensures consistency and eliminates errors. The following field types are supported.

Additional attributes may be specfied for fields. For example,

Custom fields are treated like the standard fields. For example,