Just some general notes...

- We need to show up histories for the special accounts on the history homepage. We need both kinds of history, the actual transactions and the payee history of who did what on the special accounts.

- On the enterprise systems, do it manually at first and then start automating that. If we do it that way, we'll learn exactly what is needed and then be able to help make it go faster.

- As a note, I got stuck on a login loop by entering a bad corp key on the main login. I couldn't get to a screen to retry or reenter the corp key, it kept me in a small login loop. We need to provide a way back to a screen that allows for a new corp key to be entered. This is a small maintenance task that is needed.

Moving buttons to tabs on reports - see image gallery

Recording notes, expenses, emails, and general stuff.

On 11/1/19, Brandon got stuck on a login loop by entering a bad corp key on the main login. He couldn't get to a screen to retry or reenter the corp key, it kept him in a small login loop. He got out of it due to his knowledge of other pages that allow for the corp key value to be entered. Other users may not know of those other pages. We need to provide a way back to a screen that allows for a new corp key to be entered. This is a small maintenance task that is needed.

Multiple developers were on the morning meeting. Bryan had some questions about a new report that was needed. Once we were done, Wayne jumped in and had a number of ideas and questions. One of Wayne's suggestion for Bryan was using black box technology and then using an include on the black box pages. That is a way to get a one-to-many out of the black boxes. Each corp would have its own page by corp id number (normal black box) and then virtually include a centralized include file. Great idea.

Steve and Wayne were talking about server stuff and cluster stuff. We are needing some new servers and trying to get some cluster stuff going. Lots of needs and trying to see what happens and how things grow and spread. On our side, we are seeing more and more need to see where corps are at, where they are going (growth models), and even planning for the future. Trying to stay on the top side of things.

Talking with Eric about special accounts. We talked about our next round on this project. We are hoping to deal with some of the newly requested rules for the customer loyalty points. Below is a possible list of new rules for the loyalty points.

- More possible rules...
- Limit by customer type (list)
- Maybe exclude by single items (list)
- Maybe a date range - program start date and program end date (strings or dates)
- Showing a dollar value on the receipt (toggle) - we currently already have a toggle to show the points on a customer receipt, but we haven't been showing the dollar amount, just the point amount.
- Maybe look at parent attribute as a include/exclude (list) - not tons of requests on this one yet

Steve and Eric were talking about aggregated data. Steve was talking about scratch reports (perfect report per day) and then moving on to aggregation once the scratch reports are correct. Small little reports per day and then turning it into a reoccurring task that is done after hours and even populated back into the enterprise system. Extract, transform, load - and other data warehouse type levels. We were also talking the difference between true data warehousing vs simple roll-up and small aggregated data. We even were talking about future and down the road options. A true data warehouse is deep and plays on the analytical levels and even clear out to the deep business intelligence (BI) stuff.

Working with Steve on some of his API socket stuff. Small work session. He is making great progress. After the work session, we split up and worked on our own projects. Busy times.

Level of Access to ERP for NJ DOH Regulators:

Issue: A question was raised as to the level of access to MPX NJ’s Adilas ERP system, i.e., whether a custom dashboard can be developed to limit access to certain records not within the purview of Medicinal Marijuana Program regulatory oversight.

 

Answer: NJ DOH requires read-only access to entirety of ERP system. Limited dashboard is not feasible. See Section E (p. 2) of attached ATC Internal Management System SOP provided by NJ DOH, which provides: “The ATC shall provide read only access to the entirety of the system to the MMP.”

 

 

Sean Barravecchio

Director of Compliance and Security

Citiva Medical, LLC

115 Broadway, 3^rd Floor

New York, NY 10006

Direct: (212) 257-3145, ext. 217

Mobile: (631) 767-3615

Email: sean.barravecchio@citiva.com

Got into Josh's tax breakdown project and started pulling out code and merging in pieces. Started with corp-wide settings, then on to mini invoices, then to printable invoices, and also on to PDF invoices. Ran out of time, but started to working on the print simple invoices (show multiple invoices at a time).

Steve and Bryan were talking about being able to add an additional payee (salesperson) to invoices. We originally talked about flex grid. Then Steve jumped in and mentioned that we already have a tool to allow adding additional customers to invoices, quotes, and stock/units. We spent some time and looked over the options. I'm really glad that Steve jumped in and made that suggestion. As part of the conversation, we also talked about existing pages, searches, reports, and even tying things clear out to payroll and what not. Lots of options, we just need to figure out which direction we need to go.

After that, we spent some time going over ways of tweaking and manipulating ecommerce line items. We talked about ways of hiding things, switching id's, and other small tricks. Bryan is working on the invoice rounding in ecommerce land with special fees (handling fees) to help round the invoices totals after taxes.

We started out the morning talking about helping our users succeed using steps, limits, and pagination (how many records to show per page). Dustin had some questions and wanted to go over some options. He has 4-5 different things that he could do to speed up one of the pages. We went over his ideas and made a small plan. I pointed him to some files where we do somewhat similar things for different processes.

After that, Steve and I did a small work session on the internal API socket stuff that Steve is working on. He is playing with multiple corps and doing aggregated sales data. We did some light debugging and went over flow and options.

When I wasn't talking or showing the guys stuff, I was setting up the POS (point of sale) hardware to make sure that everything was working. I have a demo later today.

Alan did a team training event. We had Josh, Danny, Steve, Wayne, Bryan, Russell, Alan, and Brandon on the training meeting. The main topics were dealing with using different tools for different jobs and then going into a small quiz/discussion on what tools work best for what needs/jobs/projects. Good discussion. Some of the topics were dealing with loops, data structures, options, and scenarios for different tasks.

See attached for a link to the video.

Shannon checked in right on time. However, the training meeting went over a bit and two of the developers had questions after the meeting. Both Bryan and Josh had different questions about the projects that they are working on. By the time I got to Shannon, we ended up canceling the rest of our meeting so that I could prep and test the POS (point of sale) hardware for the demo. That really helped me out, as I was struggling to get enough time to test everything. Good stuff.

Update on Camp Adilas progress. We postponed this due to the demo today. Both Chuck and I went and met at Bridgerland for the demo.

They are looking for a demo on Adilas POS (point of sale) features. They have interest in multiple stores, inventory tracking, revenue reports, POS demo with equipment, and eCommerce.

I went into Bridgerland and met with their people. We had about 10 people in the demo. That was both good and made it kinda rough. Good because we had a lot of questions and interactions, bad because we had so many different needs and wants for the demo. That made it a little bit tougher. We also only had just over an hour to answer all of the questions.

They had questions on adding inventory, tracking work orders, manufacturing (recipe/builds), basic sales, reporting, etc. We tried to mix the demo and some show and tell, some training, and some bouncing. Ok, a lot of bouncing. Like I said, I think it was both good and bad. We'll try to change a few of the variables for next time.

Some of the total time was setting up and taking down some of the POS hardware and pieces. The total demo was only about 1.25 hours. The other time was driving into town.

On the morning meeting. Danny Shuford and Dustin were on there. Danny needed some help with his local development environment. We went through a few things and then he was going to keep going and even try to reinstall some of the pieces. After Danny and I finished, Dustin had some questions about pagination and limiting certain processes. We talked about some options and tools such as the FORM scope and the session scope. We went over a few code samples of setting things up, checking for the correct values, and even cleaning up the custom session containers after we were done. Great little meeting.

Meeting with Alan on a number of topics. Just trying to be on the same page. We started out and I reported to him about my demo yesterday and how some of the users really want a super skinny and basic interface. Then, later on, they may want more tools and options. We talked about how that seems to be an issue every time we do a demo. They want the functionality, but they want it super simple and buried and/or configurable to their needs. Interesting, but a common thread. Here are some other topics that we talked about:

- Dealing with navigation - iceberg analogy or maybe icebergs (plural)

- If presets exist, allow the user to reset to blank or to the defaults

- Analogy of drinking from a drinking fountain vs a fire hose

- Create a "simple" shopping cart

- We could add configuration later on

- Devs (developers) often keep adding, design guys are more simple

- We have to and need to play in teams. That is the future.

- Training the team, project management, and building projects as a team - some new challenges. Some of the project management may need to be done prior or separate from the rest of the team project stuff.

- Making sure we have good default or master tables (for copying database tables and structure). That lead into some talks about the developer update table page and how we could use that page to help with the maintenance on the database.

- The last major topic was maintenance. We need to build as if for years, yet still solve the current needs.

Alan and I are going to try to have a weekly meeting where we can just bat ideas around to keep us on the same page. We are thinking about Wednesday mornings.

Recording notes, small code changes, pushed up a couple of new pages dealing with the tax breakdown project. Sent out some emails and updates.

Email from Drea...11/6/19: Is there a way to track the key stroke history for the gram tracker inside the cart? I know on the history homepage we have the ability to track key strokes, but will changes to the gram tracker show up here? We have a client who's gram tracker got changed (to an excessive amount) to allow over limit sales and they would like to see who changed it.

Currently can't track history on gram control.

I asked Eric Tauer (adilas developer) to share with me a paragraph on some terminology used in data warehousing. Here is what I got from Eric on 11/16/19.

There are different technology approaches to Data Warehousing (DW).  My experience is related to the following...

A DW stores data for the purposes of on line analytical processing (OLAP).  The DW’s data sources are typically concerned with on line transactional processing (OLTP).  The physical data models used for OLAP and OLTP are structurally different.  OLTP is relational, at least to 3rd normal form.  OLAP is denormalized.  Denormalizing data has costs that benefit analysis of the data.  The cost of denormalized data is not beneficial for OLTP.  This means these two different data architectures are optimized for business analysis (OLAP) vs. transaction storage (OLTP).

