Recording notes from 2/17/25 to 2/21/25.

Finishing up the new Texas 130U form for title and registration filing. Cascading help files and changing some verbiage for the forms (document management stuff). Made sure that every server was updated.

Meeting with Hamid. We went over some AI stuff. Talked about the future and where things are going. We then went over plans for the presentation gallery. After that, I showed him the Knox report and how that is looking. We then finished up looking at adilas and document management, PDF forms, and how to overlay data and populate PDF forms on the fly. Mostly a show and tell and light play session with code and PDF's. Hamid is interested in learning how to populate PDF's. He is going to prep a PDF for next time and we are going to work on it.

working on the new Texas 130-U form for trailers, titles, and registration paperwork for the state of Texas. Getting the new form ready. Copying the older fields from a pervious version. Looking over the new form and making adjustments.

Emails and internal tech support with Sean and some customer upload questions.

Notes from Bryan: Turnkey Adilas setup for HostHuski

My notes: Working with Bryan. Talking about AI and SaaS (software as a service). Going over the Knox report and playing with it. There are a lot of things happening, all around us. Bryan showed me some of his work on the quote and invoice flex attributes and how they flow through the shopping cart. Talking about how to bulk create sites inside of adilas. Talking about automating the corp setup, corp-wide settings and defaults, templates, and other quick corp creation process options.

Working with Shannon on some planning. I made a document last night and used some AI to help me organize it. We then took some of Shannon's notes and ran them through AI. We filtered it down and then did some more brainstorming. At the end, we ran that through AI as well. See attached for our results. Our plan for next week is to go over the results and boil things down again and again. We are making progress. Kinda fun to use AI stuff as well.

Back working on the custom sales breakdown report. Working on output and light math. Finished up the first round. Still need to do some testing but it is at least presentable. Merged in my branch with the master code branch. I will make some more modifications but at least you can see it on the master branch, and it will be live on all servers tomorrow.

Working with Russell on the Yogen Fruz sales breakdown report. We worked on some JavaScript, CSS, and report formatting. Good little work session. It is helpful to get a second pair of eyes on the same code and same page. It helps to refine the experience, both coding it and for the end user.

Working with Cody on mapping out the database for his UML diagrams. Somewhat of a small work session. He would ask about certain fields and I would tell him what they did and how they were used and/or related. We would then move on to the next piece. If he didn't need me, I was working on my own stuff.

Working on the sales breakdown and comparison report for Phillip and Yogen Fruz. Going over math and differences and difference percentages. We have to start with the initial value as the base of a 100%, then do the compare (division and such) from there. Fixed the diff function and started to work more on output.

Emails. Back on the CSV upload with mapping options for parts and items. Added the upload code and did some light testing. Pushed file up to all servers. Sent out an email to Sean and Cory to let them know how to use it. After that, I paid a few bills and cut a couple of checks for Cody and me from inside of adilas. Quick phone call with Sean to go over the new tool.

Meeting with Cory and going over her short list of to do list items. We went over a small quote and touched base on all of the other projects that are needed right now (once again, just the short list).

Quick chat with Wayne about queueing up server-side processing. Talking about a quick need for simple ecommerce. This (simple ecommerce) seems to be a reoccurring theme.

Switched over to working with Shannon. Working on the formatting of presentation gallery. We spent some time talking about the attributes and results - showing some of the cool things that people are doing with adilas. Marketing, showcasing, samples, & mixing different kinds of results. We really want to cover the who, what, when, where, why, how, how many, etc. - all in the presentation gallery.

Back to an original thought, about mixing business functions, application players, and core concepts to get some cool results or desired outcomes (leaning this way - changing the attributes section to be called desired outcomes). Design your own systems. Help people... that's what we do. We have a ton to offer, and we keep building and refining it every day. This change, from attributes to desired outcomes, may be a little gift (comment from Shannon).

Helping Sean with a new item upload page. Did some planning, then started to build out the page. Multiple steps. Set the corp key, choose some defaults, do the mapping, and then process the uploads based on the mappings and settings. This should help us out in the future.

Phone call with Steve about a huge data dump for a client. 30-45 systems (corporations), 5-10 year's worth of data, with tons of reports and exports. Thinking about 3 options - 1. Kelly doing it all (consulting fees). 2. Reduced storage options. 3. New reports or bulk export tools (csv or excel format). Talking about automation options from Wayne and how he would possibly do it. He would be doing things on the server level. Talking about possible automation ways that we could go with and what that might look like.

Meeting with Cody. Going over UML diagrams that he is working on. Talking about efficiency, reuse, pros and cons of copy and paste, pros and cons of duplicating data, and math on the fly or precalculated math. Lots of good topics. Here are some of my notes:

- The importance of refactoring. Keep refining and paring things down. Make it smoother as we go.

- Talking about mini conversions and other options. Mini conversions is a sub of sub inventory (parent/child inventory). For example: Say you have something that gets sold by the case, by the bottle, and by the fluid ounce. You have to be able to go up and down the conversions to show what is really there. True inventory tracking.

- Talking about lots of suggestions and what makes sense to change out and/or leave.

- On the mini conversions, we might be able to hold the conversion id's and the math all on the same table. Help the users setup the conversion charts and/or relationships. Especially if we don't know the conversion factors or ratios (custom conversions or custom units of measure).

- We have had a lot of wild west style development (anything goes). There is a need for specific roles and company structure (adilas jelly fish model - future plans for where we are heading as a company).

- We mix so many different business verticals. That has been a huge blessing but also a small curse (so diverse).

- Cody was pitching that we need a primary role of a database admin type person (specialists per role). Creating the chain of command, down the different roles. Basically, turning the wild west into a more modern city (modern development environment).

- Talking about someone who knows how to work really hard and how to help them to work smarter and use technology.

- Cody wants us looking into growth, in the long run. Talking about a master plan and then breaking things down into more digestible pieces.

- Talking about internal education and structure. We need our team to know what to do and how it (all of the pieces) fits with the bigger picture or the whole.

- Figuring out what we have, suggestions for what to change, and future plans.

- We then got into time sub inventory and parent/child relationships. It gets deep, pretty quickly.

- Growth is hard to manage sometimes.

- Talking about independent developers, light guidance, and working on our own. Reasons for building out the UML diagram. Not just for Cody but for all other developers who will be working on this project.

- Building out the dream. Getting organized (not really official, but pretending that it was official). It will all help in the long run. Risk vs rewards - push/pull in the organization. Unofficially organize ourselves (at least on the development side).

- Link to the interactive map - small visual for how things are organized.