Page 1 of 1

Additional Form

PostPosted: Wed Apr 03, 2013 1:23 pm
by fibres
Hi Guys

Is the additional form feature from OSDial available in Vicidial?

I saw it on their site on a screen shot, I understand that OSDial is based on Vicidial so wondered if Vicidial had similar features.

Regards

Re: Additional Form

PostPosted: Wed Apr 03, 2013 10:02 pm
by mflorell
OSDial is a very old fork of Vicidial, and it is missing a lot of features available in the current versions of the Vicidial code. That said, we added Custom List Fields a couple years ago to Vicidial. This is how we do custom fields in a very customizable and very scalable way.

Re: Additional Form

PostPosted: Wed Apr 03, 2013 11:30 pm
by williamconley
In Vicidial, when you create custom fields in a List, you are actually building a custom "Form" with those fields in it. This becomes a new tab available for the agents in addition to the standard client data tab and the Script tab. The campaign can be configured to show this new Custom Form by default for the agent ... which sounds an awful lot like an "additional form feature" to me. but try to avoid using "OSDial" on this forum as that software is so obsolete people may ignore you. LOL

Custom fields must be activated in system settings, and then your user must have "Custom fields modify" activated to allow you to see/create custom field entries and menus.

It is an excellent feature and has matured quite well. Solidly implanted in the system now and thoroughly tested.

happy hunting. 8-)

Re: Additional Form

PostPosted: Thu Apr 04, 2013 7:48 am
by fibres
Hi

Thanks for clearing that up Matt. I wasnt looking to use OSDial as I know Vicidial and have been using it a long time.

Thanks for the pointers william. I have looked at the custom list bit and it looks really good. Did exectly what I wanted in minutes.

One query though. Where exactly in the database does it store this information? As in the results that are gained from the custom fields?

Regards

Re: Additional Form

PostPosted: Thu Apr 04, 2013 3:15 pm
by williamconley
each list has a "custom_XXXX" table created. If you move a lead to another list, you must populate the origin list field in that lead before moving it so the system knows where its custom data is stored.

the custom table is not created until there is data in at least one lead (requiring a place to store the data, of course).