Handling Critical and Effort-driven Tasks

Microsoft Project recognized a number of different types of tasks. Tasks with no duration, for example, are considered milestones by default. Critical tasks make up the critical path, one or a series of tasks that, ultimately, determines how long a project will take.

Working with Critical and Effort-Driven Tasks

The Tsk class exposes the IS_CRITICAL and IS_EFFORT_DRIVEN properties to handle critical and effort driven tasks.

Critical and Effort-driven Tasks Microsoft Project

To see whether a task is critical or effort-driven in Microsoft Project double-click a task in the Task Entry form.

An effort-driven task in Microsoft Project

Getting Critical and Effort-driven Tasks

The following code examples show how to get information about whether a task is critical or effort-driven.

// For complete examples and data files, please go to https://github.com/aspose-tasks/Aspose.Tasks-for-Java
// The path to the documents directory.
String dataDir = Utils.getDataDir(CriticalAndEffortDrivenTasks.class);

Project project = new Project(dataDir + "input.mpp");

// Create a ChildTasksCollector instance
ChildTasksCollector collector = new ChildTasksCollector();

// Collect all the tasks from RootTask using TaskUtils
TaskUtils.apply(project.getRootTask(), collector, 0);

// Parse through all the collected tasks
for (Task tsk : collector.getTasks()) {
    String strED = tsk.get(Tsk.IS_EFFORT_DRIVEN) != null ? "EffortDriven" : "Non-EffortDriven";
    String strCrit = tsk.get(Tsk.IS_CRITICAL) != null ? "Critical" : "Non-Critical";
    System.out.println(strED);
    System.out.println(strCrit);
}