Hi OTRS users (and developer),
sorry, but I have to come back to my question, because I am bothered by this problem on the besides that really fine running system:
Gerold Gruber wrote:
Hi,
we use otrs for a couple of months now and become more and more familiar with the system. Recently we updated to 1.2.4, we run on SuSE with postgres.
One thing I noticed now, where I would really look for a solution: I configured the customer info to be shown (config see below), but it is not always shown as I would expect: a) when the ticket has a customer user and a customer assigned, then the customer user info is only shown for cus.user with a completly lowercase email adress (=login) (admin area, customer user data). b) when the ticket has only a customer assigned and no customer user, then one customer users data is shown (customer all lowercase so far here), even that of an invalid customer user, that belonged to that customer!
How can I make the customer user data show up in case a), when the customer user email resp. login contain uppercase letters? Why did I see infos of an invalid customer user in case b)?
Best regards
Gerold
from Config.pm: (additional fields in database created, this works)
# ShowCustomerInfo*
# (show customer user info on Compose (Phone and Email), Zoom and Queue view)
$Self->{ShowCustomerInfoCompose} = 1;
$Self->{ShowCustomerInfoZoom} = 1;
$Self->{ShowCustomerInfoQueue} = 0;
# CustomerUser
# (customer user database backend and settings)
$Self->{CustomerUser} = {
Name => 'Database Backend',
Module => 'Kernel::System::CustomerUser::DB',
Params => {
Table => 'customer_user',
},
# customer uniq id
CustomerKey => 'login',
# customer #
CustomerID => 'customer_id',
CustomerValid => 'valid_id',
CustomerUserListFields => ['first_name', 'last_name', 'email'],
CustomerUserSearchFields => ['login', 'last_name', 'customer_id'],
CustomerUserPostMasterSearchFields => ['email'],
CustomerUserNameFields => ['salutation', 'first_name', 'last_name'],
# ReadOnly => 1,
Map => [
# note: Login, Email and CustomerID needed!
# var, frontend, storage, shown, required, storage-type, http-link
[ 'UserSalutation', 'Salutation', 'salutation', 1, 0, 'var' ],
[ 'UserFirstname', 'Firstname', 'first_name', 1, 1, 'var' ],
[ 'UserLastname', 'Lastname', 'last_name', 1, 1, 'var' ],
[ 'UserLogin', 'Login', 'login', 1, 1, 'var' ],
[ 'UserPassword', 'Password', 'pw', 0, 1, 'var' ],
[ 'UserEmail', 'Email', 'email', 0, 1, 'var' ],
[ 'UserPhone', 'Fon', 'phone', 1, 0, 'var' ],
[ 'UserMobile', 'Mobil', 'mobile', 1, 0, 'var' ],
[ 'UserFax', 'Fax', 'fax', 1, 0, 'var' ],
[ 'UserCustomerID', 'CustomerID', 'customer_id', 0, 1, 'var' ],
[ 'UserComment', 'Comment', 'comments', 1, 0, 'var' ],
[ 'ValidID', 'Valid', 'valid_id', 0, 1, 'int' ],
],
};
_______________________________________________ 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 Support oder Consulting f�r Ihr OTRS System? => http://www.otrs.de/
