Expand my Community achievements bar.

Don’t miss the Workfront AMA: System Smarts & Strategic Starts! Ask your questions about keeping Workfront running smoothly, planning enhancements, reporting, or adoption, and get practical insights from Adobe experts.

I need help with a document report filter. I want to show documents uploaded to an issue where the user team is assigned to a private approval process

Avatar

Level 1

Hey Community. It is a bit complicated.

I have issues/requests with documents attached.

Approval processes are also added to the issues/requests.

There are teams assigned to the approval processes.

 

Besides other filters I want to show documents where the user is part of the approver team. But I don't get to the data via EXISTS statement.

 

This is what I currently have:

currentVersion:proofID_Mod=notblank
EXISTS:A:$$OBJCODE=OPTASK
EXISTS:A:ID=FIELD:opTaskID
EXISTS:A:teamAssignment:teamID=$$USER.teamIDs
EXISTS:A:teamAssignment:teamID_Mod=in
opTask:status=CLS	RLV
opTask:status_Mod=notin
OR:1:currentVersion:proofID_Mod=notblank
OR:1:opTask:status=CLS	RLV
OR:1:opTask:status_Mod=notin
OR:1:owner:homeTeamID=$$USER.teamIDs
OR:1:owner:homeTeamID_Mod=in

The last OR filter for approver teams is missing because i don't know how.

Last try was:

OR:1:EXISTS:B:$$OBJCODE=OPTASK
OR:1:EXISTS:B:ID=FIELD:opTaskID
OR:1:EXISTS:B:approvalProcess:accessorIDs=$$USER.ID
OR:1:EXISTS:B:approvalProcess:accessorIDs_Mod=contains

But this doesn't work
Thanks in advance

3 Replies

Avatar

Community Advisor

your question is similar to this one:
https://experienceleaguecommunities.adobe.com/t5/workfront-questions/report-filter-for-tasks-using-c... 

 

I would recommend that you go through the ARVSTS object as well. Link it to the opTaskID instead of the taskID. I am guessing... do you have a team assigned to the approval and that's what you're trying to get? if so, that would probably be stepApprover:teamID or something along those lines.

 

You don't need the AA line unless you're angling for a particular status.

 

For more on EXISTS statements, we're holding a webinar at the end of the month.
https://events.teams.microsoft.com/event/2699d8d3-233a-4f57-92f1-0e8bfaa01f1f@fa7b1b5a-7b34-4387-94a...

Avatar

Level 1

Hi skyhansen,

thanks for you support. Unfortunately it doesn't work.
I tested it on a copied document report with just this filter added.

I've tried:

EXISTS:A:$$OBJCODE=ARVSTS
EXISTS:A:opTaskID=FIELD:ID
EXISTS:A:stepApprover:teamID=$$USER.teamIDs

and

EXISTS:A:$$OBJCODE=ARVSTS
EXISTS:A:opTaskID=FIELD:ID
EXISTS:A:stepApprover:teamID=$$USER.teamIDs
EXISTS:A:stepApprover:teamID_Mod=contains

I also tried the userID but I don't get any results in the document report.

Avatar

Community Advisor

Oh, sorry, I should have been more clear -- the problem above is with your linking line. You are looking to link the "Approver Status" object (ARVSTS) to your document, and mentally your question should be "what do they have in common", and the answer is that both objects have an issue ID and that's what they have in common with each other. The issue ID in both of the objects (document and approver status objects), is called opTaskID. So in your case it would be an EXISTS:A:opTaskID=FIELD:opTaskID (you are telling your report, this is the field that is in common and should be used to link)