DocumentationWorkfront

Create filters with date-based wildcards

Last update: June 27, 2025
  • Topics:
  • Reports and Dashboards

CREATED FOR:

  • Intermediate
  • User

In this video, you will learn how to:

  • Know when to use date-based wildcards
  • Understand the difference between Workfront’s two date-based wildcards
  • Add a date-based wildcard to a filter
  • Create a custom date using wildcards, attributes, operators, and modifiers
  • Create a custom date range using wildcards
Transcript

When you build filters that include dates, such as entry date, planned completion date, or last update date, you can enter a specific date or select from the list of pre-configured dates such as this week or next month. However, this list might not always suit your needs. For example, a team member may want to write a filter that shows all tasks due in the next two weeks so they can start planning ahead. Or maybe a project manager needs a filter to show projects that are due in the next two months. More often than not, you’ll find yourself using date-based wildcards in Adobe Workfront to create custom dates and custom date ranges that better suit the filter and reporting needs of your users, teams, and organization. In addition, date-based wildcards allow you to create dynamic filters that update automatically based on the current date, which means you’re not constantly modifying filters to update the date information. Let’s get started by taking a look at the two date-based wildcards in Workfront. Adobe Workfront supports two date-based wildcards, $$Today and $$Now. $$Today is equal to the current date, starting at midnight this morning and ending at 11.59 p.m. It’s the most common date-based wildcard used by Workfront customers. Let’s say you want to see which projects were created today in your marketing portfolio, but you want this filter to show the current day’s projects each day. Start by creating a new project filter.

Name the filter Projects created today. The first rule will be Portfolio name equal marketing. Add another filter rule, then select Project entry date. This looks at the date the project was created in Workfront. If you put in today’s date, when you run this filter tomorrow or the next day or next week, it’s going to go back to this date. You have to edit the filter every day to set the current date. But if you use $$Today, you don’t have to update the filter. Workfront automatically knows what day it is and shows you the results that match. This not only saves you time, but it ensures you that you’re always looking at the latest information. Note, type the wildcard using all capital letters. If you use lowercase letters, the wildcard won’t work.

$$Now isn’t used as often by Workfront customers. $$Now is equal to the current date and time. This means the results you will see depend not only on the date the filter is used, but also the current time. Look at the clock on your computer or mobile device. What time is it? If you ran a filter that used $$Now, that’s what Workfront would use in the filter. This could result in you not seeing all of the information you need to make an assignment or provide an update to your manager.

You can create custom dates using either of the date-based wildcards with operators, attributes, and modifiers. You may have already seen custom date wildcards if you’ve used the pre-built date qualifiers while setting up a filter for planned completion date or another date-related filter rule. The two operators, plus sign and minus sign, allow you to add or subtract values from the date wildcard. Tell Workfront what value to subtract using attributes for quarter, hour, day, week, month, or year. Now let’s look at some examples. Project, planned complete date, equal, $$Today, plus 15D. This looks at today’s date and then adds 15 days.

Task, planned start date, equal, $$Today, minus 10D. This looks for tasks that have a planned start date that was 10 days ago. Be sure to type the attributes in lowercase. You can make more complex custom dates using the modifiers, B and E. These tell Workfront to look at the beginning or end of the attribute you’ve chosen.

$$Today, B, plus 2W. The B after today tells Workfront to first go back to the beginning of the week that today is a part of before adding two weeks of time. It knows to go forward two weeks rather than days or months because of the W time attribute that comes after the plus sign. Note, it might be helpful to look at these pre-built date qualifiers to see how they’re structured. In addition to building custom dates, you can build your own custom date ranges with date-based wildcards. Let’s take a look at an example. As part of your work tracking, you want to see tasks assigned to the team that are due within the next three weeks. You’ve already set up the filter rules for tasks assigned to your team that are part of active projects and that belong to projects in the marketing portfolio. Click Add another filter rule one more time so you can add the date criteria. For this, you’ll use Task, Planned Completion date. Expand the Qualifier field. There’s not an option for three weeks, so you’ll want to build your own. Select the Between Qualifier. This gives you fields to set a beginning date and an end date for your three-week window. What would happen if you filled in exact dates for the range? Well, starting tomorrow, this filter would be outdated. Every time you use the filter, it will go back to these specific dates. But that’s not what you want this filter to do. You want the beginning of the three-week date range to always be the current date. In the first field, type$ today. Remember to type in all capital letters, otherwise the wildcard won’t work. This establishes the first day of your range. It will always be the current date. Note, you don’t need to add a B after the wildcard in this instance. The$ today wildcard automatically goes back to midnight. So the B isn’t needed to tell it to go back to the beginning of the day. To set the end date of the range, you’ll use the$ today wildcard plus an operator and Enter$ today plus 3w. Remember, the endpoints of the range you specify for the between qualifier are included in the range. All tasks with a planned completion date greater than or equal to the first date, but less than or equal to the last date will pass through the filter. This tells Workfront to look at today’s date, then add three weeks to calculate the ending date of the range. Once you name and save this filter, you can use it whenever needed, without having to modify the filter setups to ensure it starts on the current date. Building custom dates and date ranges takes practice and some trial and error. As you’re building the date filters, check the results to make sure you’re getting the data you want to see. It may help you to study how the pre-built date qualifiers are created. You can use these as they’re built, of course, or you can modify one to accommodate the date parameters you need for your filter.

“Create filters with date-based wildcards” activities

Activity questions

  1. How would you build the filter rule if you wanted issues that have a due date of yesterday or today?
  2. How would you build the filter rule to find projects that were due last week?
  3. The following filter rules are part of a task report you use regularly. What type of results would you get from this report?

An image of the screen to create a task filter with a date-based wildcard

Answers

  1. Filter on the issue planned completion date between $$TODAY-1d and $$TODAY.
  2. Filter on the project planned complete date between $$TODAYb-1w and $$TODAYe-1w.
  3. This report finds tasks assigned to you that aren’t yet finished (in other words, have a percent complete less than 100), and that are overdue or due today. The filter rule for the planned completion date of the tasks says to look at tasks that have a due date that is equal to or before today’s date.
recommendation-more-help
c9fbcf61-6d19-481e-a9ab-f54a0ae0ee8a