Russell and I touched base first things this morning. He is working on payee/user level filters for the news and updates section. Lots of emails and text messages. Light tech support and helping here and there. Shawn popped in and we signed off on some new code and calculations for North Carolina state withholdings. I merged things into master, updated databases on all servers and pushed up new files. I let a client know who was waiting for that state.

Calvin and I got on a Zoom session and worked with Mike Harman from Caisson Labs. They are just starting to use the new hybrid desktop app that Calvin created. We had to flip some settings, check some pages, and give some light training. They should do good, once they all get going and into the groove. That is exciting.

On the phone with Calvin. We were discussing where we want things to go as far as a custom label builder. We talked about using his Adilas Label Wizard (windows software app) as a basis. We talked about building on what we have and also building as if for years. The goal is to build a label wizard and/or builder within the main adilas.biz web environment. We also discussed single labels, sheet labels, bulk labels, and dynamic mapping. We talked about limiting the number of fields that were available and how to do the data mappings. We talked about formatting, positioning, and other display options. The other subject we talked about was showing a visual of what it would look like so that the client could get an idea of what the labels would print like.

Working with Alan on the in-line dollars off discounts for the sales tax expansion project. Going through files in the shop folder and in the black box folders and adding code to display the in-line discount as needed. While I was doing that, Alan was also working on other code for in-line discounts and such.

Promised to check payroll code and look for random calcs for the state of Florida and check the FUTA (federal unemployment tax) withholdings. Reviewed a number of emails and downloaded the IRS Pub 15 for 2018. Did a search for FUTA guidelines and withholding info. Made some notes and then looked through adilas payroll pages. Wrote a report back to a client relating my findings and even included a text base code sample.

Wrote more emails and requested information about a 6 corporation data migration from the data 3 server to a new dedicated server on data 8. Spent the rest of the morning session doing light clean-up and maintenance on quote and invoice pages. I also took off the select all option on the adilas API socket page. We didn't want to allow the clients to open all of the API socket (virtual windows and doors) with a single click. The other changes helped with searching the external PO numbers on quotes and adding drill-down links to quotes and invoices from the main quote and invoice homepages.

On the phone with Calvin. He gave me a report about the adilas label builder. He is going to be allowing blocks that may contain plain text, HTML text, images, barcodes, and QR codes. The label settings will be saved and will be able to reconstruct themselves to be used over and over. We talked about a few other tweaks and such. Small update on how the company is liking his hybrid desktop app. Things seem to be working and flowing quite well.

Working with Alan on the in-line taxes.

Other emails and random tech support questions. One of them was an overview of cross corp transactions. There is tons of potential there and I'd love to see things get built out a little bit further. See the media/content for a quick copy and paste of the info on cross corp stuff.

Bryan and I got on a GoToMeeting session and worked on some of the older Flash widgets. We removed the adilas logos and the verbage saying adilas.biz from both the adilas barcode generator and the adilas check write widget. That was in preparation to allow more white label options. Basically, it made it so that the adilas logo wasn't as visible. It still has the adilas logo (just the 4 curved bars) for the background loader, but once loaded, it doesn't show any indication that it belongs to adilas.biz. Kinda fun.

Also, while we were in on the barcode generator, we split the main barcode value into two pieces. The new pieces are the actual barcode and the text that shows up below the actual barcode. The new Flash app allows for the two values to be different and/or show alternate text. The old way required the text below the barcode to match what the barcode was. This new change, adding the alt text, will open things up and will make it pretty cool. We pushed and tested both new Flash widgets on the live servers. While I did that, Bryan fixed a couple of custom black box pieces that used the older barcode generator and upgraded them to the newest version. Good session.

Light tech support and emails. Wayne popped into the meeting and had a few questions. Most of my time was doing small bug fixes and working on documentation for the adilas API sockets.

Working on the adilas API's. Added some new output values, new documentation, new files, and a new URL encoder page to help with encoding and decoding. Here is a link to the new page. [url encoder page]

