|
|||||||||
|
|||||||||
![]() |
![]() |
Documentation >> Custom Fields >> Introduction: What is a Custom Field?Introduction - What is a Custom Field?Conversant messages are stored in a database, and every 'part' of a message is a field in that database. This includes the subject, body, creation date, modification date, id(s) of the person(s) that created and last modified the message, the id of the message's label, and information about the message's attachments. Messages are very flexible, the fields in a message are sufficient for basic needs. Still, it's impossible for a single database structure (schema) to serve every need, even if the scope of the database is limited to information that can be stored in messages. Conversant solves this problem with custom fields. They allow you to extend the message database by defining additional cells (columns). These columns are fully indexed and searchable, come in a variety of styles, and can be used to add the data you need for your message-based applications. There are many possible uses for custom fields. Text fields could be used for adding keywords to a message, or for summarizing the contents of the message. Date fields might be used for... well, adding a date to the messages (what else would you do with a date field?). There are two kinds of list fields, and they're great for categorizing messages in different ways. With all of the options presented by custom fields, you might be wondering where the limits are. How far can you take this feature? We suggest that you primarily use custom fields for meta data - information that describes the messages. We do not recommend that you use custom fields to extend the database too far from its roots as a message database. Default Values
Learn by Doing!View in DG |
![]() |
||||||
This site managed with Conversant, © Copyright 2010 Macrobyte Resources |