Adilas.biz Developer's Notebook Homepage

[reset this page] . [historical web outline - entries by month] . [adilas community funded projects] . [contact adilas.biz support - email form] . [help]

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 - 5/1/2017 to 5/31/2017 - (112)
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	Shop 2579		Adilas Time	5/1/2017	On the morning GoToMeeting session. Steve and Eric were on with me. Eric and I covered a few new requests to help with the sub queues and made a list of new requested features. We launched it and a number of small visual requests came in over the weekend. Good stuff. After that, Steve and I worked for about half an hour just catching up and talking about some direction. Eric came back on around 10 am and we worked until almost 12:30 pm on some new sub queue changes. We wrote some notes down and then started to push through them. We added a couple of edit link options, added some round trip editing (return where you started from), and changed up some sort orders. We also did some special queue work and joined up a couple of existing queries. After testing locally, we pushed up new files and ran some live tests. I also chatted with Calvin for about 15 minutes to touch base on the mini conversion project. We will be picking that project back up later this week. Good stuff.

	Shop 2599		Lunch	5/1/2017

	Shop 2523		Alan Time	5/1/2017	On a GoToMeeting session with Alan. We started out and Alan showed me a documents that he was working on that talked about tons of different programming methodologies and coding processes that we could potentially use. See attached for a copy of the file. After that, we did some brainstorming on questions that need to be asked to help us cross our t's and dot our i's. We started working on the specs and plans document. See attached. It still needs some major work, but this is where things are at as of right now. Making good progress.

	Shop 2580		Adilas Time	5/2/2017	On a GoToMeeting session with Steve, Alan, and Eric. We fixed a small filter on a custom homepage that deals with quotes and sub queues. We then went into more of the processes and procedure stuff. Eric helped Alan and I with some of his background and experiences. Good to hear some of that stuff. It really helps Alan and I capture some of the gems and highlights from Eric's experiences. From Eric - "Developing without project management is like a runaway train." Well said. Eric loves small frequent deliveries. Depending on the project, you may have to go deep before being able to give a deliverable. Other projects, you can push things out quicker. Think about the low hanging fruit. What is good and will give the most value without taking forever. You also have to consider dependencies and not orphaning things off on their own. - Don't customize things if you can find a way to standardize things. Think bigger picture. Make sure that a custom job is really a needed custom job. - The adilas team is somewhat of an unstructured group of developers and project managers. We may need to mix and blend based on the client and the project. Most of our projects are small to medium. If we play in the bigger field, we do need more of a real process. That could be a minimum requirements document and a design mock-up. - Sometimes showing some small prototyping can really help the discussions and talks move forward. People love to play with things. They also tend to be more understanding if they see it being built. That is awesome. - With adilas, we are small and it is really hard to implement full on teams and processes and procedures. We have to somewhat fake it and pull things together as it comes. We are growing and building, but we are still somewhat smallish in the team side of things. - Eric has been really good at taking the "one-off" development and trying to circle it back around and make it part of the core. That is awesome. We need to keep grabbing the ideas and information and then help build out the processes. Whether it is pricing engines, loyalty points, etc. Maybe we should try to work more together as small teams and small groups. We could really gain some advantages there. - Sometimes the developers don't know the whole system. They need some help in knowing the underlying design, concepts, and reach of the project. We need to help the developers know the architecture. Maybe even have the developers tell us what they understand. We need to check for understanding and make sure that they get it and can see the vision. We virtually don't send anybody into the forest without a guide of some kind. - Limit the number of projects at a single time. The more projects you have on your plate, the more you get spread out and lose some time in the transitions. The more you can focus, the better. - Sometimes growth comes with pain... Eventually it comes back to the 4 main stages of team development. They are forming, storming, norming, and performing. Things tend to go in cycles. If things get too far out, you end up having to do tons and tons of maintenance. - Eric was saying that he would love to have some well written documents but there is a trust level and a level of comfort on who is providing the specs. Eric really loves to be involved with the actual customer. It helps you get a flavor or what is needed and what they want. - Many of our developers are virtually a one-point shop. There are some huge advantages on that kind of person. Speed to get a project done can really increase. At the same time, some smaller teams, as needed, may really help us push things through faster and faster. - What are the benefits between small groups or being a smaller one-stop-shop type developer. Eric has done a great job of checking in and making sure it was ok in the direction he was going. Truly being a isolated one-man-show isn't good for anybody. We still need to check in and get some communication going on. Often we have other projects that are circling around and could help with your current projects. - If you are in a small team, there is some potential better communications. However, the bigger the team, the harder the communications could be. If you are building in a team, it helps to not create things that are going to be left out and/or standing alone. Teams work really well if you can mix and blend the talents of the team. It is also good if more output is needed. The bigger the team, the bigger the cost, the bigger the management that is needed. - Eric really likes to be able to talk with the end users. That helps him get more into the project. If we have a number of smaller more nimble dev teams (single developers or small teams of 2-5), that would be awesome. There are tons of different personalities, we may need to cater to some of those different people and where they feel comfortable (virtual roles). - What benefits can each person bring to the table? We may want to keep things open and allow people to help play where they want to play and where they have skills. - Eric has seen huge benefits from running things through a fuller project management style. Eric also thought that having a project architect on was huge. That was the person who helped make sure that things were flowing and going in the right direction.

	Shop 2600		Lunch	5/2/2017

	Shop 2610		Virtual Post-It Note	5/2/2017	We are seeing more and more needs to be able to add sub flag, tags, and such to invoices. We have people who want to add sub locations, sub phases, etc. We have done this on elements of time but it needs to be cascaded out to all of the other players. This would be super cool. One of the current needs is fulfillment and order processing. These guys need ways of flagging and tagging things. It is amazing how many processes come back to pods, checkpoints, permissions, flags, and processes. Very important.

	Shop 2611		CCComply weekly opt in report	5/2/2017	On a GoToMeeting session with Bryan. We went over some different projects and questions. A couple of them were dealing with potential database changes. We talked about how far some of that cascades when a small change is made. He also had a project that needed a simple report for a 3rd party vendor and he wanted to know where to put it and how to structure it.

	Shop 2559		Russell Moore	5/2/2017	On a Zoom session with Russell. We went over some new look and feel stuff that he is helping Steve with on one of the pages. They are adding in tabs, side navigation, and splitting up a bigger page to make it look nice. Russell and I then merged some code for a 3rd party vendor and pushed it live.

	Shop 2570		Brandon's Custom Projects	5/2/2017	Recording notes, paying bills, and general catch-up stuff. Working with Alan on some merchant processing data and settings. Light research into a digital wallet called bitcoin. That was a request from one of our clients. I was also doing some work on the Adilas Branding and Supply reports and pages. This is an older project that Will did and I'm looking over some of the code.

	Shop 2581		Adilas Time	5/3/2017	On the morning GoToMeeting session with Steve. We were reviewing and doing a little bit of light planning. Nothing major, but touching base on existing projects, upcoming projects, some scheduling, and talking about some of our developers and their strengths and talents. Alan joined the meeting at 10 am and we started working on the new adilas project specs, documentation, features, and internal process document. We were working with a MS Word doc and organizing almost 100 different questions into logical flow and associated topics. Making great progress. Around 12 pm, Russell called and had a question. I jumped onto a Zoom session and helped him get some info on showing a product photo for a custom report.

	Shop 2305		Renew the content server SSL	5/3/2017	As a note, the adilascontent.biz server SSL expires on 5/26/17.

	Shop 2601		Lunch	5/3/2017

	Shop 2613		Meeting with Calvin	5/3/2017	On a phone call and then a Zoom session with Calvin. We were going over the mini conversion process project. He was giving me a review and we were talking about transitioning over to us (adilas) running with the rest of the project.

	Shop 2612		CCComply weekly opt in report	5/3/2017	On a GoToMeeting session with Bryan. We went over a couple of projects and did a little bit of light code sign-off for a new vendor terms field. We pushed up files and ran the updates. We also chatted about a couple of other small projects.

	Shop 2524		Alan Time	5/3/2017	On a GoToMeeting session with Alan. We spent the whole time going over and refining the process document to help us with documentation, specs, and development methodology. The doc is still not done, but getting closer. We spent close to 4 hours on the doc. See attached for the current version.

	Shop 2582		Adilas Time	5/4/2017	On the daily GoToMeeting session with Steve. We started out the day just working through some small tweaks and making some new changes. 9 to 10:30 am - Making a few small changes. We added in a small tweak to the my cart favorites buttons. We made all of the disabled subs disappear from the my cart favorites view for smart groups. All other sub views were left alone. We also added in a date/time stamp to the advanced invoice searches. We added the date/time stamp to main invoices and invoice line items. This will help users see when the invoices were created. 10:30 am - Meeting with Kelly and Danielle about financials and such. In the financial world, they really want to see certain reports and certain views. This is huge for owners, investors, auditors, CPA's, and bankers. They expect a certain format and certain key indicators and such. - We talked about a possible policy about pushing new code and updates. We have people using this product on a daily basis. They rely on it. When we change it without letting them know, they freak out sometimes. - Chart of accounts and special groupings. Trial balance, month over month financials, year over year financials. - Currently, our users have to do tons of manual entry and tweaking the system to get their numbers. For example: The user has to pull data from tons of different pages and reports and then put it together in a manual process to get the views they are looking for. We have tons of the data, but it may not be formatted easily and correctly. - People want to see tons of different view points, averages, running totals, comparative values, trends, projections, budgets, etc. - Uploading budgets and then comparing to how things are going and doing. - People want to see the year over year values vs. a single one month or one year at a time. - People want to consolidate values, merge locations, look at all kinds of angles, etc. How can we help the person look at their data in a more standard way? - Currently there are a number of ways that things could get disconnected. People want to see GL (general ledger) details. There are also tons of possible disconnects and possible variables. Some of that is due to how we are built. That isn't bad, it just doesn't follow normal roads and normal expectations (for certain users). - We talked about us either being able to export to QuickBooks or build it out so that we look like we are a little bit more stable or standard. Somehow we need to bridge that gap. - Just as an idea... maybe use a simple dash (-) instead of 0.00 on some of the financials. The dash may mean, N/A or nothing to report. Sometimes a 0 (zero) makes it look like it should be part of the reporting but we have nothing. The dash may help show that no data is there to report or don't worry about it. Kind of a mind trick of sorts. - We may need to open back up the old chart of account number fields. This already exists, we just need to re-expose it. We then need to have some mappings to that number if doing cross corp or consolidated reporting. Also by way of a note, we need a way to flag where those pieces play in and what main group or categories they fit into. This could be to any of the main 6 categories such as: Revenue, COGS, Expenses, Assets, Liabilities, Equity. If we opened up the account numbers, it could help with cross-corp mapping and such. That way you map against the numbers vs. a naming convention that might have spelling differences. - We need to move more away from transactional data and go more into daily totals per location. The transactional data is awesome but we really need some preformatted numbers, values, and totals. That would really help with speed and reporting. We have tons of cool ideas (back from 2010 ish) dealing with watchers, feeders, and standalone declarations. Supper cool stuff - well worth looking back into. - On the adilas side, we really need to look into the system-wide defaults and what gets loaded into the system. These are the generic corp-wide settings that get setup when a new system gets created. As a side note, we may even need to take out the defaults for expense types and deposit types. The girls are wanting it super clean and simple (don't even add anything as far as defaults). Maybe figure out some standards and then even keep it super simple from there. - We talked about light world building and breaking up the bus into smaller motorcycles and smaller cars per corp. This deals with breaking up the database to smaller pieces. - Some of the problems the girls are having is on the consolidation between multiple corps. The bigger the business, the more pain there is as you try to consolidate things. Making systems talk to each other, that is the trick. This will end up going clear to a full API socket level at some time. Pretty cool. - We still need the special accounts and custom tracking accounts. This could be customer in-store credits, loyalty points, etc. There are also some other needs that need to be looked at. - Danielle's top 3-5: overall chart of accounts, month over month, year over year reporting, exportability of the general ledger. - Kelly's top 3-5: trial balance, general ledger, p&L and balance sheet on the same page (trial balance), formatting of views (month over month, quarter over quarter, and year over year views), setting up the chart of accounts using the chart of account number. - We have some clients that want a really cool tool for accounting. We need both the simple and automated views as well as a more advanced model that has advanced tools and speaks a standard language. Think of a new view for users. Simple and automated or more robust and showing greater details. - Task from Kelly to me, look into opening up the chart of account numbers on expense types and deposit types. Check out the cause and effect relationships. At the end of the session, Kelly and Danielle were excited to maybe look into two different views. One for the general public and one for a more hardcore financial person such as a CPA and/or an auditor. We will tweak a few things around and see if it gives us more of the look and feel we are hoping for. Good meeting.

	Shop 2602		Lunch	5/4/2017

	Shop 2614		Touching base with Calvin	5/4/2017	I touched base with Calvin on his mini conversion project. He passed off a number of files to me to help me get going. See attached for some of the instructions.

	Shop 2560		Russell Moore	5/4/2017	On a Zoom meeting with Russell. We looked over some CSS changes and merged and pushed up some new files. We then did a little bit of debugging work and tried to help force a new version of the CSS to help prevent a browser from caching things.

	Shop 2571		Brandon's Custom Projects	5/4/2017	Emails and recording notes. Alan and I met on a GoToMeeting session to keep working on the process document. Lots of work on the actual "how" or "process" section. Still under construction, but coming along. See attached for the progress.

	Shop 2615		Data migration	5/4/2017	Special custom data migration project from corp to corp on the data 0 server for Rocky Mountain Miracles. Vendors, part categories, sub inventory templates, and parent items. I had to build a number of new pages to help with the migration. Long night.

	Shop 2587		Brandon out of the office all day	5/5/2017

	Shop 2583		Adilas Time	5/8/2017	On the morning meeting with Steve. We talked about a few things and worked on some small queries and stuff. We then started looking over Calvin's mini conversion project. We pulled down some code and watched part of the video when he handed it off. We then went into a light brainstorming session about sub inventory, sub categories, conversions, elements of time, and even circling clear around to financials and balance sheet stuff. See the section on the sub inventory doc that has a label of 5/8/17 for some ideas that were part of the brainstorming. Things we need to do to help Calvin's project move forward: - Pull some code from the auto processes stuff and script out some of the database changes. - Grab his branch files and make a few checks on what is already there. If needed, he did record a video on some of the changes. Here is the link to the video: http://MyEasySoftware.com/adilas/conversion.mp4 - We may need to check some of the verbage and naming convention on the new code and database stuff. We want to know what each piece does. - Our next major goal is to make a plan, gather up the ideas and info, and then start working on the code to make that happen. - As far as making a plan... What if we stared a new document for each of the major known pieces that still are out there to be completed and/or tied in. We could then start going through the documentation and categorizing the pieces into the correct spots. I am thinking of a new file for:

	Shop 2603		Lunch	5/8/2017

	Shop 2616		Inyo API	5/8/2017	On a GoToMeeting session with Bryan. We went over some code for some custom reports and talked about a couple other projects. We then created a custom email address for a client and updated code so that it would function correctly. The new custom email address will be used as the client emails their clients using the adilas system. We set it up so that if the person replies to the original email, it will be passed back to the correct forwarding address. After that, we talked a little bit about a custom flex grid report and doing math calculations based off of text entries. Lots of changing, filtering, and string manipulation stuff to get the calculations to work correctly.

	Shop 2525		Alan Time	5/8/2017	On a GoToMeeting session with Alan. We were talking about a bunch of the internal projects that need to be looked at. Alan recommended that we create two new docs. One for the conversion only project. Another one for the round 3 of sub inventory. He then recommended that we compare them and see what path to take. We talked about it some more and maybe we'll just create one doc and put both round 3 of sub inventory stuff with all of the mini conversion specs. They are very closely related - Part of our process is actually slowing down and thinking and planning before just jumping. See attached for some more work on the adilas process and documentation worksheet. We spent the last hour going over things and adding to that document.

	Shop 2584		Adilas Time	5/9/2017	On the morning GoToMeeting session with Steve and Alan. We helped out a client with some questions and then worked on individual projects. Most of my time was spent working on the day 1 planning process for the Round 3 of sub inventory project. See elements of time # 2618 for the project management stuff for that project.

	Adi 1436		Round 3 of sub inventory	5/9/2017	Ease of use, being able to export and pull reports. Also tying into eot's.

	Shop 2604		Lunch	5/9/2017

	Shop 2618		Round 3 of Sub Inventory	5/9/2017	This is the project document for Round 3 of Sub Inventory. See the flex grid tie-ins for sub or mini projects. Also, there is some information and more technical documentation attached to the media/content for this project.

	Shop 2617		meet with Seth	5/9/2017	On a GoToMeeting session with Bryan. We went over a couple of projects and small questions. We then worked on adding in a new API socket argument for a custom report he is working on. We talked about security and made some plans.

	Shop 2561		Russell Moore	5/9/2017	Russell called and said he would be late. Started working and paying bills and recording notes. About 2:30 pm (ish) Russell and I got on a Zoom session. We talked about the process for creating custom shopping carts and then fixed a bug out in ecommerce land. We did some testing and pushed the code. Besides that, we just touched base on a couple of things and chatted.

	Shop 2572		Brandon's Custom Projects	5/9/2017	Emails and tech support stuff. Spent some time cleaning up my office.

	Shop 2585		Adilas Time	5/10/2017	Spent the whole morning planning and documenting things for the round 3 of sub inventory project. See elements of time # 2618 for more details.

	Shop 2605		Lunch	5/10/2017

	Shop 2619		Meet with Seth	5/10/2017	Meeting with Seth from Full Circle. They may want to embed Full Circle directly into Adilas via an iframe. Pass the corp id, the keys, and user/payee id through the iframe. On coupons, sales, and promotion codes. We had a meeting with them and Seth from Full Circle pitched a small model for some coupons and such. Ortus Solutions - Some new ColdFusion tools for servers and such. Some command line tools that speed things up.

	Shop 2635		Meeting with Bryan	5/10/2017	Meeting with Bryan. We were on the phone and then on a GoToMeeting session. We then met up with the guys from Full Circle IM to talk about online coupons and promotion codes. Seth from Full Circle lead the meeting and Bryan and I gave him some feedback. The general goal of the meeting was to talk about ideas and concepts behind the sales and promotion stuff. Seth proposed some small database concepts and what not. I asked for a copy of the database (only 4 tables or so) to go over things. After that Bryan and I chatted about some other stuff.

	Shop 2526		Alan Time	5/10/2017	On a GoToMeeting session with Alan. We went over a number of older elements of time and tried to pull out the gems and pieces of information that would help us in the adilas planning, project management, and documentation methodology document. See attached for the current version of the doc. As a note, this document needs some light tweaking, but it is getting close to be ready for use.

	Shop 2586		Adilas Time	5/11/2017	On the morning GoToMeeting session. A guy by the name of Wayne Andersen joined the meeting. He was calling from Portugal. He has been programming for about 40 years. He has written a number of applications from the ground up. For the last 10-12 years he has been in the HV/AC industry. Lots of work with time capture and time calculations. He also worked with some light job costing and then do some reporting. He has done lots of database stuff and written in lots of different languages. He is looking for 5-10 hours a week and/or a smaller project. He wants a challenge and wants to do some things here and there. He is looking to help with projects, API sockets, automated unit testing, etc. Contact info for Wayne Andersen: powertoaster@gmail.com 208-991-3205 After meeting with Wayne, Steve and I chatted about some different things and such. The rest of the session was spent doing emails, recording notes, and other small to do list stuff.

	Adi 1473		Work on the adilas docs (word and PDF) - part of the developer's homepage	5/11/2017	8/20/21: 2.19 6/18/21: 7.6 6/9: 22.37 5/27/21: JM=30.11 As of 5/12/21: $7031 5/12/21: JM=17.75 Internal project helping adilas developers to standardize their processes. Many hours have been spent. Actual adilas docs section and pages have been uploaded. This may be ongoing as we add little bits here and there. As a side note, this Word doc was passed off to Chuck who started making it into a standards page for all adilas developers. This project may end up being used for internal documentation and standardization type stuff. This includes naming conventions, standard practices, code sign-off rules, expectations, CSS and style guides, etc.

	Adi 1474		Add html links from statements and customer logs to online bill pay for customers	5/11/2017	Brandon completed in early 2019.

	Shop 2606		Lunch	5/11/2017

	Shop 3017		Add links to the new word docs for project management	5/11/2017	Alan and I have been working on new Word documents to help with project management and standard procedures for the developers. We need to get those documents finished up and then link to them from the developer's homepage or some other spot. They have some great templates and good starting points for projects and what is wanted and/or required. Good stuff. See attached for a couple of the current working docs.

	Shop 3018		New web links for customers	5/11/2017	We need to add in new HTML links to help customers get to the online bill pay stuff. This could be from the customer log page or on the emails that get sent out to the client. Currently we email invoices, quotes, and statements. It might be nice to have the online bill pay links be on all of those emails. It might be nice to have those same URL's available from the customer log page where they could be copied and pasted into a handwritten email message as well. Just some ideas.

	Shop 2634		client tables	5/11/2017	Meeting with Bryan over a GoToMeeting session. We were talking about how to add/edit users for a custom job he is working on. We lightly talked about permissions and session values. We need to figure out what the session values are for a valid login in order to keep things consistent and flowing well.

	Shop 2562		Russell Moore	5/11/2017	On a Zoom session with Russell. We merged in a small tweak for a client on the adilas 3rd party page. We then started to work on some new email settings and such. Russell and Chris Johnnie wanted to send links to the ecommerce invoices and quotes instead of the older PDF invoices and quotes. Russell and I worked on two new settings and cascaded them throughout the system. We did lots of testing and even added in a link for unpaid invoices and online bill pay options. When we got all done, we pushed up the new code and did some live testing. Good session.

	Shop 2573		Brandon's Custom Projects	5/11/2017	It didn't happen. We ended up on other projects.

	Shop 2588		Brandon out of the office all day	5/12/2017

	Shop 2636		General	5/12/2017	Emails, tech support, and paying bills. Shawn Curtis came over and we were working on some small projects.

	Shop 2637		Working with Shawn	5/12/2017	Working with Shawn. He had some new code that we pushed up live for payroll stuff. Part of it was taking the state withholdings CFC and splitting it into two different methods. It was getting too big and actually capped the allowed method size.

	Shop 2638		Adilas Time	5/15/2017	On the morning GoToMeeting session with Steve. We had Wayne Andersen and Alan Williams join us for a bit as well. We got Wayne introduced to Alan and then got Wayne setup with a bit bucket and adilas account. We chatted there for a bit and then moved on. Steve and I went over some finances and then worked on our own projects. Right towards the very end of the session, we had some issues with the data 1 and data 3 servers. Spent some time on the phone with Steve, Kelly, and tech support.

	Shop 2642		Lunch	5/15/2017

	Shop 2646		CCG json storage and Campaign Rise	5/15/2017	On a GoToMeeting session with Bryan. We were going over some custom page flow and how to use the session scope to help save certain form field values in the session scope. We then talked about how to both clean things up and repopulate the correct forms as needed.

	Shop 2527		Alan Time	5/15/2017	On a GoToMeeting session with Alan. We spent most of the time going over the database project (world building). We went over the cluster controller pieces and talked tech about processes and fields. We then went through a number of tables and Alan would ask questions and we would either look things up or I would tell him what I remembered. Just trying to define the database columns and note where they connect or what the default values were. Good session. Light tech support and email stuff on the front end and after the online meeting. Just doing clean-up from the day.

	Shop 2639		Adilas Time	5/16/2017	On the morning GoToMeeting session. Steve and I started out doing some brainstorming about how to use custom mappings and special flag and tags to create some virtual mappings. We were talking about sub inventory and sub attributes but the conversation ended up dealing with ways to map things - almost the application flex grid level of mapping. We even talked about how accounting uses chart of account numbers to help with some mappings. The secret is the "chart" or "virtual mapping" part of it. Someone needs to go through and create some defaults and a basic mapping. Then people can modify things as needed. Kinda like a road or a path through the forest. Once that main road or path exists, it allows for others to expand and tweak things from there. Bryan came on and chatted with us for about an hour. We helped him with his menu board project and then we talked about some of his other projects. We also spent some time talking about the adilas 3rd party solutions page and what we are planning for that area and section. After that, I spent the rest of the session working on a custom page to help remove all existing customers from a single corporation. In this project, we don't really delete them, we kinda exile them to a different corporation which makes them seem like they are moved and gone. We then store a back-up of all of the id's and modify all other places and records to make everything tight and all cleaned up.

	Shop 2643		Lunch	5/16/2017	During lunch, I got a call from Calvin. He was going back in and working more on the custom database field names and values for the add/edit customer page. That single page, somewhat of a prototype, allows for the corporations to sort, show/hide, require (yes/no), name, add instructions, etc. The concept is needed throughout the entire system. Currently is only exists in a small page and the underlying action page. Lots of potential there. :)

	Shop 2647		Campaign Rise	5/16/2017	Bryan and I got on a GoToMeeting session and worked on setting up the Campaign Rise session values and custom page to edit the user/payee page. We added some code to show the profile pictures for the users and run all of the special checks that are needed. Most of the time was setting up error pages, application pages, and small session values.

	Shop 2563		Russell Moore	5/16/2017	On a Zoom session with Russell. We merged in some new CSS changes and some new code that allows an admin user to modify a single users snow owl theme settings. Basically, a way for the admin user to help and virtually pre-set all needed buttons, links, and functionality before the main user logs in. After that, Russell and I did some light debugging and tweaking to the adilas market pages. We added the HTML text editor to the text area fields. We also added a link to the personal profile from the headers on the snow owl theme. We pushed up the pages and did some light testing.

	Shop 2574		Brandon's Custom Projects	5/16/2017	Recording notes, emails, and light clean-up. I also ran the customer clean-up scripts to remove close to 30,000 customer records from 4 different corporations on the data 3 box. This was a custom project that Steve had me on. The sites that had customer info, weren't allowed to keep those records based off of new Oregon state requirements for recreational dispensaries.

	Shop 2649		Working on custom reports	5/17/2017	Working on some custom reports for Adilas Branding and Supply. Pushed up some new files and disabled one that still needs some help.

	Shop 2640		Adilas Time	5/17/2017	On the morning meeting with Steve. We spent the first 1.5 hours going over some of the craziness that either has been going on and/or is still going on. We were talking about a number of different projects. Some with us, some with the shop, some with the guys from AFB. There are some of them that are starting to run away and/or get out of control. We need to get control of who is doing what and what code and projects are being pushed. We need to put our foot down on some of these things and say no. We spent some more time talking about other ways of getting more control and slowing things down a bit. We talked more about processes, FTPing (sending files up and down), and code sign-off. We talked about security, 3rd party solutions, and API sockets (opening up windows and doors). Maybe we could put together some FTP options where they could only upload to the black box and custom folders. Similar to what Steve did back in the day when he was limited to just the custom folder through the system. It may be worth our time to change all of the FTP passwords and setup individual accounts. Then open and/or limit the accounts as needed. This could help us get some more control over things.

	Shop 2644		Lunch	5/17/2017

	Shop 2648		Working with Eric on planning the Loyalty Points and Special Tracking Accounts	5/17/2017	On a GoToMeeting session with Eric. We spent the whole time trying to get into the planning mode for the loyalty points and special tracking accounts sub project. See attached for how far we got.

	Shop 2528		Alan Time	5/17/2017	On a GoToMeeting session with Alan. We started out by talking about possible security holes and how to fix some of those issues. We then rolled into working on the database documentation and world building (splitting up the databases) project. Alan would ask about certain fields and I would respond and say what I knew or we would go and look things up. Making progress and flushing out the random pieces and finding out the data storage and flow processes.

	Shop 2641		Adilas Time	5/18/2017	On the morning GoToMeeting with Steve. We talked about the mini conversions project and then started into a planning and documentation session on that project. Eric popped in around 10:30 am but we decided to keep going with planning on the mini conversions project vs. switching to the loyalty points project. We'll try to make up the difference sometime this weekend. See attached for the progress on the mini conversions planning.

	Shop 2645		Lunch	5/18/2017

	Shop 2650		Campaign	5/18/2017	On a GoToMeeting session with Bryan. We looked into some logic on the Campaign Rise project. We started making a plan and Bryan is going to reach out and talk with Dave Forbis and Will Hudson about where they are at with the project. Small work session going over error messages, session values, and standard validation.

	Shop 2564		Russell Moore	5/18/2017	On a Zoom session with Russell. We got off onto a small CSS change for viewing sub inventory from inside the Snow Owl theme. It started pretty small but we ended up hitting almost 20 internal core pages, and another 30-40 black box pages to make the fix. We uploaded all new pages and did some testing.

	Shop 2575		Brandon's Custom Projects	5/18/2017	On a GoToMeeting session with Bryan. We made a to do list for his Campaign Rise project. We called and talked with Dave and then got Will on the meeting. After we were done, we wrote some notes and setup a plan to hook-up tomorrow to work more on the login and sign-up flow and process. Bryan is somewhat taking over that project to try to help push it forward as we are getting closer to a deadline. Good and productive meeting. After the meeting, I was checking some emails and recording some notes from the day. Also got on the phone with Calvin and touched base on a small tweak Calvin was making.

	Shop 2589		Brandon out of the office all day	5/19/2017

	Shop 2670		Working with Bryan	5/19/2017	On a GoToMeeting session with Bryan. We were building some of the main structure and login process for the Campaign Rise project. Lots of work on the login process and other session variables.

	Shop 2651		Adilas Time	5/22/2017	On the morning GoToMeeting with Steve. We talked about projects, finances, and options for the first little bit. We made a small plan of attack and then started into our day. I spent most of the morning do some more planning for the mini conversion project - sub project for the round 3 of sub inventory project. After that, I paid some bills and did some email stuff at the end of the session.

	Shop 2655		Lunch	5/22/2017

	Shop 2673		Virtual Post-It Note	5/22/2017	Talking with Shannon today about conversions. She was familiar with Steve's create QR code page. One of the problems was dealing with the price. When the QR code was read into the shopping cart, it took the price that was passed in and times it by the quantity. It wasn't able to do a total price it did the price per. We allow for this same functionality on buttons, smart groups, and advanced add to cart. We need to make sure and allow for price per or total pricing options for mini conversions.

	Shop 2678		Virtual Post-It Note	5/22/2017	- Are you teaching business, operations, accounting, what? Or are you teaching people to think and be creative? What is the focus? People or subjects? - I found these questions on an old post-it note on 5/22/17. The older post-it note didn't have a date on it but it was in my hand writing. So, I don't know the original date, but I liked it. :)

	Shop 2666		Campaign Rise	5/22/2017	On a GoToMeeting session with Bryan. We were working on some dynamic variables and dynamic notation stuff for his menu board project. It gets pretty deep with structs of structs with tons of dynamic keys and values.

	Shop 2665		Shannon	5/22/2017	On a GoToMeeting session with Shannon. She had some questions and we did some follow-up on some different questions and issues for her tech support clients. I showed her a little bit about the new mini conversion project. We then talked about the cart and how it does its calculations, normal math, back figuring math, and what not. We talked lightly about possible rounding errors and how the system has to do the back calcs over and over again to get to what it feels is the correct answer. Just touching base and other updates.

	Shop 2529		Alan Time	5/22/2017	On a GoToMeeting session with Alan. We were going over the existing progress for the World Building project. This was dealing with cluster level stuff (level 3), solar system level (level 4) and even world building (new corporations or level 5 stuff). He showed me a giant update query (tons of SQL statements) to help get the current database all up to date with the new changes we are planning. We took a little break in the middle so that Alan could go pick up his son from school. When we came back, we went over more database questions and looked up a few things in code and in the database itself.

	Shop 2671		SHAWN TIME	5/22/2017	On a GoToMeeting session with Shawn. He had a question about doing some state specific calculations and code to help with the payroll part of the application. We talked about looking in the cost/benefit of adding the new code and settings. We will revisit this topic in a couple of days on another appointment.

	Shop 2652		Adilas Time	5/23/2017	On the morning GoToMeeting session. Wayne Andersen popped in and we talked about general files and folders and a general overview of the file structure. He was working and looking around. He had some good questions. Steve and I worked on some small elements of time stuff tied to sub inventory. We are just barely touching the surface of what elements of time could do for countless projects within adilas. I'm excited to see what happens there. As a fun side note, Steve was talking about how we could use elements of time to virtually create our own little sub processes and create our own timeline with checkpoints and process pods (user-maintained mini groups, pods, and processes). We would really like to define that for things like the concept of the digital data assembly line and such. Shawn and Steve got on and worked on Steve's new laptop. They were messing around with the display settings and screen resolution. I then started to jump back in on the planning part of the mini conversion project. I spent some time recording notes from post-it notes into the system.

	Shop 2656		Lunch	5/23/2017

	Shop 2667		Campaign Rise	5/23/2017	Bryan and I got on a GoToMeeting session and worked more on the overarching structure for the Campaign Rise project. Lots of work with session stuff and page flow.

	Shop 2565		Russell Moore	5/23/2017	On a Zoom session with Russell. We looked over a custom gram tracker for ecommerce. We also looked over the first custom shopping cart that Russell did for a company called Kush Gardens. He is calling it the Kush Cart. Anyways, this is his first custom cart and what not. Pretty cool. We pushed and merged in a bunch of code and then did some testing.

	Shop 2576		Brandon's Custom Projects	5/23/2017	Emails, recording notes, and making phone calls. Light follow-up with some of the other developers.

	Shop 2653		Adilas Time	5/24/2017	On the morning GoToMeeting with Steve. We started into a light session being able to tie sub inventory to elements of time. This sent us off on a small little side venture. We had Shawn pop in for a bit and also Alan for a little bit. We tried to help those guys get what they needed for their different projects. As a small side note, we may want to bring in a history record for corporations, settings, locations, sub inventory, 3rd party solutions, and API sockets. The rest of the session was spent coding a new sub inventory report on the working with time and printable time pages. Trying to get things tied in together. That is awesome and part of the round 3 of sub inventory stuff.

	Shop 2657		Lunch	5/24/2017

	Shop 2668		Campaign Rise	5/24/2017	On a GoToMeeting session with Bryan. I finished up some stuff for the Adilas Branding guys and then worked with Bryan on the Campaign Rise stuff. We were going through validation and flow for adding a new payee/user.

	Shop 2672		SHAWN TIME	5/24/2017	On a GoToMeeting with Shawn. He was pitching an idea about how we could improve the general payroll functions. We are seeing a need to expand the payroll and payee to department options. The newest need is on the existing 5 custom fields. Currently they are only on the employee side and only for set dollar amounts. We may need to add two new options to each of them (10 new fields). It would be dollar amount or percentage (setting 1) and employee side or employer side (setting 2). This may need new fields and logic on the payee to departments table as well as the actual paycheck stubs table. We need this new info and logic on both sides. There are 3 known pages that do payroll calculations. There is also 1 page that shows and setups the relationship between the corps, payee/users, and the departments. The new pieces would be needed on those pages. We also need to cascade those settings to all other reports and year end forms. This also includes the paycheck summary reports and grouped totals.

	Shop 2530		Alan Time	5/24/2017	On a GoToMeeting session with Bryan and Alan. We stared out and Bryan and I were working on general flow and chopping out excess code out of the current Campaign Rise project files. There was a lot of copying and pasting and we just need to clean things up a bit. Once Alan jumped on, we switched gears and started talking about who is doing what, where are we at, and what things still need to be addresses. Bryan was taking notes and all three of us were talking about different aspects of the project. We decided to call Dave Forbis and setup a meeting between all of us for tomorrow at Bridgerland in Logan. After calling Dave, we spent the rest of the session going over the current plan and making questions that we needed to ask about. Good group effort. I'm excited to see how the project plays out. Good stuff.

	Shop 2693		General	5/24/2017	Emails, tech support, and recording notes.

	Shop 2694		Digital customer migration	5/24/2017	Did a digital migration for a client. They had about 1,000 customer records. Migrated data from an Excel file up to the data 6 server. Invoiced the client.

	Shop 2654		Adilas Time	5/25/2017	On the morning GoToMeeting session. Danny and Steve were talking about sales and marketing for the first little bit. We are going to be working more towards video training, more education, and customer service. After that, Steve and I worked a little bit more on tying in elements of time to the sub inventory stuff. We could really use the functionality of the elements of time to help give us some really rich data about what is happening (3D world building and Z axis stuff). I worked most of the session getting some files ready to push up. The new ones lightly expose the optional connections to elements of time to and from sub inventory. Good stuff.

	Shop 2658		Lunch	5/25/2017

	Shop 3016		Time template overrides	5/25/2017	We need to add some master time template overrides for the add and edit processes for elements of time. Currently, the developer has to look those up and pass the template settings in. It might work better if we remove them as arguments and just look them up and force them on the cfc or logic side of things. I have been having a hard time being able to teach the developer about the need to match everything up. It seems like extra work. So, maybe we'll just pull them off and force them as template overrides in the background. As a side note, the time template settings that are stored on the elements of time table were put in place to help with searching records. Basically, the thought was less joins to get the data back out of the system. That thought process has pros and cons. A pro is, we can filter the data better and quicker without a join. The con is we have to duplicate that data and there is no guarantee that the duplicated settings are really real. Anyways, just recording the ideas.

	Shop 2669		Campaign Rise	5/25/2017	On a GoToMeeting session with Bryan. We were working more and more on the Campaign Rise project. Some of what we were doing today was dealing with tying in to auto populated elements of time that will be used as virtual placeholder extensions.

	Shop 2566		Russell Moore	5/25/2017	On a Zoom session with Russell. We worked on some changed to the Kush cart (custom cart). We changed some CSS and added an option to flip the split cart to the right vs. the original left side for the split cart. Tested and pushed up files.

	Shop 2577		Brandon's Custom Projects	5/25/2017	Went in to town to meet with Bryan, Alan, and Dave Forbis on the Campaign Rise project. We met at Bridgerland and used one of their rooms for a whiteboarding and brainstorming session. Dave lead the discussion, Bryan took notes, and Alan and I pitched in and asked questions. We used the whiteboard and got a whole lot out of the meeting. I think that by the time we were done, all parties had a better understanding of the scope and vision of the project. That was awesome. After the meeting, I went over to the other campus and met with Nick for a bit. I had him show me around and we just chatted for a bit. See attached for a photo of the whiteboard session on the Campaign Rise project. Here were a couple of my notes: - We are going to need time id's on every po/invoice line item. Invoices should be more straight forward than PO's. The PO's may need to hold multiple children where the invoice line items will be on a one-to-one relationship. - Along with that, we may also need sub inventory stuff as well as mini conversion stuff per line item. Once again, the invoices will be one-to-one and the PO's may be one-to-many. Make a plan and then only get in there once to make all of the changes. Otherwise, it just takes longer because we will have to update millions of records over and over again. - On sub notes and sub comments (a sub of elements of time), we are seeing some new needs coming up. This includes a way to cross tie, stack, and set statuses on the items. We are even seeing a need to build out a sub table to help with read, write, display, save, mark, or highlight type status. Imagine a single element of time with a single sub comment... Say you had 10 guys on your team... What if you wanted to record who had read it, who wanted to delete it, and who wanted to mark or highlight it? You would need another table to allow all of the users to virtually take some action on the single sub comment or sub note. Then take that same concept and start saying the words: forum, social media, inbox, messaging system, mini blog, etc. You can see that we need to beef that section up. We need to be able to stack, self connect, chain, connect to other comments, nest replies, and keep track of states and statuses per user. That sounds really cool.

	Shop 2590		Brandon out of the office all day	5/26/2017

	Adi 1466		Time template overrides	5/27/2017	This would manage all of the settings behind the scenes. Makes it easier for the developers.

	Shop 2700		Working on adding time id's to sub inventory reports	5/27/2017	Working with Aspen Moore (my daughter) to help me record notes from scratch paper and other post-it notes. After a small training session, she started getting organized and spent a bunch of time putting things in chronological order by date. She was doing a great job and it was fun to watch her work. While she was doing that, I worked on adding time id's and tie-ins to elements of time to a number of sub inventory reports. Trying to get the two pieces to hook-up and play well together. Good session.

	Shop 2659		Memorial Day	5/29/2017

	Shop 2660		Adilas Time	5/30/2017	On the morning GoToMeeting session. Most of the entire session was talking about where do we want people to go and how much control is needed on the adilas side and on the other 3rd party sides. Lots of good talks back and forth. - We had a meeting with Green Stock and Adilas Branding to go over some things. This was Steve and I along with Paul from Green Stock. We spent a good half and hour and both parties pitched and summed up where they are at. As a side note, they (AFB Branding) kinda snuck through the backdoor via an association with Chris Johnnie from AFB. We just cleared the air and laid down some light playing rules. - After the Adilas Branding meeting, we took some time and started talking about our vision and what the future holds - where do we want to go? It comes down to a control issue. - Training and who can train who? - We need to help standardize things. Expectations - a virtual cookie cutter type scenario. - We are in a deep industry - a new comer won't know what to do. There are other parts of the business that are required. - We may need to go backwards and reclaim some control and standardization. - Even on AFB (Adilas For Business), Adilas Products, Adilas 420, Adilas Branding, etc. No one knows where the lines are. There is a level of confusion that comes from sharing the name "Adilas". We may need to protect that more. - On a hosted solution level, we are seeing that the more the states require certain reporting needs, the more it helps push a web based hosted solution. The Cannabis industry has really helped to push that ball forward. They have tons of state required pieces and API socket interfaces to share data back and forth. - Steve and I talked about what other verticals do we want to play in? What about building out packages and such? Then focus on those pieces and sell to those verticals. - We may want to build a report per industry that shows who is using sub inventory and who is using the new snow owl theme. Those who are not using those pieces (for some industries), they may end up going off the system. Lots of new features and functions are built off of those pieces. If they are in certain industries, and aren't using the newest pieces, they may be getting frustrated and/or missing some new key pieces. Basically a report, who is still running the oldest models and who has not progresses along with us. The remainder of the meeting was all dealing with levels of control, options, and direction. Lots of good conversations. On a side note, some of the crazy storms we have been having, could be put to rest if we were able to set some ground rules and get some buy in on those rules and principles.

	Shop 2663		Lunch	5/30/2017

	Shop 2696		Campaign Rise	5/30/2017	On a GoToMeeting session with Bryan. We were going over some code for Campaign Rise. Most of dealt with login, logout, redirects, and session stuff. We also talked about a mix between the funding that is available and the time it takes to make certain things happen. Sometimes the balance is hard to find and/or wasn't fully planned out. That starts cutting into the efficiency, budget, and timelines of a project.

	Shop 2567		Russell Moore	5/30/2017	On a Zoom session with Russell. He was super excited because they have a number of new custom projects that have been approved and they even have some funding on those projects. As Russell was pitching the ideas and talking about the projects, I had a couple of questions and concerns. As we talked, it was appearant that Russell had some frustrations as well. Lots of it was coming down to who was calling what shots and who was doing what pieces. This lead us into a big huge discussion about who is controlling the business assets (people, money, timeline, and promises made). We talked about goals and direction, roles, and who is doing what. It was good but you could tell that the frustration level was pretty high. They have new projects that deal with sub inventory in ecommerce, sub part categories, related items, sub flags and tags, searching sub attributes, and simple sizes and colors for sub inventory. We were on the same page about 90 to 95%. It was that 5-10% that was throwing a monkey wrench into the mix. We talked about things and I tried to show him where we were headed and such. In the end, we decided that we would pull Steve in and chat with him about some options. The whole day today felt like we were losing control on almost every side. It isn't that bad, but one things was leading into the next and we were feeling some accumulated affects. See attached for some graphics for projects that Russell was looking into.

	Shop 2578		Brandon's Custom Projects	5/30/2017	Recording notes and trying to figure out what to do. Somewhat lost.

	Shop 2661		Adilas Time	5/31/2017	On the morning GoToMeeting session. Steve and I started out the day going over plans and how much we need the next piece - called mini conversions. It seems to be the hottest topic currently. Of course, that always changes, but for now, it is the focal point. As part of talking about that, I showed Steve what Russell was planning for ecommerce. We talked about how we need to get things going in the right direction. Russell is planning a somewhat one-off version of what we are planning for the mini conversion section. We really don't want that to happen. It would end up hurting the client and causing more work and headache down the line. Russell's version would solve things on one end, but it would open up bigger holes later on. We just want to make sure we are all on the same playing field and same page. On a side note, the last couple days have really been stressful due to the lack of control, planning, and standardization stuff. We really need to be one. Currently there are numerous goals, direction, and other things that are pulling us apart. It is very hard to manage the whole thing and hopefully we aren't trying to take too big of a bite. Eric Tauer came on around 10 am. We then changed gears and started working on the planning phase for the mini conversion project. Steve and I took a bunch of notes and then started working through Calvin's code and database proposal stuff. We recorded as many notes as we could and then went into an Excel type format where we could build tables and simulate data flow and such. See attached for the rough notes and table layouts.

	Shop 2664		Lunch	5/31/2017

	Shop 2697		Campaign Rise	5/31/2017	Working with Bryan on a GoToMeeting session. We were working on the add/edit options for employee/user photos and uploading the correct images. This will be used for a profile piece outside of the secured environment for Campaign Rise. We also spent a little bit of time and talked about encoding and decoding stored database values. Bryan was getting the correct data but it was encoded for storage. He just needed to know how to decode the values so that he could show it in normal English vs. the stored hash value.

	Shop 2674		Danny Shuford (bulk label issues)	5/31/2017	On a GoToMeeting session with Danny. We were tying in flex grid to custom PDF labels and such. We spent the time looking around and following the logic. We did one for a single label and also fixed it so that it would work on the bulk labels.

	Shop 2683		SHAWN TIME	5/31/2017	Quick meeting with Shawn. He wanted to reschedule. Worked on other projects and such.

	Shop 2532		Alan Time	5/31/2017	On a GoToMeeting session with Alan. We talked about tons of stuff... lots of different subjects. We did a recap of where we are at with regards to internal projects vs. custom projects. We talked about finances, expenses, and revenue coming in. I then showed Alan the progress on the mini conversions project. We started talking about some disconnects with some of the new projects that are coming up. The new projects aren't too far off, but we need to communicate and pull our ideas together. We did a lot of drawings and going over what needs to happen on the sub part categories project. We also talked quite a bit about sub inventory and inheritance of the sub attributes. We even talked about possibly even looking into parent attributes vs. total sub attributes only.

What's New

Products

Find Us