Promised to work on sub inventory API's for Baker. Wasn't able to get clear to sub inventory but was working my way through.

Helped out both Calvin and Eric with some developer tech support stuff at different times.

Met up with Steve on the morning meeting. Steve has been on vacation for a couple of weeks. We spent some time doing some catch-up and planning. We jumped right in and started looking over ideas and plans for the upcoming training event.

- Steve's idea - Ground zero - adilas training - Start at the very beginning.

- Keep it simple - $100 per day

- Part of the event should focus on where we are going and where we are seeing the concepts and trends heading. These are things like world building, 3D data assembly line, and the adilas model.

- Steve really wants us to focus on the adilas model. Share the "Why". Show what we have learned and why that works. Help to enable them to think and build on their own solutions. Teach the why and the how. Teach them to play like we want to play.

- Show a demo of what we are thinking and planning on the upcoming mini conversion project.

- Steve was talking about how much the event would bring to us vs how much it costs to put it on. Tons of benefits. Let's help push things forward.

After Steve and I got done brainstorming, Dustin S. (new developer) came on and we helped him get up to speed on Git and Bit Bucket. Steve and Dustin then worked together on some state API tracking stuff. I left the meeting and did some email stuff.

Emails and tech support. On the phone with Russell. Recording notes and doing some planning. Went upstairs and did some planning on the upcoming adilas training event.

Brainstorming with Bryan. They wanted to use a barcode to prep and fill the smart groups - under my cart favorites. Bryan and I went through a funnel drill and identified requirements, inbound values, possible tools, and then what we could do to finish things up. Good practice session.

We switched subjects and talked about sub phases, sub locations, and pulling stats and reports from the data. Basically, what were my yields and such? The deeper we looked, his client wasn't using anything in the elements of time section. Bryan is going to check with Steve and see where he would recommend that he go and/or direct the client to use a different function or process.

Added the first high point black box... this is way up high and even before any logic. See the printable_parts_report.cfm for more details. We had a need, so we went in and fixed it.

See attached for the first round draft of the May training schedule.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Setting up the adilas ecommerce site to allow people to book training classes and events. Added some new daily training items (things to sell) and also did some graphic work.

Theme Links

Resources

Branch:

Google Doc

Description

Adding to the theme 10 payee footer links, and 8 corp top links

hours

Met up with Bryan and talked about how to book a fee. We talked about things on the invoice side and also on the expense/receipt side. We then helped and worked with the new high point black box page. This one was kinda funky... instead of breaking things into smaller black boxes, we had to virtually reassemble the page as a single custom page. It got pretty deep - going the opposite direction. Interesting.

More work on ecommerce photos and setting things up to be able to sale virtual seats and live event seats. Bryan came back on and we did some more work on his high point takeover project. Here is a link to the current adilas ecommerce site. https://data0.adilas.biz/shop/search_web_inventory.cfm?corpKeyId=adi%2D22

This little note was added on 5/9/18... I added a new folder with a redirect for the adilas shopping cart. Instead of the link above, that still works, I shortened it to: https://data0.adilas.biz/shop/adilas - this will do a redirect to the link above. Anyways, small little shortcut.

Russell and Steve helped us look into the ecommerce settings.

Labels - that is a big pain point. Good thing we have Calvin on the job. :)

The deeper we get into manufacturing... We are seeing the need for sub phases, sub locations, sub groups, and even repackaging and packaging of packaging. Processes and sub processes, reprocessing, & sub routines. We are also seeing deeper needs for the elements of time to be more standardized and easier to use. Eventually, these subs of time (sub flags and tags) will need to interconnect with the other main 12 main player types. They may also need to interface with subs, line items, sub inventory, and even mini conversions.

We are seeing needs to do and help with production runs, bulk packaging, greater usage for recipe/builds and automating things. We need sub inventory tied in and things in bulk. We are also seeing more needs to show reports and be able to pull and filter the data quickly.

