Which wildcard values can be used in Workfront reporting? (Select two.)

The correct answer is A. USER D. TEAM. In Adobe Workfront reporting, $$USER and $$TEAM are the two supported wildcard filter variables. $$USER dynamically references the currently logged-in user, allowing filters like "show me tasks assigned to me" to work for any user who runs the report. $$TEAM similarly…

Reporting and Dashboards

Question

Options

AUSER
BPROJECT
CROLE
DTEAM

How the community answered

(29 responses)

A
69% (20)
B
10% (3)
C
21% (6)

Explanation

In Adobe Workfront reporting, $$USER and $$TEAM are the two supported wildcard filter variables. $$USER dynamically references the currently logged-in user, allowing filters like "show me tasks assigned to me" to work for any user who runs the report. $$TEAM similarly references the logged-in user's Home Team, enabling team-scoped reports that adapt to whoever is viewing them.

PROJECT (B) and ROLE (C) are not valid Workfront wildcard values - while you can filter reports by projects or job roles, Workfront does not provide $$PROJECT or $$ROLE wildcard variables. Filters involving those objects require static or user-selected values, not dynamic wildcards.

Memory tip: Think of wildcards as answering "who is currently here?" - Workfront supports wildcards for the logged-in USER and their TEAM, because those are the two identities that change dynamically depending on who opens the report. Roles and Projects don't have that same "session-aware" dynamic identity in the reporting engine.

Topics

#wildcard values#USER wildcard#TEAM wildcard#report filters

Community Discussion

No community discussion yet for this question.

Full AD0-E907 Practice