Defining Workflow

Defining Workflow can be done in one of two ways:

Composing the Schedule dynamically in the Schedule Form.
Applying a Schedule Template to a Schedule

In either case, the objective is to express the sequence of Activities that define the work required to complete the Job. Additional attributes can be set and modified for each Activity in the Schedule, including autostart, milestones, due dates, etc....

Review the following sections for details on defining Schedules.

General Attributes

Traffic Manager	Required. If you are a member of the Traffic Management user Group, you will be automatically selected as the default Traffic Manager for the current Job. You can reassign Traffic Management responsibilities to any user defined in the system. You cannot save a Job Schedule without a Traffic Manager assigned.
Schedule Template	Optional. Provides a way to select and apply a Schedule Template to the Job Schedule. Select and apply a Schedule Template to the Job Schedule.
Calendar	Required. Select or reapply a Calendar to the Job Schedule.

Scheduled Workflow

Preds	A list of IDs of other Activities in the Job Schedule. On a live Job, an Activity will become active as soon as all of its Predecessors are finished. The sequence of Activities cannot form cycles. If an Activity has no Predecessors, it will become active as soon as the Job Schedule is saved. Predecessors are modified using the Activity Selector.
ID	The Activity ID. This is inherited from the attribute originally defined for the Activity and is used by other Activities to define their predecessors.
Activity Name	The name of the Activity. This is inherited from the attribute originally defined for the Activity, but may be modified in the Job Schedule.
Roles	One or more Roles must be defined for each Activity. On a live Job, an Assignment record is generated for each Role assigned to an Activity.

Activity Status Indicators

Inactive (no graphic)	Activity is not active, but will be later. Activity is not active, finished, or skipped.
Paused ( )	The corresponding Activity is active but has not been started. Activities set to automatically start upon becoming active will never be paused.
Started ( )	The corresponding Activity is active and has been started.
Finished ( )	The corresponding Activity has been finished.
Skipped ( )	The corresponding Activity has been skipped.

Scheduled Timeline

Duration	The number of days it is expected to take to complete an Activity. This can be inherited from an Activity’s original attribute, inherited from a Schedule Template, or defined/modified directly in the Job Schedule.
Start	The estimated/actual date each Activity starts on. All dates are estimated until an Activity is started, at which point the estimated start date is replaced by the actual start date, and subsequent estimated start and finish dates are recalculated accordingly.
Finish	The estimated/actual date each Activity finishes on. All dates are estimated until an Activity is finished, at which point the estimated finish date is replaced by the actual finish date, and subsequent estimated start and finish dates are recalculated accordingly.
Plan	The planned completion dates for each Activity (Activity Due Dates).
Milestone	When enabled, warnings will appear if the estimated/actual dates for each activity are predicted to or have missed the corresponding planned finish date.

Planned Start Date

Used to set the plan starting on the date defined here. Also used to calculate estimated start and finish dates based on the first scheduled Activity/Activities starting on the date defined as the Start Date.

Planned Finish Date

Used to set the plan assuming this as the due date for final Activity/Activities.