Fusion scenario to add tasks to a project and add predecessors to each other within the same project?

[TraKill]

Hi Community,

I am trying to find a way to add after a specific request has been created a task list(three records) to a project via Fusion. So far so good. Depending on the individual request I created three records to the project. Where I am stuck is defining the predecessors. I could only find the API call that is referring to predecessors across projects, but since these tasks are not in the project, yet, they also do not have a task number, that I could refer to as the predecessor. So the API call

Url: TASK/{ID of task}

Method: PUT

Body: {"predecessorExpression": "{{Number of task}}"} - doesn't make sense since I do not have the number.

I tried to add in the Body section: {"predecessorExpression": "{{ID of task}}"} - since it is the newly created task before, but I receive an error message: [400] APIModel V20_0 does not support action %XXXXXXXXX%XX (TASK)

Any workarounds for this?

Thanks for any advice in advance!

[nfo]

Hi @TraKill 

Assuming your task list is added to the existing task list of the project, get the totalTaskCount of your project before adding the 3 new tasks so that you get the task number required to set your predecessor expression....

Make sense?

[TraKill]

It is currently an empty project and every new request should cover those three tasks, which makes it hard to add any task number, since they will add up within the project and always have another number that they are referring to.

Example:

1. Project name: Request project X - 0 Tasks
2. Request for asset 1 gets submitted

3. Tasks for asset 1 - Task 1= Review, Task 2= adjust, Task 3= finalize
4. Tasks for asset 2 - Task 4= Review, Task 5= adjust, Task 6= finalize

etc.

[nfo]

Maybe I'm misunderstanding something but to me it can be achieved like this

First request > project:totalTaskCount = 0 then

task 1 Review

task 2 adjust, predecessorExpression: 1fs

task 3 finalize, predecessorExpression: 2fs

Second Request > project:totalTaskCount = 3 then

task 4 Review

task 5 adjust, predecessorExpression: 4fs

task 6 finalize, predecessorExpression: 5fs

Third Request > project:totalTaskCount = 6 then

task 7 Review

task 8 adjust, predecessorExpression: 7fs

task 9 finalize, predecessorExpression: 8fs

etc...

[TraKill]

Interesting. Okay but that looks like I would have to set up the total count for a huge number to start with since there is no limit on incoming requests, right? Or can i set it up more dynamically?

E.g.  project:totalTaskCount = currentTaskCount
task 1+currentTaskCount Review

task 2+currentTaskCount adjust, predecessorExpression: nameofTask1fs

task 3+currentTaskCount finalize, predecessorExpression: nameofTask2fs

[nfo]

project:totalTaskCount will always be the number of tasks existing in your project.

totalTaskCount is not something you set-up. It's counted dynamically.

predecessor expression is <task number><dependency type> (no task name, or reference or ID)

ex if task 2 needs to start when task 1 is finished, predecessor expression on task 2 will be "1fs"

see:

https://experienceleague.adobe.com/en/docs/workfront/using/manage-work/tasks/use-task-predecessors/p...

https://experienceleague.adobe.com/en/docs/workfront/using/manage-work/tasks/use-task-predecessors/t...

[nfo]

and for a PUT request the id of your object should be passed in the body.

That's why you had [400] APIModel V20_0 does not support action %XXXXXXXXX%XX (TASK)

in your case the ID is interpretated as an action name which doesn't exist.

PUT /TASK/

body

{

"ID":"xxxxx",

"predecessorExpression":"xfs"

}

[kautuk_sahni]

@TraKill Just checking in — were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!