Hi all, I am about to make some changes to the customer user backend and I need a tiny bit of advice on how to go about.
On my site the generation of a CustomerUser record needs to follow a couple of rules: 1) UserLogin == UserEmail 2) Pasword is randomly generated 3) UserCustomerID is generated using a couple of address field that I added to the backend plus some other stuff. I can take a couple of routes: I can do it the easy (and crude) way which is by just adding and modifying the necessary code in the Kernel::System:CustomerUser::DB module. It is not very clean and OTRS version dependent of course. I can also take a more structured route so others can use it as well. In this case I need to add some stuff in the Configuration file. I could just do that by adding additional configuration entries for the rules as defined above but I could also extend the Map table which would be, IMHO, the cleanest and best reusable way. In the latter case I would add a column that defines the source of the data for the particular field, that could either be another field or a routine/module definition which needs to be called. Anyone has a specific opinion on this? Did I see all alternatives or am I missing one? Thanks for your time in advance. Kind regards, Tom Hesp _______________________________________________ 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
