Expand my Community achievements bar.

Richard_Le_
Richard_Le_
Online
Type
  • All
  • Questions
  • Discussions
  • Ideas
  • Blogs
Filter by user contributions
  • Hi Madalyn,   You can't apply multiple filter rules against the same parameter, which is why this isn't working. However, what you could do is apply a prompt for actualCompletionDate allowing you to select the date range you want to pull in. And also use the text mode filter to only show tasks that ...

    Type

    Questions

    Views

    2.2K

    Likes

    0

    Replies

    2
  • Hi Gina,   The fact that the code is returning results on some projects but not others shows that the code is correct. Therefore there must be something different about the projects with no results. This is going to be one of the following: The project does not have an originating request that it wa...

    Type

    Questions

    Views

    2.7K

    Likes

    0

    Replies

    2
  • Hi,   Try the following instead:   CONCAT(‘‘https://<domain>.my.workfront.com”,“/”,“task/”,{ID},"/overview’’)   Since "ID" is a parameter in Workfront, you need to enclose it in curly brackets.   Best Regards, Rich.  

    Type

    Questions

    Views

    631

    Likes

    2

    Replies

    1
  • No problem, Gina.   In your original post, you said that you wanted to apply a filter to your report so that only projects with a turnaround time of less than 10 days are shown. The steps that I have outlined above will allow you to do this.   If you also want to show the number of days between the ...

    Type

    Questions

    Views

    2.7K

    Likes

    0

    Replies

    11
  • It would just be a case of replacing plannedCompletionDate with the field name in the calculation.   So if your field is named Target/Live Due Date, the calculation would look like this:   WEEKDAYDIFF({convertedOpTaskEntryDate},{DE:Target/Live Due Date})   Best Regards, Rich.

    Type

    Questions

    Views

    2.7K

    Likes

    0

    Replies

    13
  • The reason for this is likely to be that the task was completed after the planned completion date (with time taken into consideration). For example, if a task was planned to complete at 16:00 on 01/06/23, but was actually completed at 17:00 on 01/06/23, it is classed as late in Workfront.   You've g...

    Type

    Questions

    Views

    2.3K

    Likes

    4

    Replies

    1
  • Hi,   To achieve this, you would need to add a calculated field to your projects that calculates the number of days between the request entry date and the planned Completion Date of the project (assuming that plannedCompletionDate is the same as the target live date). The calculation would look some...

    Type

    Questions

    Views

    2.7K

    Like

    1

    Replies

    15
  • Hi,   This can be achieved with the following text mode filter:   actualCompletionDate=FIELD:plannedCompletionDate actualCompletionDate_Mod=gt   Best Regards, Rich.    

    Type

    Questions

    Views

    2.3K

    Likes

    4

    Replies

    9
  • Hi,   I can see that there are four statuses used in this formatting rule. Should all of them appear in orange when pending approval? If yes, you will need to append ":A" to all of the status codes, so the line of code would look like this:     styledef.case.0.comparison.righttext=HFA:A WJL:A EQB:A ...

    Type

    Questions

    Views

    787

    Likes

    0

    Replies

    1
  • Hi,   In the requests area of Workfront, under the "submitted" tab, there is a column called "Converted to" which will show the resolving object (be it a task or a project), which will be the item that the request was converted into.   On the actual request itself, in the details tab, there is a fie...

    Type

    Questions

    Views

    461

    Like

    1

    Replies

    1
Top badges earned by Richard_Le_
Customize the badges you want to showcase on your profile