Quick question that I'm hoping someone else has figured out :-)
I have a customer management system that allows multiple clients to
have their own lists of customers which are stored in an LDAP
directory. When a client logs in a basic set of preferences is
loaded into that users session from a database. This works fine except
now certain clients need completely different fields in their customer
add/search forms. I'm using a Webware/Cheetah solution and am trying
to figure out the best way to handle this extra 'variable' data that
needs to be added into the search form.
For example, one client is an auto dealer and they need 7 or 8 fields
that aren't part of the usual name, address, city, state zip, email,
etc. that most of the clients use. They need transaction type (new
car, used car, etc) and financing information (30, 60, 72 month lease
or sale), transaction date, vehicle make, vehicle model, vehicle year
and sales reps name. I have new customers coming on that are real
estate brokers, insurance agents, etc. each with their own sets of
fields they need to track.
As a quick solution, I created a Cheetah template that I attached to
the clients Preference object as a text field. then I "include" that
field into the search/add customer form templates. While this works
as quick solution, it's very unwieldy when it comes to making changes
to the preferences object. The preference object is a pickled Python
object that I read in upon login.
Any ideas would be greatly appreciated. one thought was to build a
user interface to the per client templates but that seems like a lot of
work since I don't necessary know what types of fields are going to be
needed in the future.
Thanks for any help