all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||
|
|||
|
|
|
Notes:
|
|
-On the API… we may need to go with all lower case. I started to play with dynamically looping over structures and the key names came out in all caps. I would much rather have all lower case vs. all upper case. The normal is called camel case. An example of camel case is: ThisIsCamelCase each word starts with a capital and then back to lower case. If I can’t get camel case, I’d rather have all lower case. -On the API (application programming interface)… Think of a corporation permission level. We normally do user permissions… what about corporation permissions? Interesting concept. -When creating and allowing users to have their own database and system. Allow them to turn on/off different settings such as payment types, log note types, tax categories, etc. let them tweak things out a bit more and make it feel more custom. -When building out each corporation in its own system. We may need to change how the application and session scopes get recorded and controlled. Some of these pieces will be lessened or removed. –Not trying to be negative, but this is going to be a big project. I’d dare say a full new version or product in some ways. -As long as we are talking about re-writes and changes. We need to limit the big queries that are capable of pulling tens of thousands of records. Where ever possible, it may require a re-write to split the search methods into id’s, pagination (controlling out flow), and then the actual data. Most of our queries are fairly small and very fast. However, there are a few big monsters out there. -On eCommerce … we need to run the whole thing right on the main adilas.biz site. We have an SSL, full access to data, methods, look-ups, and we can totally skip the web services portion of what is going on. Make it quick, simple, and all in one place. -We’ve had a request to merge customer and other records. Think find and replace on a customer level. This may also be handy on a vendor level, but we would need to be careful with parts and PO’s. Expense would be fine but parts may be a problem. -For inline custom code – what if we allowed users to define main pages. For example: what pages do you use for – printable invoice, start cart, view cart, add item, checkout, customer log, invoice home page, customer homepage. If different than the normal, pull those pieces in as page flow corp-wide settings. |