There were 5 people on the morning meeting when I joined. Steve was helping them and they were lightly in a line. Each one had some small reports and/or questions. Steve helped some of them and others had questions for me. We had Danny, Jon (new developer), Alan, and Eric online with us. Steve helped Danny, We then helped Jon with some new pages and getting started on some code changes. After that, we worked with Eric and then Alan.

After each of the other guys had their questions answered, Steve and I worked together on some logic on the cross corp (aggregate or enterprise system) mappings that he is working on.

Eric jumped back on and we merged in some new code. We then made a super small tweak and ran some tests. Pretty straight forward.

Steve and I used the last half an hour to get back on his cross corp or aggregate/enterprise mapping project. He is making great progress there.

Cory joined the meeting and we switched gears to talking about budgets, projects, timelines, quotes, and other small details about upcoming and existing projects. As a note, we are seeing a general trend going towards deeper cost tracking, job costing, special timeclocks, sub payroll options, bulk payroll tools, and summaries and aggregation of data. Lots of bulk or aggregated (summed up) requests.

3/2/20: When you go to add lines to a deposit, if you use the search field to filter data, and then you try to check all for the boxes, it won't. Also, whatever boxes you do check, it doesn't total the amount in the purple total box below.

Great meeting with both Eric and Steve. All three of us spent two hours going over a number of key points. Lots of drawings, running scenarios through financial flow calculators, and talking about options and needs.

- Math and logic for loyalty points
- Talks about costs of goods and when does this happen? Dealing with loyalty points?
- Some accountants are doing a bulk entry at the end of the year against cost of goods sold - we'd like to make ours more real-time
- Deferred revenue - lots of talks here - all kinds of deferred topics, deferred revenue, deferred COGS, deferred expenses, deferred liabilities, etc.
- New tax law changes
- Estimated redemption rates
- Things keep changing – laws, standards, needs
- We still offer user-maintained balance sheet item options
- Changing point redemption rates
- The value of a point? 
- We stamp points as is... (estimated value) – the value is determined when you want to redeem them
- Simple vs complex scenarios
- Booked value is at the current value level, if changed... what would that require? History and a physical entry that shows the value change
- If a change is made, we may need to create a dynamic entry to the transactions to show the change
- You don't want your values and actual cash values moving around
- We had some talks about not allowing manual changes
- If manual changes happen, what else do we need to clean-up?
- Cash vs accrual accounting – most companies really should be on the accrual accounting side
- So many companies track things on the side and then try to bring in and marry those things in the background. Super independent and separated systems and then trying to bring them back together.
- To overcome some of these separated systems and processes, many companies do lots of spreadsheets, sub accounts, and even paper and pencil.
- On balance sheet items, we would like a forth show amount option that ties out to the special accounts and the sub transactions.
- Lots of talks about ALE (assets, liabilities, and equity) and even allowing for information only or showing some phantom accounts - items play in but may not really show in the math or numbers - kinda like an information only account or a phantom account.
- There were some talks about adding in options to set a BSI to active (show), inactive (hide), or even phantom (show/info only).
- ACV – actual cash value
- Standalone declarations - these are things that happen that need to be recorded. The reason for the term standalone declaration deals with no background numbers or data. You are just stating a change or adjustment needs to be declared. There is more information in the developer's notebook on standalone declarations.
- Showing some greyed out fields and values -  smoke and mirrors
- Lots of talks about outside watchers, feeders, and triggers. Good stuff.

One of the other major topics was the law of deferring to something else that has more details. That could be a sub account, a one-to-many relationship with details, payments, line items, sub accounts, transactions, or other things that have sub dates, types, groupings, values, calculations, etc. Often, we defer to the item that has the best information and/or the best vantage point. That is part of what we are doing.

Reviewing code and making a few changes with Danny. He is super close. We should get it in the next push. While he was fixing a few things, I was recording notes from the day.

Working with Bryan on a couple of projects. One was dealing with exports of sub inventory and getting the sub price correct on the export. The other was going over the existing promotion (promo) code stuff for a client. It still needs a little bit of loving before we can launch it. Getting closer.

Steve and I were on the morning meeting together. We did our own stuff and chatted about a couple of ideas and options.

- We have a MVP (minimal viable product) as a full system. That included the 12 main players and 12 basic business functions. Our MVP is a fully connected system.

- Quantity of scale

- Selling this year's model - AKA the 2020 model of adilas

- We also talked quite a bit about the need for training and even specialized training for companies

Alan did a team training meeting for us today. The main subject was moving queries from an SQL editor (dedicated database tool) out to the web and interacting with Adobe ColdFusion. We do tons of this inside of adilas. This training event was more geared toward some of the benefits of using cfscript and the QueryExecute function. It got pretty deep and dynamic towards the end of the training.

See attached for the video recording.

Working and brainstorming with Shannon. We are currently working on the breakdown of the accounting business function and how that gets divided up and distributed. The main outline that we are working on is for the presentation gallery project. Our current spot is working on the how and why accounting fits into the puzzle. Kinda fun. See attached to see where we are at. You may have to scroll down quite a bit to get to where we are working.

As a side note, we see a need or a want, then we slowly keep taking steps to get us closer to that goal. Keep taking the next right little step or go in that direction. Shannon and I were talking about how the Disney/Pixar movie - "Frozen II" uses the same saying "Make the next right choice". Good stuff.

Recording notes and reviewing things.

Met with Josh and he had some questions about how to assign bulk custom PDF labels from the shopping cart. We went over the document management section and got him all setup so that he could deal with some of his questions. Mostly just looking for direction vs full on answers. Anyways, we got him going.

On the meeting with Cory, Jason, and Zack (clients). Talking about sub locations and sub phases (virtual steps in a process). Interesting conversations. We were going through flowcharts, questions, processes, procedures, ect. Line by line and talking through things. Also lots of talks about mini conversion and other future projects.

Got an email from Drea in tech support. She was having an issue with an inventory update not working. We got on a quick meeting and we ended up looking into it and changing some data. Somehow one transaction on a sub package was assigned to the wrong sub (package). We fixed it and all went well after that.

Worked with Bryan and got a few files merged into the master code branch. They were dealing with the first (scratch) round for sales promotion codes and ecommerce stuff. We pushed some of the new files up to all servers. Everything went pretty well, except for one client had an issue on data 4. In order to fix it, I just uploaded the new files again on that server and it seemed to fix things. Not sure what the issue was.

I met up with Shawn over the GoToMeeting channel. I prepped some federal withholdings from an email (data) that he sent me. I then sent it back over to him in a formatted view.

Bryan and I jumped on the morning meeting. We talked about sub inventory and how to get back to the original sub or package. Currently, for one of his reports, he is pulling in all of the transactions. He needed to be able to get back to the original package in order to provide some details. Once we talked about it, he will go in and make the change. Just needed some light direction.

Other to do list stuff. Cascading around new payroll changes and new state and federal withholdings.

Weekly meeting with Brandon

Both Alan and Chuck were on the meeting. We covered a number of topics today. Just as a reminder, here is what I had in my notes: Talked about getting some funding through grants, direction on the internal shopping cart, color pickers, project management and specs for WanderWays (Chuck and Alan doing documentation), item/product management page, discount settings, meter read items, keeping running tabs or running totals on invoices (long stay invoices and options), things on account and/or multiple payments, online bill pay, multi invoice statements, icon pickers, site builder pages, sites and sub locations, bulk edit tools, handling work orders, dealing with cash drawers, hardware/software requirements, and permissions for things like refunds. Busy meeting but some great topics. Wonderful report.

See attached for a number of screenshots.

Alan was on the earlier meeting with Chuck and I. After that meeting, we touched base quickly and talked about a few projects. Our goal is to help get a few of the close ones over the finish line.

Our meeting ended early so I started working on the new 2020 state and federal withholdings. I did some testing and pushed up files to all servers. Shawn and I have been working on new withholdings for a few days now. Trying to get everything up and online.

3/9/20: Steve recommends a scratch report to start ($1,000) in one corp ie pharmacy 1. Then AFN would need to log into each corp and pull their scratch report. They could export to excel and get the numbers they are needing. This report cost covers bulleted items #1-5. # 6 (affiliate id associated with the transaction will require more work and another $500 to determine where this is coming from and how to pull it into the report).

Once this has been created and is pulling correctly the second phase would be automating a report with all of this aggregated data. Not sure on cost of this as it would encompass an api as data needs to travel from different servers, corps. 

3/4/20: The purpose of this Scope of Work (SOW) is to have a custom dashboard with a custom report created in Adilas Account No. 870, AFN, Inc. similar to the dashboard and report that were created for Compliance reporting.

Background: AFN Inc. has contracted with pharmacies across the U.S. that are selling products offered by CBD North America. The pharmacies are members of the CBD North America referral network. The referral network enables the pharmacy to participate in the revenue sharing program between CBD North America and AFN, Inc.

Remedy: AFN, Inc. requires a custom dashboard on Account No. 870 that would show the following transaction information:

● $ amount,
● date,
● time,
● customer name,
● email address, and
● affiliate id associated with the transaction

The report that is available through the custom dashboard should have fields for entering a Start Date and End Date for the report. This report will be run through Adilas Account No. 870 with User Permissions to do so. This would be for a manual report that would be run based on User Permissions in the Adilas account. As pharmacies are added to the network, there would need to be a mechanism to add the Adilas account number to the report. Ideally, the report would be run automatically at 11:59 p.m. PST every day, it would include all the stores associated with the CBD North America referral network, and be sent to a designated person who is responsible for the distribution of the revenue.

If the automation of the report delivery would delay this project, having the fields to manually enter the report Start and End Dates will work as long as all the accounts can be added to the report as more pharmacies are added.

9/11/2020:Documentation

 getSubQueueDetails

6/30/2020: Moving ahead with this project. Starting with $500 and will most likely go up to $900, then $100/hour after that. 

List of queues, view queue, add to the queue= 3 sockets, possibly more.

3/10/20: 5hrs

3/3/20: Molly really wants to help make adilas e-commerce better. Using word press in the meantime to connect to adilas through api.

3/3/20: Molly willing to fund these api connections.

Molly needs in order to connect to wordpress.

3/4/20: Add auto print for new quotes or invoices:

Get a hold of Calvin to build something we could all use to do this. Has built for another client. Would like to make it core.

Add a noise when a quote is added to fulfillment homepage: This would be a setting. Brand new= red? Not sure how to do noise. Browser has control. 

Cory booked me some time so that I could work on this project. That was very nice. I got in a good hour and a half on it today. I'm working on passing along both a part number status as well as a QTI (transitional) invoice status. It is going good, just passing things from page to page.

Worked with Bryan on a couple of projects. We had some discussions about custom vs core development. We ended up pushing up some new code after a light clean-up. After the meeting, I recorded notes, did emails and other follow-up stuff.

On the meeting with Steve and Danny. Going over small items, projects, and new changes. Lots of moving pieces. Steve was showing me a shopping cart demo done by Spencer (outside developer) and how cool it was.

http://spencergarner.com/Applications/Adilas/Main_GUI.html
- demo page for the short and sweet cart

Steve was also showing me some of his cross-corp (enterprise level) vendor mapping project. It is looking good. We talked about a few tweaks, but making progress.

After Steve left, Wayne joined the meeting. We logged into some of the remote VPS servers and made a few changes. He also helped me with my local box, as it was running slow. While rebooting my local machine, I called and talked with my dad. He has done some grant writing in the past. I briefly talked to him and asked him if he would be willing to help me and play that game again. He said yes and we'll set something up. Fun stuff.

Working with Shannon and brainstorming and going over features and benefits of using the adilas accounting functions as part of the system. See attached for the full presentation outline document that we are working on. Our eventual goal is to get all 12 business players defined, all 12 business functions defined, and to also organize and present the 12 business concepts that we are built on.

The goal is to complete what we call the adilas formula: Results - Mix(Functions, Players, Concepts)

See attached for an older PDF flyer that lists out the pieces. The new outline will take things further and really get into more of a sales and education tool and a presentation gallery of sorts.

https://data0.adilas.biz/adilas_formula.pdf - web link to the adilas formula flyer

Shari and I got on the GoToMeeting session and had a brief chat about 2020 federal withholdings and new W-4 changes. We just launched some code the other day and need to circle back around and make sure all is well. There seems to be a problem with one of the withholding calculations.

Danny and I were working on a multi date report and figuring out final piece for totals on percent of profit. Lots of variables and lots of loops.

Bryan Dayton joined the meeting for a little bit. He had some questions and we got him going while Danny was copying and pasting code. Bryan's code was dealing with different tasks and if statements.

Russell (3rd party developer for a private VPS server) joined the meeting and had some database and inventory tracking questions. We went over a few things and got him going in the correct direction.

Steve and I were talking about our day and some of the things that are going on. We talked a lot about being able to open up the development environment to outside developers and hopefully being able to seek help there. We talked about the concept of a business platform and building and/or extending functionality off of that platform. We talked about play at the wall - API sockets and 3rd party development. We also the talents within our own internal team and praises for the guys and gals who are helping us. As we move forward, we are hoping to help outside developers use our API sockets and business platform to create their own business logic and tools.

From Steve - The ABC's backwards - C = Conceive, B = Believe, and A = Achieve - kinda fun. I think he heard that in business school or something.

Going over a plan with Shawn for some new federal W-4 fields and changes. We made a plan and decided to call it a night and hit in the morning on Saturday.

Emails and tech support

Meetings with Bowling Pro Shop owners and update to GUI and functionality

Working with Shawn on new 2020 payroll changes and new fields from the W-4 form that need to play in. Big changes this year with federal calculations. Shawn and I were on the GoToMeeting session almost all day. We were on and off from 8 am to 5 pm. I'm only going to claim an active total of 4 hours, but it was an all day deal. We were pushing code back and forth on a branch. I would do something, he would pull it and add to it, and then vice versa.

Updating all servers for day light savings. Logging in and checking all of the time zone offsets.

Meeting with Shawn to figure out where we are at regarding new 2020 federal payroll calculations. We spent an hour on the GoToMeeting session. Towards the end, we scratched out a plan and Shawn pushed up code for me to work on and clean-up.

Steve and Eric were on the morning meeting today. Lots of talks about 3rd party solutions and some pros and cons there. One, they help bring in revenue and traffic. On the other hand, we've gotten some black eyes from allowing them to say that they integrate with us (especially if it is only half baked). I can't really control that in some ways. Also, we've been beat up by promises made to our clients that we have no knowledge of. All of those things have beaten us up a bit.

Part of us wants to work on our own stuff and the other part of us really wants to help serve these other outside parties. They do bring a piece of the puzzle.

Cory, Steve, and Brandon did a little bit over an hour on working through projects and trying to figure out budgets, priorities, and project details. We talked quite a bit about how to move a project from the general pool over to the project queue. The main thing that moves a project is funding. That's a big key component.

Towards the end, Eric popped in again and had some questions. We also talked about some funding options and what not.

3/9/20: I was wondering if you guys will ever have autofill W2's (red copy) and W3's?  Same with the 1096? I know I ask about this every year.  It's just that it is so time consuming and something that should take 1 hour takes 4.  If not, what do other large companies do that use your system for payroll and tax reporting?

Just some quick notes... transferring from a post-it note to the developer's notebook.

- Get somebody for all of my (your) current projects.

- Prep and pass things around.

- Keep it going... that's how you get things done.

- A few projects that still need some loving... add Stripe and tweak the PayPal stuff - more merchant processing options

- Build out the stats and features report - part of the presentation gallery project.

Meeting with Steve and Jonathan from Epic Enterprises (business consulting). We changed gears today and dealt with some very practical things, ideas, and decisions. We went over financials, numbers, and talked about sales.

One of the exercises that Jonathan had us do was called "napkin numbers" - this is where you scribble down some basic numbers (pretend it is on a napkin or something small and throwaway) and then you try to quickly fix or right the problems. Another thing that he had us do was pretend that we had just purchased the company, as if we were the new owners. What would be the next couple of steps that we would want to do or have happen? Fun little exercises.

We talked about times and seasons and being able to control ratios of spending, funding, R & D (research and development), and building for the future. We also talked about priorities and laying out expectations and requirements.

Brandon does have a small napkin budget that they worked on. It won't be uploaded for privacy stuff, but file name has the name napkin in it on his local hard drive. Good meeting and we are making progress. Our next meeting is going to be starting into sales and making a sales plan.

On a quick meeting with Bryan. We talked about some order of operation type things and ways to track your steps and flow through multiple linked pages and redirects. Mostly code/debugging strategy stuff.

Emails, tech support, and general to do list stuff.

We started out the morning meeting with just Steve and I this morning. We were talking about moving our focus to custom code and working through projects that way. We talked about getting some funding for the house (meaning helping adilas fund the external and internal development) and getting everybody headed in the same direction. It comes back to some leadership principles and organizational structure stuff. Very interesting.

Around 9:30 am, Eric popped in and we talked some strategy and direction. So many moving pieces. It is somewhat hard to manage all of it. We made some decisions and talked about some options.

Some of the talks with Eric were about balance sheet ideas and concepts. We are working with some off balance sheet liability account stuff. This is also known as phantom accounts or non ALE (assets, liabilities, and equity) accounts. For the record, some times it may also be called off sheet balance sheet item(s).

As a side note, some times we learn so much from some of our strongest and/or biggest critics. That is very interesting. They keep pushing the ball down the road. In a way, they are one of the primary driving forces in the battle to overcome trouble and problems.

Dustin and I got on a session. He was checking in to watch some developer training. We ended up doing an hour long session on forecasting and playing with numbers and what not. Lots of sales stuff. I showed him our napkin budget and some other docs and numbers. We had a great time and talked about direction and options. Some of the topic that we talked about were ratios and what percentage or ratio was internal development and what needs to be external or custom code work. We also talked about moving projects from the main or general pool over to the project queue. Lots of discussion about picking up the service pieces that adilas automatically creates. We then ended with some budgeting and forecasting. Just playing around. Fun meeting.

Shannon joined right as I was ending with Dustin and she heard the end of our conversation. Dustin was really excited to get in there and play with some of the sales forecasting stuff that we had pulled up. So, Shannon and I's meeting started out there. We went over a bunch of the same things and even advanced the ball further. I was having a ton of fun drawing, explaining, looking up real numbers, doing calculations, and playing with the forecasting model. Tons of fun. Here are a few of the new topics that we also talked about as the meeting progresses.

- There is a golden spot where the current independent reps, consultants, and independent developers are located. Adilas is sort of a one-off placed to the side. We are seeing a need to move the main adilas company more into where the current independents are dwelling and putting up shop. This isn't bad and there is tons of room, we just need to be more connected to our clients.

- The more services we offer and provide, the sticker (in a good way) our clients become. Basically, we help and support them with their other service based needs such as consulting, training, setup, data entry, imports, exports, design work, custom code, etc.

- We are going to be actively moving the model closer together

- Pain can be a great motivator for change. If adilas has pain, we will work and build something to help elevate that pain level. Other companies do similar things. Pain is a great mover of change.

- Shannon and I looked a lot at versions and feature and how that has played out over time. Fun to look back and also cascade that same model going forward.

- From Shannon -  "As creative of a solution as adilas is, I imagine that the sales solution may need to be just as creative."

- All of our roots and origin are based off of needs and building based off of those needs, ideas, and solutions.

See attached for a funny scan of a post-it note. I was drawing some of the departments and sub sections of the adilas business model. Really rough, but kinda fun.

We have the api- we need to add it to their system. We haven't connected anyone in NY yet. Each state has their own idiosyncrasies we don't even know about until we do it.

Corp ID in NY is #760

$1500 minimum then $100/hr afterwards.

4/2/20: Was paid by Molly and completed.

3/10/20: $100/hour. 

Add the 40+ error codes that are not in the system.

Working with both Cory and Steve to talk about project management and new processes. We went over a number of new projects and also talked about options for doing better bidding, estimates, and quotes. See attached for a very loose list of things to consider. Just getting started.

Cory and I spent an hour going over notes, flowcharts, and details of a project that needed to be quoted. We used some new spreadsheets to estimate times, values, and hours needed to complete the project. This marks one of the deepest quotes that Cory and I have done together. Still learning but improving and that feels great. Good stuff.

Full visual code review with Danny on his custom daily/weekly sales report. We also did some training on arrays and how those work as super variables as compared to basic or singular variables.

Looking into custom code and special calculations for the ecommerce shopping cart. We ended up getting into some black box code and even tweaking the main page that calls the black box code. Bryan is somewhat pioneering some of the theme based (new folders or global/group) black box options. Sometimes that can be pretty rough. No one else has been in there for years and there are some cobwebs that need to be dusted and/or removed. He was dealing with 5 year old code that needed to be pushed to the next level.

Clean-up from the day, paying bills, and doing email stuff.

Texting back and forth. Shawn is still advancing the ball on the new W-4 and payroll calculations.

Recording notes from the past couple of days. Transferring scribbles on post-it notes to the developer's notebook.

Weekly meeting with Brandon

Chuck and I had a meeting. Normally we would have been going over progress that Chuck is making on his projects. Instead, Chuck and I spent an hour going over options, plans, and business stuff. We covered things from our napkin budget, to forecasts, to what we want our business model to be. Fun meeting but slightly different than many of our other meetings. Lots of potential out there. We just need to work on picking it up.

Alan and I spent the first part of the meeting reviewing and going over business plans and budgets. We talked strategy and made a few small decisions. After that, Alan gave me a verbal report of some of his projects and where things are at. He has been doing lots of code centric R & D and exploration and experimentation. What that means is testing how long things take, finding time sinks, and figuring out the best tech for each situation. Here are some of my note:

- Recording hours based off of estimates as compared with real hours spent on sub pieces of a bigger project. Comparing differences.

- Where is the time going and what pulls us (he and others) off of the projects?

- Project scope and project creep - changing over time based on level of development (basically being able to see further down the road and/or opening up new options) - big time sink.

- Doing higher load testing... Instead of testing with 10 to100 records, testing with 100,000 to a million records. Seeing and documenting bottlenecks and process time amounts to run/complete.

- Finding bottlenecks and trying to fix those pieces.

- Pros and Cons to using AJAX (asynchronous JavaScript and XML calls)- Pretty, handy for small things, but hard to debug and non efficient for large reports or queries. We have a current project that will rely heavily on AJAX calls. Testing things out and seeing the pros and cons of the technology.

- Both AJAX and JSON (JavaScript object notation or objects) have pros and cons. Just because they exist and do great, they shouldn't be used for every situration and scenario. Treat them like salt and pepper, great for flavoring but ruin things if used in too big of quantities. Both technologies tend to lend themselves to small, quick transactions or things that are not being pulled and reported on (search capability). Both technologies have their place but both are not a use all silver bullet solution.

- Test driven development is nice but it slows things down quite a bit. It does have its place, but we may not be pushing it as much. Here is an example: Alan was working on a project. The unit test were 3,000+ lines of code to test the actual page of only 1,000 lines of code. Also, each test was so individual that it really didn't test all of the pieces working together in harmony - at least on what he was able to do.

- There are a number of places, especially on the front end, where super complex code may end up creating more bugs and problems than simple copy and paste options. The complexity outweighs the benefits, especially when working with frontend code and normal HTML tags. Keep tags with tags and use more script stuff in the background where things just get called vs showing the output on the frontend.

- Alan is working on some pages that monitor all servers and check for certain corp-specific tables and database updates. He plans on beefing that up and spending more time making sure we have a stable platform and database table/row/column structure.

- We talked about using includes on the CFC's and how that works.

NEED API DOCUMENTATION. REQUESTED IT FROM CLIENT ON 3/11/20.

3/11/20: Global closed-loop or integration of eTT and Adilas should include check writing in Adilas that would send a message to eXPO to create a check and email it to the Payee or the check writer. This is for the ultimate goal of no double entry of accounting transactions. This project may have been presented or sent with a Scope of Work, but we do not have a record of that even though we were told it was in process.

NEED API DOCUMENTATION TO QUOTE THIS. CAN'T MEET THE EXPECTATIONS OF THE CLIENT DUE TO THE WAY BANKING WORKS BUT CAN DO THE REFUND BEFORE THE BATCH- WITHIN 24HR PERIOD.

3/11/20: The refund functionality is not currently working as expected. The invoice can currently be canceled on eTT, but the transaction is not sent to eXPO Financial Services for reversal of the three parts of the transaction - the sale price, the reserve held for 180 days, and the transaction fee. When this was first tested, it worked, but when tested later on, the transaction did not show up in eXPO Financial Services so it could not be canceled.

Emails and follow-ups.

GoToMeeting was our friend. Eric would show me something, we would pass files around using the repository and then I would test things on my local box. We went back and forth a number of times, testing, making changes, and retesting. Fun little process. This was one of the first times that we used GoToMeeting to virtually be in the same room and on the same code base. Fun and cool little exercise. Good use of time. Active testing and changing in virtual real-time.

The code we were checking was deep financial pieces on the balance sheet and P&L (profit and loss or income statement). Lots of new code to help with customer loyalty points and the accounting behind that section, both earning and redeeming points. Lots of work with invoice payments, auto depositing, and showing cost of goods sold entries.

While Eric was working on things, and I wasn't testing, I spent some time recording other meeting notes from earlier meetings yesterday and today. Trying to get caught up.

Going over code on a custom 3rd party ecommerce shopping cart. Lots of ins and out and possible scenarios. Making progress.

Steve and I talking about the word custom. Maybe instead of custom, we go more with settings and work on building out the main core pieces.. Make it data driven vs hardcoded.

- The current 2020 model is ready. If you would like get something more, we are open to talking and building.

- Our customers are building their own MVP (minimal viable product) - It all comes back to a foundation of permissions and settings. Very interesting.

Worked with Josh for an hour. We got a few of the new pieces of code done that he has been working on to help control the default unit of measure on a per category level. We did some testing, made a few changes, and pushed up some code for testing. The new code only went up to one server at this point.

Shannon and I were working on some new content today for the reporting business function as part of the presentation gallery project. See attached for the new brainstorming. You may need to scroll way down to see it. Our goal is to outline and present all 12 application players, all 12 business functions, and all of the core concepts that we are built on. Pretty deep dive into what we have to offer. Still under construction and in progress but coming.

Here are a few other things that we are working on and/or talked about today:

- The value of time and setting a value on our time and the time of others

- Teaching people how to treat you or treat us (as a company). It is amazing how we act and interact actually trains people what to expect, what to look forward to, and what they can get away with. Almost the rules of engagement or rules of interaction between parties.

- Growing up, line by line, precept by precept. It's a process and aren't we glad for that process.

3/12/20: Two more columns/values are needed in this look back report in order to be able to tie back to balance sheet values. This look back report is already configured for snow owl so no need to update for that.

1) In/Out Extended Cost Total (comes from usage) also called extended value and also called extended cost in the grouped view.

2) Look back date and time- if exporting there needs to be a point of reference for when the report was run. Currently it shows at the top but doesn't export.

On parent level- 3/12/20: When trying to export this report to excel/csv, it only pulls 500 reports even though there are over 1000. (The drop down arrow only allows to view 100.)

Page URL

top_secret/secure/printable_parts_report.cfm

Jonathan and I met and went over some shopping cart ideas. He is doing a great job trying to listen and come up with creative and sharp solutions. See attached for some new mock-ups and screenshots.

https://zoom.us/j/997233164 This meeting is the one you already had planned with Kelly. Cory is joining and we are going to zoom so we can show you the first 3 projects we need quoted for financial accuracy in reporting.

Working with Eric going back and forth testing some of the new P&L (profit and loss or income statement) logic and code. I was doing the testing and Eric was making changes as needed. Lots of back and forth and making micro tweaks. We got really close to being able to launch things but opted to wait due to the fact that both of us were going to be unavailable the following day.

Steve and I were going over projections, forecasting stuff, and where we wanted to head with some of our business objectives. Good little meeting and talking about the future and how we need to move more towards custom code.

Steve and Wayne and I were talking about servers and potentially moving some of the pieces away from our current hosting company. Emails.

Meeting with Jon Hudson and showing him some stuff about arrays and a small custom project that he is going to be working on.

Working with Eric on some code review stuff. We got things merged and deployed. We also talked about versioning and even better version control.  I also spent some time doing some tech support.

Meeting on new shopping cart. We talked with Spencer about mixing and blending PHP and Adobe ColdFusion and some of the pros and cons of that idea. Most of it comes down to being able to store and share session scope variables and values. Lots of other talks about cross session management and virtual internal 3rd party stuff.

Completion of project to push code to servers. Working with Danny and going through code sign-off and clean-up. We cleaned up his branch, rand some code diffs, and line by line clean-up.

Cross corp invoice to PO stuff and going over things with Bryan. We talked about possibly doing too much on one page. Currently we are doing cross corp stuff, inventory transfer, bulk edit, and dynamic cross corp mappings.

Steve and I going over things. We pulled out some budgeting spreadsheets and started going through things line by line. Talking and going over things. Part of the plan.

From Steve - A true business owner is in the replacement business. You are constantly replacing one thing or the other.

Steve and Dustin were online chatting when I joined. After that, Wayne popped in and gave us an update about some of the new servers and quotes from different businesses.

Instead of group and team training today, Steve went through a number of things with those who were online. We had Alan, Steve, Brandon, and Danny. Steve went over a document that had 10 basic steps to what we are trying to do with the custom projects. As part of the conversation, we talked about a number of other pieces such as:

- Moving things from the general project pool over to the project queue

- limiting R&D and moving R&D into real-time development (bring it closer to home)

- marketing the custom options that we have

- SaaS solutions (software as a solution)

- 2 different teams - look and feel team and backend team

Questions... how do we flag our projects for projects that are fundable? Cory asked, how are the projects related? What projects play along with that.

- 3 things - internal shopping cart, look and feel, balance sheet stuff and reporting/exporting

- MVP for the cannabis industry - balance sheet, reporting, sub inventory, mini conversions

- Building new products off of the existing platform as a service (PaaS)

- From Kelly - small group of legacy people to help fund some of the reporting and exporting - certain ones would be grandfathered into older lower rates while others will get increased rates going in the future.

- We did some other forecasting and looking at numbers.

- Grouping projects into like areas

- Lots of talk about smaller packages, modules, and list of features and options per price tag

- Changing our focus to working on client funded projects

- Getting more organized and really staying as focused as possible - working toward a goal

- Everything is trending toward our community funded projects and getting things funded

- Finding the mix and blend between client funded projects and internal funded projects

- Light crowd funding options

- Phases, even with-in our own environment - making it easier and easier to record the data and also to get the data back (reporting) and easy in/out type process.

3/17/20: New code launched yesterday was skipping a couple of things. We were looking for certain ids and they were being skipped. 125 files used list contains vs listfinds.

Working with Eric on some code. We also found some places that have older code that says list contains vs list find (the later is more direct and more distinct).

Great meeting. We were working on a proposal and going through the pieces, projects, and steps. I was helping where possible and Cory was writing down ideas and getting rough draft stuff going. After the meeting, she ended up going back over things and refining it. The proposal looked really good. Simple, but still enough to advance the ball.

Emails and tech support. Got on with Bryan and looked at some new code. It looked much better than it did yesterday and I tried to let Bryan know that I thought that he was going in a good direction. Sometimes things are tricky. After touching base, Bryan is going to keep working and we'll do some sign-off later. It's not quite ready yet. After that, I did more emails and tech support stuff.

Steve and I met to keep going over our plan. We talked about options for people and outside parties to invest and then get interest from their investment monies. Basically, a choose your product and then invest in that product and enhance it. We also talked about bringing on new developers and having them follow our new processes. Lots of talk about fully included ecommerce packages and what not.

We also talked about project enhancements and letting people know about the updates. That is still a struggle. We really want to bring the R&D more into real-time and closer to home vs way out on the ends of dream somewhere. We may end up having frontend devs (developers), middle end or middle level devs, and backend devs. We are seeing the need for each area.

Shawn and I were looking over payroll changes and touching base.

Emails, tech support, and working with Eric on the consolidated income statement report.

Weekly meeting with Brandon

Chuck and I were on a check in meeting. He was reporting on WanderWays (camp adilas toolset) and where things are at there. He is working through the code and making great progress. Last week, we ended up talking about other things and I didn't give him time to report on where he was at. See attached for some screenshots. Most of his current work has been focused on color pickers, wiring those color pickers up, add/edit sites page, bulk edit, some UI (user interface) decisions, and work orders. He has also been doing a little bit of research on other verticals and industry specific needs.

Wayne popped in and we talked about the need to get multiple databases connected to single machines. We need to virtually get some of the users off the bus and on to their own vehicle and/or motorcycle (smaller entity). We also talked about setup options, custom image tags, mappings, and making the new system setup process even easier. Thinking towards the future and being able to duplicate things on a larger scale.

Emails, follow-ups, and calling and talking with Calvin. Touching base on the adilas label builder and heading towards a web based interface. He has been super busy with his gmext (group mass texting) products but will keep us posted on progress on our stuff.

3/17/20: Similar to compare inventory page. See parent cost is off- can select the box and make it zero. Steve sees it being filtered by vendor/category.

3/18/20: Beginning budget is for time spent looking into this connection. API fees of $3500 to follow if they are interested. We will assign a developer, do a mockup and test. This will cover 4 hours of time. Sent them a quote.

3/17/20: We are working on an api that will allow the kiosk to host an external Adilas website with call backs to display an onscreen keyboard and control the various devices on the kiosk.

We will need a test adilas website we can use in order to create a working demo of the integration.

3/17/20: 1)Need a gram control that converts to oz's. 1/8th of an oz, 1/4 of an oz etc.
-Dynamic in recommended allotment (physician)= Patient(customer)
-Dynamic in available allotment (what can be purchased now)- another field in the gram control to the right of the +/-.
-Dynamic in output of reporting Qty, Conversion Chart (changing words from grams to oz's)

The gram control will need to consider THC by sub but will need to total into Ounces for reporting. 

4. ATCs shall only dispense oil in equivalencies of one-eighth-ounce and one-quarter-ounce of dried flower. Those equivalencies are:

• 1/8 ounce – 354 mg of THC
• ¼ ounce - 708.75 mg of THC

Emails, quotes, follow-ups, and working on flags and tags for our community funded projects (elements of time stuff). We need ways to add project categories, project types, and project funding options. All of that may be done using the existing flags and tags inside of adilas elements of time.

Pushed up code for the new cross corp invoice to PO stuff. Bryan has been working on hard on some of that stuff.

Russell and I got a Zoom session to go over some new pages that he is working on and some of his ideas. He showed me some new ideas to help make the invoice homepage look better and better use the space. We talked about getting mock-ups of new pages and then turning Russell and his team on those projects to keep the R&D close to the development levels. We had fun talking about plans and direction.

More emails and tech support stuff towards the end after Russell dropped off.

Steve and I were on the morning meeting together. We talked about new updates, changes, and direction. Steve had a couple of small coding questions and we worked on his cross corp mapping of vendors stuff. He was super close on one section, we just had to add some code to jump out of a loop once a match was found. Without the breakpoint, the loop would find the match and then keep going making it look like it didn't find it. Easy fix and good stuff.

We got a call from the server farm and they are scheduling a physical transfer of the servers between datacenters. We talked about some options and timeframe requests.

Lots of follow-up on emails and what not. Recording notes.

Lots of new brainstorming on the business function of reporting and what that means and does. Working on the outline for the presentation gallery. See attached.

Here were some of the main topics we are working on under reporting:

define the needs
catch the data
secure and store data
transform and progress
show and filter
reporting uses
quick search
dealing with time

simplify - one place to get your reports
you've been waiting for this
bridge the gap - between your business operations and your accounting
roll call - when you need them
live and searchable
remote access
onsite data entry points
cloudbased - access any time
real-time as it happens
always up-to-date
empower the people
customized for each user
hidden features based on permission
permission levels
enter once - use many
enter at the point of action
pass to the next step
if data is correct, let it flow
data assembly line principle
no limits
no data caps
unlimited
different corps within the same login
view at a glance
recent activity and history
automated reports with aging

Just for fun, here is another link to an older what is adilas.biz? flyer - It has some fun concepts that still hold true.

https://data0.adilas.biz/what_is_adilas.pdf - What is adilas.biz? flyer

1st report: nj doh report_1-ATC Payment Report

1)Reports pulling data from portal need to be mirrored in adilas. All data is currently there. One for each (there are 3). These should live under Health4Life custom reports tab. 
**Physician and caregiver info would live in customer logs. Lots of HIPPA concerns here- perhaps skip this report and do the other two. 
Quote on everything.

nj doh report_2-ATC Daily Purchases

Reports pulling data from portal need to be mirrored in adilas. All data is currently there. One for each (there are 3). These should live under Health4Life custom reports tab. 

nj doh report_3-ATC Patient Lists Report

**Physician and caregiver info would live in customer logs. 

3/19/20: Reports for NJ DOH will require filling out all of these fields. Creating a template that makes this easier is what is involved here. When you create a new customer, you can scroll to the bottom and enter all of the necessary fields. They will say ie caregiver instead of contact type. We will do this via settings added to the gear at the top of the customer add/edit page. https://data0.adilas.biz/top_secret/secure/field_settings_customer.cfm is the settings page where these will be added.

Working with Cory and Steve on quoting and project management stuff. As a fun side note, Steve and Cory set up another meeting and got together and were doing some quoting on their own and just brining me the bigger or more complex problems. That's kinda cool.

Wayne, Alan, and I were on a meeting going over plans for new databases options. We talked server needs, migration questions, code repository automation, and some other technical issues. Originally we were going to be working on multiple data sources on a single box. We decided to table that project for now and we'll circle back around.

After Wayne left the meeting, Alan and I spent some time talking about our business model and options for where he would like to fit. Steve came on towards the end and added some of his ideas and comments. Our main goal and focus is trying to get some of the custom code work in and done as well and quickly as possible.

Tons of email. Also working through some new 2020 payroll changes and new calculations.

I got an email from Jonathan dealing with some cart ideas and concepts for fracture. See the link below for some of his ideas and thoughts.

https://adobe.ly/33DwR4i - cart ideas and permission/roles ideas and sub dividing into smaller and smaller pieces.

7/22/2020: client interested once again. quoted at $500-$1000.

6/1/2020: Could have possible client interest in this.Waiting to hear back.

3/20/20: Molly's client paid to have subs all (from invoice adv search) added to report list. At the time adilas said they would pay to develop the same report under Inventory. It would use the same logic that was already written. Bryan started this project, Brandon finished. Not sure how far Bryan got for inventory report.

8/14/19: From Brandon's notes:

Working with Bryan on a deep sub inventory report. The thing that makes this one crazy is a mixed bag of sub inventory attribute filters (from across multiple categories). That little piece of multiple categories throws some major variables into the mix.

This is more for me... but we need to go back and do a full mini project to prep the field (general sub inventory area) better on sub inventory. We need to record the sub reference id numbers on the po/invoice line items table (both po's and invoices). We also need to record the main part id's, app type id's (items=11), and the part category id on the custom texts, custom dates, and custom numerics tables. We can use the main_id, app_type_id, and sub_id columns on the custom tables. We need to spend some time going backwards before we can go forwards with any speed. It may be a big mini project but hopefully it would help us as we try to go forward.

7/22/2020: Client interested again. Quoted at $500-$1000

3/20/20: Currently this report is under invoice adv- want to add it to PO's adv. Same logic would apply.

Back looking into the new 2020 payroll calculations.

Working on new payroll changes and monitoring servers during a physical server move and relocation being done by Newtek. We will have some servers being both up and down during the day as they move them from one location to the next. Moving day.

Steve, Wayne, Shari O., and I were all on the morning meeting and adilas GoToMeeting channel all morning. We all got on at 9 am and have been on all day monitoring and watching the progress of the move. Crazy time. This was pushed on us by the server company (actual server farm) with minimal warning and lead time.

More work on the 2020 payroll stuff and watching the servers come up and start working again. On the GoToMeeting session with Steve, Wayne, and I. We were all working on different things and randomly chatting and talking as we either waited or thoughts came to our minds. Group effort. I also know that we had Shari O. and Drea online doing tech support all day as well.

On the phone with tech support and checking out servers. Steve, Alan, and I got on a GoToMeeting session with Molly to check on some database tables that had been jammed up. We did some repair work and got things going. Long day today. But, on the positive side, we have a great team and that is awesome.

Topics from the morning meeting. Build one thing and get it across the finish line. Then do the next, and so on. Pare things down to one at a time. Steve and Eric were talking about things and different topics. We keep getting distracted by so many things going on. Steve, Eric, Danny, Dustin, and I were all on the GoToMeeting session.

Eric and I had a code review session where I would test things, make suggestions, and Eric would make the changes. We pushed branches back and forth and got it all ready to be launched. The new functionality was dealing with voiding invoices and auto rolling back customer loyalty points earned. We decided to wait to launch things until everything else (server wise) calmed down. Good session.

Steve and I were on with Wayne talking about servers, options, and what the moving of the servers would look like. This is not a physical move but a virtual move between server companies. Exploring a number of new options with another provider. We spent some time and went over a plan and a bunch of new options. He, Wayne, even showed Steve and I some new options that he has directly from the customer control panel on the new hosting environment. Some of these features will be very useful going forward.

3/23/20: Need dynamic terms to print on printable invoice and pdf. Will do two black boxes to achieve this.

3/25/20: Said no thank you via email. Will save just in case.

Semt em 3/23/20 with help linkk https://data0.adilas.biz/top_secret/help.cfm?id=464&pwd=api - help file as well as option to meet with a developer ($400).

3/23/20: I am building a website and app for my customer (a dispensary).  They maintain their product inventory in Adilas. I am seeking information on how a web developer (me) would be able to connect to their inventory db so pull and display information from their product inventory from Adilas to the new website.  That is all we are seeking to do.  The do not want to maintain two separate inventory lists. If this can be done, please help.  If not, please just let me know, and Ill talk to them about alternatives.  

I have been asked to design a website and app specific to my customer, who is also your customer.  I was able to browse through Adilas and saw Option 3 on your website.  In order to fulfill customer requirements, I will need more information, (Relevant Code), etc., to create db connection structures and fully access and manipulate data related to their website and pwa.  Is this information available, and do you have requirements for accessing such information?  Thank you for any direction you can provide.

3/23/20: See quote: Share photos across any corp, any server, any website.