07-13-2020, 03:25 PM
(This post was last modified: 07-13-2020, 03:27 PM by remkonoteboom.)
The only internal trigger I know of is that one that will synchronize task data on tasks that have the same parent, process and context. This is how TACTIC manages assigning multiple people to a "task". It treats tasks that have these three properties as identical tasks but are assigned to different people.
For example, if I have a shot, SHOT001 that have a task in the "model" process. If I add another task in the model process, then those tasks are linked unless the "context" column of the process is different.
Note: this was was disabled 4.6 as it proved annoying as multiple tasks in the same process changed dates, as Eric has just witnessed (I believe this is his problem, as he has not mentioned enough information for me to conclude that).
In 4.5, you can stop this from happening by changing the context of the second task to "model2" (or any value other than "model") as per my example.
For example, if I have a shot, SHOT001 that have a task in the "model" process. If I add another task in the model process, then those tasks are linked unless the "context" column of the process is different.
Note: this was was disabled 4.6 as it proved annoying as multiple tasks in the same process changed dates, as Eric has just witnessed (I believe this is his problem, as he has not mentioned enough information for me to conclude that).
In 4.5, you can stop this from happening by changing the context of the second task to "model2" (or any value other than "model") as per my example.