Properties Forms

most activate objects can have a properties form that is shown on the activate web portal the properties form is used to display information about the object to the user for example, a properties for a user would normally show these name, title, roles, services etc the property form is normally stored in a parameter called 'web properties' the standard system comes with default 'web properties' for all activate objects and they are generally stored at the root of the object trees these could be override if required at a lower level, however, this is discouraged unless absolutely necessary as it makes upgrading more difficult user property forms user property forms are obtained slightly differently to the other property forms the user property forms check for property forms called 'web user properties' on each of the users roles where the current user has 'view' rights on the role if one is found then this is used, otherwise a default web user properties from //resources/users the pseudo code for this is given below foreach(role r in user roles) if(user has r viewmembers and r has web user properties) return web user properties return resources/users/web user properties if a user doesn't have rights to view members of a role this will often present with an issue where the full tabs and toolbars don't show on user properties how to setup direct reports one suggested setup is to give the roles/system roles/users rights to view members of direct reports this setup enables managers to view the full properties of their direct reports faq how do i make a tab visible for all users viewing a user's properties? resources/users/web user properties form is the form that shows for users that don't have view rights on the web user properties full form you can add new tabs and other controls to this form to be visible to users who don't have full view rights