Meetings, Appointments and Tasks – take the tour

Meetings, Appointments and Tasks make up most of the work performed by people. Have you ever wished that you could add and track your favourite attribute in a task? Now you can with Jetfire. It’s simple to create a custom meeting with that favourite attribute added.

The Code

View the code
The code sample contains three workflows in the JetfireMeetingWorkflows namespace – Appointment, Meeting and Task.
The Appointment workflow inherits from Formal Workflow. This means that the definition in Formal Workflow is used as is by the Appointment workflow. The Meeting and Task workflows inherit from the Appointment workflow.


// State Transition        Command       Comment
// New -> Start            new           The workflow enters the start state when instantiated
// Start -> Scheduled      Schedule
// Scheduled -> Start      UnSchedule    The user un-scheduled the appointment
// Scheduled -> Scheduled  Schedule      The user rescheduled the appointment
// Start -> Cancelled      Cancel
// Scheduled -> Cancelled  Cancel        This is an end state
// Scheduled -> Completed  Complete      This is an end state

Figure 1: State Transitions
Figure 1: State Transitions is a comment block from the code file. It shows how the workflow transitions between states. This is enforced in the workflow by qualifying methods with the ‘states’ keyword followed by the states that the method is accessible in.
There are no properties in the Appointment workflow. All properties are inherited from Formal Workflow.