Danny checked in and had a question or two. We got him going. Paying bills, doing emails, and other small tasks. Went back and recorded some meeting notes from scribbles on post-it notes.

Weekly meeting with Brandon

Chuck and I met up over a GotoMeeting session. We started out by going over some screenshots from a meeting that I had last week with Jonathan Wells. This link shows a number of screenshots for an internal shopping cart mock-up that Jonathan is working on. Click to view cart screenshots.

After that, we rolled into some new things from Chuck. We talked about email campaigns, advertising, and training. We took a little bit of time and worked on an outline for an upcoming ecommerce bootcamp - ecomm basics course. Towards the end, we got into some new ideas and direction on the presentation gallery and digital outline of what we have to offer. Fun new things coming down the pipeline. Good stuff.

See attached for some screenshots.

Going over a big spreadsheet with Alan on the splitting up the database (world building) project. We went through things on his spreadsheet line by line and talked about scope, depth, and what each step would take. Some great conversations. We talked about testing, changing things, and cascading new changes. Some of our talks were going clear out to the universe, galaxy, cluster, and solar system levels. See attached for an older drawing of the universe levels.

Eventually we'll get things fully dialed in at those upper levels and we'll get back to world level (corporations) and location level (locations within a world) stuff. We also talked a lot about temporary steps for master corporations and sub corporations within their different solar systems (database stuff and who is connected to what).

Meeting with Wayne and going over new servers at Hostek (new server company - new to us). What do we need to do to help with upcoming new servers and helping to smooth out that road. Too many manual or hardcoded tweaks to bring on new servers and new installs. We'll get it all figured out. As a side note, we are also being requested to offer multiple different service levels to our clients. Some of the smaller ones are good to go with what they get right now. Some of the bigger dogs are wanting more and more. We are looking into options.

Group meeting with Hypur (banking entity) dealing with their 3rd party payment solution and need for multi-locations (dynamic) per corporation and a dynamic numbers of API tokens and accounts. Currently, there is only one option per corporation. They wanted a quote so I spent some time and got that out to them.

Cory booked this time for me to work on a project. I did some emails and then jumped back in on this balance sheet project and transitional invoices and how they show up on the balance sheet and eventually on the P&L once out of the transitional state or status. Made some notes where I left off. I'll be back on this later on.

Got on with Bryan to look at some code. He was still working on some stuff so I ended up doing some other stuff. I reached out to Wayne and we did some new server testing. I created a small tick list and started checking things on the new server (data 17). Pulled down files from data 0 and pushed some files up to data 17.

Helped Bryan with some questions and talked with Shari O. over the phone. More server testing. I fixed a few things and finally ran into an error. I sent a message to Wayne and called it quits for the day.

In the morning I had some Internet problems and couldn't get on to the meeting. Once I did, I ended up working with Wayne to get a more dynamic login. We are trying to make our code more portable and enhance the ability to quickly setup new servers and instances without having to hardcode certain pages. Most of my work was on the main login pages.

Wayne had me helping him do some testing on the data 17 box. Lots of changes and pushing and testing the new pages. Emails and other follow-ups.

4/2/20: Add Icon sales report: pull all sales
daily/summary of weekly and monthly-all systems.URL link
provided w/ logo to save to phone. Add custom Reports Page to the
Sales Reports to access sales report. Transfers removed from report. 

Was originally quoted on 3/19/20 for HG.

Marisa has taken over this project

4/2/20: Cory will add info to help pages.

All info that is released for new functionality needs to be in help files and on gears on appropriate pages.

4/2/20: Can't add a customer from the dispensary chooser pages. 

11/30/20: This was fixed and uploaded today. Couldn't find the other issues listed below:
4/2/20: https://data3.adilas.biz/top_secret/secure/advanced_parts_search.cfm Can't use search function here.

P.S. I noticed that on the Item Homepage where the Quick Search Function does not work, but also on the Grouped Item and Advanced Item Search neither the Quick Search Function and the Cart Function do not work. 

4/2/20: 

4/2/20: Danny asked if we have the ability to process Square payments...

Not at this time as we are not current to if they have the API availability 

Currently they have just one option for storing a merchant token for a custom payment solution. We have a scenario where a single corporation needs multiple account settings based off of locations. For example, say a single corp has 4 locations and each location needs a specific merchant account token. We need options to be able to store and use unlimited number of sub accounts.

Talk with Brandon to get details. But the idea is, we keep it as a default of 1 unless they need more. If they need more, we provide a selector where they could put a counter (say 4 or whatever). We then show them that many settings. The web page id stuff allows for multiple optional fields. We could either use those or we could make a note that we have to go external to custom JSON storage (to go deeper).

There is a target date of end of day on Wednesday 4/8/20.

As a side note, Brandon also has a new file that has all of the Hypur error messages (in an array) that would be awesome if we could include that in the existing logic.

Ideally, going forward, we are going to be moving more from the open buffet model to packages and selected product groupings. It will still all be there. This is more of a marketing type move. And, judging by our speed... it may be a while... :)

On a meeting with Steve and Cory going over projects and quotes. We are all learning and making progress. As part of our meeting, we chased down a balance sheet question with transitional invoices and then into sales tax stuff. Lots of moving pieces. We also talked about potential for new or better service levels that we could offer to our clients. Steve and Cory are doing most of the project quoting and just asking me if they have deeper questions and/or get stumped.

Working with Danny over a Zoom session. He had two new black box invoices to get a code sign-off for a client. We merged things in and pushed the new code up to the server. Emails and tech support. Met up with Bryan and went over some of his promotion code stuff. That has been a long hard project. The main difference is internal shopping cart vs ecommerce shopping cart. They have slightly different flows, so you have to play a little bit different.

More emails and setting up a new email account for Cory. She is doing great as a project coordinator.

Emails, follow-ups, and recording details and notes from post-it notes.

4/4/2020: Important pain point for client. Need to determine where the code is so we can move forward.

4/4/2020: This project is mostly complete but need to clean up the code and tie it up.

4/4/2020: When you void an e/r or deposit, it should zero out on balance sheet too.

4/4/2020: Brandon and Eric to meet and determine viability- direction of this feature. How to fix and enhance. 

Emails and recording notes from earlier in the week.

Working on some project planning for a client. Writing a Word doc with specs, to do list stuff, and suggestions for the developer.