Currently the system is quite deep and intense and can even be pretty tricky (tons of moving pieces). If we can wire things up and make it look simple and feel simpler, that would be awesome. We need the depth but we also need to back out and make it appear more simple and straightforward. What a balancing act. Here we go.

New link for the adilas shopping cart and ecommerce site: https://data0.adilas.biz/shop/adilas

Working on the easy system setup for a new adilas system. This is for the one-time setup fee, the 1st month system fee, up to 5 hours of training and/or setup, and up to 3 hours of custom code or simple data migration. Working on the links and verbage for the adilas ecommerce site.

I had a meeting with Andy from the Peak Deli at 3:30 pm. We went in and worked on his my cart favorite buttons. We ended up stacking things and making button groups for his different sections of buttons. These were things like breakfast, lunch, drinks, sweets, choose a side, etc. I think it will really help him speed things up and make it go faster. Anyways, it was fun to see all of his buttons and help him get everything all organized and what not. Good stuff.

Finished up the day by working on the adilas ecommerce page. Spent quite a bit of time pulling together assets and links for the easy system setup item. That was fun to pull all of those things together in one place. Here is the link for the new setup item:

https://data0.adilas.biz/shop/web_item_detail.cfm?corpKeyId=adi%2D22&nav=show&display=med&showCount=25&partId=389969&subId=0

Steve and I were talking about system setup options. We would like to add another system setup that has ecommerce... Here are some of the rough numbers: The normal easy system setup $989 + $100 ecommerce setup (one-time fee) + $100 ecommerce training + $67 ecommerce monthly = $1,256

Russell popped in for a bit and had a couple of questions. Steve was helping Dustin with some code changes. I was building new graphics for the easy system setup items. Good stuff.

See attached for a number of graphics that are out in the adilas ecommerce site.

Working on adding in a new easy system setup item with mobile ready ecommerce.

Jumped on a GoToMeeting session with Steve. We made a quick fix to some of his state specific API code pages. Bryan then came on and we chatted about how to run standalone discounts through the cart. There are two major steps. One is on the corp-wide setting level. The other is on the location and tax setting level. We then went through a couple of scenarios and play around in the shopping cart. I also talked about the upcoming in-line dollars off discounts that are coming soon.

Back working more on the adilas ecommerce pages. Worked on new verbage and new ecommerce images. I pushed up the new images to the earlier element of time for this morning.

Working on adilas ecommerce pieces and training details.

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

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

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

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

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

https://docs.google.com/spreadsheets/d/1ANHIdJx6zbV4BM_pZ1biOTmK-SJrKwLUoxuHYMA7BJM/edit#gid=0

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

Estimated amount Chris is willing to contribute

Gift Cards

$3500-$5000

Puch Card

$1500-$3000

Cupons

$1500-$3000

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

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

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

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

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

Working on the flyer for the upcoming adilas training classes and workshop. Spent some time at the table planning and then back on the computer putting things together. Small little random things here and there along the way.

On the morning GoToMeeting session with Steve, Russell, and Dustin. We chatted a little bit about the upcoming training, Russell had me working in the WordPress news and updates section. I then helped Dustin with some complex data objects and getting structures and arrays figured out. I was on the phone helping Bryan with SSL issues, helping Russell with some settings, and working more on a GEO tourism flyer for the training event. I was also going through a small to do list for an upcoming data migration. Checking servers and making sure things are in order. I still have a few loose ends for that project to go through smoothly.

Working on the adilas training flyers and documents. Making small adds and light planning.

We were going to do a data migration process for data 8 but couldn't RDP (remote desktop) into the server. We had to postpone the migration. Fixed the training flyer and pushed up the flyer to different pages and such. See attached for a copy of the full training flyer.

Russell and Steve were talking about the power of the adilas API sockets and how to tap into that market. Kinda like WordPress and other open source options. If we build it and make it available, other developers can then use it through the adilas API sockets. The concept of "Play at the Wall".

