Follow
Wildcard Filter Variables

***

The highlighted information on this page refers to functionality not yet generally available. It is available only in the Preview Sandbox environment.

Workfront supports filter variables or wildcards when building the following elements:

By using wildcards, you can reference a generic user or date instead of a specific user or date. In this way, the elements you build are dynamic and the results change depending on the context in which they are used. 
For example, filtering for $$USER.homeGroupID in a project report retrieves only projects associated with the Home Group of the user who is logged in. 

You can use the following types of filter variables in Workfront: 

Date-Based Variables

The Workfront date-based wildcard options can be used in combination with any date filter attribute. Choose from the following date-based wildcards:

$$TODAY

We recommend that you build date-sensitive filters using this wildcard so you avoid building the filter again tomorrow, next week, or next month.

For example, if you want to display all tasks due before today, you can use the following rule in a task filter: Planned Start Date Less Than $$TODAY

$$TODAY is always equal to midnight for the current day.

$$NOW

This is similar to the $$TODAY wildcard but includes the current date and time.  $$NOW is equal to the current date and time.

For example, if you want to display all hour entries provided up to the current time, you can do this by using the following rule in an hour filter: Planned Start Date Less Than $$NOW

NOTE This wildcard is not supported in the Resource Planner.

To indicate various periods of time and various points in time (future or past), you can combine wildcards with the following: 

Attributes  
  q calendar quarter
  h hour
  d day
  w week
  m month
  y year
Qualifiers  
  b beginning
  e ending
Operators  
  + add value to wildcard value
  - subtract value from wildcard value

For example, the wildcard $$TODAYb+2w refers to "two weeks from the beginning of this week". The wildcard $$NOW+2h refers to 'two hours from now'.

User-Based Variables 

IMPORTANT If a filter or report contains a user-based wildcard filter variable the results always show information filtered by the user who is currently logged in. When you share such a filter or report with another user, the wildcard retrieves information for the user looking at the report. The two users see different results. 

Workfront provides the following user-based variables:

$$USER.ID

The most common user-based variable is $$USER.ID. This always returns the ID of the logged in user. This is the ID used to identify which user created each object and their work assignments. 

When used in reports, this wildcard decreases the number of reports that you need to create in your system. You can create one report and share it with several users, and the results change based on the user who is logged in and looking at the report. 

For example, to build a report for all issues assigned to the user who is logged in, you can use the following rule in an issue filter: Assigned To ID Equals $$USER.ID.

Workfront uses this variable in the following built-in filters: 

  • My Reports
  • My Projects
  • My Tasks
  • My Issues
  • My Hours

$$USER.categoryID

The $$USER.categoryID variable refers to a specific custom form  associated with the logged-in user.

$$USER.accessLevelID

The $$USER.accessLevelID variable refers to the ID of the access level associated with the logged-in user.

$$USER.accessLevelRank

The $$USER.accessLevelRank variable refers to the access level rank associated with the logged-in user.

$$USER.companyID

The $$USER.companyID variable refers to the company associated with the logged-in user.

$$USER.customerID

The $$USER.customerID variable refers to the ID of the customer account associated with your environment. For your environment, there is only one possible value for this variable and it is typically used only when building integrations through the API.

$$USER.firstName

The $$USER.firstName variable refers to the first name of the  logged-in user. 

$$USER.lastName

The $$USER.lastName variable refers to the last name of the logged-in user.

$$USER.name

The $$USER.name variable refers to the full name of the logged-in user. 

$$USER.homeGroupID

The $$USER.homeGroupID variable refers to the ID of the Home Group of the logged-in user. As a Group Administrator, you can use this variable to filter only for items that belong to the users in your Home Group. 

For example, to see all incomplete tasks on projects in the finance group, use the following filter rules in a task filter:
Project: Group ID Equals $$USER.homeGroupID
Percent Complete Less Than 100

To see all incomplete tasks assigned to individuals in a specific group which is the Home Group of the logged-in user, use the following filter rules in a task filter:

Assigned To: Group ID Equals $$USER.homeGroupID
Percent Complete Less Than 100 

$$USER.otherGroupIDs

The $$USER.otherGroupIDs variable refers to all groups (except the Home Group) associated with the logged in user's profile.

The functionality of this variable is similar to that of the $$USER.homeGroupID variable, except the results display information about the user who belongs in any of the groups identified in the filter. 

$$USER.homeTeamID

 

The $$USER.homeTeamID variable refers to the ID of the Home Team of the logged-in user. As a team manager, you can use this variable to filter only for items that belong to the users in your Home Team.

$$USER.teamIDs

The $$USER.teamIDs variable returns a list of all the teams associated with the logged-in user.

The functionality of this variable is similar to that of the $$USER.homeTeamID variable, except the results display information about the user who belongs in any of the teams identified in the filter. 

$$USER.roleID

The $$USER.roleID variable refers to Primary Role of the logged-in user. Using this variable, you can report on tasks or issues assigned to a specific job role.

For example, to see all tasks assigned to the Primary Role of the logged-in user, you can use the following filter rule in a task filter:

Task: Role ID Equals $$USER.roleID.

***

>>Linked in other articles - do not move/ delete. 

>>This was included but it is not supported???:

The $$USER.roleIDs variable refers to all the job roles that are associated with the logged-in user. Using this variable, you can  items assigned to all of the job roles associated with the logged-in user. 

For example, if you want to display tasks assigned to any of the job roles associated with the logged-in user, you can use the following filter rule in a task filter:

AssignedToID Equals $$USER.roleIDs.

 

This article last updated on 2018-12-06 19:27:47 UTC