Dependencies can be defined between tasks belonging to the same project or across different projects. A task can have multiple depndencies, for example, the start of Task A can be dependent on the completion of Tasks B, C, and D. Similarly, the completion of Task A can trigger the start of Task F, G, and H.
You can define Finish-to-Start dependencies between project activities. This dependency implies that the start of the successor activity depends on the completion of the predecessor activity.
Limitations:
Elements that have child elements cannot be entered in dependency relationships. For example, a summary task with child tasks, or a change request with child tasks cannot have a dependency with any other element. Only elements that have no child elements can have dependencies.
You cannot create circular dependencies. For example, if Task A is dependent on Task B, you cannot create a dependency that makes Task B dependent on Task A.