all data is live and searchable
[reset this page] .
[historical web outline - entries by month] .
[adilas community funded projects] .
[contact adilas.biz support - email form] .
[help]
|
Adilas.biz Developer's Notebook Report - 12/1/2010 to 12/31/2010 - (30)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 312 |
|
Daily Tasks | 12/1/2010 |
• Working on fixed quantities, fixed prices and fixed descriptions for my cart favorites. • Added custom settings for my cart favorites and launched files. • Updated help files. |
|
|
AU 313 |
|
Daily Tasks | 12/2/2010 |
• On the phone with Steve going over future plans and needs for us and our clients. It is really fun seeing everything starting to come together – put the tiny pieces together in such a way that it creates the whole and everything works as one. • Ordered some new credit card readers for inventory. • Added a sped-up (faster) search option for adding my cart favorites. • Updating help files and testing pages. • On the phone with Steve going over the day’s progress. Every day is like Christmas! |
|
|
AU 314 |
|
Daily Tasks | 12/3/2010 |
• Invoices, emails, payments, commissions and general adilas stuff. • Research on what to include in the adilas update. • Small logo tweaks for a company. • Writing an email update to an associate about the scheduler application. • Worked on a general email update for October and November. |
|
|
AU 315 |
|
Daily Tasks | 12/4/2010 | • Went in to BATC to help my dad with the Jim Phillips foam clothing workshop. My dad set up the classroom, the multimedia stuff, live feeds from a camera, video screens and equipment and I was able to help. I also learned a ton of stuff. 30 miles. | |
|
AU 335 |
|
Daily Ideas | 12/4/2010 |
-An idea from my dad: Scheduler – “Any” - Any thing – app types and general generic build your own - Any place (loc) dynamic - Any # of events - dynamic - Any length (time) - Any # of participants – dynamic - Any price Jim Phillips – “Systems” -Narrated slide show. -It is a “System” – key word. -Teach the “why” – counter to the fast food mentality – I want it now! -A full system allows you to do things that others can’t do… -Practical – He was talking about heating your home – instead of having tons and tons of firewood, coal and propane… he had a set of foam clothing that cuts to the chase… -Technique and art of doing… -Why do you do it? Because it needs to be done! -Ask the question – what would I do? This helps to develop the why – the why takes time to figure out and develop. -Lab test between static vs. dynamic. Static – there may be other products that perform in this type of environment. Dynamic – real world is very dynamic. You have to plan for it. -Start from the bottom up! -Function vs. fashion – make a choice, this is an attitude. Does it work? Once you get it to work, you can make it look pretty. Pick your options. -Spiritual – attitude – knowledge – stuff (material things) -K = I x E - Information (correct and right) x Experience = Knowledge - Information x Experience = Knowledge. -When you understand the rules you are able to make better decisions. -Knowledge changes attitudes and outlook, this will change the way you do things. -Authority – choice. Responsibility. Accountability – natural flow. -Think dynamic as far as naming conventions. -On the scheduler – add a one to many from location to (rooms, offices, conference rooms, cabins, Kind bed, Queen bed, party room, gym, theater, etc.) a sub location(s). Think one to many… this could be a B&B, office, commercial mini mall, warehouse, etc. One location could have 2 of these, 4 of these and 12 of xyz… you get the idea. -On events, classes, trips, reservations – allow a single customer to sign-up for multiple items, packages, classes, time frames. -The customer could be one to many or one to one or share ticket – multi independent customers. Think about a meal tab that needs to be split between the parties. This may be as simple as multi-payments for a single invoice or ticket. -On both the training and scheduler maybe allow for web services or domain aliases. -Be able to register for classes, courses, tips, events, etc. -On the scheduler – allow it (the training) to be assigned to all of the adilas assets. Why not use the same application for training, visual multi-media presentations for groups, sales, stock units, parts, rentals and reservations, marketing, etc. If it is multi-media, let it go here and play well with all other pieces already in the system. Basically, a 1-many between the system items and the multi-media pieces or from a single multi-media piece out to multiple different items, audiences, etc. -Scheduling – employee time scheduling and shift planning. -what about mixed locations on the same ticket? -Multi-media – allow outside users to log in under a public username and password to submit content for review and formatting. This may require an approval process or an approval/sign off field(s). Only show items that have been approved. -Map touch – maybe color code sections and different departments. Keep the same color code for sub nav and/or reports and/or options. It might also be cool if you are on a page and could open up a visual sub menu. Keep things fast and efficient – this may require a hybrid solution. |
|
|
AU 316 |
|
Daily Tasks | 12/6/2010 |
• On the phone with a customer going over part numbers, PO’s and transfer invoices. • Had to fix a couple combo boxes for a company. They needed the years to update automatically. I kept running into old problems with old files, encrypted files and old Flash remoting, including files that weren’t on my new laptop. Spend quite a bit of time doing research on Adobe.com and finally ended up switching to my old desktop computer to make the edits. Posted files online. No charge. |
|
|
AU 317 |
|
Daily Tasks | 12/7/2010 |
• Working on a new price list for a customer. Worked on the categories and migrated parts. • Sent an email to the customers about what was done. |
|
|
AU 318 |
|
Daily Tasks | 12/8/2010 |
• Went out to a company to meet with an associate about the multi-media training application. My dad was there too. We met in his associate’s office and then went out in the plant for a small tour. We ended the day by saying adilas will build it and show a dog or pony show for full buy in on his and his company’s part. 80 miles. • On the phone with Steve going over what we are doing with adilas and the direction we are headed. We talked about needs, wants and the future. Things are going good. • Brainstorming on the multi-media application. Playing with layouts and options. |
|
|
AU 336 |
|
Daily Ideas | 12/8/2010 |
Ideas for the multi-media training application: - Parts list - What tools to use to work on this - Reading to a minimum - Build the multi-media tool and module just like LTF - Max of 4 deep (maybe only 2 deep) and then use mini swf files for additional sub nav o Main Sub 1 • Sub 2 o Sub 3 - Dynamic menus, buttons and fields - Help, volume, notes, main player field 480 x 360 - Show interactive crumb trail - Show indicators - Include options to loop, play next, choose… next - Any of the four levels can interact with the players - Able to add: video, text, still images, graphics, animation, gallery or slide shoe, audio, link to external asset, quiz/test/exam, interactive map, web/html, pdf, word, other. Brainstorming on the multi-media application; playing with layouts and options. - Maybe use I-frames to divide content… - Standard adilas header - - player - - standard footer or contents from the player if additional info is needed. Option to print extra content if needed. This might need to be three windows within a single master window – don’t scroll the player window (middle). (This text is describing a sketch in notebook.) - This could help with branding, searchable and printable text, etc. - I might even be able to use the same concept to help show the adilas scheduler application – just an idea. - Use this same interface to show the map/touch interface. - Important: Try to lessen the number of click. Leave menus open, show indicators, simulate a back-type button, etc. Make it a good experience. |
|
|
AU 319 |
|
Daily Tasks | 12/9/2010 |
• Adilas invoices, deposits and commissions for adilas. • Working on the Excel file for a company’s parts. • Finished migrating the parts and sent and invoice. • Did some research on W2’s and 1099’s. |
|
|
AU 320 |
|
Daily Tasks | 12/10/2010 |
• Research on W2’s and tax tables. Lots of waiting for the IRS phone system. • On the phone with my dad going over the ideas on the multi-media training tool. Did a quick dimdim session for him to see what I was proposing. |
|
|
AU 321 |
|
Daily Tasks | 12/13/2010 |
• Posted an out of business note on a company’s website. • Started working the show/hide features for the main homepage searches. • Also added some buttons to create new items (deposits, carts, PO’s, expense/receipts, b.s., etc.). |
|
|
AU 322 |
|
Daily Tasks | 12/14/2010 |
• Finished up all of the other pages that needed the main search from hidden. • Added a show/hide toggle switch to either show or hide the main search forms or search criteria. • Started to work on the “any” part of customer and vendor name searches. |
|
|
AU 323 |
|
Daily Tasks | 12/15/2010 |
• Invoicing and writing emails. • Recorded commissions, etc. • Updating help files for pages that will have add new buttons and collapsible main searches. • Worked on the “any” name filters for customers and vendors. • On the phone with Steve going over plans and updates. We also talked about merchant processing stuff. |
|
|
AU 324 |
|
Daily Tasks | 12/16/2010 |
• Working on the any name filters. • Added a new sub set of the invoice payment search and results. Basically, I took off the deposit info so that the users could create a printer friendly payment history for a customer. • Finished up pages and posted files online. |
|
|
AU 325 |
|
Daily Tasks | 12/17/2010 |
• Lots of time testing pages online. • Updated and checked help files. • On the phone with Steve. He gave me a whole page worth of new and additional features that are being requested by a company. Requests included: tweaks to the daily/weekly report, sales and promotion codes, alerts and messages back to the user, tips, credit card authorizations and posting, variable session length and more integrated links and page flow. • On the phone with Steve going over a request to be able to see random different expense/receipts and their line items. • Made a quick change and uploaded the pages. • Working on deposits and such. |
|
|
AU 2179 |
|
List for a Customer's Project | 12/17/2010 |
List for a customer: • Daily sales and profit report o Multi corp o Dashboard interface • Promotion codes tied to customers • Alerts, emails, and text messages (alert system) • Goal tracker o Sales and dollars • Cash drawer reconciliation o Take off location place holder (petty cash) o Make it interactive with deposits and e/r’s • Tips… o Cc authorization and approvals • Variable session time outs per user • Add customer type to the daily/weekly report • Add quantity totals to daily/weekly report • Fully interface for paying PO’s and E/R’s |
|
|
AU 326 |
|
Daily Tasks | 12/20/2010 |
• Entered a bunch of deposits, wrote checks, set up reoccurring payments and paying commissions. • Did some prep for a conference call with Steve and an associate. Steve and I were on the conference call for 1.25 hours. We talked with our associate about the adilas “any” scheduler. Recorded a client log and sent an invoice and follow up email. Great call and we are moving forward. |
|
|
AU 337 |
|
Daily Ideas | 12/21/2010 |
-Yesterday I went to the doctor and he told me that my allergies might be connected with my ear problems. The thing that I got out of it is “system” and interconnected parts. The same is true with the adilas system, one thing may have other pieces that need to be in play to get a full and healthy and happy whole. -On the scheduler – maybe have different sections that deal with scheduling, reservations and rentals. Basically, instead of having one dynamic name for it, maybe have 3 or 4 (as many as needed) depending on functionality. Ideas: mini blog, customer time clock, scheduler, dispatch, planner, reservations, booking, xyz, rentals, to do list, employee training, idea center, etc. -Review the idea center on MDI – pull it into adilas. -On the multi-media player – allow the user to determine what buttons to show. Play, pause, stop, rewind, fast forward, full speed, ¾, ½, ¼ speeds, loop, back to start, step forward, step back, volume, mute, scroll up, scroll down, scroll left, scroll right, etc. |
|
|
AU 2931 |
|
Daily Tasks | 12/21/2010 | On the phone with a client. We had to fix a problem with a special order, a refund, and a pulling apart of one part to create sub parts. We also talked about the flex grid and making floor plan payments. | |
|
AU 327 |
|
Daily Tasks | 12/22/2010 |
• Wrote an email to a customer about paying for floored units. • I was also on the phone with Steve for over an hour talking about new projects, directions and where we want to go. • Sent emails to some associates. • Working on adding in a checkbox to help keep search criteria forms open. They still can hide/show (collapse) but this is a setting to make them stay open. • I also added some new drill-down links to expense and deposit type totals. • Condensed the PO location contact details. • Changes some code on the printable permission list pages. • Posted files and did some light testing. |
|
|
AU 328 |
|
Daily Tasks | 12/23/2010 |
• Worked on help files and testing files online. • Did some review and research. • Spent some time thinking and brainstorming on a needs analysis for the interactive map and navigation system. Got a couple pages on notes. |
|
|
AU 2180 |
|
Brainstorming - Goals for the Interactive Map/Touch | 12/23/2010 |
Spanning from December 23, 2010 – August 8, 2011 GOALS FOR THE INTERACTIVE MAP/TOUCH 1. Visual layout and virtual navigation tool (Color code permissions – very simple: -green means go, -red means no go or stop) 2. Not all items are physical. I may need to assign a room or area that can hold or maintain a concept. 3. I want to put like pieces together. Eventually, I want to use it to help teach flow and concepts (theory). 4. I want it very open (show all p9eces) yet limited as far as access. Permissions. 5. I want it to look appealing (simple yet classy). It needs to do lots of things but maybe some of the pieces will need to be a layer deeper than the surface – say a sub set or item sub set. 6. When I click a sub, lock all main buttons, show the subs (with permissions) and options. 7. I’m not worried about eh back button or holding a sub menu. However, it might be cool if we could pass things back and forth to help with “where am I” and sub of sub navigation. Say subs on the invoice homepage (reports, searches, new, etc.) or even subs on the actual invoice (main, edit, printable, history, verify). (Main map, top level nav, sub level nav. Map: main, sub, item) 8. I’m actually hoping that this flash app will help lower the overall system needs and bandwidth. I’m trying to simplify things not make them more complicated or harder to understand. I want it to be very logical and easy to learn. (Map Sketches: see photo gallery) Don’t worry about the outside shape until the end. “Things don’t have to be square” What about? - Maintenance - Favorites - Locations - Departments - Permissions - Other reports - Recipe/builds - Forms/paperwork - System basics - Quick search - Help videos - Tutorials - Photos & scans - Taxes & collected items - Corp-wide settings - eCommerce - Check requests - Quick search - Reoccurring invoices - Rentals, reservations, scheduling: (person, place or thing) – this is not done yet but would be very cool. This could help users see another component called time management. - Maybe put time and waiting room in the middle of the diagram. Maybe include some different rooms or levels. - Some additional items have been added in case we want to use the map as a navigation tool. 9. Show a crumb trail or GPS locator of where you are at any given times… “Where am I at?” (this might go right in the header or footer with vars like the help file for main, sub & item levels.) 10. I need to be able to handle corp-wide setting and naming conventions. This means that button names may need to be dynamic. Colors also need to be dynamic. This will help with consistency. 11. Easy on the reading… (less is more), try to show things visually without going super icon happy. 12. I know that people will be using this with phones and touch screens, make it friendly… 13. Not everything needs to be forced into this visual nav and orientation concept. Most people (right now) will be using a mouse not their fingers. 14. Plan for future growth… It will be coming… For sure! 15. How much data is needed for the player? o Date o Corp-wide settings (verbage) o Permissions – (only active) o Small item details and values (mapping to subs) o Colors 16. Maybe a status bar-type feature to talk to the users… (see ARA flash app or MDI homepage app) 17. Be consistent… I have over 100+ permissions (& growing), I have 500+ pages (& growing). I need to combine all of these pieces into a single application that is simple and easy to use. 18. Audience… casual browser (just looking around), Managers (using multiple & different sections at a high level), Admin (using all areas on a casual level), users (every day, all day, 50-100 times a day), hardcore/power users (every section at super high levels, with high frequency), Accountants/Bookkeepers (specialized usage). 19. We will need personal settings to help with how to show the main homepage. I would like to replace the current homepage with the map touch. However, I know some folks are very fast with the classic html version. Maybe have some options. o Classic only o Map only o Both w/map on top– maybe just these two o Both w/classic on top – maybe just these two o My favorite button links – this is a third option and is similar to the my cart favorites but for system navigation and page flow. 20. I’d like to use a building metaphor (rooms and doors and hallways). However the real application is more like a solar system with start clusters and orbits… (sphere) 21. Coming back to the audience… Most of our current users are 16-60 years old. I would love to get it to the level 10-80 years old. Make it super simple. We can always add more features later on if needed. Eventually I would like to get this in to schools and teach an upcoming generation… 22. Looking ahead… Most people are using desktop units and monitors or standard laptops. More and more people are going to smaller and smaller devices with more and more interactivity and “richness” (user interface). Where are we headed? 23. If I have all of the basics right in front of a user… this might be a great place to help educate and show how things interact… This could be right on top of the map and show audio and small presentations of flow, options, and theory… We really need this! 24. Every morning ask the user what they want to see. Then store that value in the session scope. Have a link to reset or change interface. o Interactive platform (Flash) o Classic web interface o My Quick buttons 25. On the pages that have multiple options or search forms, provide options to only show requested forms (virtual page filter). This would work great on advanced searches, payroll homepage, etc. 26. Be able to filter existing results. Basically, make the data very easy to get at and then allow specific forms to filter the data. 27. Maybe the choice for the different skins could be on the bottom of the page as small thumbnails. 28. We may need to add in order to simplify. Add page filters, new drill-down options, etc. Break pieces in to smaller bit size pieces. 29. On the ideas and sharing (button) section. Provide an idea center type interface along with updates, tips, and community. Maybe a small forum-type deal at some point. This is where we can help the users steer the ship. Allow for comments to be submitted (maybe not shown until approved). 30. Concepts, theory, basics, dreams… show small analogies, ideas, direction, vision. Business data sphere, 1-many, client server, relationships, flow, data mapping, etc. Cause and effect, different levels, permissions, history, future. 31. It is okay to have holes… play the game (think golf). 32. Back on #25 maybe we could use buttons to help the users. Say they wanted to search invoices… maybe show something like this: (see sketch in photo gallery) o Search main invoice details – Search invoice line items – Search invoice payments – Show all search forms (3) o Just an idea… help the users know what they are looking for. o Maybe use an image map or graphic for the navigation 33. When landing on a main homepage… maybe add a similar graphic to help educate uses as to what is available. Maybe links or buttons that show: Maybe don’t even show any records right off the bat… have them tell us what they want… Or maybe run a couple of groups and use those as part of the main home page o Buttons with icons & light verbage (maybe make the buttons longer…) o Reports o Basic search o Add new o Advanced search o Basic search o Last record o Last 25 o Last 50 o Last 100 o All o Today o Yesterday o Tomorrow o This week o Last week o This month o Last month o Ytd o When using icons allow them to be standard for flash, html, images, etc. o Maybe check for flash on pages… if they have it use it… if not, have a back-up option 34. The main homepage searches may need to be buried one level deeper. Or we need to look at how to get the biggest bang for the buck without hurting the server. Quick groups with drill-downs may be our best option. Move searches to a page called basic search or something. 35. Dreamweaver has an editor tool to help with image maps. 36. As of 6/9/11... the goal has switched to just show where we are going until we can get it all done. We have to buy some time to get the other pieces in to play. 37. Add a standalone homepage for every section (in the interactive map) this will help with favorite button links. 38. On the top of each page… add a visual crumb trail of, you are here… (map) (invoices, edit main) 39. The graphics may be simple if we could use a mini version of the page or section where we are headed to. Basically, instead of spending tons and tons of time developing hundreds of new icons, use the mini page version. It may add consistency without tons of extra work. Also put numbers out to the side to help with tech support. Then again it might get touch with dynamics and permissions. Maybe number everything and show a red light or green light for permissions. o Basic Search (green) o Advanced Search (green) o Add/Edit Sub Type (red) o Spacing – Quick & brief description 40. Related to the above idea… the graphic should be around 100X60(ish) and there should also be different help options. Quick help – getting started – step by step – more help. Not sure on wording but help to educate your users. 41. When showing sub menus and options… make sure and remember the custom code directory, the web services stuff, and other hidden tools that may be needed on a one-by-one basis. The reason for this note is these are some pages and tools that are hidden but still serve a purpose. We may need to increase the page count so that each section has a good landing spot (a sub home page or base). 42. What if we took the permissions to a graphical interface as well. That might make it more intuitive and easier to give and assign permissions. |
|
|
AU 329 |
|
Daily Tasks | 12/24/2010 |
• Working and brainstorming on the interactive platform map. Drawing ideas on paper. • Spent over an hour on the phone with Steve going over other ideas. |
|
|
AU 330 |
|
Daily Tasks | 12/27/2010 |
• On the phone with Steve going over progress and direction, good stuff. • Answering phone calls and doing tech support. • Research on Blueberry screen capture software, looked pretty cool; it runs about $200. • Random emails and such. • Brainstorming on the interactive platform map. |
|
|
AU 331 |
|
Daily Tasks | 12/28/2010 |
• Working on the mock-up for the interactive platform map. • On the phone with an associate going over new features and changes. • Fixing an invoice for an associate. • Recording web hosting bills. |
|
|
AU 332 |
|
Daily Tasks | 12/29/2010 | • On the phone with Steve going over year end stuff and ideas and needs for adilas. | |
|
AU 333 |
|
Daily Tasks | 12/30/2010 |
• Emails and new logo for a company’s play site. • Working on Authorize.Net research and going over documentation. Got stuck on XML name spaces. |
|
|
AU 334 |
|
Daily Tasks | 12/31/2010 |
• Working through the pages for Authorize.Net gateway connections. • Working on submitting transactions via manual entry and card present modes. • Full database back-up. |
|
|
AU 3564 |
|
2010 | 12/31/2010 |
YEARLY ACCOMPLISHMENTS 2010 Steve, This is a list of things that happened and accomplishments made during the 2010 year on adilas. It was a great year with tons of great stuff. If you need more detail, just let me know. I have everything documented down to the date. January 2010: • Brandon and Andy created their first video tutorial. It never got published but it was a 4 minute video on using the adilas shopping cart. • Small face lift to the main adilas.biz site. Added the cloud background. • Created a number of new flyers. Added options for dynamic name and contact info. • Lots of brainstorming on marketing, what do we do, and how can we get it out to the people? • Came up with a new slogan: Your date, you cache & retrieve it, we secure it. • Prep and research for the dewy decimal system. • Encoded sensitive database fields for storage. Examples: bank accounts, routing numbers, customer and employee SSN’s, driver license numbers, EIN’s, and usernames. Passwords were already encoded prior to this. • Added a forgot password helper page. February 2010: • Added a multiplier for the recipe/build prep page. • Added the add as advanced PO line item page. This page allowed for mini conversion calculations during the add line item process. • Added new PDF forms. 1 for Texas and 2 for Colorado (paperwork). • Posted the first round of the dewy decimal stuff online. Hundreds of files were updated. • Small fix on internal transfer invoices. Added current costs to items. March 2010: • Added units of measure to parts, PO’s, invoices, and quotes. • Activated corp-wide settings: show bin numbers, show unit of measure, and show line item numbers. • Steve loaned some money to adilas. Thanks! • Added a sort order option to PO and invoice line items. Included a bulk sort page for changing multiple sort values at a single time. • Added code to help automate bad debt payments. • Added the profit and discount calculator. Linked up the profit and discount calculator with the loan payment calculator. • Brandon and Andy worked on some marketing ideas. • Added a tools and features list to the main adilas.biz homepage. Also a small scrolling flash movie with the features. Most of the ideas came from Brandon and Andy’s marketing sessions. April 2010: • Added special line item settings to the corp-wide settings. Over 100+ fields. Things like: Labor, Supplies, Other, Collected, Fee, Dealer Handling, Discount, Freight, etc. • Added a merchant processing prep step to help speed up the transactions. We were experiencing long wait times (every once in a while). • Added a grouped customer log report. • Added the profit percentage to the global parts mark-up tool. • Added a price helper field to the add/edit number page. Local java script to help with profit margins, mark-ups, and pricing. • Added a price switch to trailer and toppers. They were always a mark-up value and we added options to choose between a list price and the mark-up value that was calculated on the fly from the basis. • Applied the stock/unit price switch to all stock/units and made it part of the global stock/unit mark-up tool. May 2010: • Created the mini invoice or 3” customer receipt. • Added the last 4 of the credit card numbers to the payment notes for reference. • Tons of time working onsite at an adilas client’s. Great ideas and training ground. • Added the barcode generator. Added page tie-ins and posted a free barcode generator on the main adilas.biz homepage. • Added a recalc taxes switch for invoices with multiple locations. This is an after the fact deal and allowed for items to be pulled from one location and then flipped to another location. The taxes would be recalculated and invoice values changed. • Added the financial flow calculator and worksheet. June 2010: • Spent more onsite time at a client’s (on and off throughout the entire month of June). • Added a new tax category called “With Tax Included”. This helps back into a bottom dollar value. • Added a discount calculation option right from the profit and discount calculator page. • Added a printer friendly link to the printable PO page. Took off all of the extra navigation and quick search info. • Lots of new corp-wide settings. Added the barcode quick cart, quick cash checkout, number of payments on checkout, customer web settings, show/hide prices, web return address, and barcode label sizes. • Changed all of the disabled/helper fields to a light blue color with black text. The old way was a white field with a light grey text value. The new fields stand out and are easier to read. • Added the PO quantity to the add/edit parts page. This is really handy when adding new parts from within the PO line items mode. • Added the apply quick discount to the edit cart line items page. • Added the auto calculate change due setting. Recorded the info and helped show the actual change due. July 2010: • Brandon and family moved from Salida, CO to the Logan, UT area. Salida was the birth place of adilas.biz application. Spell Salida backwards… you get adilas. (2001-2010 9 years) • Added tons of new details to the grouped daily/weekly reports. Showed tons of new break-downs and details with drill-down links to underlying data. • Added a corp-wide setting to help limit and/or open up location specific inventory tracking. • Major push to activate all existing corp-wide settings. Didn’t actually complete until August 2010. • Added the key word “All” to all of the quick searches. August 2010: • Combined a push on all of the corp-wide settings. • Added external customer PO #’s to invoices and quotes. • Finished up the basic corp-wide settings. In all, updated and changed over 700+ files in all. Files were from the main adilas.biz site, secure backend, data components, web/customer files, etc. • Did some page clean-up and added some CSS (style sheet) changes to every page in the site (while checking for corp-wide settings). Tightened up the overall look and feel of the application (minor changes to the eye but helped to standardize code and flow). • Added new drill-down links to the history homepage report. • Created the mini version of the daily/weekly report (3” format). September 2010: • Added a corp-wide setting for specific unit names. • Added a new global find and replace part number feature or tool. • Added the first round of the advanced add to cart section or page. • Added a gateway connection to the Merchant One online credit card gateway. This was the second merchant processing option for adilas customers. • Added a test page for all merchant processing accounts. • Did a full rework on the USAePay gateway code and merchant processing code. This rework eliminated the random slow connections and made the entire system seem like it was working as fast as lightning. USAePay was the original merchant gateway added to the adilas.biz system (11/2009). October 2010: • Tons of brainstorming and documenting ideas and concepts. Worked on mapping out system players and processes on paper. • Created an interactive map of the adilas business platform. Map is just in concept stage and was drawings and graphics. Used a “building” layout to show players, concepts, and virtual departments. The building metaphor has rooms, sections, hallways, doors, and shows relative connections of the pieces (strategically placed items to show flow and relationships). • Presented the map concept during a whiteboard session in Salida. • Added all special line items, as their own group, to the history homepage as drill-down links. • Lots of brainstorming on the scheduler application and the element of “time”. • Ordered a new dedicated server for adilas.biz. • Switched to ColdFusion 9 as our scripting environment. • Tweaked the code that deals with changing part numbers. New code will help to cascade changes to the appropriate other tables. Much cleaner and hug time saver. • Went to live on the new dedicated server. Saw major increase in uptime and speeds. • Put up the first round of the adilasuniversity.biz site. Small graphic with some links and some verbage. November 2010 • Added some new filters on the update inventory counts pages. They were a barcode filter and a vendor quick switch field. • We have over 100+ domain names pointed to the adilasuniversity.biz site. This is mostly for future marketing and domain real-estate protection. • Added a link right from the default photo (thumbnail) to the add/edit photo page. Idea came from a guy named Logan out of Denver, CO. • Added a total or bottom dollar value to the advanced add to cart page. • Full rework on the advanced add to cart section. Included tax calcs, back calcs to quantity and prices, discounts, mark=ups, etc. • Added the part category as a filter on the main part number search. • Added the my cart favorites section. This is a user-maintained dynamic button section that allows for searching of parts, recipe/builds, adding items to cart, displaying advanced add to cart options, and custom setting (quantity, price, and description). • Brainstorming on adilas university and a multi-media training tool. December 2010: • Added a special my cart favorites search part number interface. • Posted an out of business note on the Morning Star Automotive website. The turning of an era! Thank you Morning Star! You got us where we are today! (site will be left up as a demo site) • Added buttons to create new items (deposits, carts, invoices, quotes, PO’s, expense/receipts, BSI, etc.) • Added show/hide toggle buttons to show/hide the main search criteria for reports. • Added the “Any” name option for customers and vendors. • Reworked the customer payment history report. Allowed custom settings to be applied and the ability to hide the deposit info. Basically, a printable customer payment history report. • Added a checkbox to help keep the search criteria open if needed (got a little too aggressive on the show/hide options). • Condensed the PO location/contact info for printable PO’s. • Working on a graphic version for the interactive business platform map. Really excited about the future! |
|