Task dependencies

Task dependencies cause a requirement, called the following task in the Maintenix UI, to be created, terminated, or completed when the prerequisite requirement is completed.

For example, a task dependency is used for a repair task that requires a follow-on inspection. When the repair task (the prerequisite) is completed, the inspection task (the following task) is created.

Both the prerequisite task and the following task must belong to the same organization, or share the same non-root parent organization.

In Maintenix, you create a task dependency by identifying the following task that is associated with a requirement definition. On the Details tab of the task definition in Maintenix, you can see all dependencies a requirement definition has to other requirement definitions, whether the requirement definition is the prerequisite task or the following task:

You can create following task dependencies on requirement task definitions that are in Build or Revision status. You should not create following task dependencies in reference documents definitions because they are never initialized as active tasks; the work described in reference documents is executed and completed using linked requirement definitions.

There are four types of task dependencies in Maintenix: