Hello all. We're looking to add otrs to an existing system, which contains large amounts of customer information. The customers all have a unique identifier, and I would like to be able to use that same identifier in otrs. Basically, I want to keep our existing customer data in our existing system, and offload the support/tickets/related stuff to otrs. Can someone point me in the right direction to do this? Writing a few modules/components to pull data from our existing system isn't an issue, I'm just looking for pointers of where to start. Thanks.
On 14 Jun 2005 at 16:46, Jeremy Blain wrote:
We're looking to add otrs to an existing system, which contains large amounts of customer information.
The customers all have a unique identifier, and I would like to be able to use that same identifier in otrs.
Basically, I want to keep our existing customer data in our existing system, and offload the support/tickets/related stuff to otrs.
The easy way would be to have an existing LDAP interface to your actual customer database. Then following this example shouldn't be too difficult to fetch your customer data from your current system: http://doc.otrs.org/1.3/en/html/customer-user-backend.html
Can someone point me in the right direction to do this? Writing a few modules/components to pull data from our existing system isn't an issue, I'm just looking for pointers of where to start.
Another approach would be to export your customer data from your actual system and import it in OTRS user database periodically. I think that it would be easier than writing a perl module to allow OTRS to speak with your current user DB. Regards, --- Victor R. Rodriguez Departamento de Sistemas Valoraciones del Mediterraneo, S.A. ---
participants (2)
-
Jeremy Blain -
Victor Rodriguez Cortes