10/7: 33.63

John is helping with this:

Shawn and Brandon are payroll guys. Shawn has upped the number of states. 10-12 states currently. 

Year end forms

Currently one at a time for payroll. Can pull multiple time cards per department.

New sites for:

• Chris Scholle
• Chris Johnnse 
• Dave Forbis "Foretech Services"
• Wayne Moore

Concept based sign-off procedure-we need to build it.

Reread the project management document.

• Budgets
• Plans
• Sign-offs
• Code review
• Timelines
• Client involement
• Communications
• Deployment
• Wrap-up

-Inventory thresholds per location reorders

-Chris Johnnie idea

-Add an item photo as we add the physical item.

Cleaning up small to list tasks. Emails, tech support, and paying bills. On the phone with Shannon going over ideas for mining information and getting her help with user guides, help videos, news and updates, etc. She is going to be having a baby and will be letting others take over some of the tech support stuff. She still wants to be involved, just at a different level.

I also talked on the phone with Calvin for bit. He reported on his demo with client for his hybrid desktop/web API app and what he is trying to get done. All is well there. We did talk briefly about using tablet and smaller mobile computers. We also talked about the possible limits of using tablets and trying to pair them with hardware, printers, and scanners. Mobile is nice, but sometimes you sacrifice options and features for size.

At 2:30 to 3:15 I had a meeting with Jason and John from Baker. They are building their own frontend application to do online ordering for a mutual client. They still need some help with fully connecting to the adilas API sockets and being able to interact with sub inventory. We talked and I showed them around. I told them that I would make sure and expose some of the sub inventory methods to the outside API.

On a Zoom session with Calvin debugging a remote login API socket call. It came down to URL encoding the values that we were passing. Some of the usernames and passwords had special characters and it was causing the server to send back random errors. We finally got it figure out.

Tech support and helping out Chris Johnnie with some new merchant account settings for some of his stores.

On the morning meeting with Steve and Russell. They were talking about how Bridgerland could help with outside development and doing smaller projects. Part of the puzzle is how we empower our users. It is so important to empower our users at the level that they need (go to the source). That is a huge core concept.

Taking the email options out to the bulk level and also allowing users to make the email come from their own servers.

As the guys were talking, I was doing some research on the old adilas website. Lots of good PDF files, help files, graphics, and flyers. Here is the old website link: https://data0.adilas.biz/old_index.cfm

Eric wants to talk about coupons and loyalty points. We talked about a guy named Chris Johnnie and some prior planning that may have been done by Russell and Chris. We are trying to pull things together and make everything happen.

From Eric - It is so expensive to keep stopping and starting - we lose tons in the transitions. We need to focus and stay on track.

Eric was expressing some concerns about sub inventory on the production side of things. Steve chimed in and was talking about how some people don't even know what else is possible and already built. The trail is faint and many people have been gone in different directions. We need to define the best path and then help educate others to play the game.

Manufacturing is a whole new level - You have raw goods being made into finished goods. Lots of internal flipping and tweaking. You need bill of materials, sub assemblies, recipes, other tracking needs, etc. We talked briefly about parent inventory and sub or child inventory. Some of the big needs come when they have sub assemblies and use semi raw goods and then push it into another finished good or product. You have to be at the sub level in order to really track that information. It gets into sub locations and sub phases and all kinds of other subs. In the background, we are seeing the _Z coordinate (depth and stacking) coming more in to play.

We are having a number of clients that are fighting against change. Some of the subjects are the way the one-to-many relationships are setup and what the individual people think should be the best option. Some of the questions are things like - one PO with multiple line items or one PO per one line item. Which one holds the location and how do you move things around. They want to group things but also be able to move things independently. They need both... basically, I'm part of this group but I also play over here and here. Very interesting.

This is a side note, but we end up spending so much time managing our customers because they all want to chime in and say what they feel is the best. Custom is awesome but it can also get us in trouble. Custom is really easy on existing and established pieces. One of the main problems is when we get into uncharted territory, people have all kinds of ideas and what things would work best. Once the trail is set and people are using it, they tend to go with what is already there unless we make it too hard. When the trail is not fully established, it turns into the wild west (anything goes) really quickly.

Once people get what they want, they tend to want to get to it quicker. They also want more. This could be more options, more control, more access, more of almost everything. They basically get addicted to data and ease of use.

Steve was doing a demo on sub phases, sub groups, and sub locations. Lots of using elements of time and special flags and tags to track all of the details.

One thing that will help people is showing them how to get back to their details and data. We (developers and power users) know things well enough that we pop through screens, skip steps, and go really fast. A new user is watching and they just get lost. So many moving pieces. It hasn't been smoothed out and/or standardized yet to really make it manageable and easy to understand. We either need to slow down and/or make the path more direct and discernible. Make it obvious and straight forward.

A note for us... We can use these subs to hold the sub details and sub data. We need to show things in very general levels and make it look simple unless the user wants to get clear down to the lower detail level. Think of the world building graphics that have universe level, world level, location level, group level, individual level, and the underlying data level. We need to allow the users to navigate at whatever level they feel most comfortable. We need all of the deep, deep, sub data, but that may be too much detail for some people and/or users.

There will be a greater and greater needs for mini conversions and how that effects things. Steve has already done quite a bit of work on the custom/build_complex_labels.cfm page. We need to use that as a great starting place. Lots of moving pieces. It goes like this... You have to have a parent item. Parents have subs or children. Those children then get broken down into smaller pieces and sub packaged. That is mini conversions.

We keep pioneering small little projects and getting some testers and people who keep pushing on things. Adilas is literally a giant testing environment and a virtual idea farm. We keep planting and harvesting ideas. They just keep coming.

Going back to manufacturing - there are tons of batches, sub batches, lots, and even reprocessing and repackaging pieces. We need to keep defining the road and helping the people who will be coming down the road later on. Kinda like Eric was saying... We need to focus and get pieces done and standardized - we get pulled in so many different directions. We lose a ton in the transition and switchover between projects. It gets very expensive and takes a ton of time and energy. In manufacturing, they often will set up an assembly line for a certain run... They then run that product until it is done. If they had to switch lines (assembly lines) every couple of hours, they would have tons of down time. Maybe we need to do similar type things. Make a plan and then work your plan.

The other gem is using the people who know it... get the reps and the clients together that know what is going on.

Flow - We can link all kinds of stuff together. That is a whole other level. If we can get the job done and get the person to the correct next step, we can help them keep moving forward. It comes down to flow and planning. Steve wants Dustin to help with some of that flow. Steve's words... "we need to train the system". That helps the whole thing go better. Dustin's words were... "the system almost needs rails". They then talked about wizards, steps, and showing a logic path and where they are on that legend or helping them know what is next and where things are at. Walk them through it. This could be crumb trails, legends, wizards, etc. Good stuff.

Working on adilas ecommerce pieces and training details.

Morning meeting. Steve was working on code. I was updating adilas ecommerce stuff. Russell came on and reported on some of his projects.

Information from Russell and Chris Johnnie about coupons, loyalty points, and gift cards.

- Gift cards - be able to get a random number and put it onto a card. The random number makes it harder for someone to use another card (security issues). He needs to be able to scan it and see what is on the card. He also needs a spot to scan the card and have it use that as a payment option. It needs to go full circle. They need to be able look things up, add to it, take away from it, and view levels. Both tied to a customer and not tied to a customer (generic card). Be able to use this in both the normal secure cart and the ecommerce cart. Easy to load card.

- Punch cards - every cart that is $15 or more is eligible. If the cart is a counter sale, they could be prompted to sign-up if they want. Once they are in, the points would automatically accumulate based off of the rules. Once they get to a certain level, say 15 points, they get $10 off of the purchase. They want it really automated and almost a non-thinker type process. They want a quick interface to allow for the sign-up process.Just to recap Notification when a customer is eligible, notification when a customer has points they can redeem. Customers can choose how much they want to pull out. They must pull out blocks of points at a time. For example they have to pull out 15 Points to get $10 off. They cannot pull 10 points and get $7.50 off.

