all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
||||||
|
||||||
|
|
|
Notes:
|
|
-Packages – This is a sub off the parts department and section. We need a sub section where users could create packages. This would pull from inventory and virtually be its own little item (one time usage) of a bigger bulk item. This also may end up helping with conversions. -Packages could also hold prices, custom descriptions and prices, sales, expiration dates, set quantities, etc. Think of buying ground beef from the store. Most likely, you only want one part number for ground beef. However, you may sell thousands of smaller packages. Each with its own weight (quantity) and price. These could be set up as subs of the main ground beef part number. -Each package would get its own id and its own barcode number. I’m thinking about something like “pkg778” where 778 would be the auto generated id number. Anyway, something simple and unique. -On custom barcode labels – We’ve had requests to make dynamic reports connect to the barcode generator with specific dynamic content being passed to the generator page. How cool would it be if you could map and create custom label formats using a point and click interface. Then be able to assign those labels in-line or natively into the system. You name it, you create it, and you assign it to an application type. -On adding flex grid tie-ins. – we had a request to create a custom page that allows multiple pieces of flex grid be tied or added in bulk. Once again, what if you could choose which fields to use (point and click), name the custom page, and then only have those fields show up on the custom page. This could be very powerful and could create some cool options. The flex grid has over 40+ fields. If we could customize and/or assign fields especially in the add mode, that could really help. Some people have been intimidated by the flex grid… but if we could simplify it that would be awesome! The add multi part just deals with how many records or tie-ins to add at once. As a side, see the email to our rep in Colorado dated 6/7/13 for more information. -I was thinking about potential benefits for each adilas corporation having their own database. I have already previously listed a number of ideas. These just need to be added to the list. Custom fields, custom data types, custom tables, custom link and relationships, and custom naming. I also thought about individual back-ups, disaster recovery, flushing inactive or old data, and limited reach on outside hack attempts - All good things. It takes more work to manage but the benefits are awesome! -On the admin side – what about having a master data source per server. Then it (the master) could look-up what data source to use per corp. Because it could use a looked up value vs. a cryptic value, it could be harder to hack and thus better security per corporation. -The deeper we get, the more and more security will play a role in the application. -Harness the tools we already have in the shop – save settings, name reports, assign to different people, limit by users, locations, other criteria. Set defaults, change naming, and even alter or tweak in-line flow and functions. We already have thousands of pages that could be tweaked to new and huge levels. Pretty cool! -At some point I may need to look into a CDN or Content Delivery Network. A guy at Newtek said to check out a company called “Cloud Flare”. I haven’t had any time yet. In the meantime, we will most likely set up our own content management system inside of adilas. |