We are planning to use OTRS for a medium-sized project merely for call-logging.
For that we have a customer database.
I imported the user database into OTRS.Customer_users and works fine.
However to search for a customer you have to give a name, email or customer_id in the search field.
My question is, how can I extend this search so that I can search for other attributes like zip-code (that's most important attribute).?
Currently i'm exploring "kernel\modules\AdminCustomeruser.PM", but I haven't find a solution yet.
OTRS Customer search
Moderator: crythias
-
- Znuny newbie
- Posts: 61
- Joined: 17 Dec 2010, 13:22
- Znuny Version: 3.0
OTRS Customer search
OTRS 3.0.7 with MySQL on Windows server 2003 r2 server with AD integration for customers.
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: OTRS Customer search
You can add zip code in the search criteria of Config.pm. You may have to copy stuff from Defaults.pm. Take a look at the admin manual.
zip code is not exactly a one-to-one search, though. It could be for you, but ...
zip code is not exactly a one-to-one search, though. It could be for you, but ...
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
- Znuny newbie
- Posts: 61
- Joined: 17 Dec 2010, 13:22
- Znuny Version: 3.0
Re: OTRS Customer search
thnx!
Worked:
CustomerID => 'customer_id',
CustomerValid => 'valid_id',
CustomerUserListFields => [ 'first_name', 'last_name', 'email', 'zip' ],
# CustomerUserListFields => ['login', 'first_name', 'last_name', 'customer_id', 'email'],
CustomerUserSearchFields => [ 'login', 'first_name', 'last_name', 'customer_id', 'zip' ],
CustomerUserSearchPrefix => '*',
CustomerUserSearchSuffix => '*',
CustomerUserSearchListLimit => 250,
CustomerUserPostMasterSearchFields => ['email'],
CustomerUserNameFields => [ 'title', 'first_name', 'last_name' ],
CustomerUserEmailUniqCheck => 1,
Worked:
CustomerID => 'customer_id',
CustomerValid => 'valid_id',
CustomerUserListFields => [ 'first_name', 'last_name', 'email', 'zip' ],
# CustomerUserListFields => ['login', 'first_name', 'last_name', 'customer_id', 'email'],
CustomerUserSearchFields => [ 'login', 'first_name', 'last_name', 'customer_id', 'zip' ],
CustomerUserSearchPrefix => '*',
CustomerUserSearchSuffix => '*',
CustomerUserSearchListLimit => 250,
CustomerUserPostMasterSearchFields => ['email'],
CustomerUserNameFields => [ 'title', 'first_name', 'last_name' ],
CustomerUserEmailUniqCheck => 1,
OTRS 3.0.7 with MySQL on Windows server 2003 r2 server with AD integration for customers.