Joined the morning meeting. Steve and Danny were on. Danny was looking for some marketing stuff and testimonials. We chatted about a could good options and persons to contact. After that, Steve and I spent most of the morning session going over projects, small questions, changes, and going over direction.

Alan and I did a code review session for a project - customer photo api - 1692 in adilas. The new code allows an outside developer to upload a photo for any of the 12 main players within the system using and external API socket. We went over code, samples, documentation, etc. Good meeting and well done.

Jon Hudson joined the meeting and we spent an hour going over snow owl data tables and how they interact with different JavaScript functions. The older tables worked with the older JavaScript. The main difference is that the snow owl data tables can sub filter the records either through user interaction and/or pagination (next page of n). Anyways, those changes to the table output broke some scripts that help with auto checking/unchecking all boxes or doing automated math. We got him all lined up and passed him off some files with notes and samples.

4/6/2020: Changes to these pieces that were created by Bryan several years ago. In two corps: 979 and 980.

4/6/2020:  Currently it is hard to audit deposit/expense history, since when the main amount is updated, an original value and the edit value do not show in the history. Also line item history.

4/6/2020: Client is having connectivity issues with Headset. Developer needs to look at the api.

4/6/2020: Took over customer tax id field= currently wouldn't work for medical dispensaries. To use this properly need to create a separate field for password. Add to the database, hard code, make it so it can't be seen as this is a security issue. May need to disable current settings.

Going over project questions and doing some project quoting and prep work. Cory is rocking the house and doing awesome. Really excited for her and what she is doing. All of us are getting better at communication, quoting, and project management stuff.

Met up with Danny to go over his next project - id #1449 in adilas. The project deals with customer fields names and aliases. The first one that has been requested is the "terms" field and the alias as chosen by user under the settings for that section. We are planning on prepping the field to make it even better and better for future field name aliases and corp level settings. Good stuff.

We spent an hour and went over two new projects. One is for a custom payment solution and the other is 3 state required reports for a client out of New Jersey. We spent half an hour a piece and got both projects lightly mapped out. One of them will take some additional follow-up and back and forth with the client to go over questions and options. Alan is doing a great job.

Bryan and I looked over some code for his promo code stuff for ecommerce. We made a few tweaks and then pushed and tested some of the new code. The merge and the push took some time but we got it done.

Just for fun, these are some notes from Steve to his friend Danny.

adilas is the future of cloud
custom cloud

Current SAAS (Imagine a static cloud with our competition on that cloud)
Future CSAAS (imagine a dynamic cloud with just adilas on it)

Old SAAS is version based (updates roll out via version)
Future SAAS is custom based (updates roll out real time and are client driven)

Not only is adilas changing real time, adilas changes are driven by the client.

This creates the most powerful software and a client can drive their business forward.

Times change, software must change with the times

Business processes change, adilas changes by businesses.

Look at the black box code you just completed, that was an extreme example.
Look at the view only code you just completed, that was specific client based update that all clients have access to. Many will never use this but it's part of the process to build the solution bigger.

adilas - Expanding and Refining Functionality, Driven by Business

adilas gives businesses the ultimate tool

--------

As part of our meeting, Chuck joined us and we talked about the presentation gallery (navigation, slides, and talking points) vs a real self-guided website that has a self-contained sales pitch. Great little meeting. See attached for a small version of where presentation gallery and slides are headed.

- Talking about custom code, internal development, project mangement, consulting, and pushing things forward.

- Bringing as much as we can into the core.

- Trying to add a new layer of flexibility and professionalism to the projects that we are rolling out.

- We are trying to help the clients see more of what we are doing.

- Trying to get to a more proactive approach vs a defensive or reactive mode or approach.

- We are looking to gather in all of the good ideas and then roll out the projects accordingly.

- If we use adilas as the source, we could use the people and talents around us to get the best possible projects and features.

- Black box and fully custom code. That is still needed. Where possible we want bring things back into the core and use settings or whatever to help all ships rise with the tide.

- Cautions - between who is driving what projects and where are things headed. We want to make sure that we are all headed in the same direction.

- Bug fixes and helping in the tech support areas and what not.

- Sometimes we are so busy, we skip over some of the other good ideas and things that could really help.

- Constant changing - code changes, languages change, businesses change, expectations change, etc. We have to be able to keep rolling and changing as things happen or we see things trending towards different solutions and options.

- Building to settings and permissions vs hardcoded - make it data fed vs strict line by line or manual changes.

- One of the hallmarks of what we do is let our clients help direct us where we want to go by offering a customizable solution.

- Where do you see yourself? Once we learn things, we tend to have a big tick list of ideas or things that we want to build. Looking long-term, do we stay were we are at or do we keep moving. Means vs ends.

- Meeting with Bryan to dial in the phase 2 option for coupons and promotion codes. We want to get a full plan together for the phase 2 options.

- Talking about sanitizing the content that gets shown on the web and available to the general public. We talked about multiple elements of time, show/hide settings on the web, and using flex grid tie-ins.

Outlining and brainstorming with Shannon some fun ideas dealing with business intelligence and big data - business functions.

4/7/2020: 

Alan wound up taking this on and it is completed now! 2/17/21

see api bulletin 64.

Private demo between Jonathan Wells and some other clients and reps.

- How can we make this easier and more virtual handrails (keep people on course). Easy out of the box.

- We have built on top of some of these pieces over and over again.

- 2 main things - navigation (go and do) and reports (view and see)

- Trying to get rid of human error - as much as possible

- Anything that can be automated, let's do it.

- Renee really wants to make sure things are being dealt with and she is being heard.

- Who do you want to be as a company? Piecemeal or fully funned - also the size of your business.

- They run their business from the numbers side of things (mix of operations and accounting).

- There is some pain if you try to mix tons of different software packages.

- In a closed loop system, you get cause and effect type relationships.

- Human errors - being able to look at those numbers and making changes. If we could get rid of a number of those human errors that would help.

- Time to get things done - if I can enter it at the source, game on. If I have to go back later, no deal. That makes it really tough.

- There are a lot of tasks that are done outside of the adilas system. Currently, the client is using a number of spreadsheets, label printers, etc.

- Learning navigation

- Bouncing from page to page and end up being left on certain screens - doing things that take you full circle so you are back where you started from.

- Labels and auto printing

- Industry specific code vs a general or generic system

- The client wants to see a start to finish process. I login in, I then clock in/out, I start a cart, I add a customer, I do whatever...