- Coupons - add, edit, copy, delete (permanent hide status), details - coupon code, coupon text or description, quantity, status, type ($'s off or % off), usage (unlimited, limited amount, unlimited no additional discount, limited amount no additional discount) , customer limit, specific item or part id, status (blocked or open or deleted), minimum value to activate, etc. See Russell's page afb_coupons_rules_logic_settings.cfm - branch ram-42. See the link below for the spreadsheet planning.

10 - 1 with Eric - planning out the loyalty points and special accounts.

Estimated amount Chris is willing to contribute

Gift Cards

$3500-$5000

Puch Card

$1500-$3000

Cupons

$1500-$3000

We talked quite a bit about using the builders and logic (part of the UI) as the master options. The builders might be things like locations, part categories, customer types, and even the item or part id level. Lots of field names and lists to  help us make and generate the rules.

We do have a more complicated issue when we do cross-corp loyalty points. These cross-corp things struggle with pre-calculated totals and such.

We talked about migration paths and getting existing customers into the basic loyalty points as well as getting new customer using our basic adilas loyalty points.

User communities - who wants to join up and put a list of priorities together. We then work and prioritize these features and get them in place as soon as possible.

As part of the conversation, I gave Eric permission to run with the basic loyalty points. He will get a plan ready and then re-present it back to me before going into the coding stage. Good stuff and trying to remove as many obstacles as possible.

Meeting with Chris - rough budgets - Gift cards (3,500 - 5,000), coupons (1,500 - 3,000), loyalty points, rewards, and virtual punch cards (1,500 - 3,000)

Chris wanted to make sure we got his other details from Russell. Chris is looking for timeframes. We went over what Russell passed over to us on element of time # 3742.

Steve jumped on and started talking monies and strategy for repayment. Possible white label options - going forward. Chris has been a great asset and contributor for years now. The goal is to get the developers funded and pushing on the projects with minimal side tracks (focused). We are looking at $2,000 this month and then $2,000 next month. That would be a great start. Whatever Chris throws over, we'll put it on the balance sheet and then pay it back out at $1,000 per month. Steve will enter things in and then send Chris a screen shot of what was booked.

Different topic - competing with Air B&B - booking timeshares, rentals, reservations, etc. All kinds of people put up their properties and then let it get scheduled out, paid for, and reserved. This seems to be the new way people are booking their vacations and travel. Basically, people have the items (camper trailers, cabins, houses, apartments, condos, etc.) and are willing to rent them and let others use them.

Affiliate programs and referral programs - more extended options - it could go all kinds of ways and get pretty deep. This could also tie into coupons, discounts, campaigns, and even rentals and reservations. Steve and Chris were talking about taking Air B&B type concepts and mixing that with affiliate programs and referral programs.

Setting up some custom adilas email addresses for a client. This allows them to email out of adilas and then we place some forwarding options on the account to make all replies hit another outside email account. Kinda some smoke and mirrors.

On the morning meeting with the guys. One of the first topics of the day was a client's system stats and how to monitor who is big, small, or somewhere in between? We have a few small reports, but we really need to beef that area up and make it more available and visible. We would love to do some visual stats, like the new invoice homepage that Alan made. The difference would be that instead of just invoice and sales data, it would be corporation (world) or location level stats and data. That would be really cool. We went into one of the servers and checked around. The data 0 box had over 1,000+ unique logins yesterday. The corporation in question had over 55 unique users yesterday make and/or modify an invoice. That same company had over 110 unique users affect an invoice in the month of October. We would like to make those kind of stats available and ready for viewing. It helps with decisions and what not.

As we were talking about shared hosting plans, we had the idea of creating an in-depth news and update with information about shared hosting plans (standard adilas accounts), semi-dedicated plans (limited number per server), and fully or full dedicated plans (private server boxes or cluster). We also made a note that some of that info may go well in our ecommerce pages and section. Basically, let the companies decide if they want to upgrade and what not. Show the features, advantages, and benefits of what we have to offer.

Along with that discussion, we had some talks about how fast things are changing all around us... think of technology in general, software packages, servers, hardware, and even versions of existing products. Everything keeps advancing. It becomes a maintenance balance to keep up with things.

Steve wanted to be fair and look at upgrades and maintenance from both sides. What are the clients wanting and/or expecting (their side)? What are we wanting and/or expecting (from our side)? Where do we meet in the middle and who pays for what? Great questions.

We also talked about the fear of selling and making the sale. Sometimes it is scary to virtually rock the boat. This was mostly on my part, but I was expressing that sometimes my angle and strategy is very open and doesn't commit and/or over commit on certain things. Each person needs to be their own style. Later in the day, I was challenged to write a big email to open the door to a client about getting on their own box. It made me think of a quote from Spencer Johnson's, "Who Moved My Cheese" book about dealing with change. It says - "What would I do if I weren't afraid?" That is a good question to ask. It is even more fun to ask yourself that question and then actually go do it. Difficult but fun.

Historically speaking, we are seeing things such as the data 0 server. It was setup in 2011 or 2012, it is on a 2008 server, it uses older versions of ColdFusion (coding environment) and older versions of the MySQL database. That conversation moved us to talk about older technology like fax numbers and other older hold-overs and such. It is amazing as it comes down to a form of maintenance and upkeep. Lots of the new things are going to faster processors, solid state drives, and up to date versions of both software and hardware.

A quote from Steve - "Lessons in time". It is amazing what we have learned over time and by trial and error. We keep learning as we go.

Towards the end of the session, I helped merge in some new code from Bryan. His code was dealing with show/hide option for 2nd vendor/payee tied to PO's. After merging code and pushing things up, he went in and did some live testing. After that, I helped get Steve's latest code branch merged into the master code repository. His code is currently all in custom pages and mostly dealing with the cannabis vertical. He's got some good things going. On that note, he would love to turn over his code work and swap it out for more sales work. He is really good at that.

I worked on some feedback for Dave Forbis and a new graphic that he sent to me. See attached for a copy of the new graphics.

Eric popped in and we setup some bigger blocks of time to work on his special account tracking projects. As we were talking, Eric was talking about project management and the "risk factor" within project management and risk management. He is excited that our current project will help other pieces and clients, but it not dependent upon other pieces in the system. Our goal is to get that section finished and launched by end of the year. That would be awesome.

This is an observation, but there is a growing need to keep breaking things into smaller and smaller pieces. Eric had questions, just today, about how to show/hide fields, change names and aliases, etc. We have a mini project that was done and created for the customers add/edit page, but it doesn't go any further than that. We really need to break each section into smaller pieces and have group settings, page settings, and personal settings. That seems to be a growing need. Along with that, we also see a future need to sub divide the permissions into virtual functions within the functions themselves. It is crazy to see how deep those fractures are and will be heading in the future. Crazy customizable levels.

Steve and I were talking about our general direction as a company and how we want to get where we are going. Good discussion. I was running updates that Wayne had passed over to me for updating database tables between servers. I helped Steve with a small Metrc package table update and pushed up some new code. While I was doing that, Steve and Alan were working on some new code that deals with looking up both adilas id numbers and Metrc id numbers. Lots of back and forth between the two systems. Metrc is a state compliance system that we have to integrate with for some of our clients.

Steve, Bryan, and I had a discussion about the adilas user group and when to launch some of that code. It currently exists, it is just somewhat hidden. We were talking about working with Wayne and his open id (open users) stuff. Eventually we would like to have all of the users held outside of the main corporations (a general user pool). Then, once we have that, we could then allow the users, in the open area... to vote on things, add new projects, and participate as they feel prompted.

Steve would love all of the users to login into their own area... Then we could allow them to jump into the virtual data sphere and either start working, participate in the adilas community (all kinds of stuff), sell their own skills (real users doing training on what they do best), buy stuff, request access to certain sites, get training, etc. Lots of good options.

Steve was talking about first impressions and helping to really help get some "wow's" and "that's cool". Steve wanted Bryan to start working on a timeline type page and/or report. Steve was talking about 4 main things that he would like in our virtual lobby - what are we working on, where do you want to work (what corps have granted you access), news and updates, and a virtual marketplace to allow you to offer your services (what are you good at). As far as the what are you good at (virtual job board), it would be super cool if we could show stats on what you have done in the system. For example: John Doe has 32,000 expense/receipts that he has made and 150,000 invoices and 10,000 uploaded photos and scans. Expand that idea, but just some ideas and such.

Bryan and Steve got in to talking about some cool timelines, CSS templates, Inspinia and bootstrap options, awesome look and feel, etc. We also talked about how to move open community projects (general pool) into the adilas community funded projects (projects that people could donate and/or help fund) and how that would work. It would be super cool to show and allow votes to be cast on what people want, projects to be planned and commissioned and assigned, and parties being able to help and fund things as they see a need and/or want to participate. Great ideas.

4.30 - Flex Grid Tie-Ins

-Create data relationships, connect players together (tie things together), 15 custom fields per the 12 main players- create your own customized database, notes

-Can add log notes to any of the 12 main players, unlimited in quantity

-Virtual buddy system

4.30 - Flex Grid

Understanding the Basics:

The flex grid tie-in application is a standalone mini application or customizable database that rides on top of your entire adilas system.  Flex grid has 3 main uses.  It can be used as a virtual buddy system, tying things together and creating data relationships.  Flex grid also allows you to add additional notes or logs to any of the 12 main players.  Another use is to create your own customized database for each of the 12 Main players with up to 15 custom fields and unlimited subs per each main player, to track any special data needs.

Flex grid arches over the entire application because it can be used with, and between, any of the 12 Main players.  You can add an unlimited amount of flex grid to an object and flex grid is almost as unlimited in the ways it can be adapted to fit your needs.  

Getting Started:

Flex grid must be tied to a main or “host” object, one of the 12 main players.  To add flex grid, go to the individual object (Such as: Invoice #97, Employee - John Doe, Customer – Jane Smith, E/R # 65, etc.) where the flex grid needs to be attached, and add your flex grid tie in from there.  When you are on the main object and have the necessary permissions there will be a link that says “[add new flex grid tie-in]”, there is also a link to view other flex grid pieces already attached there.

To set up your own customized database, go to the flex grid tie in homepage to add and manage your custom fields.  With the admin permissions there is a button right in the middle of the Flex Grid Homepage that says “admin – manage custom fields”.  We would highly recommend taking some time to plan out what you need/want for your flex grid before going in to set it up.  You have 15 custom fields per Main Player Group but the 15 custom fields can contain subs in the form of dynamic drop-down lists, or a combination of a drop-down list and open entry field, it depends on your needs.

Get to the Flex Grid Homepage from the Classic Homepage under System Maintenance – Flex Grid Tie-In Homepage; My Favorites Homepage under Flex Grid Tie-Ins – Flex Grid Homepage; or the Interactive Map under the flex grid tie-ins button at the top.

Suggested Permissions & Settings:

Permissions:

Basic Use:

System Search: “Flex Grid” – this allows a user to search flex grid pieces from the quick search.

System Maintenance: “Add/Edit Flex Grid” – this is the basic flex grid permission and allows a user to add, edit, view and search flex grid pieces.  

***The 12 Main Players Groups: Though they may be named differently in your adilas application (i.e. if you call your customers – patients, clients, etc.; or your parts – items, services, etc.)

o Balance Sheet Items

o Customers

o Deposits

o Elements of Time

o Employee/Users

o Expense/Receipts

o Invoices

o Parts & General Inventory Items

o PO’s  or Purchase Orders

o Quotes

o Stock/Units – Serialized Inventory

o Vendors

Admin Use:

System Maintenance: “Admin Flex Grid” – the admin level for flex grid allows the user to setup the custom fields, essentially creating a miniature customized database for the information you need to track for that main player group. With 15 custom fields available for each of the 12 main players, and potentially unlimited subs this creates a very expandable and flexible mini application.

Related Pages & Help File Links:

Flex Grid Tie-In Homepage:  Helps with understanding flex grid, getting started with lots of good information and some examples for using flex grid.

https://data0.adilas.biz/top_secret/help.cfm?id=323&pwd=flex

Admin – Manage Custom Fields:  This page is where you set up your custom fields or your custom database.  There are a lot of options here, you can pre-set your subs or just leave it as an open entry field.

https://data0.adilas.biz/top_secret/help.cfm?id=324&pwd=flex

Add/Edit Flex Grid Tie-In:  This page is going through the actual process of adding new pieces of flex grid or editing existing pieces of flex grid.  This page comes up after you have linked from the “[add new flex grid tie-in]” from an individual object page.

https://data0.adilas.biz/top_secret/help.cfm?id=326&pwd=flex

Additional Content:

- Graphic:

o Where the 12 main players are in green & flex grid highlighted in yellow on the interactive map

- Lots of good videos on this --- but that can come later

- Or even showing some screen shots of some Flex Grid custom set up pages – this helps me have an idea of the organization – what it looks like to have all Open Entry – what it looks like when you have populated subs, etc.

- The Teacher site and The Seamstress both have some good flex grid pieces you can show… I’m sure there are others too.

11.6 - Roll Call Accounting Principles

-Roll Call Accounting is the ability to track objects and data over time using a series of dates and flags. Imagine the web server or computer asking the objects and data to return and report. What's your story? Who created you? Where have you been? Where are you headed? Who are your buddies? Where do you belong? When did you finish? etc, etc, etc. Virtually require each piece of data to hold its own luggage.

-The concept of a roll call is what you learn back in kindergarten/first grade when the teacher is asking, “Where is Johnny?” or “Is so & so here?”. So basically what we do is track the life cycle of data. All data has a life cycle and goes through different processes in that life cycle. The roll call comes into play by asking the data questions such as where the data was at a given time, where it is now, who touched it or performed certain actions, etc.

-There are 3 main groups of history tracked in Adilas: Effectual – what shows up for roll call (where is an object at, with date & time stamps), Historical – who touched what (actions/histories), & Financial – what & where does this show up on the financials.

-We have determined that there are 12 main players in the system. Some of the roll call is talking to those individual players or groups and asking them questions based off of the state or status they are in, what point in their life cycle they are at, where they need to go next, etc. That might sound random to keep it that broad, but each individual player performs certain tasks. Many of those tasks can be mapped directly back to the financials such as sales, quantity - inventory tracking, expenses, COGS, payroll, taxes, etc. Everything has a date/time stamp along with what phase or step it is in. We simply map to that. That is roll call accounting.

-Here is a small example. Let’s say a customer comes in and wants to buy something. Before the sale happens, your product is in inventory, and no monies are owed by that person. Once the sale is complete, we now have a reduction in inventory, we have new sales money that either needs to be deposited or is still owed based on payments made. We have a tax liability, we have COGS, and we know a profit that was made. All of those pieces can be mapped back to physical spots on the P&L or balance sheet. The important part is progressing that data through the data assembly process where you are flagging, dating, stamping, etc. The data if it’s ran through the assembly line process actually allows us to do the roll call accounting.

-A huge part of the roll call accounting piece deals with allowing your data to flex. Disclaimer: certain accounting people may start freaking out at this point but if you don’t allow your data to flex or go into virtual waiting spots while the data is waiting for some of its other pieces you have to do all sorts of adjustments to keep everything picture perfect. Our concept is that things often flex. We hold them in that flex state until they can pass that next checkpoint which is where they are flagged, stamped, and then can get passed on to the next step.

-Some people say, “Okay I see how that can happen once”, meaning a flex point, but what we see is that it happens over and over and over again. This is why we treat it like the data assembly line. Some data might go through 3, 4, or multiple steps until it has completed its entire life cycle. But if there is any data that has an issue or has a need to allow for time to pass before completing its life cycle it needs to stay in that flex zone until it is ready to be advanced. This could be waiting for another process to happen to the data, another person to perform a certain task with the data, waiting for something to happen physically before the data can be advanced, etc. There are endless scenarios that cause this circumstance where the data needs to flex or get held in a waiting area of sorts before it is ready to progress down the data assembly line.

-The link below is an entry from 2014 where we were expanding our vision of how we have seen things start rolling in this roll call/data assembly line type concept. The entry shows a number of small drawings as well as information. If you are interested in this concept, it might be a fun read for you. https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=2894

-Here is some additional content on roll call accounting.

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=roll%20call

All master developer lead training. We will also use this entry to record all approved independent developer training (training done on their own). This will also be used for general staff training, regardless of department where they work.

3/15/22: meeting with Alan, John and Brandon and fixing some local server issues. time id 2166: finishing up the look and feel update and putting in a pull request.

4/20: 27.44

from 4/14: 30

Up to 3/1: 26.48

from 11/19 through 1/1/2022: 112.4

11/18: 15.56

11/17/21: 17.5

10/21: 12.08

10/18: 38.04

10/5/21: 27.07

John is working on this:

2/25/21: Notes from today's meeting with KW and SM. Also from another eot that I just found today.

1) Choosing the hour is available for the everyday option. When you choose a day or a range of days, you should have the everyday functions of adding time frames. Multiple per day would be great ie 9am-10am, 10pm-11pm (Happy hours- only Monday through Friday)

2) Settings that allow the discount engine to connect to e-commerce!! 

