Generic schedule importer based on the following rules:
 
Importing a schedule data file into CruOps
 
1. Sign in as Admin
2. Select the Area whose schedule you will be importing - this is optional if the AreaID 
is included in the data file - if its not included, the Area selected will be used
3. Select Tools | Schedule Importer | Import Schedule from the menu
4. Select your schedule data file
5. Any schedules which cannot be successfully imported will be displayed. If the process 
fails, you will receive an error message. The status bar at the bottom of the Main form 
will update showing which schedule line is being imported.
6. Once completed, verify by viewing the Schedules Listing tab.
 
 
Schedule Import Data File Layout - Comma delimited fields
 
Opinits, ShiftStartDate, ShiftEndDate, ShiftLength, WorkCode, WorkType, AreaID, Remarks
 
example data file - cut and paste into a txt document, save and import - you should
receive at least one error message because of an invalid area id which will
make the person unidentified - based on I90 database
 
 
"EY","6/8/01 06:00"
"EY","6/9/01 06:00","6/9/01 14:30",480,"WK","Regular",3,"Requesting Leave"
"EY","6/10/01 07:00","6/10/01 15:30",510,"WK","Regular",27
"EY","6/11/01 08:00",,510,"WK","Regular",27,"Requesting Sick"
 
 
OpInits - 2 characters denoting the operating initials of the individual, must match 
operating initials being used in the database or the line will be rejected.
 
ShiftStartDate - must be a valid date/time - if it is not a valid date/time the line will 
be rejected.
 
ShiftEndDate - optional - if included it must be a valid date/time - if it is not a valid 
date/time the line will be rejected. If its not included and the ShiftLength is 
not included, the ShiftEndDate will default to eight hours after the ShiftStartDate.
 
ShiftLength - optional - if included it must be a number representing the length of the 
shift in minutes. Ex: 8 hour shift would be represented as 480 (8 hrs * 60mins/hr). 
If its not included and the ShiftEndDate was not included, the ShiftLength will default 
to 480 minutes (8 hours). If both ShiftEndDate and ShiftLength are included, ShiftEndDate 
will be used and the two items will not be compared for validation.

WorkCode - optional - if included it must match a workcode defined in CruOps - if it does 
not match, the line will be rejected. If its not included, the WorkCode will default to 
"WK".
 
WorkType - optional - if included it must match a work type defined in CruOps - if it does 
not match, the line will be rejected. If its not included, the WorkCode will default to 
"Regular".
 
AreaID - optional - if included it must match an AreaID defined in CruOps - if it does 
not match, the line will be rejected. If its not included, the AreaID selected at login 
will be used.

Remarks - optional - limited to 250 characters in the database. Any remarks included 
will be displayed as remarks in the schedule listing in CruOps.
 
Error checking:
 
Simple error checking for field items are accomplished to make sure the
data type expected is the data type received
 ex: shift start date is validated to make sure it is a date
 
Data value range checks and comparisons are not done.
This is left up to the schedule program which was used to generate the import file.
ex: comparisons - if a shift start time and end time are 10 hours apart, 
but the shift length supplied is for 9 hours, the shift start time and 
end time is used and no error message is generated.
ex: value range check - if a shift start time and shift end time are 20 hours 
apart, no error message is generated, the schedule is imported as is.
 
Existing schedule check - there is no check for an existing schedule for an employee 
within the new schedule time frame. In other words, if you import the same schedule 
file twice, you will have duplicate entries. Since the import option is limited to the 
admin account, the import function should only be used by a limited number of people, 
and they should know what’s been imported and what hasn’t.