Customizing the LDAP fetching

Hello OTRS list, I have successfully got an OTRS 2.4.7 installation up and running with LDAP based customerinfo + some custom fields also fetched from LDAP. There is however some things I'd like to do with the fetched data before returning them, how would I go forward to do this? IE: I'd like to get 2 attributes from an object, then do a IF statement on them, with output coming from the IF / ELSE instead of just the RAW output being parsed directly to the frontend, for example the compose view. How should I go forward with fetching more then 2 user objects? Our users are defined several places for different roles, I'd like to do a tree walk for the same user object found one place, in another place, almost identical structure, if returned, then showing below customer info as its own category with the fetched LDAP info from here too (in compose view for instance). Can I also based on the LDAP do a fetch within the same CustomerInfo, to another module / script and return to the main map for the user. (Our department info is not stored in LDAP, its stored in an external database that can return the information based on the username specified.) Last Question -> There is also dynamic data stored on the user, will this get fetched every time I open the post after save too, based on username or just on the compose? Ideally every time the post is opened for at least one part of the post, ideally a small standalone script/module that fetches this. Thanks for all replies (-: Best Regards, Rune "TheFlyingCorpse" Darrud
participants (1)
-
Rune 'TheFlyingcorpse' Darrud