3) Possibly the discount happens in the cart and not when added to the cart. (In ecomm only adding one item at a time) This will help with the buy x get y. *We did determine that the limit of how many line items can  receive the discount happens in the cart, so it seems there is already coding there for this.
Minimum =needs to pull from the cart info and not from when scanned.

4) Adding functionality that allows for multiple categories and multiple items. Currently, if you choose one category you can assign specific items. If you choose multiple categories you do not have the option to assign specific items.

5) A snow owl pop up so you can sort the vendor list or item list as they are super long. Would be great if the vendor list only included inventory vendors, and even better only vendors who are associated with the categories or items. 

6) Not imperative but an add or edit or submit button at the top would be helpful.

7) Not imperative but would be nice to show in an item if it is linked to any discount engine items. Similar to how it shows that an item is connected to a smart button. Could go right there next to the smart buttons.

**There seems to be a weird scenario, where if you have the wrong vendors populated in the list for the item that you choose to discount, when you add that item to the cart it doesn't recognize the discount. Kind of goes back to limiting the vendor list.

Adding other notes: Everything on this date was quoted at $5000.

6/9/2020: Notes from meeting with Kelly regarding upgrades/fixes to discount engine:

1)Currently for each line item you add through the discount engine, it creates a description in the non printing notes. This can get messy for searches. Possibly make this a permission- do you want this to print? Or, only print once.
2)Most people want to price items more than they want to give discounts. 
3)Needs to work in e-commerce.

Josh will be finishing up phase one of discount engine this week (9/11/19). 

Buy X get Y (a more flexible BOGO). This has been asked for quite a bit by clients. Josh estimates this is a larger scope, as additional fields would need to be added to the database. Estimated time would be 2-4 weeks.

Buy X Get Y
   -  Categories for X
   -  Categories for Y
   -  Parts
   -  Vendors
   -  Time Periods
   -  How many max uses
   -  Make any purchase on Friday, get a free joint

Buy 2 Get 1
Buy 5 Get 2

3/13/20: Molly specific requests: Updates requested, including improvement for: Tiered Pricing, Buy x Get Y. Corrections for Buy X, Get X: not just Line QTY Requirements but Add Total QTY requirements so this works for people who scan. 

11/25/19: Not sure how high on the priority list this is. Putting it down in the list for now.

