Hi Lars,   The best way to achieve this is by using the "canStart" attribute on tasks. Once all predecessors have been completed, the task will show canStart=True. Or it will show False if there are still predecessors outstanding.    Using this attribute you could build a report to show all tasks as...

You're welcome Nick. If this solved your problem, please can you mark it as an accepted solution so that others know that this code works in the future? 

Hi Justin,   Yes, this is possible. Going into the proofing activities tab on any given proof will show you all interactions a user has had with a proof, including a record of when comments where deleted.      Regards, Rich. 

Hey Nick,   I've been having a play around with this and I believe that the below EXISTS statement should do it:   EXISTS:a:$$EXISTSMOD=EXISTS EXISTS:a:$$OBJCODE=PROJ EXISTS:a:programID=FIELD:ID EXISTS:a:status=CPL EXISTS:a:status_Mod=in AND:1:EXISTS:a:$$EXISTSMOD=NOTEXISTS AND:1:EXISTS:a:$$OBJCODE=...

Hi Seth,   Using this text mode in a proof approval report gives me the Project Name as a clickable link that takes me directly to the project:   displayname=Project linkedname=document namekey=view.relatedcolumn namekeyargkey.0=documentVersion namekeyargkey.1=document namekeyargkey.2=project nameke...

Hi,   Have you checked what cost type is associated with the task in the tasks finance settings? If you have a rate associated with the user's profile, the cost type will need to be 'user hourly'.    Regards, Rich. 

Hi Kundan,   No problem. I'm not sure I understand your question. A filter is independent of the grouping. Any filter applied to the planned completion date will not affect the parent task name or reference number.   Please clarify and I'll do my best to help.   Best Regards, Rich. 

Hi Kundan,   Try the below text mode for your grouping.   group.0.linkedname=parentgroup.0.namekey=view.relatedcolumngroup.0.namekeyargkey.0=parentgroup.0.namekeyargkey.1=namegroup.0.valueexpression=CONCAT({parent}.{referenceNumber}," - ",{parent}.{name})group.0.valuefield=parent:namegroup.0.valuefo...

Hi Ian,   Yes, External Users do not have permission to create requests within Workfront. The user has to have at least a Request access level. You would need to go to the user's profile in Workfront and upgrade their access level before they can submit requests via email. You must also ensure that ...

Is the request queue shared with the user submitting the email?