Brandon wanted me to add some notes, this is Russell Moore. As mentioned above we are talking about the possibility for third-party solutions as well as full Corporation solutions running off of the adilas API. One of the other subjects we were talking about was to design the inside of adilas with a constant html structure, so that every time we decide to change the look and feel, it can be done as easily as possible. Somewhat like the concept of CSSZenGarden.

Helping Steve and Dustin with what they are doing. Steve was working with a custom wire job for elements of time and Dustin was working on combining structures and arrays to make complex data objects.

Spent some time working on the data 8 server and making sure we could get into things there. Submitted some tech support tickets to get some files and folders copied between servers for a migration project. Also worked lightly on the adilas training event and image. The WordPress news and updates was doing something funky on the image and the way it was cropping it.

Sending around emails about the upcoming training event in Logan, UT.

Quick meeting with Bryan. He had some questions and we ended up looking at existing reports and then saving those reports to the favorites as preset custom reports.

Back working on reoccurring elements of time. This is a calendar view that allows you to duplicate, copy, and/or setup reoccurring elements of time. This project has been sitting on the sidelines for a number of months. Trying to get it done before our next training event.

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

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

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

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

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

On the morning meeting. Russell checked in and we pointed him in the direction of API sockets and helping to train the new developers. Dustin and I worked on a small project to fix and show the sub connections on the time sub special flags and tags. We needed to tie-in the app types, main id's, sub id's, and table names. We worked through the project in somewhat of a training type scenario. I had fun, coded, answered questions, drew little sketches, showed pictures, and Dustin followed right along. Great session.

Working on reoccurring elements of time. Also, Calvin called and gave me a small demo of his adilas label builder app. We also looked at some other custom labels that he had done. Good meeting.

Got on a meeting with Bryan. He had some questions about flipping servers and running custom reports for Expo (3rd party solution and white label). We went over some options and even did some quick concept coding to get the ideas across. After that, he had a couple other questions that we looked into. We talked about black box code and how to put custom JavaScript in the bottom and top pages for the black box access stuff.

I was going to be meeting with Eric, but he called and said that he was slammed and behind on things. We will reschedule for next week. Alan called and we chatted for about 15 minutes about USAePay, new gateway settings, and in-line discounts and in-line dollars off. After that, back on reoccurring elements of time.

Small updates on where things are at with different developers. As a fun side note, we had our first person register for all four days of training and pay online using our ecommerce site. We have had people paying their monthly bills for quite some time, but this was the first start to finish ecommerce sale for a training event. Kinda fun.

Wayne popped in and wanted to talk about QuickBooks integration. He is working on the customer integration process. How do we sync things up and who is the master. Is it adilas or is it QuickBooks. It sounds like a setting. We also talked about other possible options such as flex grid, custom tables, etc.

Wayne would also like to help us out with our servers and such. That would be awesome. Keeping things standard and really automating things. He would love to setup things programmatically vs full manual processes. Currently it takes us 2 to 6 weeks to setup and get a new server fully ready.

After I got done speaking with Wayne, I went in and worked more on the reoccurring elements of time. I have a working version done, but it is not currently tied into the system. The page is uploaded to all servers but it has not yet been standardized and/or help files fully created. The page name is top_secret/secure/setup_reoccurring_time.cfm?id=190 (some real id number - the master id to copy). I'll get back to it a little bit later on. I'm just glad that I could get it this far right now. It still needs a little bit of loving.

Working on the custom code part of in-line dollars off for the in-line discounts project.

Part way through, I met up with Steve and Dustin and helped them fix some merge conflicts on their branches. We got everything merged in and pushed to the live servers.

On the morning meeting with the guys. Quite a few of us were on this morning. Steve and Alan were mostly talking and dealing with some changes to the Metrc API and state systems. Wayne popped in and chatted with Steve. Wayne is looking to play a little bit deeper and be more of a regular developer. He is retired but looking to re-enter the scene a little bit more.

Russell popped in and he and I did a different Zoom session. He showed me some of the news and update feeders. Basically, he is designing the snow owl footer to be able to consume internal corporation information (elements of time) as well as outside feeders from WordPress sites and feeders. Tons of new options and such. Pretty cool. Russell and I chatted about how deep things need to be in order to play the game. On the programming level, we have to go super deep, but on the surface level, we have to make it look very simple and easy. Somewhat of a paradox.

