I was in the zone the last few days and I finished phase 1 of 4 of this project and committed to svn/trunk. I have also re-prioritized the development phases because the former phase 2(rewrite of the lead loader to include custom fields and import templates) looks like it is going to be a much larger job than I had initially though, and I would rather get custom entry forms and exporting working and in production rather than have it wait on loading custom fields pre-populated.
If you get a chance check it out and let me know what you think.
Keep in mind this is purely the admin and database side of things, there is currently no agent interface use of these fields.
Here is a screenshot of the edit custom fields page:
http://www.vicidial.org/images/custom_l ... enshot.jpg
And here are the help entries for it so far:
Field Label - This is the database field identifier for this field. This needs to be a unique identifier within the custom fields for this list. Do not use any spaces or punctuation for this field. max 50 characters, minimum of 2 characters.
Field Name - This is the name of the field as it will appear to an agent through their interface. You can use spaces in this field, but no punctuation characters, maximum of 50 characters and minimum of 2 characters.
Field Description - The description of this field as it will appear in the administration interface. This is an optional field with a maximum of 100 characters.
Field Rank - The order in which these fields is displayed to the agent from lowest on top to highest on the bottom.
Field Help - Optional field, if you fill it in, the agent will be able to see this text when they click on a help link next to the field in their agent interface.
Field Type - This option defines the type of field that will be displayed. TEXT is a standard single-line entry form, AREA is a multi-line text box, SELECT is a single-selection pull-down menu, MULTI is a multiple-select box, RADIO is a list of radio buttons where only one option can be selected, CHECKBOX is a list of checkboxes where multiple options can be selected, DATE is a year month day calendar popup where the agent can select the date and TIME is a time selection box. The default is TEXT. For the SELECT, MULTI, RADIO and CHECKBOX options you must define the option values below in the Field Options box.
Field Options - For the SELECT, MULTI, RADIO and CHECKBOX field types, you must define the option values in this box. You must put a list of comma separated option label and option text here with each option one its own line. The first value should have no spaces in it, and neither values should have any punctuation. For example - electric_meter, Electric Meter
Field Size - This setting will mean different things depending on what the field type is. For TEXT fields, the size is the number of characters that will show in the field. For AREA fields, the size is the width of the text box in characters. For MULTI fields, this setting defines the number of options to be shown in the multi select list. For SELECT, RADIO, CHECKBOX, DATE and TIME this setting is ignored.
Field Max - This setting will mean different things depending on what the field type is. For TEXT fields, the size is the maximum number of characters that are allowed in the field. For AREA fields, this field defines the number of rows of text visible in the text box. For MULTI, SELECT, RADIO, CHECKBOX, DATE and TIME this setting is ignored.
Field Default - This optional field lets you define what value to assign to a field if nothing is loaded into that field. Default is NULL which disables the default function. For DATE field types, the default is always set to today unless a number is put in in which case the date will be that many days plus or minus today. For TIME field types, the default is always set to the current server time unless a number is put in in which case the time will be that many minutes plus or minus current time.
Field Cost - This read only field tells you what the cost of this field is in the custom field table for this list. There is no hard limit for the number of custom fields you can have in a list, but the total of the cost of all fields for the list must be below 65000. This typically allows for hundreds of fields, but if you specify several TEXT fields that are hundreds or thousands of characters in length then you may hit this limit quickly. If you need that much text in a field you should choose an AREA type, which are stored differently and do not use as much table space.
Field Required - If set to Y, this field will force the agent to enter text or select an option for this field. Default is N.