One client experiences that the discount engine takes quite a while to load (I haven't see this, but Drea did see it on this clients system). Wants to add buy x get y.

Interested in having boxes next to the days of the week so you could run a special Mon, Wed and Fri. 

Have the vendor list after the categories, and if you only choose one category, choose the vendor, and only have that vendors items populate in the list.

Can you exclude specific items from the discount, the way you can include specific items?

Discounting based on key words.

/top_secret/secure/setup_new_employee.cfm

7/6/2020:Total Time: about 91 hours

3/31/20: Progress has been made on classic homepage look and feel.

, Payee permission, corp wide settings and manage corp info pages

2/3/20: Brandon will relay this project to Russell, Chuck and John. The trio will have a budget of $1,000 to do the four pages. If it isn't enough we will determine at that time how to move forward.

1/30/20: Cory met with Charles and saw the mock-ups he and Russell have been working on (have 17 hours cumulatively into potential project). Quick and relatively easy way to make adilas look more updated/relevant. Start with Classic homepage- keep same functions but move around and simplify. Would be a relatively uncomplicated page. Payee permissions is much more complicated and more time consuming. Go through adilas one page at a time- open to customer feedback for direction. Hoping they see classic and get excited. 

Charles can work on this at the same time as his other projects. He can do front end design and development and code the front end. Needs someone ie Russell to wire up the back end. Russell is interested in working on this project as well.

** check with Brandon- has Eric started on duplicate permissions? If this project gets done is that as needed ie should he be focusing on something else?

Meeting with Chuck and a new developer named John Peterson from the Logan, UT area. We had a fun meeting and went through some introductions, had a small Q and A session, and went over some project details. All of us were using webcams for this meeting. We don't often do that. Planning for the future, we are planning on having Chuck, Russell, and John work together as a small team of developers, designers, and project managers. Exciting times.

I will get the non-compete and non-disclosure documents over to John and Chuck and Russell will help get him going. We also briefly talked about other future options that may play out, depending on how this little arrangement works out. On a different note, we at adilas are really grateful for these guys/gals who are willing to help us out and play the game with us. Lots of moving pieces.

After John left, Chuck and I went over a few things dealing with WanderWays - camp adilas and some design decisions. Chuck is going to be organizing resources and assets to help standardize the process. Basically a style guide of sorts. We are using the WanderWays project as somewhat of a guinea pig project to help figure out some of these things. We also went over a few new layout options, some new code enhancements and even some fun pricing stuff. Chuck is adding in some flavor (light jokes and play on words) into the pricing matrix. Fun stuff.

Meeting with Jonathan Johnson from Epic Enterprises. All of met online, due to the corona virus stuff. Steve, Brandon, and Jonathan were on the meeting the whole time. Shari O. was on for a bit but had too much to do. We took a bunch of notes and sent her a copy. The notes are Brandon's computer in a Word document. See attached for a local (on his computer) reference. Good meeting.

We had a good meeting with Jonathan Johnson doing some business consulting. Steve and I met with him for the first couple of hours. We then invited Danny and Marisa in to talk about sales and marketing strategy stuff. I took lots of notes and they are on my local hard drive.

- Figure out how to use your consultant well and then do it, use them as a tool. This was a request from Jonathan.

- In decision making, step up to the plate and swing. Let's get to work.

- We really need to keep applying what we are learning and what we know. Knowledge, unapplied, doesn't do much.

- We are looking for help to build a sales and marketing department within the adilas business model and structure.

- Dealing with leadership and decisions, we need goals, focus, direction, and a plan. Take those next steps and get going.

When I joined the morning meeting, there were multiple people on already. Danny, Dustin, Eric, and Steve were on. They finished their business and then each of them ended up leaving except for Eric. He had some questions dealing with custom industry-specific interfaces and the printing of labels. I gathered up some resources for him and sent him a number of links as well as showed him how to access the pieces inside of the system.

Steve and I chatted about some marketing ideas and Danny chimed in that he really enjoyed the business consulting meeting yesterday with Jonathan Johnson from Epic Enterprises. Good stuff.

Meeting with Jonathan Johnson from Epic Enterprises - we took tons of sales and marketing notes. Brandon has those notes on his local computer. There is some flex grid on this element that points to the file (somewhat hidden from prying eyes).

Great little meeting. We met with John and talked about a bunch of different options. Brandon has some notes from the meeting. We asked about his current experience with doing adilas development, where he wants to go, what he would like to do, etc. Fun meeting. We determined that he would like to work under Russell and be on that small developer team. He anticipates that he could have up to 10 hours a week to help with code, backend, frontend, and UI/UX type projects. Sounds good to us and we'll keep moving forward.

First code review with John. It went very well. He is working on some new application and new session values. The older snow owl pages used to pull numerous queries to populate the snow owl headers and footers. The new code sets a date/time stamp and watches to see if anything has changed. If not, it skips certain pieces of logic and uses stored values in the session scope vs running a new query for every page. Efficiency stuff.

As part of the code review, we went over some logic, memory locking, dynamic notation, some new custom functions. John did a bunch of refactoring of code to simplify some of the pages. It looks good. I was very impressed. Awesome.

Russell and I met over a Zoom meeting. We were merging in a new branch of code from John Peterson and some new snow owl pages. The primary new page was the classic homepage. This one has it's roots back to 2006 and before. One of the first pages that was part of adilas and fully based off of permission. The new page gives the older page a facelift and limits the number of clicks that a user has to make.

Here is a link to a news and updates page for the new classic homepage.

The merge process was somewhat complex and we had a multiple step process to deploy the new code to each server. We had to add some new custom files, new folders, and flush the application variables. We finally got it all pushed up. Along the way we had to make a few tweaks for it to run on the older servers.

At the end of the meeting, Russell was showing me some of his progress that he is making on running reports to breakdown his small teams efforts and time spent on projects. This is all part of trying to get better and better at project management.

Emails and follow-up.

Shannon and I spent the session working and formatting the presentation gallery outline. We also tried to add some new images to help break-up the space as well as a small intro into business world building (towards the bottom of the page). See attached.

Here is some text on world building. Just for fun.

Moving Toward Full World Building

If you cut through all of features and bullet points above (pretend you are looking at all of the presentation gallery outline stuff) the end goal and idea is for you to be able to solve any of your business needs. A good portion of what we offer and peddle are hope, vision, potential, and making your dreams become reality. 

This is why we are trying to introduce world building. The concepts of 3D World Building or Business World Building have been in the works for years. Adilas didn't start out with world building as the main goal. It kind of evolved from just taking one step after another, trying to solve our own business needs. 

The goal is not just the operations, accounting, or the data. The goal becomes capturing the story with all of the details and interactions. It is the story that brings the dates, times, numbers, locations, and groups together. 

Mixing all of the pieces together gives the values (data) or players (characters - pretend like it is a game) life or almost a personality. For example: Say all you know is we have $5,000 on 25th of October. That doesn't mean that much if that is all you get. But if you knew that the $5,000 on the 25th of October came from 20 different invoices at a single location that were collected and then deposited by John. That helps tell the story. Say you also had all of the underlying details of what each invoice was holding, what each customer bought or purchased, how much money was paid and how much was still owed... You could see inventory levels, notes, histories, trends, states, statuses, and other important details. Now you are getting a story. That is the goal!

Russell really wants to be an organizer and/or a creator. That is awesome. If Russell had his way, he would want to be a designer and work on the frontend user experience. I see Russell as a guy with his nose to the wind, looking for what is coming next and what is trending... (like a character from "Who Moved My Cheese" by Spencer Johnson - the character's name is "Sniff" - a mouse character that follows his nose as a way of navigating the maze).

He has been doing great as a coordinator and project manager as well. Super awesome. As we kept talking, we talked about designers who had to turn into developers to get their ideas into the real world and into being used. They, the designer type persons, come up with the dream, but then they needed to get it to work and/or come alive. Hence, a designer tuned developer. Kinda fun. Both Russell and I have walked that path. The other common path in the development side is just starting with the code and jumping right into code vs being on the creative/designer side first. We haven't seen a developer turn to a designer very often... it usually only goes one direction.

We are faced with a challenge and then trying to make it happen and/or getting that scenario all worked out. That is what we do every day. Ideally, we are wanting to give back and say thank you for the opportunity. Along with that, we also are trying to bring a value to the mix and/or bringing a value to the team. Delivering a value for money and/or some other form of compensation.

Russell and I were talking about what makes us tick... Russell was saying that he loves the details and seeing the data. Basically a visual representation of what he is doing. Seeing the data builds the trails and records the story. Fun stuff.

The deeper we go, the more that communication and maintaining things becomes important.

Assigned to John Maestas with guidance from Dustin: 7/30/2020: This page needs to be conditioned: Finding patients who have not been in 90 days

Web link - no_purchase_report.cfm

This is the guide for what it should look like: Web link - sales_parts_by_weight.cfm

Original notes on the entry - Dustin's colleague is interested in working 10-20 hours a week with us. He is also a student.

Cory and I met with John and chatted and talked with him for about an hour and a half. John showed us some of his work, graphics, movie editing, and some of his code work. We would like to give him a chance and see what he can do. He is busy for the next week and a half but should be able to get with us again next week to see what the next steps might be. We also talked about how adilas works and what it would look like if he were an independent or sub contractor for us. As a fun side note, John is an adilas user and has worked with some companies that used adilas. That will really help.

8/19/2020: Dustin will be first point of contact for help/training/support and will bill Adilas for this time.

Steve and Sean going over sales stuff. They were talking about the Apple Model and how someone greats you when you come in and then you could be helped by someone else by going through some sort of simple queue type process. Danny checked in. After that, we helped Steve with his local environment. Both Dustin and John Maestas checked in. Some small intros were made and what not. John is Dustin's friend. John is just getting going with us on some development projects.

They then started to talk about different versions and generations, for example: generation 3 or generation 4, etc. Dustin has been responsible for some of the new versions out in cultivation land and what not. It is fun to see the progress and the changes over time.

After these guys left, we went into a sub meeting of sorts and worked through some things. Sometimes, our clients, want industry specific processes that are fully built out and completely industry specific (super narrow focus and/or paths to choose). As we were talking, we ended up talking about drawing out the processes, pretending to do simulations and different use cases. We also talked about being proactive vs reactive  and/or passive. We really want to help our users out and then let them help us refine it vs waiting completely on the client's input. Sometimes they don't know what is possible, they tend to stick with what is set in front of them.

Often, our clients don't realize that we can customize it (tweak or refine the processes). That seems really trivial to us, but thinking in custom code (what is possible) is a skill. The deeper we go, the more we are seeing that all of our layouts need to be fully customized or customizable and based on settings. That sounds awesome, but that adds a whole other level of complexity. Small and skinny yet totally data driven.

We need to get back to the limited flex grid pages. Make it slick and skinny. We are already using it for Beaver Mountain, but want to make it good to go for all of our clients. This would be so cool, but it will take some more work. Having said that, we really really want to get back to this. The limited flex grid is a way of setting up custom fields and dynamically populating a really small add/edit form that only shows what they want or need vs all of the possible fields.

As a side note, the flex grid table has over 40+ different fields that we can and do use for different things. Imagine is you could setup a simple form that only had 5-6 of those custom values. It then becomes really simple vs too big or too overwhelming. The goal is user defined simplicity, yet still being fully connected and powerful. If needed, we could always flip over to a full or more extended mode if some other field or value is needed. It is almost like layering the interface and the data. Super simple on the surface, but deeper or more rich as needed (layering).

We got off into communications and dealing with outbound messages, communication options, and getting people connected to the correct sub or special pages (combo of communication and navigation options).

Next, we got talking about building out custom skins (wrappers of the logic and data) and how that plays into the mix. We did some light pitching and talking about different packaging and marketing options. Some of the subjects that we chatted about were things like ski area, gun shooting lanes, classes, and then working with people in those industries to build and test out products and services. Basically, have or get a dream, build it, and then use people who are in that industry to test and give feedback on interface, navigation, user experience, flow, and functionality requirements.

On the marketing and sales side, if we have someone who is using our product in a specific industry, that testimonial does tons for helping others in that industry to be willing to jump on board. We have also found that if we find someone who is in an industry and they are willing to help, provide feedback, beta test, and give ideas... that is like gold and helps the process get smoother and smoother. It is amazing how a little bit of icing makes the cake look that much better.

Expanding into other horizons, we really want to do this. Our conversation circled back around to the dream it up, push on it, and we'll help you wire that up type model. You dream it up, we'll wire it up. Making things simple, powerful, and easy. Awesome words/phrases, harder to do, but possible. We also talked about opening our eyes and minds to what is possible. Being able to see and/or imagine is sometimes harder than you think. Once we can see it, the next phase is letting our users and clients catch that vision. Once you can transfer the vision, others start helping to beat that drum and making it happen. Share the vision!

As we look at the MVP (minimal viable product or minimal viable plan) type approach, we get pulled out of the dream land and back into - what are the next step or steps that need to happen. You can't lose sight of the goal, but you also have to make it work (along the way) vs just the dream at the end of the tunnel. Having said that... one thing that has been very successful for us is... get them hooked on one aspect and then letting them go and start dreaming. They'll start putting the pieces together. You just have to get that process started. Sometimes with an MVP type approach and then let it grow from there.

Here are a couple of other topics that were discussed: saved reports and connecting to them, other future projects (fracture), reviewing topics listed above, automated and predictive logic, aggregates and quick starts, templates, build your own processes (data assembly line and flex bubbles or flex pods), and other topics. Good meeting. Lots of new ideas and also firming up some of the older ones that keep circling around.

John and I met up and went over his data table project. We did some code review and got it all pushed up live. This was his first live project. Good stuff.

John and I got on a meeting. We have a new corp-wide setting that is needed. This corp-wide setting is dealing with sub barcodes and what values are added as a prefix or frontend value to the barcodes. The main meat of the barcode is an auto id that matches the primary key id number for the record. The precursor or prefix is a string of characters that help us look for the correct barcodes. We did some planning and then right into code when we were ready. We started with the new database script that was needed to get the project started.

John and I are cruising through his project. We went over our database update for a new corp-wide setting and then started into building out the add/edit process for the new sub barcode prefix project. Small work session.

Working through his new project on the a new sub barcode prefix setting. We finished up the add/edit form today. Tomorrow, we'll be on to the action page to help the user submit and make the changes stick in the database. Small training session.

Emails and recording notes.

2:00 pm to 3:00 pm - Meeting with John M to work on his project. We have not launched it and pushed it live, the development of the project is completed. This is a new corp-wide setting to help control the prefix for the auto sub barcode values within sub inventory. The project included a new database update script, add/edit forms, validation, passing the data to the database, and then using the new setting when the keyword "auto" is used on sub inventory barcodes. Pretty cool. Also, John is doing great and really catching on. Good stuff.

A bunch of the guys and gals were on the meeting when I joined. Marisa, Sean, John M., Steve, and I were on there. Sean and Steve were talking about needs for the gun dealership. They need a cross between a stock/unit (serialized inventory) and a part or general inventory item (bulk or widget inventory). As they were talking, I jumped in and mentioned that we had a similar request back when we were working with Barry at GPS Autotrackers. He, Barry, wanted to be able to sell things in bulk, but still track things with specific data (say a serial number for each GPS unit). He wanted the invoice to be something simple like: Sold 400 GPS units for a certain amount. Then, somewhat hidden and/or off to the side, here are the 400 serial numbers that go along with that (extra details or extra information or data).

As we talked, we ended up pitching a couple of different ideas of how we could figure that out. Option one was just use normal stock/units (existing serialized inventory stuff). Option two was parent/child inventory with a single parent and tons of subs (existing). The third option was a parent item, a sub item with a certain number (quantity), and then hold any extra info in a special table that is setup to hold the extra details. In technical terms... a one-to-many-to-many or in basic terms a parent item, one or more sub item(s), with one or more extra detail(s) per sub. We did a number of drawings and ran through some verbal use cases and options. The option three stuff seemed to have the most potential.

We talked about an extra sub table that could hold things like: auto id, corp id, part id (parent), sub id (subs), special tracking number (serial number, vin, batch, rfid tag number, etc.). It would also have columns that we could connect it to things like a PO, an outbound invoice or quote, and maybe even a separate tie-in to a customer if needed. As a small side note, we were thinking somewhat of a mini flex grid type table (similar concept but smaller in scope).

We don't know what to call it, but there is already some prior entries and ideas called a mini unit (see other entries).  This is a cross between a stock/unit and an item or a part number.

Wayne joined the meeting and we switched gears into servers, hackers, and how to help protect ourselves. We've had some hackers circling around us this past weekend. All part of the game. Wayne is doing a great job and showed us what he is seeing using some of his tools, logs, and outside monitoring services. Good stuff and we are so grateful for his skills and help. Wayne was showing us things and Steve and I were asking questions. Some of the other guys were just listening in.

Meeting with John M at 1 pm. John and I went over files and folders and how the black box code works. We helped him get set on his way for a new and upcoming project. Small training session.

Meeting with Eric at 2 pm. He ended up texting me and we'll hit it tomorrow. Spent the rest of the time recording notes. Emails.

Danny joined the meeting and wanted some help understanding a project that he, Wayne, and John were working on. We did some drawings to help and explained some of the why behind the project that they are working on. Once Danny knows what is going on, he really likes to jump into it. He likes getting his head wrapped around it, at the concept or theory level first.

After that, we worked some on his projects. He is doing great.

12/2/20: As of today, 4.07 hours for JM

11/18/2020: As of today, 2.22 hours for John

11/3/2020: Add another argument: check for dups (yes/no)= in this case no.

Pass in a variable
Will need to cascade
Not a database change. Standard API

1)Put in documentation
2)Pass to method
3)Code to method
4)Check internally