- How can we help you - through settings and configuration - toggle on/off

- On invoice homepage and invoice reports. They would like to see time.

- Being the brains behind other peoples offerings.

- Using X-ray vision, can we see under the covers and see what is really making this thing work?

- Defining our mission and our purpose - that could be really huge.

Eric and I met up and used this time as a work session. We explored some options on the discount engine and got together a small exploratory plan. We then made some fixes, pushed up some code, and did other tech support and email stuff during our session. Kinda of a clean-up and touch base session.

Emails and prep work on a payroll settings project.

Chuck reported on a number of things that he is working on. He is working on setting up an ecommerce class towards the end of April. Working with Marisa on email campaigns, and other training courses. We also talked about direction on the presentation gallery and heading into the slides and page layout options. After that we went over tons of adilas ecommerce settings and internal training.

On a code review session with Alan. We made a number of code changes and did some testing for the new Hypur project. Hypur is a 3rd party solution and does custom banking and has a custom payment solution. Fun session. Back and forth code testing and making changes. I was coding and Alan was mentoring me.

Round 2 of the Promotion Codes. Round 1 was completed by Bryan Dayton on 4/8/20 (see element of time # 1626). It was mostly done for expo and needs some small upgrades to make it public ready for all users.

Brandon and Bryan met on 4/8/20 to talk about the round 2 options, specs, and requirements.

Brandon and Bryan met a couple other times and made the quote on 4/15/20. Brandon has the quote on his computer. Right around 50 hours.

Emails and projects. Checking on Hypur code and following a bug around.

Round 2 brainstorming for the promotion codes with Bryan. Uploaded a small doc with notes (posted on a different element of time inside of adilas.biz). Just getting started. After that, emails and clean-up from the day.

Emails and merging in new code for the Hypur project. Did it after hours. Testing what I could and grabbing screenshots of the new changes and pages.

Emails and other to do list stuff. Dustin, Eric, and Steve were on the meeting this morning. They were each touching base and getting instructions. Steve and I ended up talking about projects, recap of what is going on, and direction. Lots of things in motion right now.

As a side note, with the current craziness that is going on all around us (viruses, Covid-19, Corona virus, etc.), Steve was saying that there is a small wave of people becoming more independent and sub contractors vs traditional employee type models. He was talking to a banker/consultant and she was stating that there is an actual wave of people pursuing the independent type model. Interesting.

Four of us were on the meeting to go over projects. We had Cory, Eric, Steve, and I, all in together going over plans and options. Lots of discussions about business verticals, MVP (minimal viable products), themes/skins, and bulk back box type options. We also had numerous talks about picking up low hanging fruit, doing gap analysis (we are here and we want to be over there - what is the gap), building the core on rules, assignments, and settings. Lots of good direction.

Shannon and I met up and did some more brainstorming on business intelligence and big data business functions. See attached for more brainstorming. The goal is to create an outline that a rep or consultant could use for talking points about the adilas application. Chipping away at adding in functionality and backend documentation.

4/9/20: Requested by Danny per Steve.

Emails and recording notes.

Talking and working on the round 2 of the promotion codes. Uploaded file and made some new decisions. Small work session.

Continue where we left off conditioning pages for session scope to allow cascading of alias fields for customers (custom field settings for the add/edit customer fields). We had a pretty good work session and made a bunch of progress including a new method to look-up and create the dynamic field setting structure (way we hold the data and put it in the session scope for later use).

Tech support stuff. Jumped on a meeting with Wayne, Steve, and Dustin. Working on some new servers and testing new server setups with the other guys. We also talked about servers and automating things. Trying to iron out some of the kinks and manual processes. Working on different support tickets and small bug fixes.

4/10/2020: currently you can search by salesperson/budtender but the name doesn't pull into report or export. super_invoice_line_results.cfm

4 different spots are touched. One tricky thing is updating a column count. middle to low weight. Danny or Bryan could do. 3-4 hours.
In the future choose certain columns. 

We need to do some rework on the payables section of the site. Also, we need a super admin level for expense/receipt and some of the paid status and payables portions. This could be a special page that allowed for backend admin controls, manual paid switches, etc. See element of time id # 26 for more info (going way back).

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=22&id=26 - payables rework project ideas

4/17/2020: See quote. Old notes below. Sub settings will cure the restore to cart issues related to gram control.

4/10/2020: When you restore to a cart, the gram control isn't working.
I have many companies that want to assign subs to quotes, them included. 

Bryan and I worked on some ideas and requirements for the thresholds and inventory engine stuff. We want to take it way further than it is, but that takes time, money, and planning.

Part way through our meeting, Steve jumped on and showed us a bug on one of the servers. We flipped into emergency mode and made the changes. A file folder had been moved on the server and it was causing all kinds of errors. We got it fixed.

Calvin called and I gave him an update on where we are at and what projects are going on and being worked on. He reported on the web version of the adilas label builder and what not. Good catch-up session. We've both been super busy.

Emails, tech support, and small code fixes. Lots of little things.

Trying to help a client with some API socket connections. Other tech support stuff and checking some code.

Find and replace stuff, code review, etc.

Chatting with Steve and going over some date code stuff. We, both of us, keep getting pulled off the road and working on small little projects that turn into bigger projects. It's a hard balance between doing something yourself or turning it over and getting someone else to do it or help with it. Emails and text messages.

Project planning and coordination with Cory and Steve. On a big scale, we are seeing lots of interacting and connected settings starting to popup. That is both good and bad. Good in that people can set what they want. Bad in that they then have to be educated on what choices to make. Growing pains in the world of settings, configuration, and permissions.

- Talking about sub inventory and new package management settings and rules to play by. Auto open new packages, auto close 0 quantity packages, and other open/close type settings or rules.

- We have a client that needs really high numbers for invoices, invoice payments, invoice line items, PO's, and other places in the system. We talked about options to expand our current database tables or maybe go more along the lines of real in-line extensions and what that might do or handle. Imagine if we could flag a certain invoice that it has super high numbers. We could then use a custom table, such as custom_big_numerics, to hold the numbers in. We could set up the system to check for really big numbers and then run accordingly. Lots of talk about flagging and tagging records, and then rolling over to real in-line extensions to help handle the special cases. Think database extensions vs fixing the whole system to handle the random couple that exceed the norm. Some good ideas there.

- Along the lines of huge numbers. We may also want to include huge positive numbers, huge negative numbers, and huge numbers of decimals (details after the decimals).

- Quick update between Eric, Steve, and Brandon about some 3rd party solutions and their API socket access and traffic (server weight and traffic requests). Sometimes we get weird spikes in load and traffic. Some light talks about what some of the these 3rd party solutions are doing and/or requesting. We may need to get Wayne involved with this and see what requests are being pushed through (backend logging and reports).

- Database Admin stuff and helping us find slow or bigger queries and helping to prioritize the refining of those pieces. Making things smoother and smoother.

- Talks about custom code lists of corp id's and pulling that list into code as needed. Sharing those lists between developers and/or making it part of the database and being able to pull in data fed data. We also talked about data controlled lists and being able to assign certain 3rd party solutions to certain corporations. Almost a secret list of sorts dealing with who can play and who has access.

- Silly subject about data and how it gets abused by outside parties. The silly subject of "data rape" and getting access to data from parties that don't really need access to everything. Talking about 3rd parties who virtually rape (misuse or abuse) the data to get more info than they should. For example, once the invoice info window or door gets open (normal API sockets), we have seen that the 3rd party companies are going clear back in time to get all of the sales history. The name is probably wrong, but it is what was being said as part of the conversation. Sort of silly. Basically abuse and/or misusage of information and expectations of parties, vendors, and our clients or system users (corporations and companies).

- Talking about a new page to bring in a quick item or items. Industry-specific flow and what the different levels would be. For example: What is your business vertical, any sub selections, any state-specific requirements, etc.? We then show specific pages to help gather the information and the flow.

- Lots of other good talks about label printing, automating things, and industry-specific skins, flow, and options.

4/13/2020: Create a setting that warns people when they try to make a vendor inactive who has live inventory. 

Met with Bryan and went over some options on a custom report that he is working on. The code is dealing with inventory level thresholds or the inventory engine stuff.

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.

Working with Danny on some merge code stuff for his dynamic customer settings.

Brainstorming on the business function of business intelligence (BI) and what that means. See attached for some our brainstorming ideas. Still working on this section, but some good ideas are starting to formulate.

Some of the main topics of business intelligence are:

Making informed business decisions
Types of intel
Power is in the data
Conquering gaps and needs
Real-time reliability
Permissions and levels
Activity and history
Cloud based platform
Looking to the future

4/13/20: Per Steve=should be another setting to choose from to give more control to salesperson over how items enter cart.

4/14/20: https://data0.adilas.biz/top_secret/secure/check_search.cfm?fromDate=all&toDate=all&checkNum=all

when you go to check, all, can't use the link

Working on a large code merge and then checking individual files. Light tech support.

Per Steve to discuss data points in compare inventory page.

Join Zoom Meeting


https://zoom.us/j/997233164


Meeting ID: 997 233 164

On a Zoom session with Cory, Steve, Kelly, Sarah, and myself. The subject was aggregated P&L (profit & loss or income statement) reports. Lots of good and fun ideas floating around. This is a spot where we can really help businesses and gain more visibility in the business intelligence (BI) realm. Here are a few of the notes from the day.

- Log any changes made to older things (invoices, payments, line items, deposits, expenses, etc.). Once logged, show a report for both audit trail as well as what changed and who touched it. Even to the level of notifications and communication stuff.

- Lots of talk about the need for the ice-down dates and how that may play in.

- Getting into the business intelligence (BI) level with quick data, summaries, totals, and aggregates.

- We do great at transactional data - right now. We would love to move more into the aggregate type levels.

- Seeing the bigger picture.

- Using BI functions to help drive revenue for us and our clients. This is what our clients want. Quick and reliable access to counts, sums, averages, maxes, mins, and stats and reporting.

- Big need to be able export the data. We also talked about being able to import data, even from other financial or operational type software packages. Along these lines, we also talked about the need for API sockets to help both push and pull the data as needed.

- Some other names and phrases that deal with bigger or summarized systems. Things like enterprise, consolidated, multi-faceted, etc.

- Dashboards and being able to show and compile the aggregated data.

- Playing with the ideas of "Powered by adilas.biz" - Having adilas being under the covers, somewhat in the background, but built on our business platform.

- A super general BI enterprise solution. Maybe even a product that rides on top of the bigger platform.

- For fun... we built a small fake database to show where we were headed. Just playing around.

Merging and helping Bryan with his custom report for the thresholds that Josh built. This is a sub set of the inventory engine project. Eventually, we would like to replace the existing pieces with a more robust and location specific threshold system. Stepping stones along the way.

Talking about quotes, standing up for ourselves, piggyback options (somebody pays for one thing and the next person pays for the next and so on), and re-inventing ourselves and our style. Steve and I had a good 1.5 hour phone call going over a bunch of the pieces. Lots of options on the BI (business intelligence) side of the equation.

We may be able to offer the full solution at a price that is awesome and great. This would be the current and normal transactional data system. They could do everything and see everything. If they, the clients, want the enterprise edition, we would love to add a roll up aggregated business intelligence option that could be put over the top of the existing transactional system. This seems like a logical option and upgrade (value add-on).

We talked about the core product and then other layers or extras that are on top of or surround the core. Lots of exciting options that could be come up with and/or built to help with those other higher levels. Bulk tools, aggregated data, special dashboards, etc. If the clients need multiple systems, and those systems all need to be consolidated and/or aggregated as well, that's just another layer that we could roll things up into.

Instead of selling modules or small parts of the system. The main product would be the entire core (all of the pieces). You could then build on top of that and/or get the enterprise type packages. That seems like a better way to sell it vs splitting all of the core features up into smaller pieces. You basically need the whole core and then you add on after that. Great idea.

Some time was spent talking about making some offerings to parties and induvial to help with sales and offering commissions and birddog type fees. We want to get some people pushing on this and see who can sell what we have.

Our plan is to stick to the line in the sand mentality and it people complain, we simply ask them to contribute via ideas, feedback, seed money, or custom projects. If they don't want to do that, we'll just get to it when we can. That's how we have to play. We have been virtually beat up and down and we can't keep doing that. Our time and our product are of worth and value. We help a company by bringing value. 

Leadership, there are tons of different ways to play the game. Our style is currently, let's empower those who want to play and see where things go. Empower the people. Also, as we keep going, we are learning more and more how to focus and really try to do one thing at a time. That is really tough. Sow the seeds and then reap the harvest.

Another fun note is when Steve and I get together and we start talking, we generate excitement and energy. It is exciting to see of the dreams and ideas coming to pass and being implemented in the system. That is really fun. A portion of that energy is what gives us passion and really drives us.

Lastly, stick to it. That's what we keep doing and we're pretty good at that. Keep sticking to it!

Recording notes and checking emails. Wayne joined the morning meeting and we chatted about servers, load balancing, and load testing. He is working on gathering tons of stats and data about the servers and their usage. He showed me some of the new stats. Some of it was surprising and some of it was what we thought and/or expected. As part of this, we have to keep watching out for outside hack attempts and bad connections. This includes brute force and API socket attempts. All part of the game.

Chuck and I met and had a good little update meeting. I updated him on a few things and he reported in on the projects that he is working on. Good stuff. He reported on his slides for the presentation gallery project, ecommerce training, working with Marisa on marketing stuff, and the internal project for new look and feel on the corp-wide settings page.

We spent some time talking about filling in gaps and checking to see where we are vs where we want to be. The difference is our current goal and ongoing project. Fill in the gaps. We talked about taking care of known needs, coordinating with others, and taking care of our existing clients. Great meeting.

As a side note, we may end up offering some free training courses to help train the trainers and get the curriculum down better.

Alan joined the meeting but so did Wayne with an issue or bug that needed to be fixed. The meeting between Alan and I had to wait almost half an hour as we looked into some errors on the data 3 and data 8 servers. After awhile, we determined that the error was coming from bad customer data (special characters in key fields). It was causing a JSON parsing error (splitting things back up into smaller pieces for normal usage - parsing data).

After that, Alan and I touched base on a number of projects. He has finished two custom code projects and both of those are deployed live and being used. He is on a couple of other custom projects right now as well. Good progress.

For my update to Alan, we did a lap around the system and looked at banks, payables, payments not yet deposited, deposits, P&L (financials), and who owes us money (accounts receivable stuff). Making progress.

4/15/2020: expo needs to move from13.5 to 15.5

Custom_big_numerics (new table) New territory. How deep is it? 20 plus pages, new db, logic, flow

5/7/20: 33 remaining fields to be conditioned to be dynamic. 

4/15/20: Currently almost completed terms. Will continue to work on the others.  

4/15/20: This api error refers to getLookupValues

4/15/20: Need a developer like Alan to look at core folders and files with Molly on clients server to make sure all is up to date.

4/21/20: Quoted to Move all 27 Systems to new VPS environment and Upgrade see Quote 1798

One of my contacts from Utah State University contacted me and we met online over a video chat. They have some Adobe ColdFusion projects that may need some help and wanted to talk to me about developers and ways that I could point them in a good direction. Kinda a code/consulting visit.

After the consulting meeting, I ended up on a phone call with Russell talking about upcoming projects and direction. He is going to be joining us more here in the next couple of weeks to a month. He is currently full time at school (online school due the virus) and only doing a few hours for us. We are hoping to change that here in the next few weeks. He has done a great job. He is also helping to coordinate jobs with some of the other developers.

Talks and discussions about automating the printing of cart and invoice labels. Eric and I spent a good half an hour going over current flow, code, and options. He is looking to see what he can do to limit the number of clicks and make things more versatile and automated. That's the goal.

I spent the rest of the time doing emails, follow-ups, and recording notes.

New project with Danny. We went over a new dynamic customer input setting for the additional contacts that are available when adding a new customer/client. The new settings would allow us to show/hide up to 3 additional contacts and prep the forms with specific values.

After the meeting with Danny, I got a call from Steve. It's his day off, but he was checking in on some server issues, server loads, and discussions about moving clients around to newer servers (load balancing).

Round 2 of the promotion codes stuff. Bryan and I met for an hour and finished up the planning portion of the round 2 for promotion codes. The original release was mostly done for a single client and needs some re-work to make it ready for the general public. Lots of planning and recording info to prep for the new project. It will end up being a $5,000 for the second round. We put together a quote and updated the main project details.

Spent an hour recording notes from smaller post-it notes into the developer's notebook and elements of time. That helps because it makes them public and searchable for future reference. It is worth it.

There were 5 people on the call when I got in. Each of them asked some questions and then eventually bailed out to work on their own projects. Here are some things that I pulled out of there discussions.

- What is the real purpose there? Thinking on a per page level. If that is known, that can really set the tone for the project - aka a focus. Basically, being more clear on the objectives and then sticking to it. That really helps. Idea was presented by both Russell and Danny.

- Some marketing ideas from Danny about free software and then charge for other pieces and/or services. He was talking about a product out there for music lovers and how the sound mixing software was free but they had to pay for specific hardware. Lots of options.

- Eric was talking about being able to build business processes. I would love to take that to the next level. Think how cool it would be if we could setup an area where people could build a business process, name it, setup defaults, determine layouts, requirements, and flow. Then, once those pieces are set and in place (saved), we then could show and use those real settings. Imagine being able to setup your own data assembly line and then the system helps you keep and maintain those business processes. If you need to alter something, you could go back and just tweak some of the setup pieces. That would be so cool.

- Talking about auto printing from the web and using a queue of sorts and then doing the print jobs based off of a service that monitors that queue.

- Talking about custom code jobs. How are jobs coming in and being completed? We have lots of independents and what is the plan for the adilas shop (dev shop) and the projects being passed through? Along those lines, we need to take care of the house. The house being adilas. Often, some of the independents do the work, they get paid, they move on, but they suck tons of resources from adilas without paying for any of those usages. Time, talent, and money are all resources... we need to make sure we are managing and taking care of those pieces.

- Eric was talking about rough estimates and how he likes to bid a project. If needed, he sets up an estimate and then says he bills by the hour regardless. If things get deeper, he then lets the client know that it will be different then the original estimate. It flips it back on the clients and they get to say yea or nay. It's a way to somewhat protect yourself.

Steve and I worked through some questions that he had on some code. After that, we started talking about marketing ideas and small pieces of the sales plan (up and coming plans).

Proposal for all that want to sell adilas

- Old whole message - how do we sell the model that we have right now?
- So many people say - we can't sell it, it needs to be fixed
- What are we focusing on...

- Some salespersons need the wagon loaded for them - almost after the fact sales vs up front sales

- Side note, we are gaining control on the custom code stuff. We want to do the same thing for sales.

- If people want to play, game on. If not, we'll get the next one.

- It is what is... (meaning the system). We can build it out to your specs but that is by quote - pitch some of the other services.

- What do we tell to the salespeople that is available (our current offering)? Sell what we have. It has value.

- A good problem to have is - how many new clients we need to setup.

- McCorvey's is one of our poster child type accounts
- A stud who takes care of the whole thing
- Mel and Tish were the salespersons, but they didn't do any of the real setup

- Salespersons don't need to know too much... enough to play the game

- No contract - minimal risk

- $1,000 simple start-up - that could cover, setup, some light training, 1st month, and some custom code and/or data import

- Selling is telling - get the word out. Not everybody likes strawberry ice cream, but some people do.

- We have people wanting to help with setup, but they don't like to do cold sales.
- We keep trying to force these setup and consulting people to be salesperson but they aren't that person.

- We would like to get a full sales force... we could sell the opportunity to sell adilas to other salespersons... It is all about potential and realizing that potential.

- Sell the vision

- Pricing - we need a basic model with enough to cover the salesperson and the house

- What is produced on a sale... that we could share with those who are helping the process
- Bird dog fees - one time deal
- Monthly reoccurring - able to share that with the salesperson
- Commissions based on participation
- just talking about this... hourly vs commissions - hero to zero or zero to hero - leaning towards strictly commission based

- On sales and a sales force - full commission based doesn't cost us anything

- In real estate, they have to pay a broker fee to play the game (where are you hanging your hat) - basically, charging for the opportunity (taking care of the house) - We, adilas, have time and energy in this as well. - We almost want the persons to either fly and thrive or weed themselves out and move on.

- Pitch the opportunity to make reoccurring revenue - Sell it once and then reap and reap (harvest that effort).

- Bonuses, games, and other stuff

- We've got to have salespeople on our team but we can't force non salespersons to be that salesperson.
 
- There is an old sales opportunity flyer... Maybe look at that and revamp it and/or pull some pieces from there

Great little work session meeting. We started out and Shannon and I went over some of the new updates and happenings. It is amazing how quick things change in our world. After the update and chatting about new changes, we spent the rest of the time brainstorming on business intelligence (BI) and how that plays in. See attached for our brainstorming (you may have scroll way down the page).

- Shannon and I were talking and drawing small models of the power packed core (transactional data core - main part of the adilas.biz system) and then how we could add value add-on's going around it. Think of a small target with a couple different rings. The inter ring is the adilas core or the transactional data core. Then the rings around that would be the other add-on value rings.

- Here are some possible value add-on rings that could play into our model... once again, just brainstorming...
1. The adilas core and transactional data core
2. Industry specific skins, white label, or add-on's
3. Custom code, skins, API sockets, or 3rd party integrations
4. Business Intelligence (BI) dashboard and stats, graphs, and special reports
5. Enterprise level - unlimited options to interconnect multiple corporations - consolidated system

- See a need, fill a need - movie "Robots"

- Our landscape keeps unfolding right before us and even right underneath us - keep adapting

- Harvesting tons of prior work and efforts (some of our new brainstorming efforts - good stuff)

- Value add-on like a car, you need the basics (say the core) and then you may do other value add on's beyond that.

- Custom code and other interfaces are a part of the value added layers (core model with target like rings around the core)

- Industry specific layering, may be multiple levels deep, if needed.

12/23/2020: As of today, 5 and 8 are completed. The rest of the project is multiple projects and needs to be requoted if K wants to proceed.

11/9/20: Surfacing parent and sub inventory quantity(view only)one value: #8=Pulls off the parts homepage. $400 for this one.

11/6/2020: 8 hours to date:
10/28/20: #1-4 have been completed as of today. 

#5 will completed this week.

#6-9 need to be fleshed out.

9/28/2020:

top_secret/secure/global_parent_core_updates.cfm

1) item description: yes, easy

