all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||
|
|||
|
|
|
Notes:
|
|
-We need a hidden table for makes and models. Along with this, we need to monitor name changes and who is doing it. These two sections run on a global table but we need to monitor who is playing in the tables. -A database table called “models copy” was put into the main database. It was used to copy old model names across to the new table where somebody was messing around. When the dust settles, we need to remove that table at some point. -It would be very cool if we could use the interactive map and allow users (say at a trade show or just in general) to click on an area and then be taught about what goes on in that area. -The term ”splits” – it deals with payments on account. What it really deals with is how adilas virtually splits a bigger payment into smaller details to satisfy the smaller sub expense/receipts. A good analogy is ordering lunch (a few different people) and getting individual checks. The boss comes and decides to cover all of the individual checks. This creates a one-to-many relationship between a bigger master expense/receipt and smaller sub expense/receipts. The splits come into play as we use the master to satisfy the subs and create the new relationship. Another analogy – multiple invoices making up a statement. -It would be really cool if you went to a section in adilas and it showed options for what was there… a visual map to the different parts of the layout and flow. |