Hi Michiel,
I'm afraid I ran the cowards race and chose to join last_name and
second_last_name into Users.last_name in UserObject->UserAdd and
UserObject->UserUpdate. This way I don't need to change lots of dtl files.
What I would like to do?
- Change all those «$QData{"UserFirstname"} $QData{"UserLastname"}» with
«$QData{"UserFullname"}»,
- UserObject->GetUserData would use UserObject->UserName to create
$User{'UserFullname'},
- UserObject->UserList would use UserObject->UserName to build the fullname of
the elements of the list,
- I would create a config option which would allow admins to define a
UserFullnameTemplate using UserData fields (maybe several templates: short,
long, last_name first, initials, et cetera).
But I don't have time nor resources to do it properly.
Kind regards,
Juan Clavero
OTRS 3.1 on CentOSLinux [Apache and MySQL ]
connected to an Active Directory for Agents and Customers.
-----Mensaje original-----
Date: Sat, 6 Apr 2013 14:22:43 +0200
From: Michiel Beijen <michiel.bei...@gmail.com>
Subject: Re: [dev] Full name of agents
To: "Development community of OTRS. org" <dev@otrs.org>
Message-ID:
<cabd0r116z7mi1f8xw+umgaxhkuokbb04e-y1x3rcwn5ohwr...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
This is an interesting issue. I had a similar problem. In The Netherlands
people have a middle name sometimes:
First name: Louis
Middle name: van
Last name: Gaal
The middle name belongs to the last name, you would say "Mr Van Gaal" but some
systems store the middle name in a separate field. This is even required for
governmental systems. In that case you can get trouble mapping the names to
OTRS.
It would be the best I think to use the full name function you mentioned, where
you can map all fields you want, to create a Full Name field and include it so
you can use it in all the places we now have ?UserFirstname UserLastname?. What
do you think?
Mike
Op 5 apr. 2013 13:13 schreef "Juan Manuel Clavero Almir?n" <
juanm.clav...@ibsalut.es> het volgende:
> Hi all,
>
> In several countries in the world (among them, Spain), people have a
> first name (simple or compound) and _two_ family names (one for each
> parent)...
> there are all sort of variations according to family tradition and
> nobility, and lately due to different forms of family.
>
> Now I've been asked to customize OTRS agents to the spanish way: ldap
> stores the information and I can retrieve and store it: firstname and
> lastname in it usual place (DB->users) and second lastname and any
> variation as user preference (DB->user_preferences).
>
> My problem is how to show it: UserObject->Username is easy to modify,
> but is almost never used... and there are too many different places
> where it's shown using $QData{"UserFirstname"} $QData{"UserLastname"}
>
> Anybody has done something similar?
>
> Kind regards,
> Juan Clavero
>
> OTRS 3.1 on CentOSLinux [Apache and MySQL ] connected to an Active
> Directory for Agents and Customers.
>
> _______________________________________________
> OTRS mailing list: dev - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/dev
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.otrs.org/pipermail/dev/attachments/20130406/bdfc51c7/attachment-0001.html>
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
