How do I build a report to see all upcoming Task Approvals based on role ID? | Community
Skip to main content
AndrewGr1
AndrewGr1
Level 3
December 2, 2024
Solved

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

  • December 2, 2024
  • 1 reply
  • 1414 views

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!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sven-iX

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

 
 

1 reply

Sven-iX
Community Advisor
Sven-iXCommunity AdvisorAccepted solution
Community Advisor
December 2, 2024

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

 
 

    AndrewGr1
    AndrewGr1Author
    Level 3
    December 3, 2024

    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

      

    Sven-iX
    Community Advisor
    Sven-iXCommunity Advisor
    Community Advisor
    December 3, 2024

    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. 

      Terms & ConditionsAccessibility statement

      Loading footer...