Begin and End Dates

These fields can be used to record original and/or revised begin and end dates for a project or task.  

• Original Begin Date - Could be used to capture the original begin date for the project.

• Original End Date - Could be used to capture the original end date for the project.  If a value has been populated in the Original Begin Date field, the value in this field must be greater than or equal to the value in that field.

• Revised Begin Date - Could be used to capture a revised begin date for the project.  

• Revised End Date - Could be used to capture a revised end date for the project.  If a value has been populated in the Revised Begin Date field, the value in this field must be greater than or equal to the value in that field.

Note regarding Revised Begin and End Date: If the project is a Billable project (determined by the Billing Type field), and the project has a Contract, and the Billable Project Changes Require Contract Modification (unanet.billable.projects.contractmod.asof.date) property is true, then you must enter a contract modification to change the dates.

There is currently no relationship between the project level, task level or person assignment begin and end dates (they do not constrain one another).

For most computations, the Revised Dates are used and as such, Revised Dates are not optional.  A blank begin date is considered by the system to be BOT (beginning of time), and similarly, a blank end date is considered to be EOT (end of time) and these values will be physically stored if no date is supplied.

Task Dates and Dependencies

Task Revised Dates will default to the project dates.

Grayed out dates on the Task list indicate that particular task has a derived date (e.g., the dates are determined by the Dependency settings).  When editing a task that has dependencies, the date will also appear in a light gray text and only by checking the "Update Revised Dates" can you directly manipulate those dates.  Note, however, that doing so will remove any dependency information and the newly entered dates will be saved as entered.

Enforce Project/Task Dates

The Project setting Enforce Project/Task Dates can be enabled to prevent time and expense charges beyond the dates provided on these screens.  With that setting enabled, these dates are interrogated and can influence which projects and tasks will appear in the user's timesheet project/task dropdown lists.  

When a user is charging time or expense actuals, the system will first validate that the entry falls within an Assignment date range (should one exist for this user for this project/task), beyond that validation, the system will only restrict the entry to the project/task dates when this option is enabled.  When enabled, the charges must fall within both the project and task begin and end dates.

Link Assignment/Plan Dates

Individual Assignments and Plans can be configured to have their respective dates linked to the Project/Task dates (rather than supplying their own explicit dates).  When Assignments and Plans utilize this setting, any changes to the relate Project/Task dates will also be reflected on those linked Assignments and Plans.

Changing this setting will trigger re-rating, which may modify existing time entries associated with non-LOCKED, non-EXTRACTED time for this project.