John M or Bryan

John and I looked over a project, made some changes and basically did a code review and push session. Good stuff. He seem to be doing great and jumping in and playing well.

1 pm meet with Danny - We met and did an hour long session on making the age verification or age prompt modal work out in ecommerce. Danny and I have spent a number of sessions on this project. It is somewhat of a training project for Danny and he is killing it. I'm really happy and excited for him.

After that, I merged and launched some new code from John M. dealing with the new corp-wide setting for the sub barcode prefixes. Nice little project, and he is starting to cycle through things as well. Good stuff.

Cory and I talked about projects and worked on detailing out a new one for John M. It deals with some new arguments being passed to web API sockets for adding and updating customers. Working through things, going over requirements and notes for the developer.

Morning meeting and Sean, Steve, John M, Eric, and I were on there. Steve and Eric were going over Metrc issues and talking about database inserts and checking for duplicate records with the Metrc integrations. We then switched gears and started talking about other projects. Sean and Steve were talking about order of operations and needs out in mini unit land (a mini unit is a cross between a part/item and a stock/unit - sell in bulk but track by serial number). Anyways, they are working on a section that deals with orders, backorders, and being able to sell in bulk but still track all of the sub details. We ended up talking about options to flag quotes, orders, and even possible steps and/or phases. Some of the questions where dealing with how to track and manage some of those pieces.

As we got deeper and deeper, we started talking about progression and how we use different tools at different phases of a project. The first tool we use is our minds and head, if we run out of space or the project gets too complicated, we switch and go with paper and pencil, word processing documents, spreadsheets, databases, and software type packages. There is a progression. We usually need the next step as things get more involved and complicated.

This conversion, about progression and what tools to use, lead to a topic of mind mapping, flow charts, use cases, and recording other possible scenarios. If you only have 1 basic path, you may not need this kind of a tool. As it gets more complex, you need better and better tools to help you dive deeper and remember things and also make sure that certain key pieces get included. Good conversation.

John and I did some code review and got some new files merged into the system. After that, we switched gears and did some work on his other project that just got assigned to him dealing with dups on an API socket. He is working through things and doing great.

John jumped in and we worked together to get him pointed in a good direction. His current project is dealing with duplicate customer records via the adilas API sockets. The project has six phases, he is on phase five right now. Making progress and in good spirits. Good stuff.

Code review and push with John M. We were working on the new code to allow customers to be duplicated or not based on settings. Our original code didn't care at all. Then we added code to not allow dups. Now we have code that can work either way. We had a client that wanted multiple records per client to track their behavior. Kinda weird, but that's what they wanted. On adding a customer/client you can now specify if you want to allow dups or not, if you use the adilas API sockets. All internal actions still prevent the duplicate records.

Without getting too carried away, we ran into a bug. It was any new code, it was actually dealing with cross corp rewards and customer loyalty. We spent a little time on it but had to move on. It ended up being a setting that someone was toying with for testing. Kinda frustrating to hit the errors while we were testing new code. It made the new code tests feel flawed, even though they were fine. Interesting.

Going over option for inserting meta data in key pages. Danny was heading up a discussion about SEO (search engine optimization) with John M and myself. I was taking notes and the other guys were commenting and providing ideas and info. We started out with intellectual property and went from there. Here are the basic notes.

