Search The Adilas.biz Developer's Notebook
Time Period:
Daily (enter the day you want to see)
Monthly
Custom Date Range to
Template Filter:
Color Code:
General Text Filter:

(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:
 
Adilas.biz Developer's Notebook Report - 4/1/2018 to 4/30/2018 - (77)
Photos
Time Id Color Title/Caption Start Date   Notes
No po photos available. Click to view time details.
Shop 3615 Adilas Time 4/2/2018  

On the morning GoToMeeting session. We had Steve, Alan, Eric and I on the meeting at different times. Shawn came over to my house part way through as well. Eric, Alan, and I were working on the sales tax expansion and rounding error stuff. Steve was doing his own projects and Shawn was working on county specific payroll stuff for the state of Indiana. Mostly a work session today.

 
No po photos available. Click to view time details.
Shop 3640 Adilas Time 4/2/2018  

Calvin and I jumped on a Zoom session. We went over the requirements for creating a new custom_json table. This table will store JSON object per main object (any of the 12 main players) and any of the line items within the 12 main players. We also briefly talked about voice to text conversions.

Spent the rest of the afternoon working on custom code, black box stuff, and cascading tax rounding error stuff to all the servers. Light tech support and emails.

 
No po photos available. Click to view time details.
Shop 3638 Adilas Time 4/3/2018  

Morning meeting... got reports from Alan, Steve, and Russell. I was working on some small changes and taking the rounding error off of the mini invoice (3" customer receipt). Other small changes.

Eric will be coming in at 10 am to talk about loyalty points. Eric and I talked for a couple of hours about the special account tracking project. This deals with loyalty points, gift cards, in-store credits, you name it... We did a lot of drawing and even got into some small scenarios. We went full circle... we decided that they all go together and then not all together and then back to all together. Eric was tasked with looking into things a little bit deeper to see what we can do and what plans we can make.

Shawn came over and was working on state payroll stuff.

 
No po photos available. Click to view time details.
Shop 3639 Adilas Time 4/3/2018  

Working on some small changes for the sales tax stuff. Did some testing and decided to take off the option to format the price per based on the number of decimals. This allows the system to have more flexibility and use any number up to 5 decimals as needed. Uploaded to all servers and did some light testing. Calvin called and we talked about transporting JSON inside of other JSON objects. I showed him where we were doing it right now and hopefully that works for what he has planned.

 
No po photos available. Click to view time details.
Shop 3633 Flash 4/3/2018  
 
No po photos available. Click to view time details.
Shop 3646 Adilas Time 4/4/2018  

On the morning meeting with Steve and Russell. Topics for the day.

- News and updates and being able to push things up and out to the users. We even talked about social media and being able to push notices to the clients.

- Huge need for training and especially live training. We definitely have a big need there. We also need to use technology, but there is still a need for trainers and actual instructor-lead training courses.

- Russell was saying - we need to have multiple power users to help with the training - nobody knows everything and we have masters in different areas. Including reps, consultants, developers, tech support, and visionaries.

- Setup a class and setup minimum number of participants - do it and make a profit so that we cover everybody involved.

- We also talked about making adilas into a bigger mash-up (mixing technologies and features). Steve and I have always pushed for internal development and internal features. We are seeing that some of the newer developers almost immediately look into the other existing products out there and how to mix and blend them together vs just building internally. Later in the meeting Steve and I were talking and he said - sometimes you have to buy what we can't build. We used to have to build our own in order to do things. Now there are more options that are available. Things keep changing. Steve liked the words collaborate vs mash-up. Different angle and play on things. As long as the public sees us as Adilas, it may not matter if we collaborate and use other technologies. We already use tons of outside software and database packages to provide what we currently provide. The concept of white labeling and being a backbone with an alternate face and/or user interface - that is kinda what we are and what we do. We may need to use some of these collaborating steps as interim steps. As we keep going, we may end up engulfing and pulling in some of these other pieces and features. Quote from Steve - "We are in a crowd."

- Let's setup a class and charge $150/day per person. Let's do a 3 day class. Maybe even have different breakout sessions and such. We are thinking of a hotel meeting room and what not. Maybe every other month or at least quarterly. There is a need there.


 
No po photos available. Click to view time details.
Shop 3648 Adilas Time 4/5/2018  

Joined the GoToMeeting session from the Orem, UT, Library. The kids are on spring break. Chatted with Alan for a bit about EMV chip readers and gateways and then chatted with Steve for a bit. I merged in his code branch and made a few changes to the adilas 3rd party solutions page. Emails, phone calls and tech support stuff.

 
No po photos available. Click to view time details.
Shop 3647 eXPO: login 4/5/2018  

Working with Bryan to get the expo login and logout pages working.

 
No po photos available. Click to view time details.
Shop 3641 Brandon out of the office all day 4/6/2018  
 
No po photos available. Click to view time details.
Shop 3652 General 4/7/2018  

In working on some new payroll changes and looking over code that was done by Shawn.

 
No po photos available. Click to view time details.
Shop 3653 Payroll changes 4/9/2018  

In working on payroll changes. Shawn got me some code and I was looking over things. Reformatted the code and ran it locally to test it.

 
No po photos available. Click to view time details.
Shop 3645 Adilas Time 4/9/2018  

Our code is one of thousands of possible options. If we have to protect something, we will protect the concepts that support the code not the code itself. It technically could be coded in any number of languages and in many different ways and manners.

Eric popped in and we chatted for a bit. He will be checking in around 10 am tomorrow.

I spent most of the morning working on new payroll files from Shawn for adding in states, counties, and new code for the state of Indiana. Shawn got on the meeting and was reviewing some code on his side as well. Mostly a work session today.

 
No po photos available. Click to view time details.
Shop 3650 Lunch 4/9/2018  
 
No po photos available. Click to view time details.
Shop 3651 Adilas Time 4/9/2018  

Emails, tech support, and talking on the phone with Calvin. We were talking about his custom JSON storage options. He was asking if he could convert certain vales into Base64 for the ability to transport JSON objects within other JSON objects across the adilas API sockets. We chatted and hopefully have a good direction. Calvin is working on a custom desktop app that plays with adilas backend database over the cloud, web, and across the adilas API sockets. Great project, it just takes a while to get all of the pieces up to speed and what not. Good stuff.

 
No po photos available. Click to view time details.
Shop 3649 White label: check and push code 4/9/2018  

On a GoToMeeting session with Bryan. We spent some time talking about a white label vendor's need to get at customer (their customers) audit data and daily sales data. We talked about having to let our clients know, setting up the system, and then deciding if we are doing normal user/permissions, special access pages (view only options), or full on multi-server API sockets with reoccurring calls, real-time calls, or batches. Lots of options and ideas. Some good, some bad, and tons of cascading questions. We want to be careful and look how far things are going and/or reaching.

Next we merged in some new code for his other white label project and creating an alternate login experience. Everything went pretty well until we started flipping servers and then switching between a single corporation login vs a multi-corp login (how many corps does the user have assigned). We were pretty close, but kept running into walls and unknowns. We decided to look at it later on due to the complexity of things. End of the day.

 
No po photos available. Click to view time details.
Shop 3661 Payroll changes 4/9/2018  

Working on passing the county taxes through the calculate payroll page. That is a huge page with over 7,000 lines of code and pretty deep in places. Crazy stuff.

 
No po photos available. Click to view time details.
Shop 3654 Adilas Time 4/10/2018  

In early working on the new payroll changes that Shawn submitted. This is dealing with county based withholdings and new state calculations for Indiana.

Steve is seeing the 3rd party solutions page extending into a virtual permissions for those outside solutions to get access to any of the 12 main players. We need to show what is available and allow for what windows and doors are open. This is really common for some of the clients that are dealing with oversight or overseeing certain pieces (virtual auditing and such). We need to keep our clients data safe but also need to allow the different parties to allow or dis-allow between themselves. Maybe the secret is allowing the clients to build their own relationships between the possible different solutions and/or outside parties.

At some point, we may need some kind of history of who is opening and closing the API socket windows and doors. That may help later on if we need to figure out who is changing what.

Eric will be popping in around 10 am to talk about loyalty points and gift cards.

Meeting with Anthony Harrington about loyalty points and gift cards. Eric, Steve, and Brandon were on the meeting with him.

- There are tons of daily discounts. It gets crazy in order to manage all of those things.

- There are a number of steps that need to be done in order (on carts and checkout process). One of the things that they would like us to do is - dumb things down and make it more simplified.

- They would love to have preset discounts, sales, and promotions. Also, a lot of the different discounts are based on a day of the week and/or a specific time.

- Eric has done a number of these custom discount and pricing engines. Eric was saying that some of the discounts are not created equal... bogo (buy one get one) vs auto calculating all similar items and then repricing based off of quantity (just as an example).

- Some discounts and promotions will be standard (hoping to catch 80% or more). There may be others that are just plain custom. Those still needs to stay on that level, meaning we may still need the option for custom code.

- Anthony would love to help push the development forward in such a way that the users (adilas clients) could use the system to tweak the system. If they, our clients, need to call a developer all the time, that gets crazy and very expensive. The solution needs to be out to sales and promotions and virtual campaigns. Eric and I have also talked about allowing discount rules and such.

- Anthony has some price grouping and some needs there. Similar to smart group buttons and tiered pricing structures. He would love the cart to be able to keep track of those pricing tiers and virtual groups. He would like the ability to move and manage pricing structures based on groups (even a subset of part/item categories).

- Lots of needs for time based discounts such as happy hour, certain deals, etc. It would be super cool if we could setup all of these rotating discounts and the cart is able to apply those on the fly and as needed. Basically, we need an automated pricing engine.

- Some of these discount rules may need to be built and held in a coupon, sales, and promotions type system.

- Eric was talking bigger volume shops vs the mom and pop shops. They all want that kind of feature but it comes down to cost. If we could build it into the system, it would benefit all parties.

- Eric would like to see a printed list of what kind of discounts they offer. That would help us in the background make sure we can build out the rules that would be needed.

- Anthony would like to know a cost and timeframe. Eric was talking about phases and options for deployment and development. Then Eric talked about building out the standard features, all-a-cart features, and then also being able to customize things if needed.

- They would really like the pricing tiers to work similar to the smart group buttons without having to tie them into a button. Basically, behind the scenes, they have rules (what to do) and assignments (who can play). That is the same basic model that is still needed, just not tied to a button. This may end up being part of the pricing engine. The cool thing would be rules that could also be tied into time and time-based promotions. The higher level (meaning the top level or group level) of pricing really helps with speed to market and ease of use.

- Steve was saying that sometimes it takes years to get a stable picture of what is really needed. That is a huge key.

- Sharing knowledge and helping others be able to run and go forward. Anthony has some great operational experience... we would really love to tap into that. A huge knowledge base of experience. Another huge asset is perspective and vision. Those are both huge assets.

- There is a huge training need. Some people will use what we have but they may not even know we have it. That comes back to ease of use and education.

- Molly popped in - what comes first, the pricing engine or the coupons and sales?

- There are a few main pieces to help everything play in and work together. We are seeing sales and promotions, pricing engines (cart logic), custom labels, sub inventory, mini conversions, discount rules, tiered pricing models, customer loyalty points, gift cards, coupons, etc. They all play together and have similar pieces that need to be coordinated. We know we need all of these pieces, the trick will be what comes first? And how do we pull things together?

- As a side note... when setting up pricing groups, we may need to pull in parent attributes to help us create good groups and grouping.

- Small complaint on packaging and sub packaging, when they add a new one (sub), they have to re-enter the price (every time). They would love it to be tied to a pricing group. They also want to make sure that we keep them in a good process path. They would love the new subs to pull in the price from the group pricing vs setting it every time. They do want to be able to change it if needed, but they would love it that price auto pulled itself into a preset pricing group. This is a big priority to help make it easy and more standard.

- Mini conversions are really needed here soon. The deeper we go, the more we are needing that ability. What they are calling (our clients) packaging is really mini conversions of sorts. There are a number of clients that are doing internal manufacturing inside their systems. We need to help them out with that. Also, when the customers buy things, they want to be able to search for one item (not 50 million), and then be able to buy and sell those items in different sizes, packages, and conversion pieces. In the frontend, they want it really simple. In the backend, we need to mix and blend and cross-tie things in and maintain the correct relationships. That is really huge.

- The more we help to automate things, the less chances for user error.

 
No po photos available. Click to view time details.
Shop 3655 Lunch 4/10/2018  
 
No po photos available. Click to view time details.
Shop 3656 Adilas Time 4/10/2018  

Working on payroll changes and being able to search and show reports with the county withholdings. Also chatted and talked with Calvin about where he is at with his project. He showed me a demo and we talked about the next steps and such. Here soon, he will be to the part where we are doing recipe/builds. The client calls them formulations but basically, they are recipe/builds.

 
No po photos available. Click to view time details.
Shop 3663 White label: choose corp page 4/10/2018  

Working with Bryan on multiple different projects. We spent quite a bit of time either talking about things and/or going over questions and options. Good session.

 
No po photos available. Click to view time details.
Shop 3664 Brian Topping: Elevele fulfillment page speed 4/10/2018  

Looking over code with Bryan on a custom fulfillment page. The client just wanted to make sure that the page was optimized as much as possible.

 
No po photos available. Click to view time details.
Shop 3665 Fixing and launching new payroll code 4/10/2018  

Testing and fixing some new payroll code. I had to rewrite a state look-up to populate new state id numbers. Pushed up code and tested live.

 
No po photos available. Click to view time details.
Shop 3657 Adilas Time 4/11/2018  

In the morning meeting today, we started out talking about security and the value of data. We are seeing more and more a bigger need for being proactive on security issues. Russell and Steve were talking and I was taking notes and chiming in here and there.

- Steve was talking about a senate hearing and about how Facebook had an outside app that grabbed some of the data from their users. Big deal. We want to be proactive and setup our structure to allow data flow but only where and as needed. We also want our clients to play into the yes/no decisions of what happens to that data.

- Steve was talking and asking questions about closing down the hatch on customer data. This was mostly dealing with 3rd party solutions and internal adilas API sockets. Internally, we have often used the analogy of opening and closing virtual windows and doors. We were using similar verbage and talking about what is installed, what is still needed, and what the ideal would be.

- The value of data - this is the new gold mine. We spent some time talking about how data and being able to get at data is a new form of currency. As a side note, we had a company tell us one time that they would be willing to foot the bill and put clients on a system, pay for everything, etc. The only catch was, they wanted full access to all the data that was entered and generated. They were going to use the data for marketing and research. They just wanted the data and access to that data. That is the value of data.

- Black box and updating code. We talked core vs black box. Who is responsible for the updates? Do all updates get passed down or only critical updates? When building black box code, we need to make sure that we are going off of the last known good.

- We talked about how both education and maintenance are more important that new features. Sometimes that is hard to see.

- We need a team meeting to cover security, API sockets, and black box code.

- Shannon could be a good tester and even a person who could record and present the new features and such. Have her support a support team. We would love to tap into her mind and see what we can pull out.

- Speed at which things are going - it is hard to slow down enough to do help files, news and updates, videos, and training. However, that is part of the education and maintenance that is needed.

- We may need to hire out some technical writers.

- Lift where you stand - everybody just helps where they are. Russell brought up this point that he learned from Dieter F. Uchtdorf, Quorum of the twelve apostles.

- We are seeing a problem with only certain people having the knowledge... For example - Will did the direct deposit section... nobody else knows about it. Alan did the EMV chip reader stuff for credit cards... nobody else knows about it. Russell did the email marketing stuff. Same deal, no one else knows it as well as he does. We need to share and spread the knowledge.

- Change - we are seeing that we are either too busy and it is hard to learn something new or the new way is harder (or seems harder) than the old way. We often resist change.

- Sadly, our focus tends to be on what is not done or what is still needed vs what is done and what works. We may never get to the end of the road. Maybe we need to change our focus.

- The other idea of the day was... schedule what we need... this could be training meetings, harvesting experience (info mining sessions), harvesting knowledge from the person who did it, and then publishing that information for others to see and/or use. Help educate ourselves and our users.

 
No po photos available. Click to view time details.
Adi 1471 Schedule data mining sessions with Shannon to get common tech support stuff 4/11/2018  

Shannon learned a ton in tech support over 2 yrs.

Goal is to determine top questions asked by clients.








 
No po photos available. Click to view time details.
Adi 1472 Sub inventory API sockets - currently, they don't really exist in our public API sockets 4/11/2018  

Brandon completed 2019

We have lots of documentation, samples.








 
No po photos available. Click to view time details.
Shop 3666 Barcodes and discounts 4/11/2018  

Just some ideas on barcodes and set discounts. I just responded to an email asking if we had the availability to scan a barcode and have the system do a set discount. I had to reply and say no, not yet. I did say that we have custom button that can have a fixed price or a variable price but we can't auto include set discounts based off of barcodes yet. I did mention that the custom button could contain custom verbage. When all is said and done, I can affect a price but not by showing discounts.

So, where do we want it to go? I think that barcodes are very important and a great way to do a direct search and/or find a specific thing. It really speeds things up. We would need a system in place to be able to interpret the barcode scan and then know what to do based off of that barcode. This comes to a logic and/or smart cart type brain or mentality.

I would also like to see our custom buttons have the ability to store, show, and calculate specific discounts. To take that one step further... It would be nice to have the same functionality as the buttons without the button. Basically, make the logic and functionality of the buttons be more generic and transparent. That way we wouldn't have to use the buttons.

This is just an idea... what if we made a whole other section where people could build hidden buttons. Basically, the system could use the same tables and logic but no physical button exists. The new entity could be called a price/discount programming or a pricing engine. People have loved our buttons and what they do... they just want things more on a global and easy to update bases. What if we took the logic and functions of our buttons and made them more transparent and/or showed them as pricing rules. We then get the advantage of the buttons without using the buttons... Maybe we focus more on the barcode part of it and then go from there. That could really work and would be awesome. Anyways, just an idea.

 
No po photos available. Click to view time details.
Shop 3668 Show more data - parts and invoice searches 4/11/2018  

We have had requests to be able to show more data on both parts and invoice line item searches. Both of those sections currently have advanced searches, but the output (fields and values) are hardcoded and somewhat limited. It would be nice if we allowed a pick and choose-type interface like we have on some of the other advanced searches. It would also be cool if we allowed all of those searches to be saved as favorites as well.

While on the same subject, we need to be able to more fully search RFID tags from the quick search, be able to search all existing sub inventory pieces, and other advanced searches and exports.

 
No po photos available. Click to view time details.
Shop 3658 Adilas Time 4/11/2018  

Emails, paying bills, and on a Zoom session with Calvin. He showed me a new demo of where he is and we chatted and talked about the next steps. He is making good progress.

Talking to Steve about buttons, barcodes, labels, coupons, etc. They are all ways to get things into the cart and/or affecting pricing and discounts. That is an interesting point.

Steve has really helped me delegate more. He is good at it and even encourages me to do the same. Sometimes it is just an idea or a suggestion, and other times, he may help nudge the boat in the right direction and then it makes it easier for me to do what I need to do to advance the ball. Good teamwork stuff.

Spent most of the afternoon doing tech support, emails, recording notes, and talking to Shawn about new payroll changes. Shawn and I got his system all up to date and new files pulled down. I called and chatted with SteveĀ (see a couple small notes above) and then did the other things. Busy day.

 
No po photos available. Click to view time details.
Shop 3659 Adilas Time 4/12/2018  

Talking with Russell over the morning meeting. He was showing me around the new news and updates pages. Lots of new tools and features and ways to showcase features, benefits, advantages, support items, and topics of interest. Good stuff. Russell is also putting a really nice flavor to the new graphics and such. He is taking things to a much higher level. That is awesome.

Russell and I had a pretty good conversation about the direction that we want to take. We both talked and expressed that we want to keep adilas as a general tool that could be used by all kinds of businesses and individuals. We talked about an analogy of a tree with roots and branches. Our goal is to keep things balanced. I asked Russell to help steer us in that direction. I gave him a thumbs up and the verbal go ahead.

As a side note, our developer's notebooks and meeting notes have a virtual gold mine of information, ideas, lessons learned, and vision for the future. We need to slow down enough to tap into that resource. It is huge and covers almost 20 years of experience.

Alan popped in and we chatted for a bit. We went over some our upcoming plans and how we are going to tie things together. Basically, we'll keep pushing on in-line dollar off discounts, other discount rules, and then finish up the sales tax piece. We will then roll into options to expand the my cart favorite buttons and turn that portion into the pricing engine or the foundation of the pricing engine. That will naturally tie into sales and promotions and such. We'll have Eric working on loyalty points and gift cards and special tracking accounts. In the mean time, we'll circle back around and help with sub inventory and mini conversions. Ideally we'll also have Calvin working on the foundation of the label builder pieces. Once we get all of those pieces in and stabilized, that should really help.

Alan would also like permission to setup a testing server environment. We talked about using the adilas content server as that environment. Good stuff. We need to test and be confident that things will work in live scenarios, especially with the new database changes and world building stuff that is coming up.

As we were talking, Alan would like to build in some testing and more active object oriented stuff. This means more session based stuff, classes, objects, functions, getters, setters, etc. Piecing things together and combining like code into families and related code sets. Alan and I also talked about how we really want to tie in to time and elements of time as part of the object oriented model. We went out to the developer photo gallery (old drawings and graphics from the developer's notebook) and talked about how huge the time element is to the whole project. We also lightly talked about 3D world building and concepts of the data assembly line. Good conversation.

Spent the rest of the session paying bills, recording notes, and doing emails and tech support stuff.

 
No po photos available. Click to view time details.
Shop 3660 Adilas Time 4/12/2018  

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

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

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

 
No po photos available. Click to view time details.
Shop 3667 CannaCard: check and push 4/12/2018  

Bryan and I checked out a branch of code and got it all ready to merge. We had a couple merge conflicts but got everything fixed, pushed, and online. Light testing as well.

This is kinda a fun side note... Bryan and I were talking and I told Bryan that of all of the other developers, he has done the highest number of custom projects. These are not actual numbers, but he said that he did 33 custom projects last quarter. We did some light math and came up with over 400 custom projects in the last 3.5 years. Pretty cool.

 
No po photos available. Click to view time details.
Shop 3678 General 4/12/2018  

Clean up, recording notes, and working with Russell on some of the changes to the main web site and other internal changes. We met over a Zoom session for 30 minutes and he showed me some of the new changes. They will go live on Monday. Good stuff.

 
No po photos available. Click to view time details.
Shop 3642 Brandon out of the office all day 4/13/2018  
 
No po photos available. Click to view time details.
Shop 3679 General 4/13/2018  

Throughout the day, various phone calls, emails, and even some quick bug fixing. Some of it was done in small chunks here and there clear up until 4:15 pm.

The bug fix was dealing with some custom code that was updated. We (Bryan and I) pushed the files last night. Nothing looked like it had changed other than what we changed. Apparently, there was code that was live that we didn't have. Who knows what pieces we overwrote, but we got a number of calls and questions due to the change in the code. Originally, it looked like some permissions had changed for users. That was kinda scary and so we spent quite a bit of time there looking around. What we ended up finding was the page was checking for permission id #118 (advanced add to cart). We changed the page to look for permission id #116 (sales and profit reports). We then repushed the code.

Here is the scary thing... We ended up getting calls on both changes... it just makes me wonder what else may have been changed, updated, or other code that was overwritten. We are trying to get things circled into the master code branch and I think we are doing a pretty good job. Some of these custom files haven't been watched as closely and thus we see some possible problems. Anyways, just recording what happened.

 
No po photos available. Click to view time details.
Shop 3680 General 4/14/2018  

Tons of emails are still pouring in about sales tax issues and such. That is a huge project and has so many outreaching pieces. Anyways, jumping in to see what we can get done. Tons of emails, recording notes, and paying bills. The number of emails that require long answers and bigger tech support pieces are pretty big right now. That must mean we have a bigger problem than we realize. Also, it means that people are using our system and relying on it. We just need to rise up and get things fixed as soon as possible. This kind of stuff affects consumer confidence. I've seen it before. Kinda like your kids... earn trust by the drop and loose it by the bucket.

Worked on some of the sales tax reports. Spent most of the day working on the main advanced invoice line item search, results, and super search results. Lots of exports to both MS Excel and CSV (comma separated values) files and formats. Tested files and pushed live.

 
No po photos available. Click to view time details.
Shop 3669 Adilas Time 4/16/2018  

On the morning meeting with Steve, Russell, Alan, Wayne, and myself. We started out and Russell needed to do some code sign-off. He had a number of new CSS changes, verbage changes, and small changes to links and news and updates. We went over the changes and pushed things up live to the servers. That took about an hour. After that, Wayne and I talked about QuickBooks integration and doing both exports and imports to and from adilas. This is a custom project that Wayne is looking into and has a client that is paying him to plow some ground there. We also talked about some more advanced cross-server data migration projects and such.

These are a couple of points that Steve brought up after the other guys left.

- Plan most of our changes for 100+ people and/or users... think bigger than just one or two. That helps us make the best decisions. All other things that might swing one way or another should be permissions and/or settings. Great advice.

- Steve also sees a whole new round of permissions coming... it is amazing to see how each things needs to virtually break into subs to get the level of control that you need.

 
No po photos available. Click to view time details.
Shop 3670 Adilas Time 4/16/2018  

Working on cascading the rounding error into the main sales tax report. Light tech support via email and a phone call with Calvin about his custom desktop app.

 
No po photos available. Click to view time details.
Shop 3677 In-line discounts with Alan 4/16/2018  

Met up with Alan and we went over options for USAePay, merchant processing, and reoccurring invoices. I showed him around a bit and showed him pages where certain things happen. We then talked about where we are at with the in-line discounts. We decided to reschedule for the in-line discounts. I went back and finished up some code and cascading the rounding error to the main sales tax reports and checking other balance sheet reports, sales reports, and history reports.

 
No po photos available. Click to view time details.
Shop 3671 Adilas Time 4/17/2018  

Online team meeting to cover security, adilas API sockets, black box code, and upcoming white label options. We started out with a number of reports by the different guys.

/////////////////// here are some of the quick reports by the developers:

- Eric - Fixing custom carts and working on the pricing engines. Lots of custom one-off's. Working on loyalty points and special tracking accounts.

- Russell - News and updates - new API socket feeds and such. WordPress site and other look and feel things.

- Wayne - Refactoring code, testing based design, and underlying framework. QuickBooks integration stuff - imports and exports. As a side note, Bryan has had many customers asking about similar type features. Wayne is also working on other database stuff and migration.

- Bryan - White label stuff for outside parties. Tons of custom projects.

- Calvin - Hybrid API to Windows desktop app. Custom PDF labels and printing.

- Alan - Helping Steve with Metrc API stuff. Working on tons of tax and in-line discounts. Helping Brandon with other projects.

- Danny - Generating sales - Props to the developers who are creating the functionality. He pitches the idea that the developers are accessible. Custom labels.

- Shawn - Helping with payroll, federal withholdings, state withholdings, and county level withholdings.

- Brandon - Helping the developers and doing small projects. Merging code and maintenance stuff.

- Steve - Grateful for the help with the Metrc API stuff. Working on phases and sub locations. Steering the ship. New approval levels on other state traceability systems.

//////////////////// meeting notes:

- Talking about the Adilas API and system - dealing with security. Facebook was brought before the senate due to a breach. They allowed an outside company to come in and develop an app for Facebook (basically a 3rd party solution). The problem was... what does that outside service actually do and have access to? The app ended up doing some internal data mining and then sold that data.

- We want our users to be successful - we want to enable them but we also need to protect them.

- Small switch in the sales focus. The older model was one-by-one and dealing with reps and consultants. We are seeing more of a switch to bigger companies that virtually take over the sales force and are wanting to sell our product more as a white label type application. Lots of mixing and blending of products and services. They are allowed to provide all of the supporting services that support our product.

- Ideas from the group about security:

- Russell said, bold it or make it red and let them know what they are exposing (meaning the API sockets). Allow the agreements between the parties... we are part of it, but we let them create the relationships between themselves.

- Steve said, we don't want to make our users work harder... to turn things on, but we do want to make sure that the clients know what they are getting in to. Example of what happened with back in 2015 with Hypur and Emerald Fields (two of our clients). Basically, the 3rd party solution (Hypur) got turned on and then it kept growing (what Hypur was doing and/or requiring) and eventually was trying to get at more sensitive sales and inventory level stuff. Eventually the client was super upset due to the lack of disclosure of what was going on and what was open/available to the outside party.

- We are seeing that most of these 3rd parties and white label people tend to expand what they are asking for. Bryan is seeing that more and more auditing type levels are wanted by these 3rd parties. We have also had a number of questions about different server levels and certifications. Our clients want to make sure that their data is safe and secure.

- Russell brought up the point and the difference between a couple of if statements on a page vs a full on white label type solution. We need to develop and standardize that white label type path. They need to pay for it and also be able to help maintain it (meaning the white label company). Taking things clear out to a white label theme (actual files and folders). White labeling is basically bulk black boxing but you can still use any of the classic pieces. We drew some small diagrams and talked about possible options.

- Shawn chimed in and started talking about building a city. Basically, kinda like urban sprawl or older parts of a bigger city - no plan, no alleys, buildings touch other buildings, and not a well planned layout.

- We need to stay on top of things. Keeping code and the database structure up to date. If we do this... it will help us be more efficient and save us time.

- Eric chimed in and said "process" is the solution vs simple communication only. Basically, as we are growing, we need to get to a more standardized process of development. We have a huge landscape to consider. Lots of moving pieces. Ultimately we need to adopt a process oriented approach. Wayne agrees. Different levels within software development. From critical and saving lives to making sure that we have solid code and pieces. It gets into speed and flexibility against slow and more stable type processes. Maturity in software development is sometimes measured in how well you implement internal processes. Eric thinks this is the next step we need to take as a company.

- Danny has been threatened... :) He was talking about levels that people rely on our solution and how all of that plays in and such.

- Small little analogy of the little red hen... everybody wants it but they may or may not want to participate. In real life, things cost money and take time to get done.

- From Brandon - Let's make this thing what we want it to be!

- Any core elements need to be merged into the master branch. This is required.

- Steve was saying... be on the lookout for companies and what they are wanting. That could help us know how to play with them... Maybe look deeper than the current project. We really need to protect our client's data. He was talking about the adilas market (adilas world) and also the 3rd party solutions page. We need to point outside parties to come through the main monitored pathways. We need to keep those sections updated and let the clients know what is being opened/exposed. Very important.

- The value of oversight and/or having someone to help watch them and help them out. This seems to be new trend. If that is the case, we need to make sure that they know what is going on and what is opened and what is closed (talking about data).

- Brandon will write up some super basic pieces of what our current rules and processes are.

- Alan pitched the idea... Local, live, and then into production - talking about a testing server that will be coming this year.

We ended the meeting and allowed people to jump off the meeting. We basically said we would be doing this again (meaning a team meeting) and would get them some info and instructions.

/////////////////////// after the meeting

- Alan and Steve were talking about breaking up code into logical pieces and making the road map more object oriented. Basically, organizing the use and flow of data - making the map for others to follow. Currently, we are just using Brandon's memory to help guide people to the right spot. We need a better road map that others can follow.

- They got into some technical conversations about threads, processes, RAM memory, read/write times, etc.

- Part of our process needs to be setting up and monitoring the servers (actual eyes and reports or dashboards). We need more information, stats, what pages are being used, what processes are running, and what data is being accessed and how often?

- We talked about caching, traffic, threads, database transactions, data mining, and changing from transactional data to more of an aggregated type model (summing up things and organizing things for reporting features). We need to keep allowing day to day operations but also need to optimize things for reports, exports, and other bulk reporting features.

- Alan and Steve were talking about the challenges of using outside API's and syncing up data between systems. Lots of options, but also lots of moving pieces.

- On the API sockets... We need to provide good samples of how to call things and also good response type data. It is really nice if we can format things as well. It just makes it easier for our guys and also outside developers.

 
No po photos available. Click to view time details.
Shop 3683 Little gem from the past 4/17/2018  

From a document dated 1/24/15.
This is a common saying for people who are delegators and managers and leaders: DIA or

D - delegate

I - inspect

A - approve

What if we did a similar things and used the name ADILAS as a fun project model:

A - Acquire, Accept, Approve Requests

D - Delegate to our team, Determine the scope, goals, and budgets (internal project management)

I - Inspect - details, microscope, inspect what we expect, iterations (going through the testing and processes)

L - Love (us, them, you), logging and communication, love (feedback, customer, developer encouragement), logistics, learning

A - Approve - clean-up, upload, feedback

S - Submit - close out project, push code, bill, sustain, etc.

We could develop this further... just making a note of it as often things get kicked under rugs and then never resurface. Kinda fun ideas.

 
No po photos available. Click to view time details.
Shop 3684 Sales and discount reports 4/17/2018  

We have had requests for better reports to help show products, sales, and discounts per vendor or per part category. This will be really important as the new in-line dollars off discounts come in to play. We need to be able to show in-line percentages, in-line dollars off, in-line mixed discounts, and sales campaigns. All very important and needed. A good spot might be the advanced invoice line item search and the super invoice line item search pages and results. Both of those pages also export out to MS Excel and CSV.

As a side note, there is one discount report currently in the system. You can get there by going to the invoice homepage, then click the other sales reports button at the top. Once on that page, there is a discounts report under the sales by column. Very simple report but currently the only discount report that exists as of 4/17/18. (top_secret/custom/sales_salesperson_specific_discounts.cfm)

 
No po photos available. Click to view time details.
Shop 3685 Payroll requests 4/17/2018  

Various payroll requests:

1. We have had request to be able to calculate overtime based on a daily threshold. We have seen numbers such as anything over 8 hours a day or anything over 12 hours a day. We have also see other requests to mix and blend both daily and weekly thresholds such as anything over 12 hours a day or anything over 40 hours a week. Both calcs need to play in.

2. On the time cards, it would be really nice if we added a few new totals and fields to hold other data. Currently, we are converting values (totals) into seconds and then calculating from there. It may be really nice to hold that value in a preformatted field and then run reports off of that. It would really speed up processing. Along with that, we may also want a couple of fields to help flag for overtime and even calculation what part of the record is overtime. The other request that goes along with time cards is being able to have a single date (searchable) and then be able to calculate totals that span from date 1 to date 2. This is common for people who work graveyard. For example: Clock in at 10 pm on day 1 and then clock out at 7 am on day 2. Currently, the system requires an entry from 10 pm to midnight on day 1 and another record from midnight to 7am on day 2. It would be really nice if we could allow bigger spans and have everything pre calculated.

3. We had requests to be able to keep track of sick time, vacation time, and what is still owed. Basically, keeping track of an accrual of what is still owed and what has been used. They also want to be able to set dollar value rates and have the system calculate when they earn those pieces such as available sick time and available vacation time. As they are earned, they get added to the available amounts. Currently, we are able to clock in/out for both sick pay and vacation pay, but no other calcs are done and no other data other than the actuals per pay period are recorded. This would need to be expanded and planned out better.

 
No po photos available. Click to view time details.
Shop 3672 Adilas Time 4/17/2018  
 
No po photos available. Click to view time details.
Shop 3681 Sub inventory API stuff 4/17/2018  

I was supposed to be working on sub inventory and adilas API sockets but got pulled into the virtual whirlpool of emails. Still digging out from almost a week ago.

 
No po photos available. Click to view time details.
Shop 3673 Adilas Time 4/18/2018  

Russell and Steve were talking about the process for 3rd party solutions and how to white label things. What are the thresholds, the paths, and the requirements? We also talked about getting our people into the adilas market (adilas world) and into the 3rd party solutions page. It might depend on who they are, as far as cost to be part of that 3rd party solution. Steve will be controlling that gateway for now.

- All 3rd party solutions must go through Steve to get approval. Other developer will work on the projects, but Steve will be the approver and gatekeeper.

- Talking about the value and perceived value of using adilas as a white label.

- You have to be on the 3rd party solution page and in the adilas market. Between $1,500 and $3,500 (depending on size)

- A white label gets a 30% discount on the system. They then have to take care of the support for those accounts.

- A consultant doesn't get a discount, they get a commission back to them as the consultant.

- We briefly talked about laws against price fixing.

- Expectations and requirements for people who want to play to the white label level. Russell was also asking questions about price increases and how that flows through. Steve was saying that they still get the 30% discount based off of the current price (our prices may go up and down but the discount remains based off the current price).

- We are really excited to get into pricing based off of data storage and bandwidth and usage. We need to show our users how much data we are storing and processing.

- Comment from Russell - If we go into normal black box code and/or bulk black box code (white label), the code is as is. If they want updates, they need to pay for them. Or we could add an update fee or a  yearly maintenance fee.

- Delegation - it is hard to delegate sometimes because you feel like you don't have time. There is also a comfort level and even a separation anxiety that happens as you start to delegate. Ask your self, do I really need to do this or can someone else do it? Think of a snake shedding his skin... it just needs to happen.

- We have to refine what we do just like adilas has to refine what it does. Life requires refinement.

- We are way stronger together.

- We, Steve and I, are in the business of delegation and oversight. Sell the vision.

- We are looking for people that are looking for certain opportunities and/or are hungry for certain pieces.

- Get Bryan to help pave the way for the upcoming and future white label options.

- We are looking at ways of avoiding the burning platform (proactive approaches). We are trying to push monies in key places where we see things happening. Basically, skate to where the puck will be.

- A note about "change". Sometime the word change scares people, including me. Maybe we could use the word "refinement" or "tweaking" with less fear of the actual change.

Alan popped in and both of us started working on the in-line discounts stuff. I was going through files and merging in changes from other branches and master files into our current tax branch. Alan was coding other pages and prepping files. Steve was doing phone calls and other meetings.

 
No po photos available. Click to view time details.
Shop 3686 Formating for time - maybe a small bug 4/18/2018  

Alan brought up a possible small bug in the time formatting. We have tons of code that has "h:mm" or something like that. That looks like hours and minutes, but the mm is actually a month piece. We need to switch things to an "h:nn" type mode (two n's back to back is for minutes. Alan's initial search revealed over 600+ pieces of code that may need to be switched. Small tweak, but it could really help.

 
No po photos available. Click to view time details.
Shop 3674 Adilas Time 4/18/2018  

Working on merging in files for the in-line dollars off discount project.

 
No po photos available. Click to view time details.
Shop 3682 Expo-Choose corp 4/18/2018  

Bryan, Steve, and I joined up on a GoToMeeting session. Steve started out and showed us some of his work that he has been doing in the elements of time with sub phases, sub locations, and such. Good demo and he is making tons of progress. Basically, a full on internal wire job using parts, items, PO's, elements of time, sub inventory, and sub phases (special flags and tags). Pretty cool.

After that, Bryan and I chatted about options. I tried to show him where we were headed and he brought up some valid points. One of the points that he brought up was how complex and how many moving pieces. He wanted to do a simple build out to help a single client. We talked about it and he showed me what was planned and we decided that he could do that if he used the new custom JSON table that stored custom JSON objects. The better choice is to go in the direction that Steve is going with subs of time but it does take time to build all of that stuff out. I did warn Bryan that the custom JSON will allow him to store almost anything but it will be harder to pull reports and/or search. Basically, JSON is another word for miscellaneous blob of information vs rows and columns like a traditional database table.

Our final project was going into the secure/choose_corp.cfm page and making it into a black box page. That page has been used and abused (code wise) and wasn't really that straight forward. We got in there and finally I told Bryan to keep working on it and then get back with me. We have different styles and I thought it would be better to let his do his thing and then bring it back to me when he got it work. I felt like a back seat driver... :)

 
Click to view time photos.
Shop 3675 Adilas Time 4/19/2018  

Briefly talking with Russell and Steve about 3D data tables and reports. We would love to offer different views, sums, totals, graphs, etc. We would love to create a virtual dashboard that looks cool and provides a great look at what we have stored and even what it means. We popped into some older drawings from the developer's notebook and looked at concepts for 3D calendars (virtual drawers broken down into months, weeks, days, hours, minutes, etc.), displays based off of categories and totals, and other report views.

Later in the session, I went back and spent some time and did some review of the drawings and concepts that we are trying to bring together. I would really like to get back to some of those pieces.

See the photo gallery for some screen shots. If you need more, go to the photo gallery - online developer's photo gallery

 
No po photos available. Click to view time details.
Shop 3676 Adilas Time 4/19/2018  
 
No po photos available. Click to view time details.
Shop 3687 White label 4/19/2018  

Working with Bryan over a GoToMeeting session. The first thing we talked about was how to use and setup sub locations and sub phases. I tried to show Bryan where we are headed (subs of elements of time), but since the code is not fully done, he wasn't very excited about going in that direction. We talked about it and he really wanted a super simple solution. We talked about storing custom JSON objects but that has limits dealing with searching and such. We decided that we would allow black box database tables on a per corp basis. This is the first black box code for the database. The main requirement was the naming of the table. It had to be black_box_something_corpid where something was whatever was needed and corpid was the corporation id number of the asking corp. This is new territory.

After that, we went on and worked on the Expo login and trying to get the choose corp match and follow suite. We then talked about Animate CC and what was possible. I showed Bryan a small demo of what was possible with the older Flash and ActionScripting stuff and presumably what was still possible with Animate CC.

 
No po photos available. Click to view time details.
Shop 3643 Brandon out of the office all day 4/20/2018  
 
No po photos available. Click to view time details.
Shop 3689 Adilas Time 4/23/2018  

On the morning GoToMeeting session. Russell, Alan, and Eric popped in at different times. I helped Russell merge in the new WordPress news and updates page. It pulls an API socket feed from our WordPress site. Alan reported on in-line discounts and we'll be pushing more on that project this week. Hopefully, it will be ready and be pushed by end of the week. Eric had some questions about tiered pricing and where we are headed with that. I told him that we may end up using the existing my cart favorite buttons section and then beefing that up in order to handle system-wide pricing tiers.

I spent some time looking over a large email thread that has numerous questions about calculating taxes and how things get rolled together. I was in on the client's site looking around and running my own test calculations.

 
No po photos available. Click to view time details.
Shop 3690 Adilas Time 4/23/2018  

Recording notes and on a Zoom session with Calvin. We talked about his progress on his custom desktop application. We went over the submit cart page and talked about new API sockets that he would need to use for doing invoices, line items, and sub inventory. After that we talked about a meeting between Calvin and Wayne Andersen. They swapped some ideas and Calvin gave him some code to help Wayne get started on project.

 
No po photos available. Click to view time details.
Shop 3688 General 4/23/2018  

Reworking the adilas developer's guide book. I included some rules for black boxes, 3rd party solutions, and white label stuff. See attached for a couple of the files that were sent to the developers. I also went through the old calculate taxes method and made a rough outline as to our process for calculating both normal taxes and with tax included options. I need to do a comparison to see what we do now for the tax calculations. There are slight differences... It may come back to formatting, rounding, number of decimals, and even when the formatting or rounding was done. Pretty deep.

 
No po photos available. Click to view time details.
Shop 3691 Adilas Time 4/24/2018  

On the morning meeting. Pretty quiet. Russell popped in for a bit but most of the session was a work session. I was working on building a sales tax calculator page for users to test out sales tax and location settings.

Small note on global simple getters and setters... As I was hiking this morning, I was thinking about simple getters and setters. As I was doing that, I would really like to make one super generic setter. Imagine a corporation id, a table name, an id number, a column name, and a value. It could be that simple. Then we could use it over and over again. We might beef it up a bit by allowing lists and arrays of name/value pairs but it could be pretty simple. On a simple getter, what if you could pass in a corporation id number, a table name, a list of fields to pull, and any special criteria. You may also need an order by clause, a group by clause, a limit clause, etc. All extras would be optional and well documented. If you wanted everything, you could just use key words such as all, auto, etc.

Here are a couple advanced SQL methods that we may end up pulling ideas and info from: "tableRecordCounter", "getCustomersSimple", "adminGeneralSQL", and "getSpecificCorpWideSettings". See also these pages for dynamic SQL stuff: developer_update_tables.cfm, test_page.cfm. These are listed to help with getters and setters. Just concepts of what we are trying to do.

Another small thought... While working today on a new calculator page... I was thinking that it might be good if I were to help go through the application and do some maintenance stuff. Don't do huge big projects, but do some code, get it done, merge it in, and push it up. Tons of mini projects. This could be checking pages, writing help files, doing web/API documentation, testing things, adding black box code, checking icon menus, etc. All kinds of stuff that needs somebody to look at it little by little. Just a thought.

 
No po photos available. Click to view time details.
Shop 3692 Adilas Time 4/24/2018  

Calvin called and we chatted about his desktop app and getting it closer and closer to the first release. That is exciting. The other thing that is exciting is that he, Calvin, was able to share his code or parts of his code with another developer who needs to do something similar. That helps and is awesome.

 
No po photos available. Click to view time details.
Shop 3697 Brandon Time 4/24/2018  

have to take care of some personal business.

 
No po photos available. Click to view time details.
Shop 3698 White label 4/24/2018  
 
No po photos available. Click to view time details.
Shop 3693 Adilas Time 4/25/2018  

Talking about PHP projects with Russell. We talked about using Bridgerland and their developers to help build and maintain certain new and existing projects. Russell really would like to work on some developer training courses, API socket training courses, etc. Basically, ways of making it easier to get interested people into the development side of the system easier. We also spent some time talking about other possible projects... these would be built out using PHP and then connected to and/or talking to adilas.biz through external API sockets. Projects like outside scheduling of time (both adilas and google), outside ecommerce sites, visible elements of time (public viewable), project management, and scheduling time for employees. All great options. They would also be great projects for the Bridgerland developers.

We also talked about pushing more and more on the Adilas University site, the Adilas Market (adilas world), play at the wall (web/API sockets), and creating a fun and pretty front facing site. We will fund those projects. We will keep core adilas and custom code behind the wall and keep it internal as far as who builds on it. The rest is open territory.

Russell mentioned versioning our code so that we don't hurt other developers who have already done development. This is dealing with the API and then also making things backwards compatible. Basically, we really want outside developer to play the game and "Play at the wall". Good discussion.

After that, I reviewed some notes about time clocks (see attached for an email that was sent out in December of 2016). I also wanted to make a note that elements of time # 2042, here in the shop, has a ton of information about some of the payroll, time clocks, and project direction. Just trying to keep all of the pieces sorta linked together.

I scheduled a live adilas training session at Bridgerland for May 29th, 30th, and 31st. I let a few people know and will be trying to grab some ideas and such from key users, reps, developers, and admin persons. Good stuff.

 
No po photos available. Click to view time details.
Shop 3694 Adilas Time 4/25/2018  

Chatted on the phone with Calvin going over API socket connection for his desktop application. Also did some light planning for the upcoming live adilas training session. Here are a couple of random notes... no special order at this point.

- Sell the sizzle...

- Think GEO tourism for selling the venue and location of Logan, UT. 1.5 hours North of Salt Lake, hiking, fishing, history, USU campus, shopping, mountains, rivers, valley, Bear Lake, etc. 10 minutes from Logan, you could be in the mountains.

- Guest speakers - concepts, vision, processes, procedures, etc.

- Highlight new features, new updates, and upcoming projects. Think of things like Campaign Rise (social media and custom wire job for elements of time), Beaver Mountain Ski Area and Ski School, Steve's campground stuff, Plant phases and cultivation stuff, Russell's new custom email stuff, ecommerce, WordPress integration, white label stuff, sales tax changes, new discount options, etc.

- Show what has happened, what is happening, and what will be coming down the pipeline. Maybe show a timeline with some key points and historical stepping stones.

- World building concepts and how different clients are problem solving with adilas as their worlds change and progress. Try to focus on 3D world building and the concepts of the data assembly line. Show how some of that stuff is already playing out.

- Different topic, but I would really like to get some sites out there like billboards pointing back to adilas and what we are doing. These are all of the main concepts such as 3D world building, data assembly line, creating a system, API sockets and playing at the wall, etc. These might be great projects for Russell to give his developers who are going through the program at Bridgerland. Good stuff.

 
No po photos available. Click to view time details.
Shop 3700 Expo: push 4/25/2018  

Bryan and I got together and merged and pushed up some new code for the Expo choose corp page. Basically a new black box with some underlying new pages and logic. We then briefly talked about some of the new data servers that are being commissioned and brought into the puzzle. Bryan has 3 servers that he is working on right now. Two will be dedicated boxes and the third will be a new shared server for normal adilas clients.

 
No po photos available. Click to view time details.
Shop 3701 General 4/25/2018  

Emails and tech support. Working on the sales tax calculator page to help with new sales tax calcs.

 
No po photos available. Click to view time details.
Shop 3695 Adilas Time 4/26/2018  

Talking with Russell. We talked about some small billboard sites and pointing people to adilas and the adilas community. We talked about SEO (search engine optimization) and using existing verbage to help lead them to what we have and what we offer. For example: Things like CRM (customer relationship management), POS (point of sale system), ERP (enterprise resource planning), CMS (content management system), etc. Point all of those things to where it is going... We are leaning towards 3D world building, data assembly line stuff, new school accounting, and other concepts.

From our talks yesterday, these are some other projects that Russell thought would be cool. They are: a cool mobile app, more with time clocks, time - reservations and rentals, and other mobile ready pieces.

Alan hopped on and we went over progress on the in-line dollars off discount project. Alan is making great progress and we talked about a couple questions that he had. We also lightly touched base on the reoccurring invoicing and reoccurring merchant processing pieces that he is working on for Campaign Rise. Good reports.

Most of the session was spent working on the sales tax calculator page and showing the test calculations and output math.

 
No po photos available. Click to view time details.
Shop 3696 Adilas Time 4/26/2018  

Working with Shawn to get his local database updated and ready to go. He was missing one small piece that was buried underneath a database update. The update checked one of the fields and because it was ok, it skipped the rest of the update. We had to update some payroll tables manually. This only happened because Shawn was the original developer on the payroll project. I added the second table change after the code was submitted. Long story made short, he only had half of the needed changes.

On a Zoom session with Calvin. We looked into an error on an advanced main invoice search through the API. It turned out that he needed a table in his local environment to make the API socket run. It is amazing how quick things change and move. We really need to be pretty flexible in order to play our own game. Good stuff.

Finishing up the sales tax calculator page. Working on help files and testing the page.

 
No po photos available. Click to view time details.
Shop 3702 eXPO 4/26/2018  

Working with Bryan to introduce some custom black box options for exports to MS Excel. We added in a custom black box option on the printable parts report. This is the first black box access point to alter the Excel reports.

Calvin also called in and we chatted for a bit about locations and sub locations. He has a client that wants to track super-duper-sub inventory levels and sub locations. We might have to think about that and how it would play in. We already have a ton of this... I'm just not sure if we are deep enough yet.

 
No po photos available. Click to view time details.
Shop 3703 Finished up the sales tax calculator 4/26/2018  

Finished up the new sales tax calculator page. Added a new help file, pushed up new files, and cascaded new changes to all servers. I also helped Calvin with a couple of questions that he had dealing with sub inventory. As a side note, it is crazy how much time we have spent trying to fix sub inventory. Out of all of the projects that we have ever done, this one was done by a different developer, without supervision, minimal budget, and under crazy timeline pressure. I have literally spent hundreds and hundreds of hours fixing and trying to patch that project. I don't think I will do this, but I'm very tempted to do a full re-write and bring it up from ground zero. Just venting.

 
No po photos available. Click to view time details.
Shop 3644 Brandon out of the office all day 4/27/2018  
 
No po photos available. Click to view time details.
Shop 3705 Error fixing 4/27/2018  

Got a call and text message from Shari O. from out in the field. She was trying to setup a client with the new AFB time clock application. It was throwing an error. I went in and fixed and it and re-pushed up files and let Shari O. know about it. The bug took a bit to find and fix. Once we got it, it wasn't too bad. Other emails and tech support calls.

 
No po photos available. Click to view time details.
Shop 3706 Tech support 4/28/2018  

Answering tons of emails, doing tech support, making screen shots, and small look-up reports to check for things that different clients needed.

 
No po photos available. Click to view time details.
Shop 3707 Meeting with Calvin 4/28/2018  

Online meeting with Calvin over a Zoom session. We talked about tracking inventory to a sub level. Not just sub inventory, but sub inventory and moving it between smaller holding areas. Basically, sub inventory with multiple sub locations per batch and/or per group or lot. Not impossible, but definitely a full lever deeper than just plain sub inventory. We went over a few ideas and also some pros and cons of the current options. We decided to push it off and try to tackle it later on.

 
No po photos available. Click to view time details.
Shop 3708 Adilas Time 4/30/2018  

Brainstorming with Russell and Alan about the upcoming training event.

- news and updates, snow owl theme (look and feel and custom links), ecommerce, email, time clocks, other projects

- sub inventory training

- lots of emphasis on what is new and how that works and changes.

- reflexive flex grid, 2nd vendors, review what has happened over the years (maybe even research and setup a time line), future projects

- stay on task

- give industry specific training and maybe schedule things for a different training session or breakout sessions.

- open learning time... specific time to just practice with reps and consultants

- planned and special breakout sessions. So, for example, from 1-3 pm classes taught on this and that in this room and that in this other room, etc.

- as we host cooler and cooler events... we really have to charge and be professional. Make it really cool.

- try to shoot for 4 days. the 3rd day is mostly hands-on training

- 9-10:15, 10:30-12, 12-1, 1-2:30, 2:45-3:45, 4-5 sessions.

- make each day specific to the task at hand

- best practices

- Roxanne - training on financials. Lots of others who may be able to play.

- Having a pizza party with the crew - being able to hang out

- day 1, here is what is new with adilas. Maybe here is what is coming. Make it exciting.

- day 2 and 3, more specific training - POS (point of sale) and CRM (customer relationship management) stuff.

- day 4, hands-on training, one-on-one training, group training, open sessions, and industry specific training

- thinking about skipping the financial side of things for this first training

- we teach in general and then point them to the specific consultants to get industry specific info and advice.

- Get some of the power reps and have them be ready and available to help. Maybe even allow the reps to charge extra for custom time.

- Have someone who is watching for comments online and also taking notes. Someone to help with chat

- We could use one-person Zoom sessions to answer specific questions

- Try to get both Kelly and Molly out here to the training session. It may be $500 to $1,000 per super rep. Let them know that they could extend their stay and charge for individual consulting and other outside meetings. Or we split the fees with them for day 4. Day 4 could also be their thing and let them charge what they want. We could cover their plane tickets.

- Shooting for between 20 - 50 participants.

- Try to keep things industry specific between breaks and on day 4 group sessions.

- Run the payment through ecommerce. Setup online seats and live seats (limit the quantity).

- Run the new classes through the news and updates page.

- Come up with some numbers and budgets

- Document management options - After the session, I was answering some questions about custom forms, custom documents, and custom procedures. I was answering by telling about state manifests, transfer docs, state title work, and even the vacation rental and timeshare company that has a one page form in Adilas and it creates and saves multiple contracts and agreements and records them for clients. We also have gun clubs and such that sign waivers and then assign the signed waivers to the correct client record. Good stuff.

- This wasn't part of the session, but other notes on the training event from post-it notes and my mini notebook. Dated 4/27/18... Black box, presenters choice, Q&A, business topics, meet the developers, participant presentations, demos, industry specific, what is possible with _____ (fill in the blank), and interactive & hands on sessions. Other ideas might be direct video feeds, group games & hands on activities, watch a developer work - say a black box take over or something like that, reports from the field, exploring the database, white labels, dedicated servers, timed challenges, speed and shortcuts, custom wire jobs - show & tell.

 
No po photos available. Click to view time details.
Adi 1475 Add some options to the quick search - RFID, media/content, sub inventory, sub special accounts 4/30/2018  

Use quick search to find all places a word exists, or rfid. 

Could also be for looking up gif cards, loyalty points, instore credit, media files.






 
No po photos available. Click to view time details.
Shop 3709 Adilas Time 4/30/2018  

Working with Calvin to check his desktop app with what is showing on the web version of the same data. Making small tweaks and such. I also got on a tech support call with Mike Harman from Caisson Labs. I set him up as a user and showed him how to create other users. Light tech support.

 
No po photos available. Click to view time details.
Shop 3704 GDA push code 4/30/2018  

Working on projects with Bryan. We spent some time looking over options for older Flash widgets. We decided to re-install an older version of Flash and see if we could get things to work for now (small patch job on an existing Flash widget). Going backwards is with the idea of fully rebuilding later on. Installing new/old software.

 
No po photos available. Click to view time details.
Shop 3717 Working with Calvin 4/30/2018  

Going over code with Calvin. We were testing his custom desktop application together. Basically doing something in his app and then checking the data in the normal adilas browser-based (normal web) site. Light debugging and fixing small issues and problems.

 
No po photos available. Click to view time details.
Shop 3726 Debugging with Calvin 4/30/2018  

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

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