2) reference #- yes, easy

3) Bin #- yes, easy (this is an alias- called catalog page)

4) Barcode-yes, easy

5) Discounts- in a different spot- talking to a different table= different project.(not related to this project)

6)U of M- slightly complicated= deeper (wait)

7)category: hardest of all. wait on this

8)Qty- Surface parent and child inventory (view only)= deeper

9)Replace the categories piece with multi boxes instead of one= deeper. Database change

7/13/2020: Adding more items to be globally updated per client request for a quote: will need 2 hours per each. Kelly will pay- put on Balance Sheet

- Bin Number -ok
-Barcode-ok
-Discounts-ok

Qty: Surface the parent and child inventory to view only.

Replace the categories piece with single selection to multiple boxes.

5/11/20: Global Parent attributes and global sub attributes updates:

4/20/2020: Vendor was made visible by Steve over the weekend.

4/16/2020: I have found this functionality to be very useful, but it is difficult to understand what items need to be changed quickly without research. It would increase the ability to clean up systems and implement E-Commerce if we added a column for the Vendor Name and Qty field. I also think the ability to update the Bin # and Reference Field would also be useful to quickly change reporting from item exports and invoice line item exports. 

4/16/2020: An example of the CSV(s) are attached. I am not sure if the customer report includes any category filters, but it is my understanding that current code only includes one specific category called "concentrate". 