- IP - intellectual property - natural flood - you can't copyright or trademark or paten things that already exists... if we flood the area with prior art, that effectively prevents others from claiming things as their own intellectual property. Fun discussion about where we are headed. We are sharing to protect ourselves.

- SEO - buzz word - science and art of making things show up for searches and on search engines

- Seen and unseen - matching SEO content with real natural content - light talks about the history (good and bad) of SEO

- Marketing and getting a new website for adilas - we really want to get a good plan in place and then follow that plan - up until now, it has been a very natural progression that just sort of happens. We want to be more specific and deliberate on our efforts, messages, and marketing. It is time.

- We have a bunch of different levels - main website, secured content (SEO not needed - due to login and permissions), shop (ecommerce - a little bit more tricky), web/API sockets, and other pages and documentation.

- Web content - they virtually and really score your site based on responsive design (mobile ready), same domain name (traffic and visits), amount of time on that domain (frequency and length of time on certain sites), reciprocal links (who links to who), matching content (good natural content), etc. Going over the basics.

- Meta data - key words, buzz words, include photos and videos with built-in meta data

- Sometimes it is the little itty bitty things that help - small things but a lot of small things really start adding up - almost like a virtual score sheet

- We don't want to do anything that is sketchy... off canvas text, hidden things, tags and random content, etc. Play well and be honest.

- We want a main landing page and home base that deals with what adilas is and does (as a whole). This is not industry specific, but who and what are we.

- Animated story lines and time lines

- Some other links - see chat - elevator sales pitch, presentation gallery, outline, chuck's new sales tools, etc.

Web link - adilas_formula.pdf - adilas formula

Web link - time_web_gallery.cfm?corp=748&id=7089 - elevator pitch

Web link - adilas_presentation_gallery.pdf - presentation gallery outline

Web link - time_web_gallery.cfm?corp=748&id=6914 - internal questionnaire summaries (sill working on this - progress)

- Put Danny in charge of the team - pick a team, get a plan in place, set a budget, and help to roll things out.

- What do we want to sell and pitch? Up to this point, we have been pretty off the hip... we need a strategic plan as we go forward. It is time.

Danny and Sean checked in. They were talking about some SEO (search engine optimization) stuff, a new adilas web site (coming next year), and a plan for what they want to pitch and show to the world. John M joined the meeting and he showed me what he is learning about SEO.

I got an email with a bug report in the email. I went to check it out and got sucked in. For almost 2 hours, John and I were fixing some functions and making sure that local function variables were properly declared. I was coding and John was watching. It ended up being a small training session of sorts. We talked as we fixed things and finally got it all wrapped up. We pushed up new code and let people know via email.

At the end, I did some other email stuff and recorded some bills before going to lunch.

**Total for everyone 12/3/20 to 4/14/21: $13,837.34

3/18/21: 4.92
2/23/21: 2.83

12/21/2020: JM hours as of today: 10.31
11/25/2020: 

Chuck did a great job and checked in earlier when our original meeting was scheduled. John and I were still elbow deep in a bug fix so we couldn't meet. We ended up meeting in the afternoon. Chuck is working on a number of different projects. One of them is an RMA (return merchandise authorization) page/form for the gun/firearm dealer. It is looking good and we'll most likely be wiring it up this coming week. The design stuff is done already (mock-ups).

After that, we switched gears and talked about SEO (search engine optimization) and some ideas for a new web site. Chuck would like to use WordPress for the new site. He is quite good at WordPress sites. He is also doing some research on other sites that he likes and why they appeal to him. He showed me three sites. I didn't write them down, but here was the gist... good designs, simple yet elegant, power statements, solving problems for the consumer, removing risk, good content, good use of photos and icons, strategic use of motion/animation, targeted, simple, and enough push to help you sell things without being over the top.

There were six guys on the morning meeting. There seemed to be a problem with the news and updates page (WordPress blogs and API sockets). I was working on that. I had to bypass the news and updates. I then got pulled into another error or small bug fix problem. After that, I worked with John on his chart and graph project. We were hitting some limits on how much data was being pulled into the charts and graphs. We decided to let the graphs show what they could and also show the small breakdown tables to show all of the details as well.

Danny, Sean, Steve, John, Dustin, and I were on the meeting this morning. Steve, John, and Danny were going over SEO (search engine optimization) stuff when I joined. We are going to put Danny in charge of that and let him run with it. I helped Steve with a small code fix. We then pushed up code to all servers (database update and spelling change).

Steve and Sean were talking about the accounting side of the equation and how cool of a piece that is... once someone catches the vision, they can really go and start seeing the whole picture and seeing the vision come full circle. That is exciting. As a side note, Steve and I are getting better at delegating tasks and responsibilities.

Steve and I were talking about seeing people catch that vision and then being willing to help push the ball forward. It is very fun to watch that process happen. We also talked about using internal teams to help these clients get onboard. along with that, we are more willing to spend monies to get clients onboard and going. Once they are going, we can take good care of them (internally) and service their needs.

Emails, paying bills, and recording notes.

Quote from Julie Thayne (friend) from the other day - "If you can't do what you do... do what you can." On a funny note, she said that Bon Jovi (rock singer) had a song about that. I just liked the saying. I did go and listen to the song and liked the lyrics - we bend but don't break, we do what we can. The whole song is about how we, as a people, are dealing with viruses, pandemics, change, etc.

A bunch of the guys checked in and then jumped off to work on their own projects. We had Sean, Danny, and John all check in. John was pretty excited, he is working on a project that tweaks some charts and graphs. Good stuff.

On a side note, Danny asked about Russell and what kind of involvement he may want to play. Russell has been a major contributor as far as current look and feel (snow owl theme) as well as the one who designed the current main adilas.biz web site. We would love his help, he is just busy with school right now.

When I joined at 9 am, the guys were talking about industry specific marketing and research. Mixing Danny, Sean, John M, and Steve together has been fun to see. Each has some unique attributes that mix well together (small project team). I'm excited to see what they come up with.

On a different note, Steve is going to work with John to get him going on a round 2 version of the icon menus and more options. Russell launched a new version on the new classic homepage. Steve wants John to do similar stuff on a number of pages. Instead of using screenshots for the icons (current visual) they will be using newer more modern icons such as fontawesome icons and other web specific icons. It makes it feel more modern. John will be working with Dustin and Chuck to coordinate the icon list and what each one does and/or represents. There could be tons and tons of new icons added to the mix.

Looking over some code with Steve on one of his projects. Alan popped in and gave us a small update on some of his projects.

Code review and push with John. We went over his changes that he did for the chart project (2 existing reports with charts) and the new modifications that he did. Good stuff and it looked great. A couple minor tweaks, but good to go. He is doing an excellent job.

1/4/21: 10.64 hours added
12/21/20: As of today-5.4hrs for JM
12/7/2020: John M is working on this

There were 5 of us on the meeting. We had Wayne, Alan, Steve, John M, and myself. Wayne started out and we moved through a bunch of topics dealing with serves and where we are headed and what is needed. Great meeting. Here are some of my notes.

- Most of the servers have been moved over to Hostek.

- The servers are being more stable.

- We are still having problems with 3rd party solutions.

- Our internal API socket connections have slowed down - we ended up pushing some of that back on the outside clients.

- We have moved the WordPress stuff on to its own server.

- Data 0 is working much better and being more stable.

- Wayne and the guys (John and Danny) are working on some database projects.

- We are getting close to being able to cluster those servers. Currently, we are somewhat of a 1-1 server/database setup. We would like to get into clustering of those servers.

- We are getting good read and good data back on servers and database usage using Fusion Reactor.

- The bigger clients will get what they want and our smaller servers will be able to be consolidated.

- Data 2 (new data 20) seems really busy on the database queries and requests. There are also some other servers that get hit really hard.

- From Wayne, reward points seem to be a bigger lift. We have to look up so many records.

- Cloud Flare has a hard 100 second page load limit. We still have a few pages that are big pigs. We are looking into some long running report handoffs and finishing the process behind the scenes and then either emailing it or making a new link available. Dealing with Cloud Flare, we have been happy with a ton of bad traffic that is being blocked.

- Maybe getting into threads (Alan and Wayne looking into things)

- Wayne was showing us some server stats. Lots of traffic and requests.

- We have been renaming servers and changing their domain names.

- Stats on servers, requests, browsers, pages, operating systems, device types, etc. Great stats.

- Wayne was even reporting on hack attempts and measures that we are taking to either monitor and/or eliminate those attempts. It is great to have Wayne on the servers, watching and helping to smooth things out.

- Talks about databases and having unique datasources on the same servers. This is a future project.

- Talking about internal coding practices, testing, and stomping out bugs.

- Wayne, John, and Danny are working on some big database tables and consolidating those queries and data. Along those lines, they, that team, is going to do some automated testing on the new changes. The goal is to eventually get lots of automated testing in place and ready to go. Wayne was talking about processes that were looking at automated tests, and auto deployment options, if things pass all the tests.

- Introducing bugs by making a change and then that bugs shows up on some other page (what pages affect other pages).

- Talking about bugs... how do we track those, who fixes those, and how we get those bugs assigned to the correct developers? Currently, lots of the bugs are being passed over to Wayne and that's not really fair. What are our options? We need to pick somebody to start and track that process. We are thinking Cory, right now.

- Maybe using bug tracking stuff that already exists on bit bucket (Jira) or we could write our own bug tracking pieces. There are pros and cons to both scenarios.

- We may need a full-time bug person. We have ways of seeing some of those bugs even before they get really crazy. The biggest problem is who had the time and who's job is it to address those issues? That is a missing piece right now. Some of these bugs relate to our development process and lots of copying and pasting. We are seeing many of the errors show up in logs and such, but no one is actively watching or trying to take care of that.

