all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||
|
|||
|
|
|
Notes:
|
|
-I’d like to add a new set of reports that are on the adilas upper admin level. In world building terms – this is at the universe level. This would be global specs, how many customers, invoices, quotes, expense/receipts, deposits, PO’s, parts, locations, banks, cart favorite buttons, users, logins, etc. This could be daily, weekly, monthly, or custom. It could also include photos and other universe level stats. I’m not worried about the details – this is just for general stats and usage. -As a note, we need to remember to only get what we need. Each corporation or world takes care of their own business! -Other universe level reports are: How many logins per day? How many unique users per day or date range? How many images and what is their total storage size? Etc. -We may want to standardize the customer and part number data import files and structures. If yes, we could move through those files in a much quicker format. If custom is needed, then we could run that separately or on a per client basis. Basically, I’m spending too much time on some of these files. -Ideas for a new “split cart” POS interface – Steve was playing with ideas and we are thinking about making it a new standard option inside of adilas. The split cart would be my cart favorite buttons on one side and the main cart on the other side. As a button gets pushed on the left, the right side updates and shows the changes. In a way, it will be almost like having two windows open at a time but they (the two windows) will be interacting and playing together. -Here are some needed features of the split cart: - HTML frameset – my cart favorite buttons (left side), normal adilas shopping cart (right side) - New mappings on URL addresses and window targets - Custom code for different button types and button groups - Ability to reset the split cart - Ability to toggle between a normal cart and the split cart - Simple dynamic nav on the left. - dummied down interface - Maybe even a dummied down cart for the right side -Along with the split cart, it would be cool, if we had a couple more personal settings to go along with that. I was thinking: Normal cart or split cart (cart view modes), who’s cart favorites to use, and any other my cart favorite settings that might be needed. -Help our users get in and out as quick as possible. At the same time, they still need to provide enough data to make the trans-action happen. -A possible usage of “invoice classifications” (future project) is as a custom “checkpoint” for invoices. This could be a date and/or a date range, an invoice classification, and maybe some notes. Invoice classifications may also be used for eCommerce or even steps in the eCommerce process. For example: ordered, filled, skipped, backordered, etc. -A couple pages back there is an entry about making a data or business data assembly line with custom checkpoints. The invoice classifications or something like that may end up playing in or filling that need. As a note, we already do a custom mapping for “transition invoices”. The invoice classifications could easily be something like that and/or something similar. For future reference, see top_secret/secure/view_transition_dates.cfm for more info and sub settings for transition invoices. |