Hello, My Business (IVECO) asked me to create a process with a huge number

Are these user input tasks meant to be real tasks in a process or more for data input purposes? Create simple processes for each different task and allow the user to start them with quicktasks. Maybe you have some states in your process so you could activate only necessary quicktasks.

User input task should be real tasks..I'm also worried about the maintenance of the task's dependencies..I don't want to become crazy if some logic will change in the future (Maybe could be useful read the dependencies from a CDT table mantained by an Administration Process)..So you suggest to create 130 quick task? Could be fine..thanks

It depends ... Is your process straight forward and are the tasks done serially or is it more like case management where your users decide what to do in each state?

For our purchasing process I have a model that is not much more than a data container and a sub process for the quicktasks. For each state a defined set of quicktasks is activated. Each quicktask represents one action implemented in one model. These models receive the data, update it and send it back to the data container.

Using this design an update of the process itself (the "logic") is no problem.