- We tend to use junior devs (developers) and send them into a page, have them make some changes, and then go from there. It would be awesome to help them know and learn the why.

- We would like to make a standard operating procedure (SOP) for how to deal with bugs. Also, it could be training, operator errors, settings, processes, procedures, etc. We will start getting into this. We had some discussions on some of internal issues that we have. Who will fix it, what data was passed in, how can we duplicate those errors, etc.

- Two possible roles - one who collect and logs the errors. The other is a developer who can get in and get things fixed. Along with bugs, we need to also set priorities for those bugs and those bug fixes. We may need more than just one bug guys. We may need to pick and choose based on the bugs.

- Getting Wayne a mini me helper - how to jump on the servers, interact with Hostek, rebooting servers, resetting services, stopping the auto deploys, etc. We will be starting out with John Maestas as a mini me helper for Wayne.

- Data normalization rules and redoing some of the database tables. On this first round, we will do the minimum levels to get it ready to do clustering. We will normalize where possible.

- On the server side, the database are the weakest link. We would like to get these clustered and backed up even better than they currently are. Wayne and John may be looking into this as we go forward. Currently, both Hostek and Newtek are doing daily back-ups of the data, but sometimes a lot of data passes in just one day. We may need to get a smaller increment for our back-ups.

- Light talks on server caching and calls to the database. Trying to be more efficient. Limiting the number of requests per page.

11/11/25: Bug in the snow owl database search. Even if there are more than 50 records, only 50 records display.

Needs to be fixed: Web link -custom/metrc_dispensary_homepage_new.cfm

Fixed: This page is an example of it not working: Web link - deposit_home.cfm

This is a page where it works: Web link - receipt_home.cfm

As of 3/1:12.33

10/18: 2.37

10/7/21:JM: 59.57

12/9/2020: Project id for John M and Wayne

50 million videos... on YouTube... close to a year and a half of training that we recorded. I'll bet over 100 hours of training that was recorded. We haven't categorized it yet, but here is the link: https://www.youtube.com/user/adilasbiz/videos

Danny, Steve, and John were talking about SEO (search engine optimization), training, and getting the word out there. We have tons of stuff, but no one knows where it is and how to get it. We are looking to change that up as we go forward.

Sean was talking with Steve about reaching out to our clients and getting them all on board and updated to the newest levels. We are really excited to get in there and start taking care of our clients better and better from the inside vs the older outside independent model. Really good stuff. We are trying to mature and develop as a company and as a family unit.

2/8/23 created video.

1/24/23 created video.

1/23/23 checked and pushed with Brandon

Through 4/14/: 46.29

Through 3/1: 173.39 hours

12/21 through 1/22: 62.93 for JM

2/3/21: 35hrs
1/4/21: 15.59 hours for JM
12/14/2020: Brandon and John M will start meeting this week to get the ball rolling.

1/4/21: 2.32 hours for JM
12/14/2020: Dustin and John will be working on this per Steve.

Both John and Sean joined the meeting this morning. Mostly just touching base and passing along updates. Both of those guys are doing great. We talked about how we plan on refining things over time. It's fun to nail things right out of the gates, but sometimes it takes time and practice. We will keep refining as we go.

1/4/21: 10 hours for JM
12/16/2020: John M will dig in to javascript

https://data20.adilas.biz/top_secret/custom/discount.cfm

22 Smokin Saturdays = can't edit

Working with John and going over a payroll overview. We ended up spending a bunch of time looking at time cards and how those play into the mix. See attached for a video recording of most of our session. We kept going after we stopped recording, but it will give you the flavor, if you want to see what we were saying.

Web link - time_web_gallery.cfm?corp=748&id=2042 - link to a page with tons of notes about payroll, timecards (time cards), other smaller mini project pieces. Basically, a small core of a project that could be connected to and/or linked into the rest of the adilas system. Possible starting place or core.

Server meeting with a bunch of the guys. We had Steve, Wayne, Eric, Alan, John, and myself on the meeting. Later on, we were joined by others as well. There are some of my notes.

- Some of Steve's top 3 for the year was - 1) servers, 2) customer care,  3) look and feel

- On the auto Git updates... we are thinking that once a day may be enough... also doing this off hours.

- Idea  - kill the rej files, do the merge, check again, if rej files exist - do a hard replace

- Wayne and John are working together to cross share knowledge

- Eric - question about a build (manual process) vs an auto merge or auto build process

- Wayne - the more servers we get, the more time consuming and demanding the processes may be - trying to get to the automated testing levels (becoming a given)

- Light talks about file corruption and cascading bad code

- We have very interlinked code that is complex and has multiple usage modes - we really need the testing

- Some of our issues are singular... meaning they happen once or once in a blue moon - in general, most times thing flow pretty well

- There was some talks about different branches, staging servers, testing servers, etc. It still comes down to time and efforts.

- Our model gets even deeper, once you add all of the custom stuff per server

- The Wayne and John (virtual partnership) is going to get a second pair of eyes on the processes. Getting a different perspective.

- We have a Cloud Flare filter and/or blocker. That is good and bad. We are getting timeout issues when certain pages take a long time to load.

- Cory and Shari O. popped in and were talking about client needs and wanting to get to their data, even it it takes a long time.

- Steve was chiming in and talking about clients and their needs and being able to provide the data and services that they want.

- Wayne was talking about other threats that we are facing, including outside threats, hack attempts, and traffic outside of our direct control.

- We can't turn off the security to allow for clients to just have full access to their servers.

- Wayne was proposing that we look at the long running reports and pages and try to fix those pieces. Steve was then talking about how much time and efforts that would take to fix and modify those pages and reports.

- We have some pages that need page specific settings. Currently Cloud Flare (the frontend filter) has server settings but not page level settings for timeouts and such.

- Some of our efforts need to be on optimizing code and reports to make them run faster.

- Talks about security and firewalls.

- Updates on some of the bigger or global projects (big tables and prepping for cluster models). Wayne and Alan were talking about servers, code changes, and getting deployment and testing options.

- Emails and talking about mail servers

- Trying to work more as a team, communications, updates, and helping each other.

Touching base with the guys. Emails and a small bug fix. Working with John on some special characters and how to watch for them and replace them (sanitizing data).

John joined us on the meeting . Wayne showed John and I some of the things that he is working on, on his own, for his own house - automating all kinds of circuits, switches, and parts of his house. Kinda an in-depth  demo or tour of what he is working on. Fun stuff. Lots of ideas and possibilities. He loves to automate things, sometimes at really high or deep levels.

After Wayne left, John and I started looking over the IRS Pub 15 for tax year 2021. This will be a project that he and I are going to be working on here in the next few days.

John and I jumped on a meeting to go over some payroll stuff for 2021. We made a rough plan and I gave John some homework to start looking into some pages and database tables. We also downloaded the 2021 Pub 15 from the IRS website and started to look through it. We will hit it again tomorrow. Good session.

Steve, John, and Dustin were on the meeting. We did some catch-up and checking in on different projects. I merged in some code for John on the discount engine. After that, Dustin, Steve, and I got into some talks about wellness and crazy sicknesses and such.

Taking the next steps... sometimes, you have to get to a point and then decide what to do next. There is no possible way to plan every step. You kinda need a general goal or direction and then you just have to start going down that path.

Working on payroll for 2021 with John. We went over the tax table copier page and ran some of the code. We then got into some data exports to get John's local environment all up to date. Started working through the Pub-15 from the IRS for 2021.

Sean, John, and Steve were talking about demos and sales when I joined in this morning. Touching base on different projects.

Payroll prep stuff with John. We were working on building some new internal tools to help us bulk add/edit tools for federal tax tables. We mocked up a design and started building on the pages. John was coding and I was passing him little snippets from other projects.

Serialized inventory and playing with ideas on mini units. Steve, Sean, John, and I were doing some brainstorming. We were drawing, talking, and playing with simple scenarios in Microsoft Excel. See attached for our Excel sheet (small mock up and playing). Parent inventory, sub inventory, and then clear down to what we are calling mini units (serialized subs).

John and I had a great work session on federal payroll taxes today. We were working on a special copy table and update table (in bulk) tool for us to use to get taxes from last year and then update the ones that were needed for this year. Good session. John is going to do some data entry before our next meeting, but the new tool is mostly built (an internal tool for developers).

I got a text from Cory and Dustin and they needed a file merged in and pushed up. We got them all taken care of and good to go.

Quite a few on the meeting this morning. Mostly just checking in. Some of the guys were prepping some demo sites and doing some internal training. Steve was talking about some new angles for possible white labeling. He has a meeting later today with a current clients that wanted to pitch some ideas.

I sent Danny a list of domain names that we current own and also some that we have let go. I want him to help take a look at those and see if he and Marisa want to do anything with them.

As part of my clean-up process, I ended up doing tons of FTP (file transfer protocol - aka uploading and downloading files from a server) to back-up an older server that we are going to be letting go. The server is one of our original servers and was used clear back in the day when it was called the Morning Star System. As I pulled some of the files down, it was a blast from the past. Lots of fun memories. That's where it all began, back in the day (2001-2008). Adilas did come along until mid 2008. Just for fun, I am going to attach a history doc that talks about the process.

Towards the end of the time slot, John was the only other developer on the meeting. I went through and showed him around on some of the old files and website stuff. We sure have learned a ton over the years.

Great server meeting with myself, Wayne, John, Cory, and Steve. The goal was to fill in the virtual gaps and make sure that everybody knows what is going on and where we are headed. I think we made some great progress. I emailed the meeting notes to all parties that needed them.

