As of v5.1, Aeon supports the creation of new custom fields for Transactions, Users, and Activities. These fields are created and defined in the Customization Manager's Custom Field Definitions table.
Creating Custom Field Definitions
The Custom Field Definitions table is located in the Customization Manager under System | General | CustomFieldDefinitions. Once a field definition has been entered in the Custom Field Definitions table, that field will be available on all Transactions, Users, or Activities (depending on which context type is chosen). Fields are always blank when first created.
Definitions include the following properties:
|This value is auto-assigned.
|Can be Transaction, User, or Activity. This determines which forms, web pages, etc. will have access to the field.
|The type of data that will be stored in the field. Options are:
|The name of the field used in internal processes. (See "Short Name Restrictions" section)
|The display label for the field that will be used in the Aeon Client.
Short Name Restrictions
Short names are used in some internal queries, and so have the following restrictions:
- Short names may contain only alphanumeric characters and underscores
- No two custom field definitions may have the same short name
- Short names may not have the same name as the primary key of the table to which they apply (e.g. Transaction custom fields cannot be called TransactionNumber)