Workflow tab fields

To specify anchored dates for a task, click the column, then select Anchored from the menu. The task date cannot move even if the dates of the tasks it is dependent on change.

If a dependency is not met, the dates in conflict appear with a different icon and in a different font.

For example, suppose task 2.2 is dependent on task 2.1. If the target end date of task 2.1 is after the target start date of task 2.2, both the target end date of 2.1 and the target start date of 2.2 appear in red, if you anchored the date for task 2.2 by selecting the lock icon in the Anchored Dates column.

Schedule Through

Indicators for which dates to use when determining task dates. The following options are available.

Business: indicates that this task includes only standard, non-holiday, non-weekend dates. This schedule is the default for all tasks.

Weekends: indicates that this task includes weekends. The system includes weekends when it calculates dates for this task.

Off.: indicates that this task includes system-wide non-work time that is defined. The system takes into account these times when it calculates dates for this task.

All: indicates that this task includes all dates. No dates are ignored when dates are calculated for this task.

Target Start

The targeted start date of the task. In edit mode, use the pop up calendar to select a date.

Target End

The targeted end date of the task. In edit mode, use the pop up calendar to select a date.

Target Dur.

The duration of the task, in days, hours, and minutes. The Target End minus the Target Start dates.

Target Effort

The targeted effort estimated to complete the task, as opposed to calendar duration.

Milestone Type

A task milestone that you choose from a dropdown list. Example options might be Meeting, Event, and Job Start. System administrators set the milestone types that appear on the list.

For more information about setting up milestones, see the Marketing Operations Installation Guide.

Member Role(s)

A role or roles associated with the task. These roles can be loaded automatically from the project template used to create the project, or the project owner can set them up manually.

When an approval task has a status of In Progress, On hold, or Completed, this field is read-only.

Members

The people associated with the task.

If a workflow task has a role in its Member Role(s) column, when you assign people to roles, the workflow automatically adds a person in the corresponding Members column.

You can also add people to the Members column manually while editing the workflow.

When you edit the workflow for an approval task, teams are not listed in this field because a team cannot be the owner of the approval task.

Typically, standard tasks have members.

When an approval task has a status of In Progress, On hold, or Completed, this field is read-only.

Reviewer Role(s)

A read-only field that shows the role or roles associated with an approval task.

These roles can be loaded automatically from the project template used to create the project, or the project owner can set them up manually.

Reviewer roles are used to pre-populate an approval process.

Reviewers

A read-only field that shows the reviewers associated with an approval task. Reviewers are used to pre-populate an approval process.

If a workflow task has a role in its Reviewer Role(s) column, when you assign people to roles the workflow automatically adds a person in the corresponding Reviewer column.

Enforce Dep.

If this task is dependent on other tasks, determines how strictly the system interprets dependencies. When this option is selected, the system restricts project members from updating this task until the tasks it depends on are finished.

Required

Whether this task is required. Required tasks cannot be skipped or deleted and their names cannot be changed.

Task Code

A read-only code that identifies each task uniquely within a project. System integrators use this code to implement custom business logic involving tasks.

Notes

Any comments about the task.