The workflow and sub-projects
Sometimes the objects in your project have some tasks that are common to all objects, and some different tasks depending on the type of object.
For example, you have a project that contains both text and graphic objects.
- the text objects must go through writing and technical review tasks which the graphics do not
- the graphics objects must go through illustrating and an illustration review task which the text does not
- both the text and graphics must go through markup, translating, final review, and approval tasks
You do not want the objects to go through all the tasks in a sequential order but for the different objects to go through their specific tasks concurrently. You do this by creating sub-projects in your main project.
Sub-projects are projects within another (main) Project—in other words, the parent object is a Project. Although your workflow may contain many more steps than shown in the Sample Workflow in The ProjMan Roles topic, the sample has the main ingredients shown in a primary workflow that branches into two separate workflows—one for text and another for illustrations or graphics. In addition, the two workflows come back together at one point for review, approval and markup.