all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||
|
|
|
Pink
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Notes:
|
|
What if we added in an optional tie-in from every main object to elements of time (basically add a time_id field). That would be a new database field per every main group such as deposits, invoices, PO's, expense/receipts, balance sheet items, stock/units, customers, vendor/payees, employee/users, parts/items, elements of time, and quotes. This would allow us to easily extend the sub add-on's or sub functions of time to all main players and main player groups. We could also add time id connections to smaller subs, line items, payments, or other sub tables within the groups as needed. This will help us track sub locations, sub phases, sub categories, sub types, sub progress, etc. Going way back a couple of years, we wanted to allow elements of time to virtually adopt any other player type or player group. This way we would be starting to allow that to happen from the player groups themselves (reverse connections from player groups to time). We also need ways to tie things from elements of time back out (time to other objects and/or groups), but it would really help if the objects themselves had ways to tie to time. As a general note... we could use app type id, main id, table name, and sub id on the main elements of time to create the back tie-ins. See the flex grid and media/content for ideas on using these generic tie-ins to create a multitude of one-to-many relationships. It is fun to see some of these ideas coming around. Good stuff. |