While Alan and Steve were working, I was working on in-line discounts and in-line dollars off stuff.

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

Meeting with Anthony Harrington from All Greens. We did some light reviewing of changes since our last meeting on 4/10/18. I made some searches in the adilas shop for "pricing engine" and for "Anthony". Once the results came back, I read through and reviewed some of those notes. We talked about pushing the my cart favorite buttons to a higher level. He would love to get the buttons tied to time and to days (for example, just show up on Thursdays, etc.), be able to discount based off of category, and being able to apply those discounts in-line using percentages and/or dollars off.

I did a small demo and showed him where we are headed with the in-line dollars off discounts and such. We went through a couple of scenarios.

- On PO's, once you verify a PO, it still allows you to modify things. We talked about Ice-down dates and I showed him a demo of how things work on the invoice side of things. We talked about getting that functionality available for all of the other main system players (12 main player groups).

- He had a question around rounding tickets or invoices to the nearest dollar value (no left over cents). He would like for invoices having $0.50 or less, go down, and $0.51+, go up. I quoted him at $200. He wants this new feature for corp id #1114 on data 6. This same functionality would be really cool if it was a setting... yes/no for auto rounding to the nearest dollar. We would also need to know, what are the levels? Such as, round up on anything over 50 cents or round down on anything below 60 cents (or whatever). Basically just settings to help it know what to do. We may also need to know what part number (id) to use and what verbage to use such as: convenience fee, rounding difference, etc.

- He had a question on allowing invoices with partial payments (not fully paid). This would be an awesome setting as well. Image a setting that says allow credit to be extended or require full payment in order to submit cart for processing. Some new settings could handle that and help make it more automated.

Looking up things for campaign rise, research, and coding in-line discounts for custom pages. Got on a meeting with Bryan Dayton and went over some database changes. Emails, tech support, and prep work for the upcoming training course and event.

Russell came in and reported to Steve and Dustin about his news and update settings and multiple WordPress feeds. We then did some light planning on who was going to teach what for the upcoming training event. Lots of emails and planning.

Calvin popped in and reported on some new updates in GPS land. He has a phone provider that is offering GPS tracking with an API from a standard phone carrier and provider. That is awesome and will help simplify the process of getting the GPS data. He also gave us a small demo of his adilas label builder program.

Part way through the demo, we had to do some emergency surgery and fix a problem with the WordPress news and updates feed. It was looking for an image but one hadn't been uploaded yet, it was stopping all new logins. If you were already on, you were good, but it you were just logging in, it would block you by showing an error message. We had to tweak a few files and got everything all up to date and ready to go. Kinda crazy.

More emails and light tech support stuff.

On a Zoom session with Calvin. Going over tech level details for his adilas label builder application. We went over some of the existing label pieces and how they connect. He also showed me a custom visual builder and getting some ideas from there. We also talked about having he and his family help build out the custom labels until we get everything on a customer facing web basis. Good meeting.

2-4:30 pm working with Alan on discounts. We were testing code and running through scenarios. We found a few small problems but most of it looked pretty good.

On a GoToMeeting session with Bryan. We went through and detailed out the new corp-wide settings for invoice rounding and helping invoices round to full dollar values. Bryan took notes as we ran through settings, scenarios, and some logic options. Good session.

On the morning meeting with Steve and Dustin. I merged in some code from their branches. Wayne popped in and showed Steve and Dustin a small demo on what he is doing to help rewrite some of the Metrc stuff. He loves to rewrite things and make it look more simple. After that, Steve gave Wayne a demo on his cultivation process that he is working on. Good stuff.

Alan and I spent the last half of the session working on in-line discounts and doing some deeper testing. We were testing and making notes on bugs or light fixes that were needed. Excellent back and forth checking, debugging, recording, and testing. It made the testing so much more fun to have two eyes on the same tasks. We'll do this again.

