ayanova/devdocs/todo.txt

@@ -11,39 +11,11 @@
 
 	
 # Schedule form
-	based on datalist with lots of filter "handles" on it
-	needs a way to select which techs to show in which order, I guess ideally an additional saved view part as with filter for datalist
-	maybe could just add a small key to the datalistfilter that is only applicable to this?
-	Ideally the same datalist for all purposes so can just filter accordingly with built in pre-filter if single user etc
-	This is also so datalist can drive reporting
-	Needs to consolidate all sources of info that can go on display
-		sourcetype of event so wo, review, reminder... 
-	Keep in mind calendar / schedule based widgets which could be a view and a format saved (no UI space to adjust)
-		so maybe a "Make this view a dashboard widget" option?
-		Also, schedule based widgets give us something to immediately provide with initial release if we haven't got to all the widget types yet
-	From omnibus case 729
-		- user able to set whether they want to see 15 or 30 or 1 hour increments
-		- user able to set start time for day (i.e. some want 7am, some want 6am, some want 10 etc)
-		- ability to set to display either a single day (today) or a week around todays date, etc.
-		- case 1219 now incorporates saving user settings for days viewed on exit - so that part is already done (DON"T FORGET TO SAVE CONFIG USER HAS SET)
-		- Personal schedule in home area shows review, reminder and wo scheduled items for techs
-			only shows personal to that user
-		- Shared schedule for dispatch service mgmt area shows all techs and wo items
-			filterable to which techs to include 
-			savable filter
-			savable orderable which techs in which order
-			savable all settings
-			should act like filters for datalists but also for configuration stuff
-			user selects filter, techs to show, what order etc and then it just uses that when they select it as a view
-			Views could also drive schedule type dashboard widgets as well
-	Copy the fuck out of google calendar UI layout, it's popular and easy to use https://calendar.google.com/calendar/u/0/r/week?pli=1
-		however it is a bit too complex in many areas so just stick to the bare essentials and cleanliness a.m.a.p.
-		This I like about it:
-			One single PLUS button prominently displayed to add an appointment
 		
 
 	CASES
 		3766 - view schedule filtered by customer so can see at a glance all past and future for a single customer (more data table filter similarity)
+			"show all " but on a schedule to view that way instead of a data table
 		3697 - arbitrarily order schedule by user instead of built in by lastname
 		3698 - hide unassigned tech slot (or case 3697 above would take care of that too)
 		3511 - "Review" feature (was followup sched marker), appointments that link to objects and display alternatively in UI
@@ -51,23 +23,6 @@
 		1686 - ability to set how much stuff displays / alt schedule / calendar view??? Not sure really, it's a mish mash
 		729 - mass misc omnibus copied to above the useful bits
 
-SCHEDULE TODO:
-	Basically just replicate google calendar UI with our own related objects driving it
-	Day, Week, Month, Year, Schedule (not actually a calendar, but a list, do we need??), 4 days views
-	Data list functionality with filters to drive schedule, however people select them in the UI rather than the way we filter datalists now (would be ideal)
-		only real filters are who, when where who could be also a particular customer (or is that it's own view)
-	Making more schedule forms is a relatively cheap thing to do so if there is a customer centric view then maybe that's it's own schedule page
-		entirely, e.g. a "View Schedule" menu item option in Customer opens a customer centric view since it doesn't need a lot of other shit
-		(maybe even a timeline??)  This differs from the record history, it's the business history 
-		Also can schedule work from that calendar maybe? Or follow ups etc
-
-TO BE DETERMINED:
-	How / if show multiple users schedules at once?
-		same calendar, separate calendars?  How do major softwares booking multiple people do it or should it be done?
-			what are the tasks when multiple??  
-				compare, look for openings?
-
-
 
 
 //..........
@@ -785,4 +740,5 @@ BUILD 131 CHANGES OF NOTE
 - case 3946 at a glance wiki present implemented
 - Added work order states collection to report data for work order and status viz fields: Name, color, completed, locked
 - Added work order item status and priority Name and Color fields as viz fields to report data for work order
-- Review object added ReviewObjectViz field to report data which will have name of reviewed object or if it's not a named object the translated object type name instead
+- Review object added ReviewObjectViz field to report data which will have name of reviewed object or if it's not a named object the translated object type name instead
+- Added personal schedule form (home-schedule) for initial UI testing before implementing other schedule form based stuff such as service-schedule and others