51黑料不打烊

Understand basic text mode for groupings

TIP

In this video, you will learn:

  • What text mode is
  • What camel case is
  • Some basic 鈥減lug and play鈥 text mode you can use in your groupings

video poster

Transcript

Hi, and welcome to Basic Text Mode for Groupings. In this video, you鈥檒l learn what text mode is, what camel case is, and some basic plug and play text mode that you can use in report groupings. If you already know what text mode and camel case are, you can skip right to the Plug and Play section. It starts at the How to Remove Name prefixes on Groupings slide. Many report writers use text mode in 51黑料不打烊 Workfront because they鈥檝e exhausted their resources with the standard builder, and in some cases still don鈥檛 have the report they need or want. Although text mode is not a cure-all solution, it does allow you to get around some of the limitations that you may be experiencing through the standard builder. Click on New View. You鈥檝e seen how columns and views are created in the standard builder by clicking on New Column and then using a drop-down menu to select the available field. The standard builder simplifies the reporting tool, but because of that simplification, it can be limited. It actually doesn鈥檛 have all the fields that could be used in this list here. That鈥檚 why you may want to look to text mode to expand your options. The system reads the information you put into the standard builder and puts it into a code for Workfront to read. This is text mode. All of the same components are there. They just look different. The thing to keep in mind when working with text mode is that fields are written in what is called camel case. That means the field is written with a mixture of upper and lower case letters and no spaces. Workfront uses camel case to string words together in text mode, and most of the time what you find in the standard builder would be similar in camel case. For instance, this is how planned completion date looks in the standard mode, and here鈥檚 what it looks like in camel case. Here鈥檚 budget status in standard, and here鈥檚 budget status in camel case. There are some fields in the standard builder that have a camel case equivalent that doesn鈥檛 follow these rules exactly, but they鈥檙e usually pretty easy to recognize and they still were referred to the standard builder field. For example, duration in minutes is duration minutes in camel case, and external reference ID is X ref ID in camel case. A list of fields can be found in the API Explorer. You can learn more about the API Explorer in the advanced reporting tutorials in Experience League, and that鈥檚 a good place to go to find a link to the API Explorer.

The advanced reporting tutorials teach you more about text mode than we can do here. They contain five and a half hours of video instruction and a manual that you can download. Here we鈥檒l just show you some handy text mode code you can plug and play without having to take the advanced course. Here are a couple of plug and play text mode code blocks. The first one isn鈥檛 really a plug and play thing, but I think you鈥檒l find it鈥檚 pretty handy to know. Here we have a report grouped by team name. There鈥檚 an easy way to remove or change prefixes on groupings. You just need to edit them out using text mode. We鈥檒l go in and edit this report. Go to the groupings and click switch to text mode. All we have to do is change the group zero name key field, and that鈥檚 this right here. To remove this name altogether, we can just change this to group zero name equals.

Now we save this. There鈥檚 no name in there at all. If you want to put some name, some different name, you can do that as well. Let鈥檚 go back in here. And we鈥檒l put name, and then whatever we type in here is what it鈥檒l show. Plus it鈥檒l put that colon in there still, but there鈥檚 no way to get rid of that. You can at least put some other word in there if you want to. Suppose that in your organization, you use many levels of sub tasks. In some cases, sub tasks have the same names and can only be accurately identified by the parent tasks they鈥檙e associated with.

So if you watch the basic text mode for views, you recognize this view here of the 4 parents view. Let鈥檚 say that your boss wants you to come up with a task grouping that will group based on all the parents of a task up to four generations back. Your boss wants all the parent tasks to show in the grouping bar separated by commas. If there鈥檚 a grouping with fewer than four generations, your boss wants to only have the actual parent shown and doesn鈥檛 want to see a lone comma in place of a blank parent. So here鈥檚 the view that will do that. It鈥檚 called the 4 parents grouping.

And you can see that it鈥檚 got what your boss asked for.

Multiple parents and where there鈥檚 no parents, no comma just left there.

So how do you get that? How do you make it? That鈥檚 what we鈥檒l go do right now. Create a new grouping.

We鈥檒l call it another 4 parents grouping.

I will switch to text mode. And. Read it, whatever鈥檚 there.

And then go to our tutorial. Copy the text mode code block. And we鈥檒l plug it in.

Save the grouping. And there you go. Be sure and check out the additional plug and play text mode groupings in this tutorial text.

Task - 4 parents grouping

The following text mode will group tasks based on up to four levels of parents, and leave parents that don鈥檛 exist blank.

textmode=true
group.0.name=Parents
group.0.valueexpression=CONCAT({parent}.{parent}.{parent}.{parent}.{name},IF(ISBLANK({parent}.{parent}.{parent}.{parent}.{name}),"",", "),{parent}.{parent}.{parent}.{name},IF(ISBLANK({parent}.{parent}.{parent}.{name}),"",", "),{parent}.{parent}.{name},IF(ISBLANK({parent}.{parent}.{name}),"",", "),IF(ISBLANK({parent}.{name}),"No parent",{parent}.{name}))
group.0.linkedname=parent
group.0.namekeyargkey.0=parent
group.0.namekeyargkey.1=name
group.0.valueformat=string

A screen image showing project tasks grouped by 4 parents

Task - Percent complete grouping

The following text mode will group tasks based on their percent complete. Tasks will fall into one of the following categories when grouped:

  • 0%
  • 1% to 25%
  • 26% to 50%
  • 51% to 75%
  • 76% to 99%
  • 100%
group.0.linkedname=direct
group.0.namekey=percentComplete
group.0.valueexpression=IF({percentComplete}<1,"0%",IF({percentComplete}<26,"1% to 25%",IF({percentComplete}<51,"26% to 50%",IF({percentComplete}<76,"51% to 75%",IF({percentComplete}<100,"76% to 99%",IF({percentComplete}=100,"100","***"))))))
group.0.valueformat=doubleAsString
textmode=true

A screen image showing project tasks grouped by percent complete

Task - statusEquatesWith, then status

The following text mode will group tasks by statusEquatesWith, then by status.

group.0.enumclass=com.attask.common.constants.TaskStatusEnum
group.0.enumtype=TASK
group.0.linkedname=direct
group.0.name=State
group.0.type=enum
group.0.valuefield=statusEquatesWith
group.0.valueformat=val
group.1.enumclass=com.attask.common.constants.TaskStatusEnum
group.1.enumtype=TASK
group.1.linkedname=direct
group.1.namekey=status
group.1.type=enum
group.1.valuefield=status
group.1.valueformat=val
textmode=true

A screen image showing project tasks grouped by statusEquatesWith

Proof Approval - Group by project name

group.0.valueformat=HTML
group.0.valuefield=documentVersion:document:project:name
group.0.displayname=Project Name

A screen image showing Proof approvals grouped by project name

Proof Approval - Group by document name

group.0.displayname=Document Name
group.0.valuefield=documentVersion:document:name
group.0.valueformat=HTML

A screen image showing Proof approvals grouped by project name

recommendation-more-help
c9fbcf61-6d19-481e-a9ab-f54a0ae0ee8a