Extract, transform, and load (ETL) processes are used to get source data from OLTP to OLAP.  During ETL, change detection, aggregation, denormalization, and more are exercised to store the data for efficient analytical uses.  A common physical data architecture for a DW is called a dimensional model.  Dimensional models are also called star schemas.  Dimensions (Customer, Vendor, Product, Time, etc.) are shared among many unique fact tables (Sales, Inventory, etc.).  Fact tables may also be a view of a logical group of tables that included multiple levels of aggregated granular fact data when and where performance gains are needed.  OLAP database schema design is optimized for the success for business intelligence, and involves a great deal of business analysis to make the many decisions in data modeling that will deliver a meaningful schema for data analysis.

These are just some notes that I wanted to record. Some of them have a light maintenance type flare

- Simple POS (point of sale) interface. Be able to turn things on/off, arrange as needed, change colors, icons, tool tips, possible verbage, show/hide columns

- Simple build your own interface - dynamics - 1-10 columns (going across), 1-20 rows (going down). I also think that a small widget for the quick search might be really nice.

- The auto print invoice feature needs to be a user level setting. The default needs to be no, don't auto print.

- Kill some of the mini invoices that just have the print feature gone/missing (people who didn't want it). We had to make a number of custom invoices just to kill this auto feature. We want to reverse this, let them set the user level setting and get them back to a normal invoice. This is a little bit of maintenance that is needed.

- Kill the black box custom code for the corp 53 play site. These are the top mini and bottom mini black box stuff with smilely faces and the words custom code goes here in them. They are no longer needed. Trying to make things look more simple and less cluttered.

- On the quantity warnings and inventory engine stuff, figure out how to get rid of the warnings for the quantity settings. As a note for me, some of those warnings were on internal items such as part number other or fee or labor.

Spent some time working on some JavaScript courses. The free course that I'm taking is called JavaScript 30. https://javascript30.com/

Bryan had some new Expo code to push up to the servers. It was dealing with invoice rounding for ecommerce. This was not done as core (currently), meaning the adilas code core. It was special code just done on the Expo payment solution side of the equation. Anyways, we pushed up some new code. We then went through a number of questions. One was dealing with custom spreadsheets, using existing spreadsheet templates, usage of API sockets, play at the wall - type mentality, and also a project dealing with adding additional salespersons (employee/payee) to invoices and quotes. This project would not tie into payroll, but it would be tied to invoices, quotes, stock/units, etc. Very similar to the existing additional customer tie-in options. We went over ideas and light direction on those projects.

Just for fun, I also showed Bryan a couple of screenshots from both Jonathan and Chuck (adilas designers) to let him see where we are headed. Fun meeting.

Recording notes and transferring handwritten post-it notes (scribbles and quick notes) to the correct elements of time, here in the developer's notebook.

Steve and I had a work session this morning on the GoToMeeting. Steve is working on a project that will take data from a single corporation and send it across to another corporation to hold and store aggregated data (pre summed up data). As part of that project, he needs a custom black box database table. We spent the whole hour going over the format and how to best figure out a solution. See attached for some graphics that we were using to go over different scenarios. The graphics don't mean anything, just scenarios and samples. Playing around.

Meet to continue pushing on projects list.

Our meeting today started with some light tech support stuff and some training. She had some questions about customer loyalty points, recipe/builds, and how to get sub inventory to work in and through the recipe/build process. We chatted about a number of ideas and options. She was taking notes and will be adding some of those things to the master to do list (adilas community funded projects).

A couple of my notes were about subs in recipes, being able to duplicate a recipe (new idea), and showing the subs just in time when the recipe is going to be used. We talked about the options between setting things up directly with certain subs (on the setup pages) or on the build prep (just before running things) and the pros and cons of both options.

We talked about some new corp-wide settings dealing with setting up subs only and also helping set those values when adding inventory. Helping to speed up the process.

We also talked about a mini project costing model and tying that out to a recipe/build (costing things out as they get made).

Working with Shannon on 11/7/19 - this was in prep for a demo for a local tech college and trying to make it more simplified. We had a good brainstorming meeting and here are some of our notes:

- Every business offers a service or product to their customers.

- Milk before meat - only run as fas as you are able.

- Pain is a huge motivating factor for change.
>> - We can handle certain levels of pain
 >> - If it gets unbearable, we are looking for change

- We want to make it easy, digestible, and pretty (yet still powerful)

- We need to show you that it is doable and we can do that by breaking it down into simple chunks.
>> - If you have to bounce everywhere... it may look like it is super complicated. Being able to bounce is super cool, but it may look intimidating.
>> - They want it to do the super complicated stuff (the little stuff) but they (meaning users) sometimes get overwhelmed when you show them without some of the other context.

- We may not even realize that we are in a world... our world becomes just part of what we do and how we do things.

Ideas on a general tour...
- top level...
strip mall** (think of the diversity in a strip mall - tons of little shops, right next to each other)
big hallway
universe
worlds
departments
locations within those areas
business needs
point of sale
invoices
collect monies
customers
tracking things - sales, customers, inventory, expenses
paying our people, timecards
accounting
paying taxes
reports
data storage and processing
ecommerce
analize and adjust accordingly

- Business functions - we have already defined 12 of the business functions

- Tools - I really liked how Shannon kept saying the word tools - that's what they really are.

- Processes are going to change based on needs and industry (business vertical).

- Meet the tools** (players may be the wrong word) - pages and options (not 1,000's of  pages but only 6-10 pages total - make it chewable - little tiles)
 - group and simplify, then go deeper as needed. think of being able to fly over the whole and drill-down as needed. Be able to navigate at any of those levels

- Using tools to get the outcome that you want.

- Mixing and blending tools, goals, and outcomes to build your world.
>> - As you are picking and using tools, you are virtually building your world.

- What tools do you use all the time? Those become important and you want them right at hand for the task that you are doing.

- pull pieces from what Jonathan is already working on
>> - go, do, see
>> - Almost a geo tourism type level. Basically the reasons why you go where you go to do what you want to do. What else is in that area? If you have multiple things in the same area... that increases the pull for that area. Getting the biggest bang for your buck.
>> - Look at all of these other pieces and features that you get. Instead of just getting one of the things that you want, you get 10.

- Be able to jump from the tour into real live scenarios
>> - What if there were canned scenarios that you could walk through? That would be awesome.
>>  - Be able to link out to other resources (videos, photos, graphics, images, help files, articles, research, etc.)

- World building (advanced concept) - maybe talk about such and such land, and this land, and that land... they are really worlds or part of a world, but maybe the word land or area or department may help people follow things better. Be able to flex as needed.

- Data assembly line - what an awesome concept, but it sometimes takes people time to warm up to that idea.

- Visual outline (foldable or unfoldable - maybe use +&- signs) - be able to jump where ever...

- The adilas cafe... work, play, buy, sell, learn, community

Steve and I met with Chuck. We started out talking about a prior demo that Chuck and I did. We then rolled into an update on the camp adilas project. Here are some of our notes:

- On the demo that I did, I opened it up too much and it ended up going all over the place. Not very focused.

- Create canned versions of what we can do and how we answer some of their needs. Almost the elevator type pitch (30 second or 2 minute overview).

- Maybe a concept map (like a site map)

- What can we do?
>> - Say something like - point of sale... walk through the steps
>> - Say taxes... walk through the steps

- Idea - create a simple web page and show some sort of nested titles (see Chuck's report page for his camping site and then be able to nest sub sections under those tiles).

- Protoype in Adobe XD for now, then maybe switch to WordPress or some other thing.

- Have Brandon create a list or outline and then have Chuck help put things together.

- From Steve - grateful for Chuck being able to bridge the gap between the look and feel and the sales side.
>> - Helping to get into the marketing groove.

- Start building out some specialized industry flyers. We need a general one and then some that are specific to industries that we cater to.
>> - Icons and helping to drill-down into the deeper specifics

- Chuck would like to see - testimonials and customer endorsements, backing, recommendations, and validation.

- How are we going about our building process? From the look (look and feel) down to the code vs code up to look (what is our approach?).

- Getting some of us out in the field really helps build and refine the system. As we sit through training and demos, we will have ideas and see things that need to be cleaned-up. Great use of time and resources.

- Reduce the learning curve - that will help get people more into the product.

- Being able to link out to specific screenshots as part of a presentation and/or demo.

- The power of the quick search inside of adilas - go anywhere - that is awesome.

- Any choice that the user has to make (over and over again), usually makes a good settings.

- Designing both levels normal web (desktop/computer) and mobile (responsive).

See attached for a number of new screenshots from the camp adilas or campground interface project.

Working with Steve on his internal API socket project. He is catching the vision and doing great. His project is taking daily sales numbers from corporation and sending them over to an enterprise system that is getting aggregated numbers for multiple corporations (worlds). He is starting simple with one corporation and will eventually add the others. He just wants it to pass the correct data right now. We looked over his database design and system update. As a side note, this is a black box table, meaning it is a custom project.

Both Bryan and Eric jumped on the meeting for a bit towards the end. They had some simple questions and just needed a sounding board.

Jonathan, Steve, and I had a good meeting. We covered a bunch of topics. The notes below are what I pulled out of the conversation. Also, see attached for some new screenshots and concept art.

- Giant group project - Steve, Brandon, and Jonathan all working together - mulitple inputs and ideas.

- Jonathan really wants to create an edit "your page" type interface.

- Lots of icons vs tons of text - simplify.

- Fix some of the snow owl navigation to match the settings. This is true on the drop-down menus and possibly on the all_advanced_searches.cfm page. As a note, the snow owl menus have both on canvas and off canvas drop-down menus.

- When the users are searching for categories and navigation options, maybe think about adding in some flags and tags to help find the nav links and pieces. For example: Say you have a page called advanced invoice search. It may be nice if it has flags such as inventory, POS, sales tracking, etc. Help the users find the related pieces.

- Modals and small in-line pop-ups for settigns and drill-downs.

- Lots of talk about custom homepages, pages that are not part of our normal design process or something custom or specific for a certain user.

- Custom navigation options - simple, preset, build your own, help them find the sweet spot (not too many, not too few navigation tiles/buttons).

- We talked quite a bit about the top bar icons (existing) and how many of the users really like those icons buttons.

- What about things like help files, logout, switch corps, customer queue, shopping cart, chooser, saved favorites, my settings, etc. These are some of the existing top button links and icons.

- We have so many clicks... wearing out the mouse pad or the buttons on the real mouse. Pretty deep and it takes a lot of clicking some times.

- The user specific pallet and being able to condition little mini widgets - charts, aggregated page totals, counts, reports, buttons, froms, etc.

- Blank canvas, setup your own tasks.

- Being able to see preset numbers, values, totals, whatever. We will need to figure out what pieces are wanted and/or needed per section. We can figure that out.

- Expanding and contracting things. This could be settings up sizes for mini windows and mini widgets - getting to just the information that you want.

- Steve wants to be able to scroll both up and down. Basically setting an anchor point or starting point for scrolling. He would like to load things and be able to scroll up or down.

- Lots of asynchronous loading. At a different time, we even talked about a thing called lazy loading (prepping behind the scenes).

- Being able to have sub pages built into a bigger master page. Steve liked this idea.

- Split screen, frames, and sub windows. Being able to remember different sizes and persets.

- Seeing what pages are being used the most. That could really help us know where to focus.

- Problems - load time is slow, too many clicks, want to get to info and may or may not want to go to the actual page. We almost need aggregated totals and being able to push and pull that data to different places. Quick totals or mini widgets - specific to a certain task.

- What if we allowed for a multi split screen?

- Going back to tools that you use - set up your own interface so that you have all of the tools that you need for the job - Example: Say a handyman with a trailer full of tools. He will grab what he needs for the current job.

- Help people get to where they are going - analogy: All the tubes of paint on the right, just drag them out and setup your pallet. Hide the clutter and simplify things. When ready, start painting.

- Everybody is going to be a little bit different, help them succeed. Let them pretend that they they are virtually "shopping" for or from a list of options. What do you want? That could be links, lists of options, functions, pages, or preset or known values or counts. All kinds of ways to get things setup - drag it out, click on it, activate it, choose from a list, use preset settings, and then start using it. Just ideas.

- Custom dashboards, custom widgets with stored settings, lazy loading of pages in the background.

- Some people like it, some people don't, but lots of our navigation is "go anywhere" type navigation... being able to jump as needed is a huge thing for us. We love it.

- People get good in the system. Let them fly once they are at that point.

- Two complaints - look and feel and too many clicks.

- Ice berg(s) - there may be multiple pieces sticking up.

- Keeping the cart icon as a valid nav piece at all times.

Currently this pulls data from all corps potentially. Someone needs to be coached through looking and pulling the data. Surfacing this information would make this deeper level of history available to more users on an independent level.

**From a sales perspective it is good to know that this level of history is available. The location homepage history is being tracked as well.

This idea came up when trying to figure out how to make the sg&a flow easier for Herbo. This is a great way to help with that flow, as you could duplicate, and then switch out parts that weren't relevant.

Completed on 11/26/19

11/25/19: Brandon, Steve and Alan are meeting on this issue Mon, Tues and Wed this week to make some headway.

From Steve: 11/8/19:I've cc'd in Cory so she can add a ticket and we will dig into this issue. Thanks for the awesome explanation and details.

Danny, Dustin, Steve, and I were on the morning meeting. We answered a couple of questions and both Danny and Dustin jumped off to work on their own projects. Steve and I went over some internal API questions and we sent Steve in a direction to build a complex data structure for his API socket data. He is having fun, building both the sending and receiving side of the API socket. Often, as developers, we only get to play on one side or the other of an API socket call. Sometimes the other part of the puzzle is built by a different company and/or an outside 3rd party entity. Nice little work session.

Emails, recording notes, paying bills, and recording expenses.

From Bryan Dayton on 11/11/19 about Square as a merchant processing option.

Hey Brandon,
The Square code is on branch ADI-447 pull request #682. A client paid +$1,700. for this build. They ended up switching gears and the project never got fully finished. It is close. It is almost completely done and would be fairly inexpensive (approx. 5 to 20 hrs) to implement Square as a merchant account type. Thanks for all your help!
Bryan

Recording notes and pushing up tons of new screenshots from meetings last Thursday. We had a great meeting with Chuck and with Jonathan. Over 10 screenshots from each meeting. Here are some links to those pages.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5085 - meeting with Chuck - future demo ideas and camp adilas update.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5153 - meeting with Jonathan - general system navigation and reporting options.

Met up with Bryan on a couple of projects. Some of the questions were quick and some we actually looked at some code and made plans. Mostly a general work session.

I was working on some research for an adilas tour or presentation gallery. Lots of fun, took lots of notes, reviewed quite a few existing documents, and trying to string things together. Towards the end, I also paid some bills and did some email. I may fill in some more later... (planning notes and pieces).

Reviewing some mock-up video walk throughs from Chuck and the camp adilas project. See the links below. The password is camping.

https://vimeo.com/372499060 - 17 minute walkthrough of the camp adilas project

https://vimeo.com/372500075 - 6 minute walkthrough on advanced reservations
 
These are private videos. The password is "camping".

Paying bills and recording expenses.

Steve had some questions on his API socket that he is working on. Eventually, he will need to add in a number of loops and loops within loops. We are seeing about six levels deep on the loops. This is for his aggregated daily sales totals and passing data back and forth between servers. The loop levels are going to be: loop by corp, by store/location, by vendor, by category, by form (a sub group within a category), and by size (another sub group within the form group). Six levels deep. He is planning on biting off one piece at a time. Lots of loops, arrays, and structures within the arrays.

Danny popped on and had some questions. Eric came on and had a few questions as well.

Before the training meeting, Wayne joined the meeting and we talked some server stuff. We have decided to pause the AWS stuff for right now. We need to work on some internal code changes so that we can get to a clustered environment. One of the first major hang-ups is how we store images per corporation. These are logos, watermarks, and all of the images and scans per main player groups (all 12 player groups - invoices, customers, items, expense/receipts, stock/units, elements of time, deposits, etc.).

We are planning on doing a group project where we go in and fix the image storage stuff as a group. That will be fun. We also briefly talked about Docker images and how those will and/or may play in to the mix. We talked about how nice a Docker image would be for new developers coming on and being able to setup their local environment in a nice and easy way. Big time savings.

Team training meeting with Alan. We had Bryan, Danny, Dustin, Josh, Wayne, Brandon, Steve, Russell, and of course Alan on the meeting. The topic of the day was simple to complex data structures. We started out with Arrays and then went deeper. Part of the course was showing the difference between script vs tags (how to code ColdFusion - CF script vs CF tags).

We got into topics such as member functions, structures, queries, objects, algorithms, and deeper into conditional logic.

See attached for a link out to the video.

Talking with Shannon - 11/12/19. We did some review from last week and made a few new notes and expanded on some of the other topics that we were talking about.
 
- Geo tourism - showing a grouping of similar things to create more of a draw to a certain area. For example: Say someone was interested in ghost towns and old historic farms. If you could show on a map a place where quite a few of these things are located, it creates more of a draw for people to do things in that area. Once they come into that area, you show other things that are available. The more things you have to do in a certain area, it becomes a choice to go or visit there due to how many things (that interest you) that you could do from one spot or location. What if you could sell software and web ware systems like that... Look at all of these similar things that you could do from one place.

- Saving time and energy if you get everything in the same place.

- 1 thing or multiple pieces (what is the best bang for your buck).

- Pain levels - 1 thing could be really good but then you have to mary it with tons of other things, even though it is really good, it can become painful.

- Tiles (navigation buttons) and allowing you to preset just the ones that they like and/or need. Imagine presentation settings.

 - Helping to customize the options and presentations - It makes it a better presentation and it shows how settings work.

- Pain - where are the needs going to be? Anticipate some of the needs before giving a demo or presentation.

- Getting on their level... speak their language.

- Some people aren't into world building, or concepts, or history. What if you could offer multiple angles on the presentation? Let them choose the topics and the approach angles.

- Shopping for your interest(s)... what interests you?

- Write their questions and then help to navigate to those pieces
>> - go to the area, talk about what is needed, if it explodes, try to get back in line.

- Shannon was talking about looking through a "lens" and then following that through to the end. Meaning, pick a flavor for the demo or for the question and then follow it through. Help the flavor maintain itself while looking through that lens.

- Being able to link out to research (showing the need and how it can help). Giving some of the pieces backing.

- Multi learning in an awesome tool - videos, graphics, icons, graphs, etc.

- Settings for the demo... what do they call _______ (fill in the blank) - corps, locations, customers, parts, salespersons? Make the changes and then save in session scope for the current demo. Be able to reset as needed. Along those same lines. They could fill in a background image (overarching flavor), show/hide certain tiles (navigation buttons), and setup the correct naming for the demo. All of these settings could be part of a custom demo. That way the presentation could already be speaking the clients language. If you got fancy with it, you could even swap out demos, step-by-steps, key features, etc. Each business vertical could be different and/or have different options.

Currently you can pull an employee report here: https://data4.adilas.biz/top_secret/secure/printable_vendor_list.cfm?type=3&status=1&pageType=main&id=0

which is great because it is snow owl. One client asked if more payroll info could be viewed ie department as a column. 

Making phone calls and chatting with our guys. Made calls to both Chuck and Eric and chatted for a bit and answered some questions.

Steve and I were working on his cross corp aggregated daily sales totals. He is passing data back and forth over an internal API socket. Working through some of the logic. Steve is doing a great job.

We met and checked in with Cory about some projects and some needed quotes. Steve and Cory ended up talking quite a bit about payroll, taxes, cost accounting, etc.

- Options for bulk payroll calculations. Maybe be able to do 10/20 at a time and bulk submit for processing. We talked about some of the variables like hourly, salary, commissions, child support, 401K's, meal plans, etc. There are a number of variables that play into payroll and payroll calculations.

- We also talked about bulk printing checks and processing things in bulk. We do great one by one, however many of our users want to speed things up and play in bulk.

- Need for a cashflow statement

- Small talks about financials and plugging starting numbers. One of the topics was - yes, you can do it... but how much detail do you want along with it? We can plug numbers but if you want drill-down details, you need some more info.

- What about customer attributes and being able to add flags and tags to the customers.

Meeting with Chuck, Steve, and I. We went over some of the new screenshots and I took a number of new screen clips. We talked about the videos that Chuck had created. He will re-render them later, once he gets a full version of the software studio that he is using for capture. Steve suggested that Chuck look at some of his brighter colors and help soften and/or tone them down a bit. Just a suggestion. We also talked about more settings and getting a sign-off from Marisa on the flow and functionality. That is our next major stepping stone. We will keep refining things until we get that sign-off. From there, we will start moving to actual code.

If you want to see the mock-up videos for the camp adilas project, click here.

We also spent some time talking about the upcoming Bridgerland demo and what we wanted to do there. I proposed a few ideas, we drew some loose sketches, and setup a new time to work on the project. Leaning towards a configurable presentation gallery vs a perfectly straight in-line presentation. Lots of fun ideas and concepts.

See attached for a number of new screenshots.

////////////////////////////////////////////////////////////////////

Notes from Chuck - sent via email on 11/13/19. I thought that they would go good here.

I had a meeting with Marisa and Danny today at 11-12.

Here are my notes from the meeting.

Overall they are very impressed and happy with the new colors and setup of the current layout
 
Updates that I need to do:
- Marisa is going to think on a better verbiage for the split sites setting.
- Need to add a setting for a waitlist for those who have already created a reservation but want a different site if it comes available.  For example if they are currently in a site with only electricity but would also like one with water and sewer hookups if it comes available
- A way to merge duplicate records (in case there was as misspelling on a record) - this isn't an essential launch feature but would be nice to have
- Add (FT) behind RV icons on sites to be more specific
- When the check in or out button on sites is clicked it will launch an invoice so the user can see if the customer has a balance and needs to pay in which case it will go to a payment option, or if the customer is paid in full the user can look over the invoice and then email or print an final invoice for the customer.
- I want to redo the layout for the user setting as it's confusing
 
At the end of the meeting Marisa was asking a time table for completion as she is excited to sell it!  I told her "maybe spring, and that I really didn't know".  - hope I wasn't overstepping on that :)  she is really excited to get it out.

Made a call out to Dave Forbis, project manager. Spent some time updating some black box code for Scott Jolley dealing with invoices and tax breakdowns and showing customer loyalty points.

Danny and I met up over the morning GoToMeeting session. We had some struggles and switched over to a Zoom session. We were trying to get his local development environment up to speed. It was having problems with pulling in sub inventory and running the basic shopping cart. We got it fixed and he is off to the races.

- We are looking at the next major steps in the building process.

- We need to get off the single instance of our program running. We are trying to get to a clustered type configuration/interface.

- This is a list of the shared resources on the servers

- images (12 photo galleries), logos, alternate logos, watermarks, csv, some PDF's, part categories may have images, snow owl theme has some defaults, ecommerce default images, browser tab icons, images out in ecommer land (sending file references through API sockets).

- To pull it down a bit, images for the 12 players, look and feel stuff, custom utilities (csv's and PDF's).

- The CSV files are created and used immediately.

- There are some PDF stuff like labels, merging into multiple labels, public wavier type stuff, barcode images, QR code images

- Name for the project - shared files service

- We are going to create a shared file service object - to start with, we want the services to look to the older, shared folders, for these assets and/or files (images and what not). At some point, we would like to switch out this service so that it could point to the new location. We want the backend pointer to be flexible so that we could change it if needed.

- At some point, we will actually need to move all of the resources to the new location (say the content server). This could be a pretty big migration process.

- There may be a series of requests that build and save things locally (just like normal) and then it also queues up another request to sync and/or update on a different storage location.

- If we make a request to this service... what do we need to tell it? For sure corp id, server name or server address, what files are needed, etc.

- Some of our shared files (such as images) are used and called in different ways. For example: Parts are dealt with differently than invoices and those are different then customer images. All 12 main players are slightly different. We would need to standardize those things. We could use a custom tag that interfaces with the service layer.

- Potential to set some of these shared file paths in the session scope and then build all of the pages based off of that. We are really interested in the main source or location for the URL. The main login or switching corps are both major triggers that we need to catch and reformat the URL to those shared files. Once we have it, through the service, we store it in session scope.

- The init phase - we need a reasonable default value to start with. We talked about using corp 1, 22, or 53. Long story made short, we need a safe starting value and/or default.

- What about white label options. We talked about using a default corp of 1 (unassigned). We also talked about default logos that are not adilas specific. An idea from Alan, each person is tied to a single home planet (home corp), maybe use that as the inti or default look and feel until they say something different by switching corps.

- It might be good to go in and get a precise list of visual elements that are needed. At the same time, we may want to make all of these visual elements non brand specific (looking towards more white label options).

- We also talked about the fact that eventually, we want to split out the users from the different corps. They would have a master user id and then be tied to other local boxes and databases.

- We could build an automated process to help migrate some of those pieces. At the same time... we could standardize the names of the logos, alternate logos, and watermarks. We could rename some of the assets as needed to help standardize things. We talked about standardizing the logo name as well as the logo extension (say .png as a default).

- There are a ton of image file format tools out there. Originally, we were limited to certain file types and options. Not some of those limits have been removed.

- As a side note, we have a need to do multiple file uploads.

//////////////////////////////////

Switching to a group project type build out

- Turning to the building and training process - Wayne really wants to get some of the test driven design in place and get the guys doing testing and passing those tests.

- Baby steps - add a parameter, go test, add a parameter, go test, etc.

- Trying to instill best practices

- Wayne will have a testing repo called "testing_adilas" - We will all use that repo (code repository) for all unit testing.

- Wayne is going to be focusing on the "process" of doing this as a group. There will be some mistakes and problems, but we will use those obstacles as learning opportunities.

- There may be some homework projects and passing pieces off to others in the group.

- Letting everybody dive in and write some code.

Shawn and I were supposed to touch base today but that didn't happen. I ended up doing emails, checking on a duplicated user on data 8 (got it fixed), and recording some notes.

Russell's secret formula to success is: To pray hard, to work hard, and utilize the strengths of those around you.

We were working on a few small CSS and header/footer changes. Also some light tweaks on the developer's notebook and the adilas community funded projects.

Looking at some small bugs with the cross corp invoice to PO functionality.

Recording notes from yesterday and transferring notes from post-its to the developer's notebook. Emails and other stuff.

Went into Smithfield to work with my mom and dad on a business called Moore Repurposing. They basically get donations and then take the items and try to sell them and/or repurpose them. They are going to be using adilas as their backend tracking solution. We spent some time talking about what is needed, how things will work, and some other overarching goals. We then sat down at the table and started writing out a virtual checklist to help them know what to and how each thing tied in to the bigger puzzle. Super fun couple of hours. We made a to do list and then started working through some of the pieces. Lots of our work was done with paper and pencil/pen to start with and then we moved to the computer once we had a plan. Good stuff.

With Steve on the morning meeting. Walking through a process by baby steps. Helping to educate the client along the way. Taking the time. That is awesome.

Sometimes companies almost cripple themselves by putting certain pieces of data in all of these different pieces. The more the data is able to be in a centralized location, and accessible by all (based on permissions), that makes a difference. There is some value to that.

Working on the view only permissions. He is working on customers, vendors, and quotes. He is going in and shutting down some of the editable links. Making some of these sections view only.

- Working on a stacked, layered, and drill-down type learning model. This is somewhat of a presentation gallery of sorts.

- Start gathering these resources and help to organize them. That is my goal.

- Let's look at some of the levels... Thinking of the ice berg type analogy (show a little bit and then expose more as needed)

- Top level -- similar to the adilas café - work, train/play, learn, participate in the community, sell, buy, research

- Flipped over to Word to build an outline. Hopefully see attached...

We started to build out a visual tile board based on the adilas formula flyer. Here is a link to the older flyer...

https://data0.adilas.biz/adilas_formula.pdf - adilas formula flyer

We had a small discussion about world building and how it sometimes confuses people - almost too bold and too abstract. We talked about ways of softening that. For example: Say the different stores in a mini mall or different departments in a big organization. In a way, those smaller pieces or entities are building their own world.

What if we approached it by saying... currently you need a POS, an ecommerce package, a CRM, an ERP system, accounting, etc. Inside of adilas we allow you to pull those things all together under one umbrella. This becomes the virtual universe for that company. Show them how we can pull all of these things into one system. We are also really flexible, configurable, and nimble.

Results is one of the main four topics (results, business functions, application players, & core concepts). The results (what you are looking for) are huge. This side plays more on the emotions and wants of our users.

Link to a fun Ted Talk by Simon Sinek - https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action?language=en

Here are a few notes from the Ted talk:

- Why - Share the why

- The golden circle - 3 levels - innermost level Why, middle level How, outer level What

- Help people learn from and be driven (of their own free will) from the inside out (why, how, what)

- People buy why you do it, not what you do

- Attraction of people - people who believe what you believe

- Driven by a cause - willing to put in and work with blood, sweat, and tears

- Prove what you believe by why you do it

- Helping to take and push a cause further - Once again, because they want to...

//////////////

Going back to the sales document that we were working on (notes from above), Chuck sent me an updated link. Click below to see the Adobe XD layout. Pretty cool.

https://xd.adobe.com/view/e01cc5b5-caa2-4b84-4727-58b1b2ea764e-962d/

Steve and I worked on his API sockets for cross corp aggregated data. This is still a custom API socket, but he is making progress and hopefully having fun. Good stuff. We ran the update to push the new table live. We were then testing things live and doing some light debugging. We had to switch between GoToMeeting and Zoom due to Internet issues for our meeting. We ended up just using our phones for the audio (talking) stuff.

Bryan and I didn't end up meeting due to schedules. We were going to be working on some cross corp code for invoices to PO's. I ended up recording notes, doing images, and even reviewed a Ted talk video. See other notes from today for more details.

Emails, reviewing some new stuff from Chuck (sales flyer stuff), and recording notes.

Steve, Danny, Eric, Alan, and myself were on the morning meeting. Danny had questions about how to be more productive in keeping project notes, searching for things, and getting to the project details quicker. We mentioned that he could build his own top payee links (custom button) or write the id number down and then be able to go from there. We also briefly talked about having a super flexible quick search option for expanded time search. Something that would search elements of time and be able to search the mains (normal titles and notes), the sub dates and times, the sub comments and notes, the sub flags and tags, and other pieces. That would be really cool. Maybe a time-all search or something like that.

Eric and Steve were talking about new rules for the customer loyalty points and adding in some new rules. Eric is getting close on that stuff. They spent some time talking about discount rules and other advancements dealing with the special accounts and the customer loyalty points stuff. We are making progress there.

Steve and I were talking about an upcoming demo and some of the needs and direction of where we are wanting to go. Steve offered to fly out and help with setup and what not if needed. We went over a few items and talked some strategy.

After that Alan and Steve were working on some Metrc packaging stuff.

Bryan and Molly jumped on and we looked at a small bug in the cross corp invoice to PO code. We jumped on live servers and looked at database records and tried to find out what we were able based on simple searches and changes. We then tried to implement the new changes. Bryan is going to put up some small changes and we'll do more testing and go from there.

Went into Bridgerland for a 2nd demo. We were in the main admin boardroom. We had about 10 people. Some of them were the same and some of them were different than last time. The whole demo felt smoother and on a better level. The first one we were fighting against a time constraint and we had multiple people who wanted to see different things. By way of a note, I used Chuck's new sales flyer graphic to help show some of the options that were available. See the link below for a sample (not the actual graphics but at least a taste).

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5211 - some new sales flyer sample graphics done by Chuck

We spent about 3 hours in the demo and covered a number of different topics. I felt like it went much better. Both Chuck and I were there at the live demo. Afterwards, the main college President came and chatted with Chuck and I. He is a great guy and I've known him for years and years. He has always been a great supporter of me and my family. Awesome stuff.

Danny, Dustin, Steve, and I were on the morning meeting. Danny had some Git (code repository stuff) questions. Steve and Dustin were working on some bug tracking. We also showed the guys some of Chuck's new layouts for sales. We had a bunch of fun ideas. Some of the ideas were being able to change the backgound images, changing the main presentation settings, and even being able to click on a link and have it automatically switch background images, verbiage, and settings. A simple little URL switch and all of a sudden, you have a customized presentation. Super cool idea.

On this same line of thinking... if we can flip the demos and presentations really easily, we could potentially use the same presentation gallery to do different presentations for different verticals. We just store the settings, verbiage changes, images, and even options, features, tools, and usage models. That would be super cool.

- Maybe using the ice-down date as a transfer between transactional data to aggregated data... That is a great switch and/or trigger. Similar to the water to ice analogy... The transactional data is kinda loose... Once it gets pushed to the aggregated data, we really want that data to be more stable (more like ice). Great idea.

- What if we had some bulk tools on the transactional side to post and/or lock things down. Once that data is locked down, we can then pull that data across to the aggregated system. Steve was talking about a possible two-part effort. They get to set a date (virtual line in the sand) and things behind that date can't be changed without altering the ice-down date. We also allow the users to lock things down on the transactional side of things.

- On a different note, Steve would like to build things out to a trust level... Making a number of adilas players as dependable cofounders. As a side note, we could use the new customer loyalty points to keep track of a virtual club member point system. They, the special accounts, are already setup like mini bank accounts.

This was postponed due to travel for Alan.

Shannon and I spent the whole time going over the next levels of the outline for the sales and presentation gallery concept. See attached for the Word document with our brainstorming ideas.

Here were some of the ideas... rough outline - all of these were under the main title of "attributes"

1. Attributes
1.1. One System
1.1.1. - What does that mean?
1.1.2. - What would it cost?
1.1.3. - Do I have to pay for different pieces? 
1.1.4. - Modular or all in one?
1.1.5. - Does it really cover all of my business needs?
1.1.6. - Is it expandable?
1.1.7. - How deep does it go?

1.2. Customizable
1.2.1. - Branding
1.2.2. - Look and feel
1.2.3. - Settings
1.2.4. - Permissions
1.2.5. - Page flow and processes
1.2.6. - Add or subtract fields and values
1.2.7. - White label
1.2.8. - Custom dashboards
1.2.9. - Custom reports
1.2.10. - Custom code
1.2.11. - Custom design
1.2.12. - Custom database

1.3 Powerful
1.3.1. - Business Functions
1.3.2. - Tools
1.3.3. - Features
1.3.4. - Processes
1.3.5. - Automation
1.3.6. - Exports of data
1.3.7. - Custom reports
1.3.8. - Mobile
1.3.9. - Web based
1.3.10. - Adaptability

1.4 Dynamic
1.4.1. - Relational model (one to many)
1.4.2. - Scaleable
1.4.3. - Flexible
1.4.4. - Custom naming conventions
1.4.5. - Custom field options
1.4.6. - Show/Hide settings
1.4.7. - Settings
1.4.8. - Configuration options
1.4.9. - Navigation
1.4.10. - Everything

1.5 Cloud Based
1.5.1. - Any browser
1.5.2. - Access
1.5.3. - Storage
1.5.4. - Up time
1.5.5. - Auto upgrades
1.5.6. - Anywhere
1.5.7. - Any time
1.5.8. - Any device
1.5.9. - Convenience
1.5.10. - Centralized data
1.5.11. - Collaboration
1.5.12. - Minimal IT requirements
1.5.13 - Paperless office

1.6 Unlimited
1.6.1. - Users
1.6.2. - Usage
1.6.3. - Locations
1.6.4. - Invoices
1.6.5. - Customers
1.6.6. - Inventory
1.6.7. - Storage
1.6.8. - Processing
1.6.9. - Corporations
1.6.10. - Advantages
1.6.11. - Access
1.6.12. - Potential

1.7 Results
1.7.1. - Analytics/stats
1.7.2. - Reports
1.7.3. - Data
1.7.4. - Business Intelligence
1.7.5. - Exports
1.7.6. - Monitor business health
1.7.7. - All Data Is Live And Searchable

1.8 No Contracts
1.8.1. - Month to month
1.8.2. - Client satisfaction
1.8.3. - No licenses
1.8.4. - Yearly review
1.8.5. - Self serve model
1.8.6. - Full access to your data
1.8.7. - No limits (devices, users)

11/20/19: Steve sent a note with data- please see attached.

Cory emailed Steve Mitchell asking for more data to demonstrate what exactly is being pulled from the CA DL to determine what needs to be fixed/edited.

From Steve Mitchell: We are trying to swipe in new customer info at Euflora Long Beach and apparently everything is jumping into the first data field.

From Brandon: One of the main pages will be top_secret/custom/process_drivers_license.cfm - pretty heavy in script and string manipulation.

- Camp adilas overview - see screenshots - lots of new work on the mobile side of things. Exploring all of the different screenshots and options.

- We spent some time and did a small review of the demo yesterday.

- We still used world building but we related it to pieces that they could understand (going from full abstract to hey, this makes sense - speaking their language and at their level). That is huge. We talked about how we could do the same thing in a more general way.

- The demo felt more prepared and more simplified. That was good.

- One thing that came up... tracking history and seeing who does what in the system (the hidden audit trail and use of different logins). We introduced this later on in the demo but they really got excited about it. We may want that to surface earlier as what is going on and a key feature.

- When doing the ecommerce demo... that was a little rougher. We had to keep switching between systems due to images, settings, and being able to flip to the more pretty and mobile ready version. We had a few rough spots in this part of the demo.

- Lots of talk about the permissions page (aka the football field of permissions). We want to get the permissions broken down to a better level that is easier to understand and to copy/apply. They (our users) are wanting to break them (the existing permissions) into custom permissions, sub functions, and other functionality. Deeper control, yet a simpler interface and experience.

- We spent some time and talked about the new sales outline that Chuck is working on. We used it in our demo, our morning meeting today, and almost every other meeting today. Pretty cool. We like the direction that we are headed. Click here to see a small sample.

- As we build things out (in the sales flyer)... we would like to connect these to videos - we talked about keeping things generic and highlighting the pieces vs our brand (white label options).

- There were some conversations about talking about world build and getting it into a more simple thing analogy right off bat. Maybe even some scenarios that deal with beginner, intermediate, and advanced concepts. Once again, help it be more consumable.

- Brainstorming on world building ideas... We could start with a web layout, index page and then it goes from there, or icons and a more structured layout. We spent some time talking about how to help get our users and others to get their heads around the concepts. We ended up watching two videos to help us get into the frame of mind. The links are below.

http://www.brandonmull.com/site/video-bestbook.html - Brandon Mull (author) - What makes a great book (world building concepts)

https://www.youtube.com/watch?v=RN4Ka0IXdp0&feature=youtu.be - Shannon Moore - System thinking - fun video from an older training session

Molly and Bryan joined the meeting. We introduced them to Chuck (designer) and showed them some of the new things. After Chuck left, we looked at the cross corp invoice to PO functionality. There were just a couple of tweaks that were needed. After we figured out what was needed, Molly left and Bryan and I added some code and then pushed files to all servers. We are making progress.

Cory jumped in and we did some catch-up. She had a few questions about some projects that are either all the way done or almost done. We got updated on some of those pieces. We also did some light training on stock/units and opening up both ecommerce options and API socket options for stock/units. Lots of good things are happening.

We had to unlock an invoice to allow a client to go in and edit things. We unlocked it and recorded a history note that stated who did it and why. We don't normally do that, but it was a valid client request. We added the history note to cover our own rear ends. I'm super grateful that Cory is grabbing the ball and running with it. She is almost singlehanded running with the project list and keeping us on target. She is doing an awesome job.

Recording notes and adding in new mobile screenshots for the camp adilas project. See this element of time for the new screenshots.

Pretty quite morning. Both Danny and Eric popped in briefly. Mostly just a small work session and doing normal day to day stuff.

11/25/19: Check with Bryan to see if they are looking at a custom solution.

Josh has had requests to connect e-commerce to discount engine.

11/20/19:From Paul:  I'm reaching out because we are running into a bit of an issue with our customers and Ecommerce. We currently do not post our weekly specials to our Ecommerce page due to the limited availability of certain products, etc. We would like to begin posting these online however what we will really need is the ability to set "maximums" for items that way customers can only take 1 unit, for example, if we only have 10 vs trying to order all 10 and others wont be able to purchase any which is pretty unfair. Does Adilas currently have this feature where we can set maximums for items in inventory or is this something that you would have to program for us?

Cory is thinking if there is a way to connect the discount engine to e-commerce then this could possibly solve the issue, as limits can be set in there to determine how many of one item can be sold per cart or per line item.

11/25/19: Drea's client had the idea to manually create a PO for the 5g and flex grid it back to the plant. That way the plant is still with its batch and available to be harvested with the rest of its weight.

11/20/19: Drea has a client who is non metrc who needs to pull 5 grams out of a plant but doesn't want to harvest the entire plant- wants to keep it with the rest of the batch. Currently there is no way to do this. Cory suggested harvesting the one plant, and keeping notes the entire way with the PO # for that plant to be able to track it and ultimately add its weight in on the final internal build. Not ideal, but that was what I came up with.

Original plan was to touch base and work with Shawn on some payroll stuff. I tried calling and reaching out but was unable to get ahold of him. We'll try again next week. I left both some voicemails and text messages.

In the mean time, I replied to emails and did some light tech support stuff.

Meeting with Russell over a Zoom session. We worked on a code merge for the adilas community funded projects and the developer's notebook. We went in and did some testing, both without a valid login and with a valid login. We made a few changes and got the code pushed up to the servers.

We also talked about some new projects. We are going to be sending Russell on a project to help us develop the next round of the data tables. The other project that we are going to have him work on is some research to help restructure the main adilas business. Steve has some fun ideas and wants to include some features with cofounders, dependables, trust, coop, etc. Some fun ideas.

We started out the meeting this morning with a question from Dustin. He has some super complicated JavaScript going on one of his pages. As we got into it... we found that one of his functions was creating some hidden form fields but the names were the same (duplicated) which prevented some of his other JavaScript from working. We figured it out and he was off to the races again.

Steve and I had some talks about custom code and even ways of getting at some of the custom code that is outside of the main adilas.biz framework. For example, one of our developers has been working on a number of custom Windows tools (done in C++ or other languages). We don't have that code in our code repository, that developer owns and controls that. If changes are needed, he has been doing that. We have a scenario where we need to make a change but the developer is super booked on another project. This is the first time we've faced something like this. Just talking about options and what we would like to do. No major plans, just having some talks and discussions.

Towards the end of the meeting, we had some other developers join us for a group training meeting.

Team training lead by Wayne. Talking about unit tests and test driven design. The original meeting between Alan, Wayne, and Brandon may be seen on this page:

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5192 - prior and original notes for the project

Those who were in the meeting were: Brandon, Steve, Alan, Bryan, Danny, and Wayne.

- Unit tests - Using Ortus Solutions and TestBox - Click here for a link to TestBox. In TextBox, all tests begin with the word "test".

- On unit tests, you virtually fake everything else and just test the piece that you want. Super important for complex steps, phases, status changes, variable scenarios, etc.

- On the naming convention for tests... tell it what you are doing, what you are looking for, and what to expect. This is all in the test function name.

- We went into some light instruction on doing some testing.

- Google Wayback Machine - we were having fun looking back in the past (what the Internet looked like in the past). We went way back in the adilas history to 2008 and 2010 and were able to see some archived screenshots. Kinda fun.

See attached for a recording

///////////////////////////// - different meeting

After the main training was over, Wayne stuck around for awhile and talked with both Brandon and Steve. Lots of fun ideas and experiences were being shared. I wish I would have been recording things. Here are some of my notes.

- We talked about project management and writing out full specs on certain projects. Sometimes that is super tough due to limits of knowledge and building what is wanted vs what is being specked. There is a difference and sometimes you don't know until you get into things. It is so important to take more of a try storming type approach vs a strict requirement based set of rules. Things get pretty dynamic.

- How could we sell what we have without breaking the bank? That is huge question. As part of this conversation, we started talking about the SaaS model (software as a service) and how that model is somewhat taking over due to the benefits. We keep making it better and better over time.

- Some of the key things that are driving our sales are word of mouth, businesses expanding (existing companies needing more systems), etc. Not a whole lot of cold calls and direct selling currently.

- Expectations and scope of what is expected... currently, there are no real defined operating parameters. That creates a problem.

- Metrics and controlling what the expectations are and then playing along with that. That could be number of users, locations, invoices, inventory items, bandwidth, storage, processing, etc.

- What are the benefits that the clients are looking for? Figure that out and then show them what you are helping them with. That validates the cost and satisfies a need. What is the value to someone and how do you show/portray that value? Value means something different to every person.

- Going back to the wayback machine - One of the screenshots showed some super general stats, such as: x number of invoices, x number of PO's, x number of expenses, x number of deposits, and total pennies coming in and total pennies going out as of that date/time when the page was loaded. Kinda fun. People want to be able to see their stats.

- Small discussion on who pays for what... someone comes up with a  good idea but then who pays for that? Often that cost is passed back to the core adilas team and we are then tasked with the building, funding, supporting and other pieces. That gets really heavy some times.

- Just an idea... what if we showed what we are contributing to the core... say the new customer loyalty points or the discount engine - Those were thousands and thousands of dollars and were new free features that everybody just gets. We are building on this thing everyday.

- Another subject was... if we build something and nobody else wants it... then who pays for that? Or you have a company that wants something and they request something custom and then nobody else even knows that exists. In that scenario, other people would love to use it, but they don't even know about it. That makes it tricky, especially for who is going to fund that new development and/or maintenance.

- Long story made short, people want their data and access to that data. The battle keeps going.

- Sometimes we only recognize things that are not going well... everything else seems almost a given (what is going good). Well, it takes time and money to get all of those things to run smoothly. That's a challenge.

- Wayne was saying that Steve and I's goal is to help other people catch our vision and then run with it. The trick is getting other people to want to play that game along side with you.

Shannon came on at 11 am and was ready for the meeting with Brandon. Steve, Brandon, and Wayne were still on a different meeting. Shannon had fun listening in. Lots of fun stories.

Once everybody else left, Steve and Brandon kept talking about ideas and options for awhile. Most of it came back to working our plan and being willing to keep pushing on things everyday. We have lots of ideas and ways to help speed things up, but mostly, we just need to keep pushing and working the plan. Building towards the dream and towards the vision.

Lots of talks about where we are going and how best to get there. Good stuff.

- Chuck is working on details and nitpicky things on the camp adilas project. Things like layout, margins, spacing, etc.

- On the extra services... Chuck is seeing that there will be an extra page for a mini shopping cart for general items, additional services, etc.

- We also talked about some of the next steps. These are in no particular order, but we talked about getting sign-off's, locking down the project scope (aka round 1 vs round 2), creating tour/marketing videos, starting to build our own CSS libraries, prepping for the next level or next project.

- Small note about videos. We talked about some sort of fund raising campaign and the pros and cons to that. Our current plan is to make the videos for us... either to help sell or pitch the product or to show people what we can do as far as a full end to end layout and design option. Both of those are really cool and will help us gain ground. Good stuff.

Met with Jonathan today about some of his layout ventures and site mapping and exploration stuff. We are making great progress. As a fun side note, in his demo today, he is hitting on almost everything that we have thrown at him via ideas and/or requests. I'm really impressed. And the best part... we are having fun along the way. Here are some notes from our meeting.

- We went over some of the things that Chuck (another designer) is working on and how that plays in.

- https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5211 - sample screenshots from Chuck's sales work (presentation gallery)

- Jonathan then did a demo of his new layouts and I took 20+ screenshots. Super cool. I challenged him to create a virtual walkthrough video so that I could show it to other people. I'm super excited about that. Lots of refinement and making things more and more simple to handle and navigate.

- We talked about design systems or a system style guide - CSS - These are basically documents with visual elements and technical specs to help everybody on the team be on the same page. Helping to make the layout and look and feel all congeal and work together.

- https://data0.adilas.biz/css/ - Small link to some of our existing CSS style sheets - This was a simple page that has a bunch of dummy data on the page. We will use some of these pieces to create the system style guides and design systems.

- After we get some of the styling fixed and lined out, we'll start going through the app and working on flow and processes. We will hit the most used sections first such as clock in/out, shopping cart, searching for items, invoices, quotes, etc.

- My goal - if we can sell what we have and keep it powerful, easy, and pretty. It is already very powerful. We need some loving on the easy and pretty part of that equation.

- Making it easy so that we can go to the masses. We want to open things up a bit. Along with this, we realize that some of our legacy clients may never switch, but all of the new clients will start out on the new features and hopefully enjoy and gain from those new developments and new design UI/UX (user interface and user experience stuff) and love the products. We will keep heading in that direction.

Danny was ready to push up some of the view only permission changes. We got in there and looked around. He is about 80% done with that project. We talked about a few things and I spent some time listing out a few changes that I would recommend. For his first multi-page project (over 20+) he is doing awesome. Most of Danny's other projects have been a single page or a custom PDF label or something like that. I am impressed. Good stuff.

The 4 places that he is working are PO's, vendors, customers, and quotes. Just by way of a note, we may need to go back through some of the pages and actually remove some of the columns due to the removal of the drill-down links and navigation. This could be done later if needed.

Recording notes and doing emails. Lots of moving pieces. It is fun but it can be a blur of craziness as well.

Recording notes and uploading images and screenshots.

Uploading screenshots from yesterday. Over 40+ screenshots were taken yesterday during different meetings.

Current new VPS model environments, 1 for BTC and 1 for current new adilas clients. 

All Bio Track state system API updates.

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

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

Possible ideas for clients not on metrc would be to simulate some of metrc process. 

For the PO, create PO- instead of current way, you would have an interface to create the main part similar to the small option on the bottom of the metrc add new inventory page. Once you filled that it, you would go to the mapping page, like for the metrc api. it would have all of the parent items for that vendor and fields where you could enter quantities, similar in look to the update po fields/boxes. This would create the new subs, and you could also add the sub attributes on this page, so you don't have to go back in to each sub on a PO and add sub attributes ie strain, testing, etc.

If the parent doesn't exist, there is a link where you can add new, just like currently on the api mapping page. 

Some people find the shopping cart overwhelming, even the kush cart. This would create settings or a template where you could check boxes, or uncheck boxes to determine what showed up in the shopping cart- similar to the boxes you can check or uncheck for the fields you want to show for customers. Or, the boxes that you can check for some of the advanced searches. This would allow clients to have only the info they want to see in the cart, which would make it appear simpler even though all of that data is still there.

The current classic cart has the most functionality. The Kush cart looks the best. The short and sweet is the most modern, but we want some cart options that have settings, tabs, ect. We also have mock-ups from Russell, Jonathan Wells, and others. We really want to see what we could come up with here. Brandon has more information and directions, once someone is assigned to this project.

This could tie in with the custom cart settings, which would allow you to choose to see discounts in the line descriptions.

Currently, if you use bulk discounts, update the cart, and then go in a second time and edit the bulk discount and update the cart, the second time you can no longer see what discount you awarded. It is still being calculated but no longer shows up in the line item. Client would like to be able to see what that discount was.

Please see attached images.

This was tackled with another project.

Possibly related to the custom cart settings. Checkout options are available in the settings.

When you bulk print labels in a cart, you have to take multiple steps and switch printers multiple times. Click 6 times. Could the bulk print labels screen show up when you click checkout (could it auto print for medicated items?- I don't think so) or could the screen pop up then and you print, and then you make a payment, flip the printer to the receipt etc. Trying to speed things up. Client willing to pitch in on making this easier.

4/20: 27.44

from 4/14: 30

Up to 3/1: 26.48

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

11/18: 15.56

11/17/21: 17.5

10/21: 12.08

10/18: 38.04

10/5/21: 27.07

John is working on this:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Buy 2 Get 1
Buy 5 Get 2

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

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

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

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

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

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

Discounting based on key words.

Josh popped in and was asking about simple bug fixes. He wants to be one of the guys to help respond and fix some of those smaller bugs (say 1-4 hours - little mini projects.). Yesterday, he and Alan knocked out a small one that our users needed. We were shooting around some ideas and challenges. There was some talks about ways to gather the help/support info from the user on a per page basis. We also talked about who services those tickets and how we track them. We are thinking about elements of time and using that tool to hold and process the help/support tickets.

Danny chimed in and was talking about the tech support process and also the follow-up after the fact. Building customer loyalty by providing the fish to the seal (reward) and following up. You gain a lot of ground that way.

We did a small demo of some of the new screenshots from Jonathan. Lots of good ideas and options. Steve really liked a number of the new concepts that he was brining into the mix.

Build and break, build and break. This seems to be a reoccurring theme. Build it, let people use it (almost even abuse it), when it breaks, you rebuild it and start over again. You have to do this over and over again.

Cory jumped in and we started to go over the list of adilas projects. The ones on the call/meeting were Josh, Cory, Steve, and Brandon. We created a new priority of 11 and started putting in smaller projects and bugs into that area. We also created a new small bug report, just for Josh to look at and start chipping away. Lots of good talks and communication going on.

People have been asking for more simple interfaces. This deals with bringing in inventory and running things through the shopping cart. Super simple stuff. They either want super simple preset interfaces or a fully configurable interface where they could point and click and show/hide things.

towards the end of the meeting, both Josh and Cory were talking about projects and list and Steve and I were on different calls and meetings. That is super cool as well. We have a lot of really good people playing the game with us. That is awesome.

Eric called in and we chatted over the phone. I got on his branch and started looking over some of the new code. I spent most of my time on the database updates. Looking over some of the new code for customer loyalty points and some new rules. Eric is getting ready to add three new rules... They are exclude customer types, program end date, and exclude in-line discounts.

Towards the end of the meeting, we switched gears and started to talk about data warehousing and deep aggregated totals and report optimization. Eric started talking about dimensional mapping or a dimensional schema (star schema or data cube - intersection of points to a specific fact table) - 3d data modeling. Eric and Steve started getting into the quick and dirty of what Steve is working on. Super cool custom mini projects working on pulling in daily sales totals.

Adding in screenshots to the latest notes from working with Jonathan. See the link below for details and screenshots.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5221 - latest layout screenshots

We started out talking about options. Both Steve and Alan were on the first part of the meeting. Around 3 pm, Steve had to take another call and dropped off. Alan and I spent the rest of the time working on the project. Here are some notes that we took. We ended up making a new corp-wide setting and coding a quick and fast sub inventory search option.

- Ways of speeding up the cart search, especially for sub inventory or known sub inventory scans and barcodes.

- We could use session switches - are we searching subs or parents?

- On the seaches... switch the order. Maybe start with subs and then parent items. Currently, the different pages do different routines to search for the inventory values.

- Indexing of the database tables.

- Possible other table to show a summary of the main packages. Millions of sub transactions could be summarized into hundreds and thousands of actual packages, not millions (all of the sub line items and details per invoice or PO).

- Too many likes & wildcards. We looked into the normal part/item number searches. Each one has multiple places where we do like or wildcard searches. That slows things down. It does make is super flexible, but it does slow things down.

- See corp-wide setting #37 about the cart quick search drop-down options. We ended up adding a new one called Sub Barcodes. It will be launched when the new code gets approved and released.

As a fun side note, Alan and I built this whole piece together. I was coding and Alan was coaching me and pair programming with me. Good stuff.

Working with Alan on splitting up some new code into DAO's (data access objects) and services for sub barcode searches. We built it out yesterday using normal tag based code (more traditional code) and then today started to go through things and refactor the code into more object oriented code using script vs tags (way of coding a page or functions). Alan is teaching me some of the new or more modern skills.

Alan did some team training on if statements, switch statements, for loops, for each loops, while loops, and do while loops. We had Alan, Brandon, Steve, Danny, Josh, Russell, and Wayne on the meeting. Here are a list of smaller sub videos that were shown. Each of these are less than 4 minutes each.

https://youtu.be/IRY9B43QbBM - if statements
https://youtu.be/c6ObO5Ind8U - switch statements
https://youtu.be/jxfhdJsAD8I - for loops
https://youtu.be/o6S6NMrIPC8 - for each loops
https://youtu.be/NMoOKoAMJSI - while loops
https://youtu.be/9lTQlrbtHP0 - do while loops

See the attached video link for the full 1 hour training meeting.

Brainstorming with Shannon on sub features in the business functions realm. We spent some time brainstorming about sales, inventory tracking, POS (point of sale) features, and CRM (customer relationship management) options. See attached for our working outline document.

Working on ideas for the presentation gallery and trying to break things into smaller pieces.

1. Business Functions
1.1. Sales
1.1.1. Inventory tracking
1.1.1.1. Start to finish inventory tracking
1.1.1.2. Item usage histories
1.1.1.3. Unlimited
1.1.1.4. Reports, exports
1.1.1.5. Images, scans, multimedia
1.1.1.6. Units of measure
1.1.1.7. General items
1.1.1.8. Serialized items (stock/units)
1.1.1.9. Time or services (unlimited)
1.1.1.10. Fulfillment
1.1.1.11. Sub inventory (parent/child)
1.1.1.12. Transfers
1.1.1.13. Internal builds (manufacturing)
1.1.1.14. Ecommerce settings
1.1.1.15. Updating inventory counts

1.1.2. POS (Point of Sale)
1.1.2.1. Invoicing
1.1.2.2. Quoting/Ordering
1.1.2.3. Secure shopping cart
1.1.2.4. Barcoding
1.1.2.5. Custom buttons
1.1.2.6. Discounts & campaigns
1.1.2.7. General items
1.1.2.8. Serialized items (stock/units)
1.1.2.9. Time or services (unlimited)
1.1.2.10. Locations & tax settings
1.1.2.11. Hardware options
1.1.2.12. Custom designs & layouts
1.1.2.13. Ecommerce tied to POS

1.1.3. Customer options
1.1.3.1. Loyalty points
1.1.3.2. Preset discounts
1.1.3.3. Purchase histories
1.1.3.4. Payment history
1.1.3.5. Accounts receivable
1.1.3.6. Customer billing
1.1.3.7. Online bill pay
1.1.3.8. Images, scans, multimedia
1.1.3.9. Customer accounts
1.1.3.10. Reports, exports

1.1.4. Reporting
1.1.4.1. Sales reports
1.1.4.2. Profit reports
1.1.4.3. Daily/weekly/monthly reporting
1.1.4.4. Per locations, per salesperson
1.1.4.5. Deposits
1.1.4.6. Purchase histories
1.1.4.7. Trending items
1.1.4.8. Automated P&L
1.1.4.9. Exports
1.1.4.10. Advanced filtering
1.1.4.11. Save your own reports

1.1.5. Payment solutions
1.1.5.1. Normal POS options (cash, check, etc.)
1.1.5.2. Merchant processing (credit cards)
1.1.5.3. Online bill pay
1.1.5.4. 3rd party payment solutions
1.1.5.5. On account (customer credit)
1.1.5.6. Custom configurations

1.1.6. Ecommerce
1.1.6.1. Real-time (live) inventory counts & tracking
1.1.6.2. Fully integrated systems
1.1.6.3. Online product purchase
1.1.6.4. Customer login portal
1.1.6.5. Online bill pay
1.1.6.6. View histories, statements, orders
1.1.6.7. Fulfillment
1.1.6.8. Fully configurable (settings)

1.1.7. Other special functions
1.1.7.1. Work orders
1.1.7.2. Layaway
1.1.7.3. Recipe/builds
1.1.7.4. Hidden line items
1.1.7.5. Reoccurring
1.1.7.6. Barcode/QR code generators
1.1.7.7. Emailing capabilities
1.1.7.8. Discounting engines
1.1.7.9. Quantity tracking & thresholds
1.1.7.10. Loyalty points
1.1.7.11. Gift cards

1.2. CRM
1.2.1. Sales & purchase tracking
1.2.1.1. Payment tracking
1.2.1.2. Monies owed
1.2.1.3. Accounts receivable
1.2.1.4. Purchase histories
1.2.1.5. Invoices/quotes

1.2.2. Customer profiles
1.2.2.1. Holds additional information & subs
1.2.2.2. Log notes
1.2.2.3. Additional contacts
1.2.2.4. Reoccurring billing
1.2.2.5. Purchase & payment history
1.2.2.6. Groups & types
1.2.2.7. Preset options - discount, tax category
1.2.2.8. Photos, scans, files, media
1.2.2.9. Expandable custom fields
1.2.2.10. Manage relationships

1.2.3. Customer tracking & follow-ups
1.2.3.1. Unlimited notes & logging
1.2.3.2. Show/hide notes on calendar
1.2.3.3. Show/hide notes in customer portal
1.2.3.4. Purchase histories
1.2.3.5. Accounts receivable

1.2.4. Calendaring & scheduling
1.2.4.1. Elements of Time
1.2.4.2. Reporting
1.2.4.3. Billing

1.2.5. Unlimited customers

1.2.6. Photos, scans, other files & media
1.2.6.1. Unlimited

1.3. CMS
1.4. Expense Tracking
1.5. Payroll
1.6. Calendar
1.7. Data Connection
1.8. Accounting
1.9. Reports
1.10. Business Intel
1.11. ECommerce
1.12. Big Data

Group meeting dealing with camp adilas project. We had Chuck, Marisa, Danny, Steve, and Brandon on the meeting. We are all really excited to see where things go. Good stuff.

- We talked about confirmation numbers and being able to add and search those.

- Being able to change customers after the fact. This could be the main customer or adding additional sub customers, depending on needs.

- If more options are needed, it will be built on top of the existing adilas backend platform - that opens up a number options.

- Report settings - adding prebuilt reports based off of the settings. Being able to tweak things as needed.

- Permissions and fully removing certain icons from the menu systems based on those permissions or lack of permissions. We decided that fully removing those options would be best for this project.

- Mobile and being able to help solve issues on site - this is huge and could be a great selling point (the mobile version of the app).

- We talked about helping with real traffic flow (actual cars, trucks, vans, SUV's, RV's, campers, trailers, etc.). If we can help alter the bottlenecks, that may be a huge help. The mobile app will open up some options there. Some good discussions around that topic.

- Self check-in options

- Digital signatures and disclaimers - other possible customer portal options

- "I'm here" button and then help them get checked in

- Using other adilas reps and consultants to help do other things and provide other needed services or additional options. This could be design, web work, custom code, training, setup, map stuff, etc. All kinds of options.

- Cart settings for scans and presets. Being able to show preconfigured add-on's and normal barcode scanner POS options.

- Being able to set a default home screen for different users. For example: the check-in desk, the gift shop, the reservations desk, whatever.

- We got the verbal green light to move from graphic concepting to HTML/CSS - clickable web mock-up with dummy data. After that gets finished, we'll actually wire the whole thing up via backend server-side code and database connections.

Awesome meeting. See attached for the video recording of the meeting. There are also a number of still screenshots in the photo gallery.

////////////////////////////////////////////

These are some notes that Chuck submitted after the meeting.

Hi everyone,

Here are the notes I took from today's meeting.  Let me know if I missed something.

Notes from meeting with Brandon, Steve, Marisa, Danny and Charles on the design sign off
 
Tweaks that need to be done to final product
 
- Reservation # added to invoice (under Invoice in the upper left corner of the invoice) and possibly use a bar code or QR scan for the invoice to pull up the invoice.
- We can use a setting for a seed to generate the reservation number for example use a date and site number for the seed or something similar
- We need to have the ability to change or split the invoice for different customers.  This can be placed in the settings icon on the invoice
- Have a go to admin that would place the customer back into the Adilas back end if they needed to adjust advanced settings
- Add a vacant filter quick button to the sites page
- Ability to add quick buttons to the menu list.  The customer would be able to add favorite searches or functions to the menu list by choosing an icon and setting up a tool tip.  Setting would be found under the setting icon for each section
- When we get to doing the front end we should look at having a self check-in option that can either be a full self check-in or an I'm here button to notify the user that a customer is there and ready to check in
- Need to look at icons and standardize some of the icons.  Replace the cog with filter at any area that a filter is being used instead of settings.
- Be able to set which cart/invoice section is default (cart, invoice, or scan)
- Make a user that only has access to the pos system and can just sit and scan
- Changed the calendar to have green vacant and red filed on the sites overview
- On the calendar ad function so you can click a day and it will take you to the sites page for that day
- Add a date range either through search or above calendar to change the background of the calendar pages.  When one of those dates is selected it will take you to the sites page with that date range pre-loaded

Working with Alan on refactoring code into a DAO with services (new coding techniques for me). We had to do some debugging and ended up merging in the new code and pushing it to all servers. This refactor job was on the new sub barcode search options from the shopping cart. The older ways still exist, the new way shortcuts a few steps and is much quicker if you are scanning sub barcode values. The timeframe is less than a 1/3 of older code run time. Good stuff.

As a side note, I don't think that I could code the DAO's (data access objects) and services (functions and methods) all by my self. I still need Alan to prompt me and help with some of the syntax. Enjoy the opportunity to keep learning.

We had Wayne, Dustin, and Eric on the meeting this morning. Pretty quick for each of them but we made some good quick check-ins. Wayne reported on a new VPS (virtual private server) that just got setup and lightly released. The only thing different on this setup was the database configuration. The database for this server is on a Linux box and not directly on the same server. We are experimenting with speed, traffic, and some other variables.

Dusting checked in and let us know what he is working on. He is good to go and making progress. Eric and I then worked on some changes and updates for the special accounts and some new rules for the customer loyalty points. We also setup some other time to do more code review. Good session.

Alan checked in and we made some plans. Pretty short meeting.

After that, I spent some time working on recording notes to elements of time from yesterday.

Working with Eric on code review for three new rules for customer loyalty points. The new rules were exclude customer types (list), exclude in-line discounts (yes/no), and a program end date option (future date). We got the code merged in, tested, and pushed up live. I did have to alter the database update script, but we got that working as well. We just had to account for servers that didn't have anybody using the new special accounts stuff yet. Minor tweaks were needed.

All sales efforts for Campgrounds 

Touching base on 2020 tax and withholding updates. Shawn and I touched base and will be hitting things next week.

Both Alan and I got on a meeting and divided up a bigger code merge project. This is the tax-v5 (sales tax version 5) project from last year. We broke a huge project up into 5 different pieces. We have 4 of the pieces fully launched and part of the master code branch. This is the final phase of that project. Most of the code is done but it has been quite awhile since we have worked on it. Just getting back into the project. This project deals with dynamic tax settings 6-10 and custom options for city, county, and state taxes. Lots of dynamics.

Bryan and I met up online to do some code merging. We worked on two different projects. One was some custom ecommerce cart rounding for Expo and the other one was the cross corp invoice to PO functionality. We had to login to one of the remote servers and check a couple of the cross corp mapping records. We made a small change and everything worked great. Both projects were merged in and pushed up to all servers.

Once Bryan and I were done, I ended up on a phone call with Russell. We were talking about job costing and tracking elements of time through invoices and expense/receipts. We also talked about some other user experience stuff and some graphics stuff.

Recording notes from yesterday and today. I was also pushing up videos and screenshots from other meetings. Busy times.

Calvin has been working on a new business called IT Dream Team. It deals with coaching and consulting and helping firms get their IT needs met. Calvin is working on building up a business that could be sold and/or used as a reoccurring revenue source.

As a proposal, what if the IT Dream Team (Calvin's new business) works with us as a consultant/IT department? That might be an interesting joint venture.

We ended up going short on the meeting in order to update the servers. We had some server issues on data 0 and data 2.

Steve, Danny, and I were on a GoToMeeting session. We were watching and monitoring servers, on tech support calls, and trying to get things up and running. As part of the conversation we talked a lot about some of the outside parties and being able to access the pieces that we need to. This could be outside 3rd party code, independent apps, specific code, WordPress sites, and other pieces. We really need our own access to these pieces.

Hosted solutions are big animals. We have to build it, service it, and keep it going.

We have a great team of people who all have a number of key talents and pieces. How can we keep organizing things so that we get and keep those key players.

Looking at options and seeing where we can fill in the blanks.

We talked about text message marketing and some of the crazy challenges with that. Currently, there are two main players out there. One is Twilio and the other is AWS. Both of them have some built-in text messaging options. Here is a link to Twilio - https://www.twilio.com/

Wayne popped in and we looked at data 0 and data 2. Currently, those servers are some high traffic volume players. We were talking about ways of splitting up the servers into smaller clusters and putting the databases on their own dedicated servers. We also talked about some world building project stuff and splitting up databases. As a fun side note, Wayne jumped in and showed us some of the resource monitor stuff for that server.

Sometimes we use custom code as a virtual buy-in or investment to our platform. We love it when others succeed.

Steve and I spent a bunch of time talking about our current plan and how things are developing. We will keep on keeping on. Lots of good stuff ahead.