Formatting Schedule Data

Schedule data is moved to the user's mailbox as an attachment to a new mail message. The user opens the message and imports the data by double-clicking the attachment. You must install Microsoft Schedule+ to import the data.

In the primary file, the schedule data appears to be another message in the message section. In the following example, the third message (in bold) is the schedule message, which is placed in the Inbox.

MAILMESSAGE,PROFS:SANFRAN(HOWARDS)
Folder,Sender,To,Cc,Bcc,Subject,Send-Date,Received-Date,Priority,Unread,Unsent,Body
,Bill Lee,Howard Snyder,,,"End of Month Report",19950321093421,,-1,,,#SALESPO1.SEC(54)
Phoenix Project,Pat Parkes,Howard Snyder,,,Back Office Review,,,,,,#SALESPO1.SEC(161)
,Howard Snyder,Howard Snyder,,,Schedule+,19951005022543,,1,TRUE,,#SALESPO1.SEC(356)

In the secondary file, set the body of the message to a length of 0. The Migration Wizard automatically adds instructions for importing the schedule file in English, German, French, or Japanese, depending on the language of your Microsoft Exchange Server.

Type,Length,Encoding,Islast,Name,Position,Format
Body,0,,FALSE,,,
Schedule,298,,True,HOWARDS.SC2,-1,
SCHEDULE+2 EXPORT VERSION 103
...

The first line in the schedule file must be a header line as follows:

SCHEDULE+2 EXPORT VERSION 103

Each line thereafter has schedule properties and values. The following table describes the differences between the schedule file format and the standard migration file format.

Tip  To see examples of the schedule file format, create examples in Schedule+ and export the calendar.

The following Schedule+ objects can be created in the schedule file format.

Each type of property can occur multiple times within the file. If objects of the same type are kept together, import performance is improved.

SCHEDULE+2 EXPORT VERSION 103
Projects:
{
    data
}
Projects:
{
    data
}
Contacts:
{
    data
}
RecurringAppointments:
{
    data
}
RecurringEvents:
{
    data
}
RecurringTasks:
{
    data
}
SingleAppointments:
{
    data
}
SingleEvents:
{
    data
}
SingleTasks:
{
    data
}

Schedule+ Projects

The following examples illustrate the projects format:

Projects:     
{
    Priority:     16945
    Text:     "Colossus Project"
}
Projects:     
{
    Priority:     16689
    Text:     "Region 6 Spring Sales Drive"
}

The following table describes the properties of projects.

For more information on priorities, see the Priority Property topic later in this section.

Schedule+ Contacts

Schedule+ contacts are separate from Microsoft Exchange Client PAB entries. There is no link between them. Depending on the configuration of your source system, contacts can be imported into Schedule+ if contact entries are created in the schedule migration file.

You can also create contacts from PAB entries in the source system. Users can delete contacts created this way, but they cannot add information from PAB entries to the contacts list.

The following example illustrates the contact format:

Contacts:     
{
    LastName:     "Lee"
    Department:     "MIS"
    AddressBusiness:     "12 Main St"
    CountryBusiness:     "USA"
    PhoneBusiness:     "415 555-9839"
    CityBusiness:     "San Francisco"
    Office:     "16/2102"
    Company:     "Ferguson & Bardell"
    Assistant:     "Sarah"
    ZipCodeBusiness:     "94105"
    CurrentPhone1:     4
    FirstName:     "William"
    StateBusiness:     "CA"
    JobTitle:     "Team Manager"
}

The following table describes the properties of contacts.

Schedule+ SingleAppointments

If attendees are invited to a migrated appointment, put their names into the Notes or Text property of the appointment. To make it easier for the user to send mail to the attendees or to add the attendees to the attendees list, use a semicolon to separate the names. The user can then copy the list of names into the To line of a message or to the attendees list and resolve them against the Address Book.

Schedule+ appointments can list outside attendees. Their unique MAPI identifier is stored with the appointment and is used to verify responses to meeting requests. Without an attendee's MAPI identifier, the display name cannot be added to the attendees list.

The following example illustrates the SingleAppointment format:

SingleAppointments:     
{
    Ring:     T
    AlarmAmount:     15
    Text:     "Attend training class."
    AlarmTypeUnit:     0
    AlarmAmountOriginal:     15
    BusyType:     0
    Start:     3-5-1996 15:00
    End:     3-5-1996 17:00
}
SingleAppointments:     
{
    Where:     "Rona's office"
    Text:     "Meet with Rona about shifting contacts to new employees.\
\
Rona Rumalski"
    Ring:     T
    AlarmAmount:     15
    Start:     3-5-1996 09:00
    BusyType:     1
    End:     3-5-1996 10:30
    AlarmTypeUnit:     0
}

The following table describes the properties of SingleAppointments.

Schedule+ SingleEvents

Events are different from appointments in the following ways:

• Events appear above the day's calendar.
• Events do not have attendees.
• Alarms for events are based on midnight.

