Workflow Automation / Task Hierarchies



Related tasks are linked together by defining dependencies. bCommunities allows for complex task organization that can be adapted to the particular project management culture and method of any project-based company.

Tasks can be categorized depending on their position in relation to others in the following way:

Independent: These tasks are seen in the first level of Projects screen (Dependencies View only) as they are not related to any predecessor nor successor tasks.

Dependent: Tasks shown at any level of a given project that have other tasks attached to them, either proceeding or after them. These tasks are part of a workflow from the point of view of a given user.

Predecessor: Task that precedes another in a given workflow. This task must be completed in order for the next one to begin. If the task’s deliverable includes files, those files might be the ones needed as source files for the next task.

Successor: Task that follows another in a given workflow. If the resource for its predecessor task completes it before or after its deadline, the owner and resource for this task/s will be notified of the date modification whenever Auto-Rescheduling functionality is enabled.

Subtask: A set of two or more tasks created with the goal of dividing the workload of any task between several resources.

A phase is a collection of activities grouped together in a logical order. It consists of a number of related tasks and a milestone to mark the completion of each phase within the project.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk