I did same thing when I implemented for my previous employer.
Regards Anil Patel On Jun 9, 2008, at 3:02 PM, Adrian Crum wrote:
David E Jones wrote:I can think of two main ways of doing this:1. list explicitly/inline the roles you want to show (instead of doing a query) 2. create a parent role and put the roles you want under it and query by the parent IDI like idea #2. Using that approach, a user could expand the list just by adding child roles.As for which roles to use, and whether to create or not, it's totally okay to add new roles but you might consider keeping the roles used more general and use ideas like "manager" and "worker" (or assignee, performer, whatever) instead of very specific ones.I was planning on keeping it as generic as possible. Thank you for the advice! -AdrianOn Jun 9, 2008, at 11:45 AM, Adrian Crum wrote:I have expanded the functionality of Asset Maintenance. Currently, maintenance tasks are assigned automatically to the logged-in user and there is no way to change it or assign the task to someone else. I have added the ability to assign maintenance tasks to someone else.The assignment requires a party role. Presenting the user with a list of all roles to pick from is not user-friendly because the list is quite long. I would like to have a smaller list that is more Fixed Asset Maintenance specific. I'm not sure how I should implement the smaller role list.I'm thinking the list should contain three roles: an outside service, a maintenance manager, and a maintenance worker. Should I use existing roles, or create new ones?Another idea is to populate the list with parties/roles that are already related to the fixed asset in question.Any advice would be appreciated! -Adrian
smime.p7s
Description: S/MIME cryptographic signature