4/16/2020: Spoke with Alan about various bugs (also from meeting with Kelly, Sarah and Steve on 4/14) and he will continue to plug away on them on Fridays- this is his designated bug day. He will assign his time to this project #.

Some of the issues at hand:

-Duplicate rfids
- Issues with compare inventory page- some issue that seems to be related to the last modified date.
-Something on 3/20/20 maybe was weird?
-Dates don't always sort- maybe not a bug but need to change coding of date?

4/16/2020: Currently you have to go into metrc and finalize sales. This would allow user to check box to finalize in adilas. It would need to have a couple of pages in adilas for a report and to capture who and when (history). Not sure if we have an api call in metrc.

4/16/2020: Currently user needs to edit in adilas and then go into metrc. This would make it so once you have the metrc id for the transaction, you can edit from within adilas only.

new api call to metrc. Tell it to update in metrc.

4/16/2020: Need to be able to sort parent tags on e-commerce as you want. Currently they are in alphabetical order only.

Per Brandon 5/11/20: All code exists. Just need to make a small code change. Sort by 100 currently. Surface this.

Project stuff between Cory, Steve, and Brandon. New quotes, updates on current projects, and assigning developers to new and upcoming projects. As a note, Cory is doing awesome. She is filling the wagon, doing follow-up, communication stuff, news and updates, and also saying "no" when needed. Even to Steve and I. We need that.

