all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||
|
|||
|
|
|
Notes:
|
|
-We’ve had a few requests for a smaller or limited version of the sales and profit report. The report would be at a salesperson (employee) level and would only show sold info. Any cost and profits would not show up on that report. -For XML – use adilasDataRequest and adilasDataResponse as main root elements. -Inventory with attributes. One part number with multi attributes – sizes, colors, etc. -Last costs – may be a problem. Last known costs vs. average costs. We may need ICC’s pretty soon! Maybe a corp-wide setting for costing. -On new databases per corps – maybe use an auto id for invoices, deposits, expense/receipts, PO’s, time, etc. instead of assigning new numbers by direct assignment. This could help (using auto id’s) to eliminate or minimize duplicates. -When allowing persons to submit external data, suing the open API, allow for FORM scope, URL scope, and XML options. Make it flexible yet manageable. -Use adilas university, for documenting the API. -Thinking of breaking the API into main players, functions and details or options for each function. Think outlines and drill-downs. The API will be on the tech level of the application. -We are walking an interesting line… Education vs. Development… Development is fun but without education – what does it do? Education without development – feels limited or dead? We may need to mix and blend. (Kind of like faith and works – you need both.) |