Logic fields

A unique number, for use in cascade planning, in which each task is assigned a unique number - the cascade activity number - and you can sort tasks according to their cascade activity number. When you do this, all links point downwards and the various paths through the project are distinguished clearly, with the critical path appearing first.

You can calculate the cascade activity number of tasks when rescheduling.

For more information, refer to Calculating the cascade activity number of tasks when rescheduling.

• Data - whether you want to display information relating to the live data or to a specific baseline.
• Specific task - specify specific task(s) on a multi-task bar to which you want the field to refer if required.

A number, assigned automatically to tasks when you reschedule a project, that indicates the logical path on which a task is located. Tasks with lower logical path numbers are those on logical paths that contain the least amount of total float; the higher the logical path number, the more total float in the logical path. You may find it useful to monitor tasks that are on low-numbered logical paths, as these tasks are more likely to affect the project finish date if they are delayed.

Hammocks are always assigned a logical path number of zero. The same is true of summary and expanded tasks, even if they have incoming or outgoing links.

For more information, refer to Using logical paths to monitor the erosion of total float.

• Data - whether you want to display information relating to the live data or to a specific baseline.
• Specific task - specify specific task(s) on a multi-task bar to which you want the field to refer if required.

The duration of the logical path on which a task is located. You may find it useful to compare the total float of tasks against the duration of the logical paths on which they are located, to ascertain which of the tasks on a particular logical path are most likely to affect the project finish date (ie those with the least total float).

For more information, refer to Using logical paths to monitor the erosion of total float.

• Data - whether you want to display information relating to the live data or to a specific baseline.
• Specific task - specify specific task(s) on a multi-task bar to which you want the field to refer if required.
• Override time unit - the time unit in which to display the information.

The order of a task on the logical path on which it is located. The first task on a logical path has an order of 1; the next has an order of 2; and so on. You may find it useful to create sort/groups in which tasks are sorted/grouped first by logical path and then by logical path order, as this displays logical paths in the clearest possible way.

For more information, refer to Using logical paths to monitor the erosion of total float.

• Data - whether you want to display information relating to the live data or to a specific baseline.
• Specific task - specify specific task(s) on a multi-task bar to which you want the field to refer if required.

• Data - whether you want to display information relating to the live data or to a specific baseline.
• Specific task - specify specific task(s) on a multi-task bar to which you want the field to refer if required.

The tasks at the other end of the links that end at a task (a task's predecessors). When this field is displayed in the spreadsheet you can use it to create, edit and delete links between tasks.

For more information, refer to Creating and editing links using the spreadsheet columns, Link types, Drawing links with lead/lag time and Editing link properties and entering notes against links.

• Data - whether you want to display information relating to the live data or to a specific baseline.
• Specific task - specify specific task(s) on a multi-task bar to which you want the field to refer if required.
• Style - the details you want to display about the predecessor tasks: task name, task ID, WBN pathname, path name, unique task ID, line number or none. Note that if you choose to display the line number but a predecessor task is not displayed in the current view (it may be located in a different chart, or filtered out of the view), 'ns' (not shown) is displayed.
• Info - whether to display details of the link between the two tasks (the type of link and any lead or lag on the link).
• Link category - whether to display the link category that has been assigned to the links between two tasks.
• Show link notes - whether to display notes that have been entered against the links between two tasks.

The tasks at the other end of the links that start at a task (a task's successors). When this field is displayed in the spreadsheet you can use it to create, edit and delete links between tasks.

For more information, refer to Creating and editing links using the spreadsheet columns, Link types, Drawing links with lead/lag time and Editing link properties and entering notes against links.

• Data - whether you want to display information relating to the live data or to a specific baseline.
• Specific task - specify specific task(s) on a multi-task bar to which you want the field to refer if required.
• Style - the details you want to display about the predecessor tasks: task name, task ID, WBN pathname, path name, unique task ID, line number or none. Note that if you choose to display the line number but a predecessor task is not displayed in the current view (it may be located in a different chart, or filtered out of the view), 'ns' (not shown) is displayed.
• Info - whether to display details of the link between the two tasks (the type of link and any lead or lag on the link).
• Link category - whether to display the link category that has been assigned to the links between two tasks.
• Show link notes - whether to display notes that have been entered against the links between two tasks.

Whether, according to link logic, a bar, task or allocation is able to start. 'Can Start' is displayed if a task has no predecessors, or only has complete predecessors. 'Waiting' is displayed if a task has one or more predecessors that are not 100% complete, or if there are incomplete earlier tasks on the same bar. Note that this field is concerned purely with the status of a task's predecessors, and takes no account of the progress status of the task itself; therefore, this field will display 'Can Start' for a task that is 100% complete if the task has no predecessors, or only has complete predecessors.

You could use the results of this field to derive high and low states in a priority indicator, by constructing an expression using the field and entering it as the Indirection parameter for the Priority field. As the field returns a string, the Waiting#d expression would give objects that can start a low priority and tasks that are waiting a high priority. For more information on this, refer to Calculating priority automatically.

• Data - whether you want to display information relating to the live data or to a specific baseline.
• Specific task - specify specific task(s) on a multi-task bar to which you want the field to refer if required.