This Work Tracking System is proof of concept to replace a deprecated tool that tracks office assignments, deadlines, and incoming and outgoing correspondence in my office via a Microsoft Access database.
- HTML
- CSS
- JavaScript
- AngularJS
- C#
- .NET
- SQL Server
-
"Correspondence Type": This is a legacy term from my office's original Work Tracking System and it is the term they used to describe what, in other words, are "work assignments".
-
"Records": Every Correspondence Type when assigned, given a due date, etc is saved as a Record in the database.
-
"Branches": My former office had several branches with nomenlature (i.e., "120L") and names (i.e. "Airframe Branch").
-
"Administrative and Technical Support": The only members of the staff, along with management with authority to update records in the Work Tracking System. Note: Currently, the sections of the app for the Administrative / Technical Support Staff and Management are the same.
-
"Flowtime": Every Correspondence Type has its own specific Flowtime. The Flowtime is the amount of time allowed for the employee to complete the assignment. The Flowtime is added to the date that the Record is entered into the Work Tracking System to populate the deadline.
-
"WTS Number": Every record in the database has a unique identifier (known to the users, and different from the Record index in the database). This is the WTS Number. The WTS Number is formatted as BRANCH/SEQUENTIAL NUMBER/YEAR. Note: The year is not currently designed to update programmatically. Users can search for Records via the WTS Number.
Employees can be assigned tasks with deadlines and all staff can search for assigned tasks.
Administrative employees enter records in the Work Tracking System. Records are assigned to technical employees. Each record is identified with a unique "WTS Number" and is given a due date. Employees can search for records assigned to them via WTS Number.
All code, and everything associated with the code, created by Steve Bogucki. stevebogucki12 @ gmail Dot com.