Hi there!
Our instance has a custom field call 'Peer Reviewer' that we do not want our VMO team members to ever be input to as we want peer review to be done by internal team members only.
I did find a validation rule within workflow 'Restrict to when a field is a specific value' to not allow the individual VMO users to be input into the 'Peer Reviewer' field - see below. But this is not a great solution as it creates a lot of manual management with turnover and/or new hires.
Any ideas on how to apply VMO users to a group of some kind that would make it so that group of users cannot be added to the 'Peer Reviewer' field and those users in that group will be auto updated via Okta connection or something and not require so much manual touch?
You can set a user picker field to be restricted to a group of users so that only users in that group can be selected as users through the user filtering option:
Hopefully that helps meet the need!
Adding to this...
This context configuration requires you to select User Groups and/or Project Roles that contain people who CAN be selected. There is not an option to configure it to DISALLOW selection of members of specified groups or roles. You would have to select all the User Groups or Project Roles that would cover all the people who should be selectable while ensure that none of those you have specified also include members of the VMO Team.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.