W
Wim
Guest
Hello, We generated an application for vehicletyre management. Most of the objects should only be readable for the 'standard' user. However in the order object a lot of objects come together like vehicletype, ordertype, contracttype, tyresize, tyretype, etc. Al the standard users can 'see' the relation between the order and the mentioned related objects. But also the hyperlinks leads them to the specific object when they click on it. That is not wat we like to see. We managed some extra fields to avoid that behaviour, with the type 'expression' field. Would it be possible to make a difference in the behaviour that if a user has only read-rights the hyperlink (as based on the related object) will not lead him to that specific object, where a 'application owner' role does. Meaning that in the definition of the objects like read, write, etc per role it would also be possible to decide that that specific role may read but the hyperlink will not 'work/guide to that specific object' for those roles. Maybe there is a work around instead of 'expression' fields, because adding expression fields to the objects looks a bit 'overdone'. Of course the read functionality through combo boxes or lookup needs to stay available, so selection can be made. But afterwords the 'hyperlink' should be ignored or left away for the specific role. Hope to hear your commands on this. Regards, Wim
Continue reading...
Continue reading...