Eric joined our meeting and had a couple of deeper server based questions. We talked about request timeouts, server side loops, API socket calls and checking status codes, multiple treads and threading, dishing off things to a task queue or sub queue of sorts, 3rd party error logs, and syncing data between servers. Pretty deep stuff.

After Eric left, Steve and I chatted briefly about some more marketing ideas. I pitched the core model with value added rings. Super light but a good start. Without all of the details, here are the quick levels:

1. Core
2. Industry Specific
3. Custom
4. BI - Business Intelligence Dashboars
5. Enterprise level(s)

We also briefly talked about how the corp size, number of transactions (invoices, users, and locations), data storage and usage (database size, photos, scans, uploaded files, and media/content), and even API socket transactions (3rd party stuff or other API socket usages) may all need to be part of the pricing and billing. We are thinking of setting up levels and then using that to help us to provide pricing options. Making progress.

Finished up a couple of small projects that have been hanging around. I got some new JavaScript code from Jon Hudson for a slight change on the build sales deposit page. The new code checks to see if the existing pieces are in place before just using them. This helps if any of the payments have been sub filtered before being added into the deposit.

Kelly sent me an email about a date issue on ecommerce quotes and invoices. I went in and fixed the dates to look-up and use the timezone offset. That helps stamp the history date/times according to the user that is setup to do the outside web traffic or ecommerce actions. Great catch by Kelly.