The following example illustrates the SingleEvents format:

SingleEvents:     
{
    Ring:     T
    AlarmAmount:     2
    Text:     "River City 10 mile hike and camp. (Weather permitting.)\
Call Josh at 555-1232 to make sure it is happening."
    AlarmTypeUnit:     2
    AlarmAmount:     2
    StartDate:     3-2-1996
    EndDate:     3-3-1996
}

The following table describes the properties of SingleEvents:

Schedule+ SingleTasks

Schedule+ relates tasks to projects by using the ProjectID number. Without a ProjectID number, tasks are imported without being related to a project.

The following example illustrates the SingleTask format:

SingleTasks:     
{
    Priority:     16672
    Text:     "Update summer catalog."
    AmountActualEffort:     0
    AmountEstimatedEffort:     1
    IsTaskAutoDone:     T
    StartDate:     3-6-1996
    AmountStartWork:     4
    TypeUnitStartWork:     2
    EndDate:     3-10-1996
    TypeUnitEstimatedEffort:     2
    TypeUnitActualEffort:     2
}

The following table describes the properties of SingleTasks.

Priority Property

Schedule+ prioritizes tasks by using numbers (1 through 9) and/or letters (A through Z). For example, "A1," " 3," and "B" are valid priorities. The migration file format converts this priority to a decimal.

The following table illustrates how priorities are converted to decimal versions. The ASCII value of the letter or number is converted to a hexadecimal, the number 20 is prefixed or appended as a space and place holder, and this number is converted to a decimal.

For a number priority of 3, for example, use the hexadecimal 33 and prefix 20. The value 2033 converts to decimal 8243. For a letter priority of C, for example, take the hexadecimal 43, and append 20. The value 4320 converts to 17184.

If your existing system prioritizes by requiring both letters and numbers (for example: A1, B3, or Z9), use this procedure. Convert both to hexadecimal, concatenate (link together) the values of the letter and number, and then convert that value to decimal. For a priority of A3, for example, use the hexadecimal of A (41) and concatenate it with the hexadecimal of 3 (33). The value 4133 converts to 16691.

Schedule+ Recurring Appointments, Events, and Tasks

The following examples illustrate the format for recurring appointments, events, and tasks:

RecurringEvents:     
{
    Text:     "Yearly tax audit. Start preparations early."
    Ring:     T
    AlarmAmount:     21
    AlarmTypeUnit:     2
    StartDate:     3-4-1996
    EndDate:     3-4-1996
    RecurringType:     7
    YearInterval:     1
    DayOfMonthMask:     8
    MonthOfYearMask:     4
}
RecurringAppointments:     
{
    Text:     "SATR meeting.\
\
Big Sale."
    Ring:     T
    AlarmAmount:     15
    DayOfWeekStart:     0
    StartRecurringTime:     12:00
    YearInterval:     1
    WeekInterval:     1
    BusyType:     0
    RecurringType:     51
    StartRecurringDate:     2-26-1996
    DayOfWeekMask:     32
    EndRecurringDate:     3-4-2000
    DayOfMonthMask:     8
    EndRecurringTime:     13:00
    MonthOfYearMask:     4
    AlarmTypeUnit:     0
}
RecurringTasks:     
{
    Text:     "Check online mailbox for new mail."
    Priority:     8243
    TypeUnitActualEffort:     2
    AmountEstimatedEffort:     1
    TypeUnitEstimatedEffort:     2
    Billing:     "Billed at higher rate"
    BeforeEndOriginal:     F
    AmountStartWork:     0
    StartRecurringDate:     3-2-1996
    RecurringType:     64
    WeekInterval:     1
    DayOfWeekMask:     16
    DayOfWeekStart:     0
    DayInterval:     1
    EndRecurringDate:     8-10-1996
    TypeUnitStartWork:     2
    Ring:     T
    AlarmAmount:     0
    AlarmTypeUnit:     2
    BeforeEnd:     F
    Exceptions:     
    {
        InstanceDate:     3-3-1996
        StartDate: 3-3-1996
        EndDate:     3-4-1996
        Deleted:     F
        Text: "Check online mailbox for new mail. Check for new rates."
        Priority:     8241
        TypeUnitActualEffort:     2
        AmountEstimatedEffort:     1
        TypeUnitEstimatedEffort:     2
        BeforeEndOriginal:     F
        AmountStartWork:     0
        TypeUnitStartWork:     2
        Ring:     T
        AlarmAmount:     5
        AlarmTypeUnit:     2
        BeforeEnd:     F
    }
}

The following table describes the properties shared by recurring appointments, events, and tasks.

The following table describes additional values required for the RecurringType property.

Exceptions Property

Exceptions are deleted or modified properties of a recurring appointment or task. To delete, only two properties are required: Deleted and InstanceDate. To modify, the appointment or task must be redefined as a single appointment or task, and you must redefine the StartDate and EndDate, even if only the Location property is modified.