|
Forecast/Actual dates begin as forecast dates: future dates when a task owner plans on starting and completing a task. These dates are specified while the task is still pending. When a team member actually starts and completes a task, the same dates can be used or different dates that are supplied as the actual dates.
|
|
Target dates are dates that are used to plan the project schedule. Typically, they are set at the beginning of the project.
|
|
Anchored dates are fixed dates that cannot change, even if the dates of the tasks upon which they are dependent change.
|
|
Non-work time represents dates when people do not work, so the system skips those dates when it calculates durations for tasks. Marketing Operations currently supports system-wide non-work time that applies to all tasks. It is up to the project manager to determine whether overriding any of these dates is necessary. System administrators enter and maintain these dates.
|
|
Weekend dates are dates that you use to specify work that occurs on a weekend on a per-task basis. You can schedule work on a weekend date by using the Schedule Through option for each task.
|
|
Task owners are the people responsible for running or managing workflow tasks.
|
|
Reviewers are responsible for approval tasks. These members become the approvers of the task.
|
|
Roles are used as a bridge between tasks and people. They are useful for assigning work on a generic basis. For example, each type of project you create can have its own workflow template, and the template can contain standard roles for certain tasks. Then, when you create a project, some (or all) of the tasks have a default role that is already associated with them.
|
|
Each workflow might contain users from different timezones. You chose whether Marketing Operations displays the timezone after the timestamps on the workflow and workflow columns. For more information, see Calendar display options.
|
Copyright IBM Corporation 2014. All Rights Reserved.
|