I'm not sure you're going to be able to change this. I think (but I'm afraid I don't know for sure) the section is defined by \WEB-INF\uitemaplates\com\nakisa\manager\omg\ui\subucs\sectionDesigners\DetailHistoryButtonSectionSubUC.xhtml, which after a quick search through the application looks as though it might be populated by a NakisaTrollBin.jar ... which isn't really something you should be looking to edit.
Nakisa do often write in various settings that can allow features to be tweaked and enabled/disabled. It could be that there's something you could add into SettingsResources to apply the change you require, but you would need to contact Nakisa about this as they don't document all of these options.
All this being said I would query why this is being done. It is not uncommon to say have multiple positions with the same name - e.g. HR Administrator might exist in several org units. If you are looking through several identically named org units or positions, the unique identifier is going to be the object's ID. As such it seems most logical to me to keep the ID in the history to allow a user to discern the difference between identically named positions/org units.
Regards,
Stephen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.