Alan and I were working on in-line discounts and dollars off code. He was working on some of the bug fixes and I was checking on merge conflicts. Got a call from Eric, just checking in about where things are at with the customer loyalty points. He has been slammed with custom jobs. That seems to be the case for most of our developers. Pretty crazy.

On the phone with Calvin going over the barcode generator and how to figure out what pieces are being passed by default through the system and what pieces may be needed as custom options.

Alan and I got on and did some more group testing and debugging on the in-line dollars off and other in-line and standalone discounts. Good session. We are getting really close.

Memorial Day - Enjoy with your family

Helping Tanner get started with recording hours. Talking to Calvin on the phone about SSL certificates and custom domain name pointing stuff. Emails and then small to do list stuff. Prepping for the upcoming training event. Did some work on the old adilas interactive map graphic and main homepage navigation.

Spent some time working on the interactive map layout and the adilas GPS core layout pages. These are older static graphics that were designed for training purposes. Anyways, I spent some time and added new links and buttons to the different pages. Here are links to both new pages:

https://data0.adilas.biz/top_secret/secure/interactive_map.cfm

https://data0.adilas.biz/top_secret/secure/adilas_gps_core_home.cfm

Live Adilas Class. Logan, UT - Bridgerland ATC, Custom Fit, Room 810 (computer lab). We had 4 live paying clients and a number of internal team members in the class. We had Steve, Shari O., Dustin S., Alan, Bryan, Calvin, Russell, Shawn, Jeremiah, and myself from the core adilas team. Not all of them were there everyday, all the time, but they all came and participated quite a bit of the time. We also had a number of folks join us online in the GoToMeeting sessions. We recorded all of the training except for two main sessions.

Here are some links to the videos.

video from day 1 - morning session
small adilas demo, intro, and core concepts

video from day 1 - afternoon session
new features, open q&a, and historical stepping stones

video from day 2 - morning session
POS - point of sale features part 1

video from day 2 - afternoon session
POS - point of sale features part 2 - open q&a, and world building in use

video from day 3 - morning session
CRM - customer relationship management overview

video from day 3 - afternoon session
exploring ecommerce & custom email settings - BI - business intelligence and big data

video from day 4 - morning session
tips, tricks, & best practices - small custom consulting session

video from day 4 - afternoon session
meet the adilas developers, adilas model, and wrap-up

///////////////////////////////////////////////////////////////
other notes that I took during the class.
5/29/18
- Drag and drop custom fields - they really like the custom field settings for customers. They would love that to cascade out and filter through the whole system. Point and click, toggle on/off fields, sort, customize verbage & instructions, and be able to effect the display as well.

- The need for more one-to-many relationships

- Light request for more settings on the main salesperson and other salesperson settings - be able to split the names instead of just one setting.

- A custom preset on permissions "copy and/or duplicate" permissions.

- Setup a master and then apply those settings. This could be templates and/or master files - a virtual job description.

- Floating up and down nav to help minimize the scrolling.

- The power of "templates" - elements of time, sub inventory, payee/users, look & feel, etc.

- Start by setting up the templates and then assign them as needed - that makes a great starting point.

5/3018
- Alan was doing an exercise - he had everybody list what they could for two minutes on all of the fruits that they could think of. Fun little exercise. After that, he was comparing this to development. We try to hit the fruit that is on your list. Things keep evolving and sometimes you forget things and have to add that in later.

-  Corp-wide settings and allowing you to set certain verbage stuff.

- Bryan Dayton was showing the adilas market (adilas world). We really need to get others into the marketplace.

- While Bryan was showing his profile... I was thinking that we need to help him get some better screen shots for his demo graphics. You could tell that they were done with a low end and/or free graphic editor (kinda fuzzy and pixelated).

- It helps us to have a flow and/or a clear picture (talking about custom code and custom development).

- Small demo on a custom dashboard for Global Design