After everybody else left, just Steve and I were on the meeting. We ended up switching from servers into sales and options to use the adilas platform as a whole. We talked about how muck it takes to set things up on an industry level playing field (per business vertical) and how to harness those actions. Either our own actions or the actions of our clients. Steve had a guy approach him today to talk about servicing an industry where the client has already tweaked things good enough, that he feels he could allow us to use his custom code, that he paid for, developed through adilas, to service other adilas clients. They were talking about possible kickbacks to the client for virtually figuring out the process and then helping us to market that process to others in his/her field (business vertical or industry specific flow and code). Interesting twist.

In the past, we have always tried to pitch an idea to a client where they help us build it out and then they sell it. The new angle today, is we build it together, they test and help us perfect it, then we sell it and give them a kickback based on the monthly. We make money by selling it, supporting it, and customizing it... they make money through a profit share or just a commission on the monthly. I think that the main difference is, we have never been willing to say... yes, we'll (internally) support and pitch this thing. It has always been farmed out or pushed over to an outside party.

This client that was talking to Steve has a number of the processes dialed in. They have even done their own videos (SOP's - standard operating procedures) and what not. They are not worried about competition, they see it as an angle to make more money from a different revenue stream. Interesting.

On a different note, we are starting to setup our sales, marketing, and deployment teams. That is huge for us. Also, we are trying to make sure that all of our team members have a buddy or someone else to lean on. That, in and of itself, is huge. With a buddy, you can go much further (in the long run).

At the end, Steve and I ended up in a small report on pulling down the old MSAI or Morning Start Automotive, Inc. site. We had fun doing a throwback and reliving a small blast from the past. Kinda fun. We also made some other plans for the future. Good meeting.

Working on payroll stuff with John. We went over the new federal tax tables and checked John's local values (2nd pair of eyes on the new data). We got his local environment all setup and built some replacement scripts to update all of the federal tax tables for 2021 to the new values. We coded the new updates into a script that we will use on all servers to get things up to date.

On a GoToMeeting session with Shawn going over plans for 2021 payroll stuff. Shawn is going to work on states and John and I are going to do federal taxes and forms.

We checked in on corp-wide settings, new changes, and where some of the other dependent projects are at for that section. Wayne, John, and others are all working on new settings.

We got into some overviews on where Alan is heading with his enterprise vendor list (vendor catalog type stuff). He is doing some super cool things with memory caching, getters, setters, corp models, etc. Some major code changes are coming in the corporation and enterprise level of the application. Alan was showing me a preview of some of those pieces. He also showed me some screenshots of his planning for the object manager code that he is working on. Good stuff. See attached for a couple of screen shots of his planning docs.

Sent out an email to Chuck, Cory, Sean, Steve, and myself about questions on a project that we are all working on. Trying to get expectations under control and in check. Sometimes certain projects just keep rolling along without proper steering... :)

We pushed up some new icon menu code for some of the Metrc stuff. John replaced the icon screenshots with web based icons (more modern) on a bunch of pages. Some of the other guys checked in and wished everybody a happy new year.

Working with John on the federal tax calculations. We had to tweak some things to get his local environment up to date with the latest tables and data. Going through the math and working on things.

Working on a number of different projects. Working with John on parts and sub inventory. Helping Steve with a database update and merging in some new code. Towards the end, Steve and I were talking about monies and payments and how we want to structure things in 2021. Internal planning.

Small analogy, a geode (small plain looking rock with crystals inside). Sometimes I feel like adilas is like a geode, the outside doesn't look that exciting, but the inside has all kinds of fun treasures to explore. Kinda fun.

More small tweaks and bug fixes. Working with John on older code clean-ups and changes to bootstrap and jQuery stuff. 

Steve and I were going to meet with Mike, but he had something come up. Instead, we ended up having an impromptu meeting about servers and options there. That is still a spot that brings pain. We are trying and things are getting better, but it still feels painful. Towards the end, John came on and joined us.

Working with John on payroll and tax withholding calculations. We did some light clean-up on another project and then spent the whole time working on the 2020 (last year's) W-2's and 1099's. We have to have those done before January 31st, 2021. Usually before is way better and less stressful. Anyways, we started in on that project. Good stuff.

I got a call from Shari O. about a small bug in the older classic version for sub inventory. Both John and I jumped on a GoToMeeting session and made some changes. We pushed up a new file to fix it.

John and I worked on payroll stuff. We were mostly on the new W-2 forms and working on form fields and layouts.

Small side note, some times we talk about doing bug fixes... John was saying that sometimes bigger companies change the word bug fixes for things like - stability enhancements or efficiency tweaking. They are still fixing things, it just makes it sound more stable and able vs weak and problematic. Interesting concept.

John and I were working on adding in two new payroll settings to help with populating state tax Id numbers on the W-2's. We worked on the pages, passed the values, validated things, and did some database coding to make it stick.

Towards the end, we got some reports that certain servers were struggling and we had to switch gears and jump on the server stuff.

Running database updates for Eric and John. Merging in more code that needed to be added after the database updates portion of the project. Testing and pushing up new files. Also got into some clean-up projects to help tighten some of the pages that are exposed to the public. We've been having some hackers push on every public facing page to look for weaknesses. We ,of course, don't want this, but they keep pushing and trying to find any vulnerabilities wherever they can. That ends up making us tighten things up and is good going forward but not very pleasant while it happens and/or doing the tightening up process. Anyways, made a few changes and pushed up new files. All we can do is keep chipping away at it and make it better today than it was yesterday.

There were 6 guys on the meeting this morning. Mostly just checking in and talking about current clients and client needs. Steve was working on dynamic data entry fields for vehicles and being able to modify the transmission fields. It used to be a standard drop-down, but Steve added a few values and also made it so that a user could edit it to whatever he/she wanted - being able to go outside the older drop-down options.

Eric checked in and we went over some EMV chip reader stuff. Sean and Steve and I went over some of the RMA (return merchandise authorization) stuff for the gun/firearm dealers. We mapped out a few changes. We then had John check in as well.

Working with Spencer, John, and Shari O. on pushing up and testing new Flash conversion stuff. Tons of emails and text messages.

Working with John on new 1099 NEC forms for year end payroll stuff.

This meeting was setup by Danny and Marisa. It was scheduled earlier in the week, but we had some crazy Flash conversion stuff hitting us at that time. Here are my meeting notes. Also, see attached for a number of screen shots from Marisa's presentation.

SEO meeting

- Danny, Marisa, Steve, Chuck, John, Brandon, and Cory were on the meeting

- They were talking about different phases, tools, progress

- We are looking to make our site more organic, actionable, and able to help with solving pain points

- Some pain points for others are: Missing the all in one (system thinking and system options), missing functionality, legal compliance stuff (oversight)

- We want to generate more good web traffic

- Taking courses and trying to stay up to date - Danny, Marisa, Chuck, and John are all taking some new courses to keep learning what they need to know and do. That is awesome!

- Gearing the design to help share and show what we have

- More internal linking

- Resources and support - Marisa really feels like this is a big need and wants to focus here - helping out our clients with what they need.

- Mobile friendly - 1st criteria - everything needs to be mobile ready

- One SEO, the score changes and gets degraded based on errors and missing pieces

- Changing targets - we know that we are chasing a moving and changing target

- We know who we are... be our own style - this is our plan

- Pirate ships, pirates, and boot strapping

- Pros and cons of technology choices

- From steve - keep things as small as possible, service our customers, and optimized our revenue

Steve, Shari, John, and I - random clean-up stuff, servers, custom error messages, and tightening things up.

Cory and I were going to have a meeting about things that we could tighten up on the data 0 box. Before we got into that, we talked about some of the Flash conversion stuff and possible options there...

We could switch to PDF's, programmatically alter the PDF's, do custom black box code and use the check write system as a PDF form. We could do the same things for the labels if we absolutely have to. It has been kinda a pain to deal with the Flash conversion stuff. We still have some options.

Getting back to the server health. We went through the top 10 pages that were being abused (by a hacker) and briefly talked about each page or sets of pages. We covered a number of topics. We talked about server health, usage on data 0, getting John in there working with Wayne, custom error messages, more robust passwords, other plans, and possible work arounds. Fairly deep topic, that ranged all over the place.

As one of our ideas, we talked about splitting off certain pieces of the data 0 server to their own places and/or virtual playgrounds. Instead of getting all of the traffic to one spot, we could spread things out and almost create virtual practice dummy type modules on other serves. We have already moved off the news and updates to another server. We could do the same things with the developer's notebook, some of the free dev tools, calculators, barcode generators, and even the main adilas web page. If someone breaks or hacks that server, it is a virtual dead end, it doesn't really connect to anything else.

Anyways, a number of different possible strategies to make things more solid and prepare for the future. Good stuff.

Multiple people on the meeting. Mostly touching base on different projects. We are still having some issues with the Flash conversion stuff. John and I merged in a custom timeout message. Steve and I looked over some database updates for the mini units. Eric, Cory, and I talked about some crazy wholesale taxing stuff. Basically, we have customers that need to do wholesale deals, but still charge one specific excise tax. Currently, the code says, if wholesale, don't tax anything. However, we kinda need this go between that allows for the normal wholesale stuff but still able to charge a certain excise tax. Sometimes those things get pretty crazy. To make it worst, more complex, they also need to skip certain compliance and state tracking things for these transactions. Crazy complex stuff. Thank you California... and other states, for keeping us on our toes. 

John and I were working on the 2020 1099 NEC's - forms and data overlays. This is a new payroll feature and is similar but different from the 1099 Misc that we normally do. We worked on the black and white versions, the red data overlays, and other small tweaks.

The last 45 minutes, we switched gears and looked at some new code on the check printing stuff from Spencer. We tested it locally and pushed it up online. Light testing and emailing different parties of some of the changes.