Expand my Community achievements bar.

Latest Community Ideas Review is Out: Discover What’s New and What to Expect!
SOLVED

How do I build a report to see all upcoming Task Approvals based on role ID?

Avatar

Level 4

For my Proofreading team, I would like to have a report to see all upcoming task approvals based on a role ID to see what work may be coming through. I tried messing with EXISTS statements from previous forum posts to see if I could manipulate any, but I didn't have any luck. The approvalStep name usually contains "Proofer" as well, but I couldn't figure out a way to filter by that either. I appreciate any suggestions on how to approach this. I don't want to only see current/active approvals either; I want to see all projects with task approvals that could come through. 

 

Thanks for any support!

1 Accepted Solution

Avatar

Correct answer by
Level 6

Hi @AndrewGr1 

a task has a collection "approvalStatuses" you can use.

 

Try an EXISTS filter like this and replace "###" with the roleID you need. 

EXISTS:a:$$EXISTSMOD=EXISTS
EXISTS:a:$$OBJCODE=ARVSTS
EXISTS:a:stepApprover:roleID=################
EXISTS:a:taskID=FIELD:ID  

 
 

View solution in original post

6 Replies

Avatar

Correct answer by
Level 6

Hi @AndrewGr1 

a task has a collection "approvalStatuses" you can use.

 

Try an EXISTS filter like this and replace "###" with the roleID you need. 

EXISTS:a:$$EXISTSMOD=EXISTS
EXISTS:a:$$OBJCODE=ARVSTS
EXISTS:a:stepApprover:roleID=################
EXISTS:a:taskID=FIELD:ID  

 
 

Avatar

Level 4

This didn't give me all upcoming approvals assigned to just the proofreaders unless the roleID itself was part of the approval loop. So, I ended up manipulating the code to use userIDs and manually added all those in. I will just have to update it as new people join the team. If you have other suggestions, I appreciate the support. Thanks, Sven-iX!


EXISTS:a:$$EXISTSMOD=EXISTS
EXISTS:a:$$OBJCODE=ARVSTS
EXISTS:a:stepApprover:userID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx	xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
EXISTS:a:taskID=FIELD:ID
project:status=CUR
project:status_Mod=in
status=CPL
status_Mod=notin

  

Avatar

Level 6

Oh - yes of course: I put the role into the stage approver field - I thought that's what you were doing! 

you could TRY stepApprover:user:roleID but that may be one hop too far. 

 

I'd recommend to create a team for these approvers and use that in the approval step, or use the role in the step. 

Avatar

Level 4

Thanks for the suggestion. WF didn't like that parameter unfortunately:

AndrewGr1_0-1733261500401.png

 

Avatar

Level 6

Yeah I had a feeling  
Are you able to modify the approval paths to include a team so you don't have to keep adding userIDs to the report? 

Avatar

Level 4

That's a possibility depending on how we want to use teams. Thanks for the suggestion. It's not that often we add new proofreaders to the team, so it's not a big lift to adjust the report as needed for now.