1. Date Validation within a CSV

Should invalid dates be entered in a CSV file the following rules are applied during the import mapping and validation stages should the user elect to proceed with import.  The rules vary slightly depending if schedule is in Phase 3 Kick-off or Phase 4 Execution.

 

Phase 3 Kick-off

  • Invalid start and/or finish dates the validation rule will convert both the start and finish dates to align to the project dates start and finish dates of the pipeline period.

 

Phase 4 Execution

  • Invalid Forecast dates

Should there be invalid Forecast/Actual start and/or end dates within the file the following rules apply

  • Task start and/or end date outside Project Start and Forecast End date, system will apply dates populated in the Baseline start and/or End date fields.
  • Task start and/or end date outside Project Start and Forecast End date, and no Baseline start and/or date, will apply Project Start or Baseline End Date
  • Invalid Baseline dates

Should there be invalid Baseline start and/or end dates within the file the following rules apply

  • Task Baseline start and/or end date outside Project Start and Baseline End date, system will apply Project Baseline Start and/or End date
  • File will accept empty fields for Baseline Start and/or End as generally these are tasks created post project plan being initially baselined.  User can manually enter dates within file if required as long as within Project Baseline dates.