- Steve and Shari O. were talking and doing a demo together. Steve was talking and Shari O. was driving. Later Steve and I did similar things. It really helps to split that load and have a helper. The person talking can focus on what they are saying and the demo person (driver) can draw, highlight things, and show focus areas. It seemed to work out quite well.

- Steve and Shari O. started out in a coffee shop and did some quick split cart stuff. They then went into some of the corp-wide settings to show how they were able to do what they were doing. Good flow from normal usage to how it is done based off of settings.

- Eventually we need a deep merge (find and replace) on customer records.

- Our users would like to be able to compound a discount. For example: double up points, do a 1.5 mark-up, etc. Lots of time based sales and promotions.

5/31/18
- Not many notes from this day... We started out and Steve and I were presenting on sub inventory. See the video links above for more details and info.

6/1/18
- Steve was going over the new cultivation functionality. 4 main levels for the cannabis guys... they need cultivation, production, distribution, and retail.

- Some of the these white label options should really build out and use all of the pieces.

- Page and function level settings

- Interesting topic of hardcoding & concepting vs dynamic code & production - speed, limited scope, and testing.

- Being able to lock-down certain pieces, features, and virtually ice things down (ice-down dates).

- Also, interesting as we get deeper and deeper into the industry specific code... the verbage, lingo, & the flow are really important. That is what makes it feel like native or custom code or custom software.

- Comment from Dustin - We need guide rails, guard rails, settings, templates, and easy configuration options. Help lead the people down the paths that we want them to go.

- On the data tables - it sure would be cool if you could sub filter things. It comes down to space, coding, page real estate, and planning. People want more and more custom options - to setup their flow, work space, and environment (requests for deeper and more robust world building options).

- On numeric entry fields, show the unit of measure to remove the questions (if applicable).

- Making the label options show up and be available from multiple pages and such.

- Settings are preset choices & decisions - super important.

- On Calvin's tools... Just an idea, but what about dynamic or user input boxes and text fields? This is for text that may be added on the fly. He currently has static text, HTML enabled text fields (allows formatting), and dynamic look-up text (text fields mapped to data or dynamic output). What about user input text boxes?

- Making labels and empower the users.

- We had a client/participant that recommended that we put a small icon on each page that could be a default homepage and then have a quick link to set it as the default homepage. Great idea. Basically, let them navigate there (to the actual page) and then set it as their homepage if that is what they want.

/////////////////////////////////////////////////////
Comments from Bryan - who talked with one of the participants

- When starting the class, for someone who is brand new... it might be nice to give a 15-20 intro and general overview. We just started out and jumped right in. Basically, somewhat of a canned explanation of what is adilas and what do you get with this software package. A really simple and organized intro.

/////////////////////////////////////////////////////
Notes from Dustin - See attached for full notes

General To Do's:

Need to Have each page check for the color of the background and adjust the card to be a lighter complimentary color (universal). (4,5)

Need to have api key capability for each employee that performs metrc api interaction.

Need to set up custom permission setting capabilities so that they can set permissions for multiple employees over time without having to do a redundant process. Themes and standardized user type templates.

Make a excel or csv spreadsheet that templates the fields needed for api integration to give to a customer to fill out. Maybe a master list that passes in all of the general fields and passes over unneeded fields based on customer needs.

Need a graphical repesentation of the entire seed to sale process with tie-ins to each adilas feature/tool.

Need predictive on the search vendor field on the add/edit page.

Need to have customer password fields auto-populate wherever needed. (e-commerce)

Need to have a set to default button on the nav menu for setting any page as a default homepage.

Need to have a toolbar button for page relevent tips and tricks with links to news and updates.

Need to update how people reset thier login attempts: lets add a captcha or at least put the copy paste link on the same page. Maybe two step varification would work.

When you are switching corps, instead of needing to click on the little box link, make it so that you can click on anywhere on the corp piece.

Need to have UOM type indicators on any field that holds wieghts. In most cases this could probably be hard coded.

Need to create the ability to check a box that opens all of the subs for inventory search for adding to cart.