2 messages in com.mysql.lists.eventum-usersRe: Eventum Customer Questions| From | Sent On | Attachments |
|---|---|---|
| Dolim | 19 Apr 2005 16:42 | |
| Bryan Alsdorf | 25 Apr 2005 01:36 |
| Subject: | Re: Eventum Customer Questions |
|---|---|
| From: | Bryan Alsdorf (bry...@mysql.com) |
| Date: | 04/25/2005 01:36:02 AM |
| List: | com.mysql.lists.eventum-users |
Hi Dolim,
Dolim wrote:
Hi,
I am currently running Eventum 1.5.1 on FreeBSD and I how a few questions in regards to the customer aspect of Eventum.
I am attempting to store customer data into the Eventum database, but I am uncertain of the usr_customer_contact_id and the usr_customer_id fields on how they might be used. My thoughts are that the customer's company and the customer itself - contacts in the example are stored in the same database. It is only the context and interpretation that differentiates the two. For example, Joao Inc. would be a customer, so its record would have an ID in the usr_customer_id field. Any reps/sales/contacts from Joao Inc. would also be in the same table, except that each person will have an ID in the usr_customer_contact_id field. Is this interpretation correct?
I cannot totally understand your interpretation, but from what I do understand it sounds correct.
Some of the necessary fields are in the database table like: user id, group id of the group that the user belongs to, full name, email, password, but there are no fields to store the customer's company name, telephone number, and fax number.
One thing you _must_ realize to properly understand the Eventum customer API is that Eventum isn't setup to contain all customer information. It is designed to integrate with an existing customer database.
In the example, a complex data structure is used to present what a possible implementation might look like. However, I would like to fetch the data from the database instead of parsing the data structure. Does anyone have an example or insight into some implementation methods and/or ideas?
There has been a lot of discussion of the Customer API on this list so I am sure people have written there own customer API's that store data in a database, but I have not seen any actually if released. Hopefully someone with more time then me will be able to release an implementation that will work with an existing customer system (such as SugarCRM).
At the moment, I only need a customer's name and their email address as the basic minimum, but I will be putting in more info for the customer in the future.
Furthermore, there are also the user types. What is the difference between a "standard user" and a "developer"?
The differences are pretty minor. I don't have a listing of what each level can or cannot do (though I wish I did). Developers just have a few more options and UI changes like the 'Assign Issue to Myself' button.
Regards, /bryan