This blog is to cover the basic task setup Above the Line

When I say ‘above the line’ I am referring to the area shown below which is common to most tasks.

I am using a PDF task in this example, but this will apply to most Task types.

Above the Line

This is where you will set the basic settings of the task

1. Name

   1. The name of the task: I tend to name mine relevant to what type of task it is and how they are set up
      1. In the example above PDF is the type of task, E1

The Only on Change setting is intended to save unnecessary tasks from running, so if nothing has changed in the model, the task does not run.

What Determines if the Task Runs

When setting a task schedule to Only on Change, that means that even though that task is set to run at a set day/time, it will only run if one of the following occurs:

• The date of the target file changed in Clarity since the last time it ran?

  • You can see that date on the Project Home page or

  • The Files tab for that file

    • If a

A task sequence bundles together multiple tasks in a project so that they will run together, in a single operation, in a guaranteed sequence.

That means, that regardless of the server settings, the targets in this task will all run at the same time and in the order specified in the task setup. 

If you are running a sequence on multiple targets, this could cause issues with tasks failing due to timeout issues.

The task server that claims the sequence will do all of the tasks in the sequence, for all models, in one session.

Guidelines

• You cannot mix File scoped and Project scoped