Search The Adilas.biz Developer's Notebook
Time Period:
Daily (enter the day you want to see)
Monthly
Custom Date Range to
Template Filter:
Color Code:
General Text Filter:

(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:
 
Adilas.biz Developer's Notebook Report - 2/1/2014 to 2/28/2014 - (50)
Photos
Time Id Color Title/Caption Start Date   Notes
Click to view time photos.
Adi 838 Packages and Conversions 2/1/2014   Steve and Brandon had a brainstorming session on Saturday night. We talked about taxes per part category. World building levels and tons and tons on parts, conversions, and packages.
 
Click to view time photos.
AU 1965 Daily Tasks 2/1/2014   • Emails.
• Pulling down a copy of the adilas database. This copy was as of 1/21/14, when we split the servers. Also working on search options for package and RFID tags. Added new search options to both advanced PO and invoice line item searches. Posted files online.
• Recording notes and making a back-up copy of all code files.
• Went in to Salida to work with Steve. I got him new code, new files, and updated his laptop computer. We then did three different brainstorming sessions. We did one full whiteboard on calculating taxes based on part categories. We did a full whiteboard session on world building concepts and how companies could possibly configure their worlds and universe related pieces. We then spent the rest of the evening going over RFID tags, packages, and conversions. This was a pretty long session and we got some really good ideas. As a note, we (Steve) took some pictures of the whiteboard. See element of time id #838 inside of adilas for the photos.
 
Click to view time photos.
AU 1969 Daily Ideas 2/1/2014   -We need to create a graphic to help see the vision and features and potential. This deals with world building concepts.
1. Universe Level
2. Galaxies
3. Clusters
4. Solar Systems
5. Worlds
6. Locations
7. Groups
8. Individuals
9. Data
10. Run all levels over time

-On locations and tax settings, add a new file that will allow taxes to be applied only to specific part categories. We are thinking a small text field and a comma separated list of categories. We would also like to link to a list of part categories to make it easy to get the id numbers.
-Login idea – Currently, we require a login every time. Steve thought that it would be cool to help save some of those settings if a user registers a specific device or IP address. That might help speed things up, but it may also open up a possible security hole. Maybe store cookies or an actual database lookup.
-On the hardcoded part number “verbage”, we need to change the price to $0 instead of $1. Idea came from a client.
-Steve would like us to put a list of adilas clients online. This would be advertising for companies and might help with Google search results. This would be corporation name, address, city, state, zip, and maybe logo. As a note, we may need to allow corporation to show/hide this information.
 
Click to view time photos.
AU 2925 February 2014 Monthly Recap 2/1/2014   This month adilas developers connected with Full Circle Interactive Media and began more intensive work on the adilas API (application programming interface). Full Circle is the first of a hopefully unlimited number of 3rd party solutions that will be able to work in tandem with the adilas application to offer additional services and more custom options.

All of these outside service companies or applications will eventually have to connect through the adilas API. Lots of work over many months has gone into the adilas API and will continue to do so until adilas has a fully documented and accessible API where anyone can receive permission and have the ability to come and play. This will bring unlimited customization and additional options, and this is where the future of adilas is going!

This month also marked one year for the free, 3-day adilas monthly training. We have had many great training sessions and see education and training as a growing need in adilas. In response to that need adilas also started offering weekly online training classes this month. Some exciting new functionality added to adilas this month is the ability to change sales tax per part category, shopping carts and invoices coded to hold RFID tags, and new options for advanced searching of PO and invoice line items.

*We hope you are enjoying the adilas developer's notebook! Please utilize and explore the vast search capabilities of adilas to find more information throughout the developer's notebook. For further questions, or help, please feel free to contact us at: support@adilas.biz.
 
Click to view time photos.
AU 1966 Daily Tasks 2/2/2014   • Traveled home from the Denver trip. Total mileage was listed on entry for 1/27/14. Great trip.
 
Click to view time photos.
AU 1967 Daily Tasks 2/3/2014   • An intern came over and we chatted about the week, updates, training, and new and upcoming projects.
• Prep work for projects for the intern. Light training on expense/receipts. I had him print out his own pay check out of adilas.
• Backing up files, databases, and recording notes in notebook. Talking with the intern about potential and options. He has a natural entrepreneurial spirit and I was having fun encouraging those traits.
• Burning disks of the January adilas training course. The training footage was for users who were online and requested a copy of the seminars. Emails and other tech support stuff.
• Went into town to mail the training disks. Put a number of back-up disks into the safe deposit box. 20 miles.
• Reviewing notes that my sister took on our trip to Denver. Looked at the notes from all three days of training and notes from the team meeting on 1/31/14.
• Recording notes in my notebook.
• New patient uploads for companies. As a note, all files were prepped by the intern and then uploaded by me.
 
Click to view time photos.
AU 1968 Daily Tasks 2/4/2014   • Emails and phone calls.
• Emails and prep for a phone call.
• An intern and I had a 30 minute conference call with someone from Full Circle Interactive Media. We are talking about bringing on Full Circle to help handle email and text messaging options for our clients. We talked API options back and forth. He was recommending that we use a server called Taffy as part of the Rest API. Good conversation. I then talked with both the interns about the upcoming adilas API and some of the structure of that. We had a good discussion I also talked with both guys about training other developers. We are trying to figure out best practices and standard requirements. It is kind of a learning process for all of us.
• On the phone with Steve going over options for training. My sister came over and we had a small conference call. Planning on having my sister start doing weekly training.
• Working with my sister on expense/receipts and bills. Also did some light planning for upcoming training sessions.
• Scanning bills and getting organized. Things are kind of crazy right now.
• New logo for some companies.
 
Click to view time photos.
AU 3668 Tech - Full Circle Planning 2/4/2014   Full Circle:
- Rest API – gate keeper
- Checkbox in or out
o Past code
o Corp key
o URL to the correct box – get & post
- User list – who gets access
- SSL testing or staying area database, datasource, FTP
- Proof of concept
o Opt in/out
o Last purchase date
o Last purchase location
- Taffy
o Frontend controller
o All traffic goes through index.cfm
- Cf 10 has their own
- Taffy API
- Cf 10 Rest API
- Cf cfc Remote
 
Click to view time photos.
AU 2008 Daily Tasks 2/5/2014   • Updating small help files changes. Recording information about new dedicated boxes.
• On the phone with tech support going over some server configurations. Added auto shutdowns on all new boxes. Also asked some ColdFusion administrator questions.
• Talking with an intern about web service options. We are looking into a package called Taffy as well as native ColdFusion passing simple variables.
• Recording information about what is required for new servers. Almost creating a standard operating procedure (SOP) for new services.
• New logo for a company.
• Research on web services and suppressing white space on ColdFusion output. Helping an intern with his gallery projects. He is currently working on employee/users.
• Working on using a page to help with web services and passing JSON (java script object notation) objects back and forth. Burned a copy of the Denver training course for a client in Texas.
• Working on passing JSON objects in ColdFusion. Got stuck and started looking online for ideas.
 
Click to view time photos.
AU 2029 Daily Ideas 2/5/2014   -We may need to check the conversion process between customers and payee/vendors. During testing I converted an existing customer into a payee so that I could pay them. The problem is I was not able to search and find the newly converted payee. It existed and was added to the expense/receipt but I wasn’t able to find it through the normal vendor/payee search. Possible disconnect that needs to be checked into.
 
Click to view time photos.
AU 2009 Daily Tasks 2/6/2014   • Customer upload for a client in the Chicago area. Emails and light tech support. Did two vendor uploads and invoiced client. More emails.
• Went in to Bridgerland to work with an intern on his code for new gateways. We set up dual screens and monitors and I was checking code on one side and he was reading code on the other side. We went through code for USAePay, Merchant One, Maxx Merchants, CHARGE Anywhere, and also spent some time looking at Authorize.net code. Their code is a little tricky just because it has so many variables. Another intern was there all day as well. Great work session. 30 miles.
• Prep work for a customer upload for a client. Migrating from spreadsheet to temporary databases.
• Working on the migration file for a client. The upload has thousands of records, flex grid, additional contacts, etc.
 
Click to view time photos.
AU 2030 Daily Ideas 2/6/2014   -I heard a fun quote yesterday. I heard this from a lady at Bridgerland. “Sometimes we get caught up in the thick of thin things.” Anyway, I thought that is kind of fun.
 
Click to view time photos.
AU 2010 Daily Tasks 2/7/2014   • Finished up the patient upload for a client. The total time was three hours due to the amount of data that already existed and needed to be checked and either added to the system or updated existing data. The process was a little bit more in-depth. Invoiced the customer.
 
No po photos available. Click to view time details.
Adi 835 Promised Custom Code For Natural Remedies 2/8/2014   Promised a custom label job by 2/8. The project was quoted at $100. We already have the PDF label done. It just needs to be wired up. The trick here is that the custom label needs to be fed per line item not by just connecting to the main invoice.
 
Click to view time photos.
AU 2011 Daily Tasks 2/8/2014   • Working on adding RFID and package tags to carts and invoices. Reading pages and pages of state rules for labeling and packaging. This was the first time that I had seen any of the actual rules. I only read the labeling and packaging rules. This was dealing with state requirements for medical and retail marijuana sales in the state of Colorado.
• Working on new tweaks to the adilas shopping cart to help handle new labeling requirements.
• On the phone with Steve going over questions and hot topics. The current hot topics are dealing with labels, tax categories per part categories, and custom projects and promises.

• Emails and tech support.
• Finished up the new changes on cart and invoice line items and new label requirements. Posted files online.
• Start working on adding special sales taxes per parts category. Certain items need to be taxed higher or lower than others. Our plan is to add a new field to the locations and tax settings. The new fields will be per location and per special tax option per location.
• Working on new code to allow different tax rates per location and per part category.
 
Click to view time photos.
AU 3669 Brainstorming: Taxes per Part Category 2/8/2014   Working on taxes per part category:
- Method: get the tax rate
- Limit other tax 1 category list
- Remember advanced add to cart
- Cart.cfc
- Carts
- Invoices
- Quotes
- Adv add & edits
- Edits
- Shop – eCommerce
- Buttons
- Recipes
- Special line items
- Normal & with tax included
 
Click to view time photos.
AU 2012 Daily Tasks 2/10/2014   • Emails.
• Listing new online classes. Getting my sister’s new weekly classes listed and online. Planning the February adilas training class into sections.
• Emails and tech support. Emails about custom labels, RFID tags, and upcoming packaging options.
• Working a new flyer for the February training class. Broke the 3-day training session into 12 different mini sessions. This should help with organization and keeping us more on task. Adding flyer and graphics to different pages.
• Finished up the first round of weekly classes and new training information. Posted files on all servers and checked things out. Added a link to show my sister teaching a section on systems thinking to the login and news and updates page. My sister will be teaching some weekly classes online for us. That is exciting!
 
Click to view time photos.
AU 2031 Daily Ideas 2/10/2014   -Idea from an intern about training. He thought that it would be cool if we allowed users to submit questions or topics prior, and then field those questions or topics in a session or two. Basically, give the users a chance to ask questions, pose scenarios, and become involved. Great idea. The key is submitting the questions prior to the training event.
 
Click to view time photos.
AU 2013 Daily Tasks 2/11/2014   • Working on cfhttp options for passing variables over the web. Very simple web services using form fields and simple text values.
• Started working on the new adilas API (application programming interface). Working on backend structure, flow and processes. Started coming up with parameters, validation, and creating a testing environment. Exciting stuff. This is part of the future of where we are headed. Yee haw!
 
Click to view time photos.
AU 2014 Daily Tasks 2/12/2014   • Recording notes and ideas on and in the new API backbone pages. Basically a to-do list for our API stuff.
• Working on a general API validation function to help with inline validation of dates, numbers, and strings or text values. Worked on the test page to help with a mini object builder page.
• Went in to Bridgerland to work with the interns. Spent the first hour working with an intern on the new adilas API and where it is headed. 30 miles.
• Working with the other intern on launching the code for the content server. Going through page by page and signing off on code.
• Paying bills, writing checks, and doing email stuff.
 
Click to view time photos.
AU 2032 Daily Ideas 2/12/2014   -Maybe consider making media/content a new main application type. It would also be cool to have a quick search option for files, media, and content stuff.
-On the interactive map… we may need a button to help with media/content. It may need to go up by the photo and scans button.
 
Click to view time photos.
AU 2015 Daily Tasks 2/13/2014   • Phone calls, tech support, and emails.
• Went in to Bridgerland to work with an intern on the media and content project. I worked on a mini object builder page to help an intern with the API and web services. Got some customer uploads prepped for the interns. We watched my sister’s first weekly training session on settings and permissions. She went for an hour and really did a great job. I was very impressed. She had done quite a bit of prep in reading, making an outline, a work sheet, and then presenting it. Great job! After lunch, an intern and I had a great session on what a code review or sign-off session was. My favorite part of our session was having both of us up at the whiteboard drawing out processes. We then went into code and did some testing. It was a great session. See other notes for some details. 30 miles.

• Went out to my brother’s house to get some video clips. We also talked about options for employment. My brother owes me some back pay hours. He is going to start working some of those off by taking flyers around and participating in training sessions. We also came up with a deal to set a rough budget per training session as far as cost to do video editing.
• Went back in to Smithfield to get my brother a check and some flyers. I then went to my parent’s house to take my sister some video clips and pick up a power cord for my laptop. I ended up chatting with my mom and dad about adilas for quite a while. Part of what they like about adilas is that we are helping people get skills and giving chances for individual growth. If truth be told, I really get a kick out of helping people. That is fun! 20 miles.
• On the phone with my sister going over her classes that she did today. Good stuff and great start. We also talked about some upcoming projects, options, and vision of where we are going. It sure is fun to dream. We talked quite a bit about some of the future and potential of the elements of time section and how we, adilas, will use that for training, recording, and making assets become available.
 
Click to view time photos.
AU 2033 Daily Ideas 2/13/2014   -An intern and I talked about the check-off or sign-off process for code. We determined about levels… (Little sketch on notebook page – see scans in photo gallery)

Scratch (testing & development) – Sign-off (line by line, try to break it, check everything, details) – Approval – Use or Deploy to the full adilas system
During the sign-off phase… We need to:

- Check structure and layout
- Spacing, tabs, aesthetics
- Comments, documentation, hints, and tips
- Code and verifying logic (try to break it)
- Spelling, output, results
- Check for useless arms (like a T-rex)

The intern then boiled that down into:

- Backend, coders, & maintenance – (nerds & techs)
- Runtime & execution – (computers and servers)
- Frontend & users & output – (users & people) & (Web & API – (unknown usages))
-Use elements of time for classes and training. We could use the calendar, the notes, the types or colors, the photo gallery, and soon the media/content section. The other content could be agendas, links to video recordings, and any other handouts or documents that are used. It will be cool to put and keep everything all together.

-This is an idea that I had years and years ago but I’d like to record it again in part… I would love to use adilas as the backbone tracking software for a multi-person, multi-company challenge that has different people or groups try to build new hybrid engines that use 10-12 different forms of energy. Basically, set the rules of the challenge, set-up a prize for the winners, and then use adilas to track the whole process from start to finish. This would be all the inventory, expenses, draws, deposits, elements of time, events, photos, scans, documents, etc. Part of the game would be that they, the participants, would have to use adilas and report their progress and findings to the world through updates and documentation. Run the contest for a year and even help cover the different teams through video, TV, or something to help document the process. One huge key is that all of the findings and ideas would become public knowledge. Help push the ball forward. There are hybrid engines or energy sources out there already… what if we brought them all together into a multi-hybrid system. The contest would be on the toy or smaller level. Once we work out details and ideas, we could then take those ideas to different bigger industries. See other notebooks for other ideas.

-My sister did some great training on permissions and settings. She made a small Word document with the ideas all laid out. Maybe think of ways to break the permissions and settings into smaller subjects, topics, and categories. If we could take it to a visual level, that would be awesome. Maybe think about the adilas map or the GPS core layout graphic as the visual top level layout.
As a note, the first part of March 2014 we started to change our approach… Permissions and settings are tools to help with custom usage and custom functionality. Maybe focus more on the outcome vs. the tools.
-As we get deeper and deeper… Maybe start using elements of time as our own social media venue. It could be like combining Twitter, Facebook, and LinkedIn all in one. This involves people (vendors, users, customers), logs, photos, scans, media, other content, events, dates, notes, sharing, etc. In a way, that is kind of our plan with adilas world, adilas university, and adilas in general. Adilas = All Data Is Live And Searchable!

-Along with the idea above about using adilas as a social media venue… what if we could also combine other pieces of the puzzle such as links to their personal websites, calendar events, eCommerce, history of interactions and transactions, etc. Bring things together. This could be frontend, backend, sales, support, availability, resources, options, etc. When you start talking systems or system thinking, you really start bringing things together.
-Think about the movie “Up” from Disney & Pixar. Maybe do a virtual commercial to help tell the story of what is going on and growth that has occurred. There is a fun section in the movie “Up” where it shows a story and no words are used for 5-10 minutes. In a quick way, you get familiar with the story and the characters. I would love to do that to help users understand that adilas has grown up from a baby to an adult and is still growing. If they, the users or investors, understand the history, it will help them see the vision and potential of the future. We could use this to help sell or pitch ideas, recruit help, raise awareness, and even solicit funds to help fund projects. I love the concept of using history and cause and effects to tell an unfolding story.

-As a side note, my brother did a historical recap of Bible stories and events and brought them forward into current events. He did this as a number of us were sitting around a picnic table during a family BBQ. I was totally captivated by the story and seeing how one thing created the next and the next and the next. The deeper you get, the more you could see how the cause and effect consequences both made the story and even helped feed the next steps. Very interesting. This brother is a master story teller and loves mixing history with current events. Great skill to have!
-Tools are created by people to help them do a job. Some tools are designed for both good and bad. Some tools are very generic and may be used for both good and/or bad. Imagine a hammer, a saw, and a drill. These same generic tools could build a church, a school, a house, or something for business. These same tools that build for good, are also used for destruction, war, weapons, and vice/sin. These tools aren’t bad… It comes back to the agency of the person that uses the tool and what they intend… Adilas is a generic tool. I hate to say this, but it may end up being used for various different outcomes. The tool is generic. The usage depends on the users.
 
Click to view time photos.
AU 2016 Daily Tasks 2/14/2014   • Up early to work on the API validation function. An intern helped me put it together. Spent all morning checking verbage, spacing, and logic. Trying to make things consistent.
 
No po photos available. Click to view time details.
Adi 836 Promised Custom Code for Kindman 2/15/2014   Promised to work on a percentage discount button for Ryan at Kindman. This will be a my cart favorite button that will allow for discounts to be applied as a percentage. This will require a look-up to see what is already in the cart and how to proceed. This may take some work. They would also like options for doing discounts on the cart as a whole.

As a note, the cart as a whole could also be a little bit tricky. We may want to look at a variable that gets set inside the cart if apply a discount on the cart as a whole is selected. That way it could keep the discount rolling forward as an automatic process vs. a manual process.

The other note about this tweak is that if we are in playing with my cart favorites, it would be really cool if we could open up options for putting these buttons into frames. This would allow for split cart options.
 
Click to view time photos.
AU 2017 Daily Tasks 2/15/2014   • Recording notes in my notebook.
• On the phone with Steve. We had a great three hour session. We covered tons of different subjects. I’ll record some other notes later on but these were the general subjects: new business, current needs, new developments, funding, options for generating additional capital, packages & packaging, round two for elements of time, dynamic settings, and code stuff. Great session.

• Recording notes from loose pages into my notebook. Lots of brainstorming and seeing how “systems” (bringing things together) is a huge key. Lots of fun ideas.
• Recording notes, brainstorming, and emailing Steve with an idea to help raise some funds. It started with our 3 hour conversation this morning and then grew. Maybe offer some discounts for existing clients if they are willing to pre-pay.
• Testing the API validation method and function.
• Also did a couple of logos. Updated the news and updates page with upcoming weekly classes.
 
Click to view time photos.
AU 2034 Daily Ideas 2/15/2014   Notes from a phone call with Steve on 2/15/14:

- On funding, we are looking for a loan. We are trying to steer away from investors and looking for a possible loan. Maybe offer 10% to 12% on interest.
- We could also allow our clients (top paying or longest clients) to pre-pay with a discount applied. We may want to limit this to clients that have a year or more time with adilas. Maybe 10% for 6 months pre-payment. 20% for 1 year pre-payment. 25% for 2 years. 30% for 3 or more years. Kind of like a season pass for a ski resort. They (the ski resort) get more capital up front and the lifts (servers) are going to be running anyway.

Notes on packaging or packages (sub of the parts section).

- Maybe add a 3rd item type. Other two are serialized items (stock/units) and general items (parts). The 3rd item type might be a sub or baby of a momma (either stock/units or general items).
- Keep the naming conventions as dynamic as possible.
- Maybe change “parts” to “items” at the top most level. This is clear up at the top level or 12 main system player groups.
- What if this 3rd item type was able to handle outside services, job costing, packages, subs of the main, etc.? That would be super cool.
- Conversions could be part of this sub or 3rd item type.
- There may already exist some ideas and notes on “mini units”. This is an older idea but may have some ideas for what we are trying to do. Mix between stock/units and parts.

- Package control – helping, watching, and monitoring.
- Stock/units mixing with packages or element of time to get RFID tag tracking, job costing, and subs of subs.
- Lots of new 1-many relationships.
- Round two of elements of time deals with payroll options, rentals, reservations, job costing, clear to the any person, place, or thing level. This could be to a dispatching level on elements of time. As a note, there are tons of notes on what we wanted for round two of elements of time – check out old notebooks and brainstorming pages. Look in early 2011 for details.
- Track the “time” related to packaging.

- The 3rd item type may be done by taking an existing item and creating a one-to-many relationship from it to a new group or package.
-We are heading toward generic corp-wide settings. We could then bulk change these settings based on different industries. What is your industry? Can we help you setup some common features, settings, and interface options that are used by people in your industry? Help our users get the most out of the system by using settings and permissions.
-Steve and I were working on building some new corp-wide settings… As we went through the process, we came up with a few key points to help us get started. They are: start with ideas and needs. Then do some planning. Then make new database changes. Go to the source of where things start. Build the settings, then actions and updates, and then cascade the new settings as needed. Finish up with sign-off and deployment of new features.
 
Click to view time photos.
AU 2018 Daily Tasks 2/17/2014   • Working on validation and output for the adilas API.
• Prepping some graphics for my brother. I have close to 10 logos that need to be uploaded in my email inbox. Going through them to see how easy each logo will be.
• Working on validation of the adilas API.
• Doing a customer upload with an intern. He prepped the files and now he is watching the whole process of the actual upload. Added a new logo for the company. Invoiced customer, added new logo and color, and logged information in the system. We also talked about other projects in the wings.
• Prepping customer uploads for the intern. Checking on vendor uploads for a consultant. Light email clean-up.
• Working on the adilas API backend application.
• Getting close on the first real data pass for the API backend application.
 
Click to view time photos.
AU 2019 Daily Tasks 2/18/2014   • On the phone with some clients talking about some new eCommerce settings for customer logs and flex grid tie-ins. They use the CRM (customer relationship management) part of adilas tons and tons. They want their dealers to be able to login and see the status of their apps. I did a small demo of the existing eCommerce backend and showed them how we could tweak things out a bit. They would like a quote on the new functionality.
• Phone and tech support and recording notes.
• More phone tech support for a company.
• New logo and colors for a gun play site.

• Emails and phone calls.
• Finished up the first round of the adilas API for adding and editing master corporation lists. There is still a long way to go, but this was part of a home-grown mini API that uses JSON (java script object notation) objects as part of the passing of data back and forth. We have a number of future projects that will be using an API (application programming interface) backend engine. This is exciting! Launched new code. Two out of the three servers worked great. Had some issues with the third box. Did some research online.
• On the phone with tech support going over server configuration settings. With their help, we got the adilas API working on the other server. We also went over some other server setup items. I’m very grateful for people who know more than I do. We all have our place.
• Updated server settings on all servers. Recorded some notes on server settings and tested the first little instance of the adilas API by using it. Yea!
 
Click to view time photos.
AU 2035 Daily Ideas 2/18/2014   -eCommerce ready point of sale system.
-We are really good at creating and using dynamic engines. For example: The BATC Interactive Project, Learn to Freeride (LTF), and adilas. All of these are mini dynamic engines of sorts.
-On the API (application programming interface) calls… Let’s allow all of the values to be passed in as a single object. Originally I was headed towards a number of FORM params and an object (JSON or WDDX) as the method call data. Maybe put it all together into one bigger object that will be passed as a single item. Data in will be an object, data out will be an object. Stuff will happen in between.
 
Click to view time photos.
AU 3670 Notes: Custom Project/Quote 2/18/2014   Notes for a Custom project/quote
- Reverse look-up on customer logs
- Customer logs – their own
- Check to see if they are connected to sub customers
- eCommerce backend
- Dealers & customers
- Hide/show on the web
o default to hide
- Timeline mid-March
- Need quote $400-500
- A number of new settings
- Reverse look-up might be fun to help with the reflexive side of the flex grid
- $400 for customer logs
- Additional for reverse look-up on flex grid. This gets into a security issue and which subs to show. $1,000
 
Click to view time photos.
AU 2020 Daily Tasks 2/19/2014   • Reviewing notes in my notebook.
• Working with an intern on some of the adilas API pieces. We went through our first round of code, new changes, and even did a full hour or so on where we want things to head. Good API brainstorming session. More notes will be recorded later. I need to transfer them from loose pages to my notebook.
• Phone calls and tech support. Building a custom page for a client to check tax categories for their parts.
• Custom report for a client and tech support stuff.
• Getting back into new tax settings for part categories.
• On the phone with Steve. We talked about new and upcoming projects. We also spent some time going over code and working with dynamic corp-wide settings.
• Back on tax category stuff for parts. Added part category list builders and started working on validation.
 
Click to view time photos.
AU 2036 Daily Ideas 2/19/2014   Brainstorming notes between Brandon and an intern dealing with the adilas API:

Notes from a brainstorming session on the adilas API (application programming interface). Brandon and an intern went through the code on the first round and then had a discussion about ways to improve things and help to standardize processes.

- We would like to offer 3 data exchange formats. They would be JSON (java script object notation), WDDX (web distributed data exchange) and eventually standard XML (extensible mark-up language).
- All API calls will be funneled through a single page called adilas_api_calls.cfm.
- Currently we have both FORM fields and objects that get passed in. Our plan is to move towards objects.
- As we transition from basic FORM field submission, we will need to alter the flow and order of things.

- Eventually we would love for the process to be mostly database driven vs. customer code or special include files… Ideally we might need a mix. We could use the database for standard operations and then use the database plus custom includes for any custom work. Think about a fully automated way of getting a mix of both worlds.
- We need to build out the documentation and the database for the API. Help people!
- Setup a searchable sub section of the API. It would also be cool if we could categorize and even visually display API functions and methods. Use the adilas interactive map of the GPS (global positioning system) core interface to help organize and display options.

- As part of the API, we would like to setup a 3 step testing environment to help with testing. Think of a virtual playground of sorts. The 3 steps would be:
o Prep it – a form that allows preset options and input.
o Convert it – this would format the data and show what the request would look like. And the…
o Run it – show the results and what that would look like.

- As a side note, it could be fun to allow both test and live data to be submitted. It might be cool if the developers could really see things in action and then mimic those actions in their own projects.
- On a permissions and settings level, we want to help our users, clients, customer, and outside developers. Basically, the system will have to have a number of options to help it be dynamic and flexible.

- To list a few of the options, we talked about: users, corporation (worlds), windows and doors (access), usage, limits, passwords, and security issues. We even talked about certain things that would not be allowed – rules of the game.
- We determined that we need controls on the universe level, the world level (corporations), and on the who (users), what (permission and methods), when (optional times and dates), and where (IP addresses and domains) levels.

- While talking about security, the intern mentioned about checking the existing list of black listed IP addresses and deny access to those without even checking the data.
- Every method or API call would need a password.
- We want to be able to track usage and history of who, what, when, where these API calls are used. As a note, the history may need to be added somewhere towards the top of a call or just before it gets returned.
- Make sure and run the API over full SSL (secure socket layer).
 
Click to view time photos.
AU 3671 Tech - Adilas API 2/19/2014   Adilas API
- JSON & WDDX & (XML – later on)
- Adilas api calls – cfm
- Currently we have both FORM & objects (required change)
- Change the order of things
- Love it be database driven (later on) vs. custom code or includes…
o We might need a mix. Db for standard operations and db plus custom includes for custom work
- Doc & DB – built up and detailed out
- Setup a searchable sub section of the API
- Categorize the documents and pages and methods
- Testing or playground environment
- 3 step environment:
o Prep it
o Crunch it (request would look like)
o Results (response would look like)
- Users, corps, windows, doors, usage, limits, passwords, access, and security issues – not accessible (special) to outside users
o Universe level
o World level
o Who - users, what – permissions & methods, when – ?, where – ip addresses, domains, etc.
- Check existing black listed IP addresses
- Method password for every call
- Who accesses these API calls – history towards the top checks
- Run over SSL

Brandon & an intern working on the adilas API:
- 100+ permissions
- $500-1,000 methods
- Linker – users; Linker – methods

1. Prep it! – just from fields
2. Convert it! – show it form & cfdump (Full Circle)
3. Run it! – form & cfdump; ½ FORM, ½ objects
 
Click to view time photos.
AU 2021 Daily Tasks 2/20/2014   • Recording brainstorming notes from a session yesterday on the adilas API and what direction we are headed in. Good stuff!
• Working on a customer upload for a company.
• Did customer uploads for other clients as well.
• Invoicing clients and emails.
• Went in to Bridgerland to work with an intern on the PayPal and First Data payment gateways. We did some checks on authorize.net and lots of work on the PayPal gateway. We are getting close to fully signing off on the code for PayPal. 30 miles.
• Coming up: some customer mapping for labels. This will use the custom document section and then use replace functions to trade real values where specific placeholders are used. The goal is to use the built-in adilas barcode generator label maker in a dynamic way. Anyway, that is the thought.
 
Click to view time photos.
AU 3672 Tech - Custom Labels, Notes, & Merchant Gateways 2/20/2014   Custom Labels:
- Show label on page: view cart or invoice line items
- Top Line Mapping:
- Bottom Left Mapping:
- Bottom Right Mapping:
- Description Mapping:
$____$
- Corp name
- Corp Id
- Corp Initials
- Loc Name
- Loc License
- Customer Name
- Customer Tax Id
- Customer Type
- Invoice Date
- Part Id
- Part Number
- Part Desc
- Qty
- Unit cfm
- RFID
- Price
Side Notes:
- Add name
- Add custom doc of label template
- When searching, documents & assignments, check destination & sub destinations
- For example: barcode generator & view cart
- Different fields
- Maybe also allow for exact or like or not… dynamic where clauses
- What about an internal label and a custom “PDF label”, “qty label”
- If anything is left blank, default it to the existing piece

Cloud Software Demo – Challenging & Breaking Tradition


To do list for PayPal & First Data gateways:
1. On the add edit merchant accounts page, we need to put the
a. Source Key = client Id
b. Pin value = secret Id
2. On the database: Take off the sandbox and testing vars in the merchant types table.
 
Click to view time photos.
AU 2022 Daily Tasks 2/21/2014   • Working on different logos for clients. Added new logos for multiple clients. Posted all new logos and colors up and online.
• Emails, tech support, recording bills, etc.
 
Click to view time photos.
AU 2023 Daily Tasks 2/22/2014   • Emails and looking through code changes made by Steve on the dynamic corp-wide settings for stock/units. Started to order a new SSL for the main adilas.biz site.
• On the phone with Steve going over code changes. We also spent some time and talked about mappings to custom labels. I showed Steve some of my ideas on doing the mappings. We also talked about new clients and projects and the “just in time” nature of what we are doing. It is so dynamic that just in time is almost the only way to do it. Pretty crazy.

• Messing around with renewing an SSL certificate for the main adilas.biz site.
• Working on adding and updating item/part categories for location tax settings.
• Working on actual tax calculations with new item/part categories in place. Pushing new code through the system. Lots of testing of the different pages.
• Finished up the new code for tax settings per part category. Ran the update code to add the new database columns and launched the new code. Pushed files and updates to all servers and did some light testing.
 
Click to view time photos.
AU 2037 Daily Ideas 2/22/2014   -Just in time code, just in time funding, just in time access, just in time functions, just in time everything.
-Built on an adilas data engine!
 
Click to view time photos.
AU 2024 Daily Tasks 2/24/2014   • Brainstorming on using internal JSON (java script object notations) objects to store custom page settings and report filters and criteria. See note on next couple of pages. (Below)
• Started working on the custom labels and mapping sections for internal custom mapping to the barcode generator or label maker.
• Emails, tech support, and working on the new SSL for the main www.adilas.biz server. Also spent some time talking with an intern about objects and using them inside of adilas. We also talked about ways that we have to grow thicker skin like a rhinoceros. Lots of talk about different ways of growing or growth that happens.
• Emails and phone calls.

• Working on custom code to help with barcode and label maker mappings.
• More work on the custom code for the label mapping.
• Emails and tech support.
• On the phone with Steve going over funding and new projects. He had some questions about the new corp-wide settings for stock/units.
• Fixing a small error on the standalone customer log search form. Writing an email about the customer log section.
• Working on custom label mapping for shopping car line items. Formatted the new labels and did some placeholder replacements with real values. Light testing.
 
Click to view time photos.
AU 2038 Daily Ideas 2/24/2014   -What if we used JSON objects inside of adilas to store custom settings for different pages. This could be report assignments, report settings, dynamic filters, etc. Think of the old “Mend & Repair” section but use objects to store data and criteria vs. 100’s of different form fields. Let the JSON (java script object notation) object flex up and down as needed. This could allow one single table to hold data for all possible custom settings and custom reports. That could be super powerful!
-Along with custom settings, we could even scope or do some internal mapping to FORM’s, URL’s, and variables scopes. Maybe even session and application scopes if needed.
-If we used internal objects, we could use a simple table that was tied to specific pages, one or more users, etc. Think user specific reports, corp specific reports, etc.

-If a specific report setting was passed into a page, we could go directly to that page, its object (search and filter criteria), and display the results accordingly. That would awesome! We could use this small pass through to allow users to set up their own buttons, links, and drill-down options. Mix custom code and in-line settings to get a super user-specific interface. This could end up being the “my favorites” section of the application.
-If you used objects to store settings, you could store as much or as little data as needed. The object would flex up or down as needed. This could even be which fields to show, what order to put them in, and which criteria of filters to use.

-We could establish dynamics for dates as well. This would allow for hardcoded dates or mobile and flexible dates or date ranges such as: current date, current week, last week, next week, tomorrow, yesterday, this month, last month, next month, etc. If a flexible date was used or stored, the system could figure out those settings on the fly. That would allow reports to roll or move forward or backwards as needed. Basically, time keeps moving, by allowing the dates to move, the reports are able to keep up without changing the dates all of the time. Think dynamic!

-If you use objects to store data… you could potentially use a general database to store the objects and yet get tons done without having a specific field for every little setting. Let the objects carry and hold their own baggage. This is very flexible for unknown or changing pieces however may not be ideal for standard one-to-many relationships. Basically, I’m trying to say, yes, this does exist and is very powerful but may not be the best option for every scenario. Mix and match as needed! That is the key!
-I could see objects being used where criteria, mappings, and flexible options are needed. Where things are known or standard, I could see using traditional relationship models being used.
-As a note, the application flex grid (business to business flex grid tie-ins) may need mappings and settings stored at an object level. There may be some unknowns or super complicated pieces that could be tied together with objects vs. traditional fields and columns in a database.

-If all data is live and searchable, I do see a smaller problem searching objects vs. searching pre-filtered database rows and columns. To the user, they just want to search their data. To the backend developers, that means knowing where things are at and how to get to them. Things will be buried deeper in code vs. on the surface level.
-There are some modern terms that we might want to check out. They deal with objects and such. They are: NoSQL, NoJS, JQuery, Ajax, etc.
-While on a walk with my dad this morning, we were talking about objects and options. I had the idea and thought that objects may be a way to store in-line custom code and settings. We could provide a front-end interface with options and point and click form controls. We would then roll all of that data up together and store it in a general object. Basically, instead of having a field and table for every option, we could code the options into the object. The database would then be the storage engine and then code could be stored in a generic container. Anyway, I think it could simplify storage needs and account for future growth and options.

-Another thought along those lines are dealing with elements of time and holding and storing custom JSON objects as a sub of time. This could be in the sub comments (already able to store HTML and large amounts of text) section if needed.
-Another thought was to create objects and send them back and forth to represent physical one-to-many objects inside of adilas. For example: If someone passes in the invoice number of 500, we could put all of the invoice pieces into one return object and then pass that whole object back to the user. We could pass like data, relationships, subs, and even other pieces in a virtual one-to-many relationship or object. Help make the pieces be mobile and consumable.

-As an option for group players and custom code options… what if we treated each section similar to elements of time and master time templates. We could figure out the options, settings, and built-on functions for each main player group. We could then save those options as an object. If someone wanted to tweak out the options, they could pull up the main group player options, change what was needed, and then reset or submit the object to be held in the database.
-Using objects could even expand the flex grid and add one-to-one or in-line code options right to the main object or player groups. Say you wanted a new field to be stored per invoice. Instead of using the existing flex grid tie-ins to create the new field, what if you went to the main object itself and added a bolt-on piece right to the main object. The upper main object level could then control the sub items and the data storage level. Basically, define the additional field and store them in an object at the root level. Then store the extra data at the individual or data level. Both the group definitions and the individual object pieces would be stored as JSON objects. The system could then interpret the results.

-If we got into storing pieces of code and settings as objects, one of the tricky pieces would be showing, placing (location), and formatting the output. Another tricky piece would be validation, search ability, and defaults. Anyway, it does get kind of deep fairly quickly. However, if dynamics are needed, this may be a great option and/or tool.
 
Click to view time photos.
AU 2025 Daily Tasks 2/25/2014   • Finished up the first round of code for the custom labels. Posted files online and added the first live custom mapping for a client out of Denver. Sent out a few emails to let people know about the new changes.
• Went in to Bridgerland for day one of the February adilas training course. As a note, this even marks the one year mark for holding a three day training course. Kind of fun. Our very first three-day course was back in 2013. In the class, we did an intro into the adilas formula flyer: Results = Mix (Functions, Players, & Concepts). We covered the 12 system players and then talked permissions and settings. We also did a fun “what’s new” section and showed a few of the upcoming pieces and projects. We had both the interns take a couple of minutes and demo some of the new tools and features. We ended the day going over CRM or Customer Relationship Management stuff. Great session and we all had a good time. My brother was able to be to all three days of class. It was fun to have him there in the live class. Normally, he just does the video stuff after the fact. 30 miles.
 
Click to view time photos.
AU 2039 Daily Ideas 2/25/2014   -We need a link from the apply payment action page to the customer log.
-We need a statement link from the view invoice amount owed page.
-On the statements page (creating a new statement), show the outstanding date range.
-On statements, hold the values in memory in case multiple statements are made for the same date range.
-On the actual statement, provide a log link back to the customer log.
 
Click to view time photos.
AU 2026 Daily Tasks 2/26/2014   • Emails to a client about checkout options and possible new settings for checkout procedures. He wants it super speedy but super locked down at the same time.
• Working on cascading stock/units corp-wide settings throughout the site for Steve and some of his projects.
• Emails to Steve about stock/unit settings and the size of the project, or undertaking, for dynamic stock/unit names.

• Went in to Bridgerland for day two of the adilas training course. We spent the entire day working on inventory and sales functions. We played with stock/units, PO’s, parts, items, services, etc. We sold things out using basic searches, advanced add to cart, buttons, and even recipes. As part of the class, we did two different brainstorming sections on stock/units and general inventory items (parts). Great session. 30 miles.
• Changed out the logo for a company.
• Working with the 1099 data overlay that an intern was working on.
 
Click to view time photos.
AU 2040 Daily Ideas 2/26/2014   -Steve would like us to change some of the corp-wide settings and default values. Some of these changes need to be cascaded throughout the system and into the different help files. See his cfc/maintenance.cfc file for details and notes. Some of the settings are: item and part number changes, show/hide options for line numbers, and others.
 
Click to view time photos.
AU 3673 Brainstorming - Parts & General Inventory 2/26/2014   Brainstorming on parts, items, and general inventory items. Done on day 2 of the February 2014 adilas training session. 2/26/14
Inventory:
Goals, Features, Advantages, Benefits, Pros/Cons, Known/Unknown, Shortcomings

What do we know?
- PO’s – inventory comes in on PO’s
- Vendor specific inventory – perfectly tied to that vendor, its own special…
- ***Generic inventory*** - purchasing product from multiple vendors but selling it out as the same product or at one price, (if it’s going in a bin, same shelf, mixing, etc., run it as generic)
- Different types of PO’s – 6
- In inventory, on order
- Unit of Measurements – lowest common denominator – what are you selling it out at
- Include/Do not include shipping in COGS
- 5 decimal levels of accuracy – not required, but available
- Cause & effects – payables, affecting inventories
- Get it in – PO/inventory side – then we will pick it up on the Payables side – who do we owe?
- Barcoding
- RFID tags – Radio Frequency Identifier (higher cost)
- Packaging
- Potential backorders
- Pre-ordering
- Pay before receiving product
- Shipping
- Freight – different on financials than inventory pieces
- Mini-manufacturing – making new products, buying in bulk – selling in singles
- How am I selling my products out?
- eCommerce
- Open up brand new markets
- Allow online bill paying
- Recipes – bulk, group, kit, pre-set, flex…
- Multiple pricing structures – tiered pricing structure (i.e. same item w/different pricing)
- Interface for selling advanced add to cart, buttons, ???
- Services
- Unlimited items
- Migrating – find & replace, combining items
- Data imports
- Global mark-ups
- Sales
- Discounts
- Promotions
- Customer loyalty
- Merchant processing
- Gift cards
- Planning – faster, consistency

Shortcomings/Pains:
- When to order?
- Loss/shrinkages/damages/returns
- Potential volume of inventory – can be really challenging to manage
- Tradition, legacy, how it has been done
- How will I enter everything into the system?
- Lots of work getting inventory in…
- Pro/con: Taxes
- Education/training
- Pro/con: Planning
- Expiration dates

Brainstorming on stock/units: Flavor of stock/units

What do we know?
- Serialized
- Big ticket items
- Individual Needs/Level – needs some love – what happens to THIS item
- One by one
- Vehicles
- Trailers
- RV’s
- Campers
- Planes
- Boats
- Buildings
- Hotel/Rentals/etc.
- Homes
- Motor sports – motorcycles, sleds, rhinos, 4-wheelers, etc.
- Firearms
- Jewelry
- ***Jobs*** - Job costing
- Can contain subs
- Can be sold
- Sub buckets
- Job histories
- Can be tied to locations – tracked to different locations – mobility
- 5 deep level categorizations:
o Inventory type
o Sub inventory type
o Make
o Model
o Physical unit (with additional subs)
- Sales tool – with some “haggle” ability built in – cost variables
- 100 photos per stock unit
- Manager’s checkbook – slush fund
- Fictitious costing
- Somewhat fixed items
- Mixed items: almost between serialized & non-serialized items
- Not a standalone item on invoices
- Wholesale & manufacturing of stock/units
- Stock units that product other stock/units – (manufacturing, harvesting)
- Very powerful, very diverse, very functional
- Documentation – media content, unlimited documentation, not just photos – add the design specs, the paperwork, contracts, etc.
- Rentals – (stock/units to elements of time)
- Reservations
- Needing to attribute subs to individual pieces
- Details – main
What is possible?
Features:
Advantages:
Benefits:
Shortcomings:
- They are big
- Require a lot of data if you really want to play the game
- Time intensive to sell – paperwork, financing, trade-ins, contracts,
- Human error – to help with this, making things editable & tracking histories
- Search multiple buckets – to get your data back out (pro/con)
- Economic downturns – big ticket inventory can become very difficult
- Education/training to be able to work with complicated/detailed items – associated permissions
- High entry cost to serialized units
- With more stock/units – potentially requires more people/space – money, employees, security
- Taxes and random settings
- Paperwork
 
Click to view time photos.
AU 3674 Tech - Stock Permissions 2/26/2014   Tech – Stock Permissions
- “Unit”
- Corp stock name full – “stock/unit”
- Corp stock name – “stock”
- Corp make name – “make”
- Corp model name – “model”
- Corp inventory type name – “inventory type”
- Corp sub inventory type name – “sub inventory type”
- Corp vin name – VIN serial number

Stock Permissions:
Quick Searches:
- 4 = stock/unit full
- 34 = stock/unit limited
- 83 = VIN/serial number
- 43 = stock/units in inventory
- 44 = sold stock/units
- 20 = add stock/unit to inventory
- 35 = add old stock/unit
- 36 = repairs to stock
- 37 = parts to stock
- 38 = misc. to stock
- 39 = inv. adjustments to stock
- 73 = global stock/unit mark-up
- 32 = stock lockdown & sold info
- 67 = admin checkbook – stock/units
- 30 = add/edit make
- 31 = add/edit model
 
Click to view time photos.
AU 2027 Daily Tasks 2/27/2014   • Checking code on the duplicate PO section.
• Went in to Bridgerland for day three of the February training session. We had a great session and the class really helped to steer where we went and what we covered. We talked about cause and effects, mixing, balance sheet, P&L (profit & loss), deposits, expenses, time, flex grid tie-ins, etc. We covered time cards, light payroll, and different uses for different tools. The last half of the day was mostly fielding great questions posed by the users. 30 miles.
• An intern came by Bridgerland and we met for an hour. We talked progress, new projects, etc. We also talked about work schedules and expectations.
• On the phone with Steve touching base and checking up on meetings, functions, and such.
 
Click to view time photos.
AU 2041 Daily Ideas 2/27/2014   -The star student for the February 2014 adilas training session was a guy from here in Cache Valley. He did a great job, had tons of questions, and really shined. Great interactions.
 
Click to view time photos.
AU 2028 Daily Tasks 2/28/2014   • Got some new files from an intern for 1099’s and a new form called form 1096. It is a summary report for the 1099’s. I spent all morning checking off and signing off on code. I posted files and printed out a number of 1099’s with a data overlay for copy A (the red part) of the 1099’s. He did a great job.