All new files have been uploaded to all servers.

Finished up by recoding some notes from the day. See earlier entries.

This was accomplished with message marketing modal.

4/17/2020: You can add a note in customer logs and choose to have it display for the customer when they log in. Needs to be conditioned to pop up somewhere visible- currently they would need to go to view their statement or information.

Looking over code and making tweaks on the duplicate expense/receipt project. Small rewrite of sorts. Lots of checking line by line.

On the morning meeting with Steve and Wayne. There was one of the servers that was having some issues. Wayne got it all fixed up. He is the server master. Once the hot topic was passed, we moved on to other server questions and plans. Wayne showed us tons of stats, monitors, and other things that he is doing to help watch the servers. Pretty impressive. We also talked about slow queries, how to standardize things, and setting up new VPS environments. We would like to move some of our bigger clients out of the shared environments and into their own VPS type environments. We will be starting this fairly soon.

Wayne gave Steve and I some directions and to do list stuff. We will start working on those smaller pieces to prep things for Wayne.

Cory joined us and we went over her project list and questions that she had. We did some new quotes, talked about existing projects, and gave reports where we could on what is happening. Good work session.

The earlier meeting before, with cory and Steve, sort of naturally rolled into a discussion on sales and marketing. We talked about our existing models and where we are hoping to go and get to. Good stuff. As part of the conversation, Steve had me show Cory some of the small drawings, concepts, and notes from some of our meetings last week. We are gaining ground and making progress.

Click here to see some notes from 4/16/20 (last Thursday) - lots of good sales ideas.

4/20/2020: Quote attached. Will change timing of transitional invoice from day to minute. 

4/20/2020: Adding on account as payment option for e-commerce transitional invoice. You can place items on hold without making a payment.

The meeting was originally going to be going over a deep look into the automated P&L (profit and loss or income statement) financial documents and reports. We switched it out and ended up with a group meeting on a different topic, set by both Kelly and Sarah. Good meeting. The main topics were: proposal for performance improvements, scalability, revenue increase, legacy and enterprise planning. Here are a few notes and topics covered:

- Upgrades and helping our clients get the service levels that they want. This could be dedicated boxes, clusters, VPS environments, clear out to full on enterprise type solutions. Each upgrade needs to come with a cost. We just can't do this for free as our base level product.

- Charging the correct amount for certain service levels

- What ways do we communicate and how are those channels working? Email, text, phone, GoToMeeting, Zoom, elements of time, pass along from our clients, etc.?

- Kelly and Sarah would like to get a list of who does what and who is in charge of what aspect (task or position).

- Both Kelly and Sarah were filling the role of business consultants in this meeting. Great questions and trying to keep the subject on target or on task.

- They, both Kelly and Sarah, are somewhat doing an analysis  and seeing where they can help and how best to structure things. I was impressed, they seem like they want to take an active roll and help the whole business become more fluid and efficient.

- Top priorities from Steve - cash flow, servers, customer care, and new UI (user interface).

- Light talks about sales and marketing

- Top priorities from Brandon - servers, current projects, maintenance, R&D, and planning for the future - including new look and feel for the whole system

- Cory is currently doing a great job pushing forward the custom and internal projects - project coordinator

- Charging for storage, processing, and hosting of the software package

- Software is a constant process of refining and building

- What does our team look like?

- What are the future goals? Short term, medium, and long range goals?

- Time management and where we are going

- Concept of adilas.biz as a trust

- Getting business consulting for adilas done by adilas power users

- Cofounders and a small village

Fixing a JavaScript issue with Bryan. He wanted a special series of checkboxes and the ability to check all and/or only select specific values. The page had to remember the selection and affect the underlying database queries. He was really close, we just had to tweak a few things and run some tests. We merged in the code and pushed it up to all servers.

Recording note, making some small changes, and light development work on the adilas community funded projects page. It has gone through a number of hands and lost some of its functionality. Light rework.

Danny, Dustin, Steve, and Eric all checking in. Danny is working on some customer settings for adding new additional contacts and being able to configure and preset options. Dustin is working on sub queue settings and how that relates to business flow and logic based on the queue choice (pick-up, drive-through, delivery, in-store, online orders, etc.). Basically using existing features and flagging and tagging invoices and quotes (part of an internal process).

Steve and I spent some time talking about aggregated system and what they might look like. We spent a good half an hour here and were drawing and talking pros and cons. We are still exploring some of these ideas.

Eric popped in and had some questions about auto printing labels, settings, and looking for code samples and direction. He is doing great and helping with some of the growing custom needs.

Tim with Herbo met with Steve, Cory, and I to go over his vision of an fully automated enterprise type system. We met and talked, drew pictures, took notes, and chatted about scenarios, requirements, and flow of goods and services as compared with the flow of money, funds, and financials. Lots of top down controls and bottom up mirrors, mapping, and roll call type situations.

Here are some other small notes:

