As of Aeon v5.1, custom fields have been added to existing DLL tags and can be displayed on any of the web pages once configured in the Customization Manager's Custom Field Definitions table.
<#PARAM name="[Context].CustomFields.[ShortName]">
<#USER field="CustomFields.[ShortName]">
<#TRANSACTION field="CustomFields.[ShortName]">
<#ACTIVITY field="CustomFields.[ShortName]">
<#DATAROW field="[Context].CustomFields.[ShortName]">When formatting these tags, "[Context]" should be replaced with the custom field's context type (Transaction, User, or Activity), and "[ShortName]" replaced with the custom field's short name.
Configuring Display Options
Additional display options are available for custom fields of certain data types:
| Data Type | Display Options |
| DateTime | "ISO8601" - Format date according to the ISO8601 standard. |
| Boolean |
"YesNo" - The value of the field will display as "Yes" when True and "No" when False "TrueFalse" - The value of the field will display as "True" when True and "False" when False |
These options are set in the tag's "display" attribute. For example:
<#USER field="CustomFields.[ShortName]" display="YesNo">Adding Custom Fields to Web Forms
After configuration in the Customization Manager, a custom field can be added as an additional input field on any of the relevant web forms. For specific configuration instructions and examples, please see Adding Custom Fields to Web Forms.
Adding Custom Fields to the WebValidation Table
After configuration in the Customization Manager, a custom field can be added as a required field to the Customization Manager's WebValidation table (located under Web Interface | Validation). The Fieldname and Error Tag columns for the custom field's entry in this table should use the following formatting when referencing the field, where ContextType is Transaction, User, or Activity and ShortName is the short name defined for the field in the CustomFieldDefinitions table:
| Fieldname | [ContextType].CustomFields.[ShortName] |
| Error Tag | ERRORCustomFields.[ShortName] |
OpenURL
Custom fields can be mapped via OpenURL. The AeonFieldName in the OpenURLMapping table should be in the format "Transaction.CustomFields.[ShortName]".