all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||
|
|||
|
|
|
Notes:
|
|
Sketch of a brainstorming session with a developer on relationships and how elements of time play a part of the whole: App Types (List of all 12 app types): - Customers - Invoices - Quotes - Parts/Items - Stock/Units - Elements of Time - Employee/Users - Vendor/Payee - PO’s - Expense/Receipts - Deposits - Balance Sheet Items Main Id’s (list of main id number fields) Elements of Time (main players, sub functions of time, and other options – all of the boxes in the middle were sub functions of time) 3D World Building Concepts (x= time, y = $, z = space) Time (break down time – days, hours, minutes, seconds) Developer’s ideas to help with a base time elements, time glue, or a data glue option: (as a note if we allow for different corps… you could actually even connect worlds) - Corp id 1 - App type id 1 - Main id 1 - Sub id 1 - Table name 1 - (Above – item 1) - Corp id 2 - App type id 2 - Main id 2 - Sub id 2 - Table name 2 - (Above – item 2) - Time type id - Reoccurring type id - Start date - Start time - End date - End time - Use end date - Be able to connect any two object main to main, sub to sub, main to sub, etc. - Things like single, span/range, reoccurring, etc. - Things like name, daily, weekly, monthly, annually, quarterly, hourly, etc. - As a note, we could add items 1, 2, 3, 4, 5, 6 if needed. Each one could be connected to any other player. Or even other players in other worlds. - This could really help with the application flex grid and connecting different systems together. |