- Holding companies, nesting corporations and locations going down, trickle down effect, rolling up effect.

- Id's becoming standardized through mappings. Helping to automate parts and processes.

- Attaching additional intel, info, or instructions to certain key transactions that start and/or process other steps of the transaction. For example: A new PO is brought in, a sub routine (recipe/build or assembly) is done on the items and then automatically distributed out to sub companies with instructions on how to pay either the holding company or direct to the vendor. All of this done through a single screen where the product is brought in through the master holding company and then distributed to the sub or affiliate corporations. Think of it as a process that gets started and the rest of the process is defined and setup by the info added to the starting piece in that process.

- How the holding company (higher level company or summary or aggregated company) could process things, cascade info down, get values passed back up, and controlling flow of monies, accounts receivables, accounts payables, bank balances, etc. Full control top down or bottom up. Plus, be able to stack the model as needed. It got pretty deep.

- We went over a number of scenarios and talked through flow and possible processes. Just talking and chatting at this point. Build on what we have. We already have PO's tied to vendors, tied to items, tied to locations... what if we could also tell it to distribute those items to other companies and those transactions could be run based on info in the first corporation. Instructions on how to account for things, how to pay for things, or how to differ payments or liabilities. Pretty flexible but with clear instruction on how the transaction or family of transactions needs to work. I like the word family transactions... multiple, with varied yet specific outcomes. Kinda fun.

See attached for one of the drawings that we were doing and talking about.

Brainstorming with Shannon about business intelligence (BI) and how that business function is achieved by adilas and adilas users. Fun brainstorming session. BI is so much more than just numbers and data. It could be instructions, warnings, recommendations, trends, logic, processes, automation, stability, cause and effect relationships, and it keeps going.

See attached for some of our brainstorming. You may have to search for business intel to find the entries.

4/21/2020: Per Bryan: I ran a test and the weight transferred.  The Bin Number on the parent does not.  It would not take much to plug it in - maybe 45 min-1 hr with testing and re-pushing live.

Second piece of this would be bringing in all of the other parent info related to e-commerce- Check corp wide settings or category settings: if receiving corp is hide on web, then don't bring up those fields. If it says show on web, then add all of that information to the parent.

We had our second meeting with Kelly and Sarah. Very interesting. They, both of them, are somewhat acting as business consultants for us here at adilas. They are somewhat part of adilas and have been for years, yet they are currently taking our meetings and trying to help us plan and get better and do better. Very interesting.

Here are a few of the topics discussed and talked about today.

- The diversity of the adilas organism. It is alive and growing... ever changing.

- Who is caring for the adilas.biz website. That is a primary communication and sales channel. Who is doing what and what assignments and/or delegations have been made there?

- Lots of talks about white labels and how that could potentially play into the mix. Custom skins, industry specific environments, regemented processes and procedures, defaults, settings, permissions, flow, data entry, updates, notifications... and the list goes on and on. The summary would be specific skins, specific functionality, or industry standards per business vertical.

- What would a 100% white label look like - We envision that we manage and take care of the core elements and pieces. The white label company would handle all of the rest of the pieces. Which include billing, tech support, setup, sales, training, etc. Adilas would just be in the background as a business platform or business system engine.

- Wouldn't it be cool if a real white label also offered live on-site training. Say a company uses the software package. They could charge for people to come and learn and do on-site training (at the white label's site) and show the in/outs of the software package and/or the industry specific skins, functions, processes, or features. That would be super cool.

- Question - how do we decide to switch or specialize in any one industry? Answer - So far, it has just been coincidence and expressed interest of outside parties. No real studies have been conducted. Floating with our ears and eyes open.

- Focusing on core development.

- As a fun side note, part of the meeting was going over some graphics and ideas of where we would like to take it. Just concepts and ideas and drawings (lots of analogies).

Started out by recording some notes and catching up with the day. Sometimes things happen so fast, you only have time to jot down quick little scribbles that then you translate into actual notes. Lots of moving pieces.

The rest of the session was spent on working on other or older projects. Big older merge, duplicate expenses, email to chuck, group by question, default users per system, etc.

Wayne joined the meeting with some updates on the SWC server. We are prepping things for a migration. He is going to have me do a folder to folder comparison to make sure we have all of the latest and greatest files. This was at their request as a custom job or server file audit.

Eric also joined and touched base. He reported on some projects and meetings he was part of. Today he will be looking into some POS label printing and older code from another developer, trying to finish up an older project. He is also working with a 3rd party solution that does customer loyalty points.

Logged into the SWC server and started a folder to folder comparison. Also checked some key users and corporation assignments.

Chuck and I met and touched base on a number of different projects. I gave him a small review of some of the new direction with the core and value add-on's to that base core. We went over the different outer rings and some of those ideas. After that, we jumped into some of his projects. We talked about the corp-wide settings page, the new slides for the presentation gallery. We spent some time there talking and going over ideas and concepts. Looking good.

After going over his current projects we spent some time looking for a code bug in a page that he is working on... pretty hidden bug, we couldn't find it with our first initial glance. We then closed the meeting just chatting about general things that are happening and going on - life stuff. Good meeting.

https://xd.adobe.com/view/e01cc5b5-caa2-4b84-4727-58b1b2ea764e-962d/ - current slides in the Adobe XD layout for the presentation gallery (still under construction)

Reached out to Alan via text. He was having some technical difficulties. No meeting took place. Just working on other to do list items.

Added new permissions for Cory to be able to add/edit help files (super high admin permissions). Light training and explanation. Pretty straight forward. We finished early so we went right in to the next thing and looked up some sales tax questions. We ended up doing some research on the 3rd party error logs and were able to get some specific dates and times for the client on when they changed their tax settings. Cory will take that info back to the client and explain what we found. User error vs code error.

General stuff. Emails, checking code on servers, and light tech support stuff. 

Met up with Eric to go over some new print settings for shopping cart labels. We determined that we would somewhat cherry pick some of the older code and then build from there. Eric seems to have a good idea and direction that he thinks will work.

Bryan and I looked over three different projects. Two of them were pretty much done other than small details. The last one we took a little bit longer on and had to break it down a little bit further. We did some drawings, samples, and talked about needs and requirements. Minor, but we will have to back some code out on the last project. The new code is not quite what we want. When we ended, he had some good direction on what needs to be done. Good stuff.

Emails, tech support, recording notes, and back looking at server files.