Requirements for Building TechCM Calendar in Alpha 5 V11 or higher.
Calendar must be able to work with existing tables and or new tables similar to the Calendar
Component currently in Alpha 5.
Calendar must be able to run in the browser internally and on the web without any licensing
requirements.
Calendar must be able to use all backend databases that currently work with Alpha 5.
New Table columns can be added at any time to the events in the Calendar.
New Table columns can be of any column type.
Calendar must be able to track events / projects / WBS / tasks by start date/time and end
date/time.
All events / projects / WBS / task entered into the Calendar must be logged with statuses.
Valid Statuses are: Active, Inactive, Completed, Pending, Approved and Cancelled and can be
changed by the users.
All events / projects / WBS / tasks and their statuses must have who initiated the action, who
was it assigned to and any action taken from that point on.
A notification system is needed to inform users with tasks responsibilities of the due dates of
tasks nearing their due dates.
Completed and Cancelled entries cannot be changed by anyone.
Changes to entries other than status Cancelled or Completed are not allowed except by the
creator of the entry and or the system administrator.
Calendar must be able to track projects from multiple sources i.e. Companies, Customers,
Vendors within a typical accounting system framework.
In other words, Calendars can be created with the same capabilities mentioned in this document
for Companies, Customers and Vendors within the system�s financial framework.
Users must have the ability to drag and drop events / projects / WBS / tasks for any day, week,
month or year and complete the entry in the Calendar similar to the Calendar Component in
Alpha 5.
Auto email notification of events / projects / WBS / tasks when nearing due dates.
Users on the same team / group can view the Calendar for all tasks assigned within their team /
group
Calendar must be able to work with existing tables and or new tables similar to the Calendar
Component currently in Alpha 5.
Calendar must be able to run in the browser internally and on the web without any licensing
requirements.
Calendar must be able to use all backend databases that currently work with Alpha 5.
New Table columns can be added at any time to the events in the Calendar.
New Table columns can be of any column type.
Calendar must be able to track events / projects / WBS / tasks by start date/time and end
date/time.
All events / projects / WBS / task entered into the Calendar must be logged with statuses.
Valid Statuses are: Active, Inactive, Completed, Pending, Approved and Cancelled and can be
changed by the users.
All events / projects / WBS / tasks and their statuses must have who initiated the action, who
was it assigned to and any action taken from that point on.
A notification system is needed to inform users with tasks responsibilities of the due dates of
tasks nearing their due dates.
Completed and Cancelled entries cannot be changed by anyone.
Changes to entries other than status Cancelled or Completed are not allowed except by the
creator of the entry and or the system administrator.
Calendar must be able to track projects from multiple sources i.e. Companies, Customers,
Vendors within a typical accounting system framework.
In other words, Calendars can be created with the same capabilities mentioned in this document
for Companies, Customers and Vendors within the system�s financial framework.
Users must have the ability to drag and drop events / projects / WBS / tasks for any day, week,
month or year and complete the entry in the Calendar similar to the Calendar Component in
Alpha 5.
Auto email notification of events / projects / WBS / tasks when nearing due dates.
Users on the same team / group can view the Calendar for all tasks assigned within their team /
group
Comment