- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
2 weeks ago
I'm working on RITM approvals and need to modify the default group approval behavior. I have a custom field 'approvers' (List of Users type) on the Group table that contains specific users who should receive approval requests.
My requirements:
- Use Group Approval (not User Approval) to preserve which groups were requested
 - Only users in the custom 'approvers' field should get approval requests, not all group members
 - Don't want to manually extract user sys_ids and use individual user approvals
 
Current challenge:
When I use standard group approval, it sends requests to ALL active group members, but I only want the subset defined in my custom 'approvers' field.
I've considered scripted group approvals but want to ensure:
· It still shows as a group approval in the system
· The group relationship is maintained for reporting
· Only my specified approvers receive the request
Has anyone implemented something similar? What's the best approach - workflow script, business rule, or some other method that maintains the group approval context while filtering the actual approvers?
Solved! Go to Solution.
- Labels:
 - 
						
							
		
			Flow Designer
 - 
						
							
		
			Workflow Automation
 
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
2 weeks ago
got it.
then do this
-> let the approval go to that group using OOTB Ask for Approval
-> use before insert business rule on sysapproval_approver table and see if this is generated due to Group approval i.e. Group field not empty
-> then grab the custom list field and see if the current approver is allowed or not
-> if not then use setAbortAction(true) and record won't be inserted
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
2 weeks ago
@Ankur Bawiskar any idea on this?
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
2 weeks ago
@Lisa @Lisa Holenstein any solution available from your side?
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
2 weeks ago
I don't think a custom field is required on OOTB table.
You can use Scripted Flow approval and add your required group members if you are using Flow
Scripted Approvals in Flow Designer with Flow Variables
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
2 weeks ago
Hi @Ankur Bawiskar ,
If I use a scripted Flow Approval, I need to extract the sys_ids of users from each group and then use a user-level approval, such as ApprovesAnyU[sysid1, sysid2].
However, by doing this, we lose the context of which group the users belong to.
What I want is to use group approvals as usual, but with a modification — instead of sending approval requests to all group members, it should only send them to the users listed in the Approvers custom field within the group.
For example:
If a group has members [a, b, c, d] and the Approvers field includes [a, b],
then when I use group approval, approval requests should go only to [a, b].
