The CustomerID can also be a "short code" (like company initials) that
links to the Company table (if CustomerCompanySupport is enabled, and since
CustomerID is visible everywhere, using unique numbers isn't helpful. In
fact, CustomerID doesn't have to be unique as it's sometimes helpful to
have members of the same company have the same CustomerID.
By default, the CustomerID is the email address of a customer for inbound
emails, though they don't automatically populate the Customer database.
Like I said, this value is visible everywhere, so using an auto-increment
number is going to just get in the way. If you can't figure out what to use
in its place, and don't want to use email address, consider using the phone
number or other customer-identifying attribute, such as CRM customer number
by which you might want to later report, as this will be directly added to
the ticket table upon ticket creation for this user.
On Fri, Nov 23, 2012 at 8:24 AM, Neil Simpson
Hi,
i think im missing a minor thing but can't find solution.
I have a postgresql 8.1.23 DB and otrs 3.1.6. The customer db is currently blank, when i go to add a customer to it via otrs gui i would like the customer_id to be an auto-number but i dont see how to do that. likely some DB magic but im not a dba and little experience in postgres. I can currently add any number to that field.
to be clear, what i would like: i enter customer A and he gets customer id number 00001, i enter customer B and he gets number 00002 and so on. Auto number that can't be tampered with from gui, only directly in DB.
thank you for any insight.
Neil
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs