Scope of a Task Sequence Document

Workflow definitions can be customized for different projects by placing Task Sequence documents at various cabinet or folder levels.

Multiple Task Sequence documents can be located throughout your repository. When a user attempts to change the status of a document, Astoria searches upwards in the repository hierarchy until it finds a Task Sequence document. That document controls the workflow. If no document is found up the hierarchy, the top level of the Administration cabinet is searched. This allows you to specify different Task Sequence documents for different cabinets and folders, or to specify a single Task Sequence document that applies to all objects in the repository.

Additionally, each Task Sequence document can specify that additional job-related fields, task sequences, or scheduled job notification rules can be inherited from Task Sequence documents located higher in the repository hierarchy. If no inheritance is specified, lower-level Task Sequence documents define the full workflow.