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 - 12/1/2017 to 12/31/2017 - (81)
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	Shop 3235		Brandon out of the office all day	12/1/2017

	Shop 3240		Adilas Time	12/4/2017	On the morning GoToMeeting session with Calvin and Steve. We spent the first little bit doing some catch-up and talking about new and upcoming pieces and projects. We talked lightly about budgeting and told Calvin to send us a bill for a couple more thousand to keep things going with the sales tax expansion project. After that, Steve had me merge some files for him. Them we all split up and did some clean-up and catch-up stuff. All of us bailed out of the GoToMeeting session and joined Russell on a Zoom session. Russell was showing off the AFB quick employee time clock and the new email settings. There were 9 people on the Zoom session. Some of them were: Calvin, Steve, Danny, Chris Johnnie, Russell, Molly, Shannon, Shari Olin, and myself. Great meeting and I love how well AFB is creating new tools and then making sure that they get noticed, good training, and even some marketing efforts. Good stuff.

	Shop 3244		Lunch	12/4/2017

	Shop 3248		Adilas Time	12/4/2017	On the GoToMeeting session. Mostly just working by myself. Calvin popped in for a bit. We talked about some mini ecommerce packages for new and small start-up clients. I recommended that he read some of the notes on elements of time # 667 (here in the shop) to see some ideas we were kicking around with a guy by the name of Todd Williams back in 2016. There are some good ideas there. After that, I worked on merging in code from Alan's branch to the main sales tax expansion project branch. I'm trying to get things all caught up and at least close to the same level (prep stuff for code testing and detail work).

	Shop 3241		Adilas Time	12/5/2017	On the morning GoToMeeting session. Alan and I started off together and did a little bit of catch-up. Steve joined for a bit and we chatted about projects and budgets. After that, we split up and worked on individual projects. I had tons of tech support and email stuff to do. The other guys were working on their projects and tasks. Towards the end of the session I worked on pairing down a list of files that have been changed on master and comparing it to our sales tax expansion project branch. Trying to get closer and closer to a base level or a stable reality of sorts.

	Shop 3245		Lunch	12/5/2017

	Shop 3304		Record Special Histories	12/5/2017	We have had a number of requests for audit trails and special history records for different sections within the site. Some of them are: location histories, store histories, corp-wide settings histories, changes in sales tax histories, etc. We are seeing more and more weight being put on both store/locations and corporation tables. Those tables really do a lot and control how the system works, calculates, feels, and acts. There is a lot of power there. As a side note, we could use the 3rd party error logs to record the special history notes. That section is already setup to hold JSON (object oriented) data and could maintain any and all changes. As an additional message to go along with this... the sales tax expansion project already has a small part (stores, locations, and tax settings) that will be recorded in the 3rd party error logs. That project hasn't been released yet, but it will be forth coming. This note was added as of 12/5/17 by Brandon.

	Shop 3249		Adilas Time	12/5/2017	Tech support, emails, and merging code between branches.

	Shop 3264		Russell Moore	12/5/2017	On a Zoom session with Russell. We were going over a new project dealing with a warning and info box on the top header that helps us track who has paid and who has not. This is a project that Steve had requested to help David Berkenkotter and Shari O. with accounts receivable (A/R's). We went over some ideas and I explained a couple needs and wants for the feature. Russell took notes and recorded the session.

	Shop 3303		Molly cookies/3rd party page	12/5/2017	GoToMeeting session with Bryan to talk about and go over setting and retrieving cookies from a WordPress and PHP box, and then sending them to the adilas ecommerce site for a client. We found that the PHP box was setting multiple cookies. We then did some light clean-up by setting some of the cookies to blank and then deleting them by setting the expiration timeframe in the past. We then loaded the new cookies with good data and then passed it along. Hopefully that works. After that, we just chatted about a couple other projects that are brewing and coming up.

	Shop 3242		Adilas Time	12/6/2017	On the morning GoToMeeting session with Alan and Steve. Mostly a work session for each of us individually. I finished doing some code merging and then got started back on some code review and detailed testing. I am thinking about rewriting the database updates to break this huge project into slightly smaller pieces. Maybe make it as transparent as possible.

	Shop 3246		Lunch	12/6/2017

	Shop 3250		Adilas Time	12/6/2017	On a GoMerging code, prepping, and planning my next moves. Fixed some tech support things for Shari O. dealing with default expense types for vendors. I then talked with Steve a bit about where we are headed - goals, progression, and such. Paying some bills and on the phone - other random stuff.

	Shop 3271		Russell Moore	12/6/2017	Russell called in, but no real meeting took place. He will reschedule for tomorrow and will grad some more time.

	Shop 3306		logout action	12/6/2017	On a GoToMeeting session with Bryan. He had some questions dealing with API sockets and clearing session scopes upon a valid logout.

	Shop 3305		API Refactor Code Review	12/6/2017	On a GoToMeeting session with Will. We were looking into his code for adding a from web page id field to all internal and 3rd party API socket assignments. We needed to break out of a perfect one-to-one relationship and expand things to a one-to-many relationship. The code looks good. He has a few more tweaks to make and then he will turn it over for some code review. Making progress. After working with Will, I recorded a few ideas about breaking up the sales tax expansion project. This could allow us to take smaller bites on certain parts of the project. Just some ideas. As a side note, I did post my latest text file on the element of time # 3199 just as documentation.

	Shop 3243		Adilas Time	12/7/2017	On the morning GoToMeeting session with Steve and Alan. We were all working on our own projects. I was paying bills, doing tech support, and emails. I then started to get ready to help do some code review for Will and the adilas API sockets for both internal and 3rd party vendors.

	Shop 3247		Lunch	12/7/2017

	Shop 3251		Adilas Time	12/7/2017	On a GoToMeeting session with Steve. We looked over some new page level settings for my cart favorite buttons, smart group buttons, and how they show sub inventory. I then went back to work on the new code from Will for the adilas API assignments and building it out to a one-to-many relationship.

	Shop 3263		Russell Moore	12/7/2017	Russell and I were on a Zoom session and making some changes. We added a new paid permission for the new AFB Quick Employee Time Clock app. We added some custom email addresses for AFB and for Russell with an adilas.biz extension. We pushed up files and tested. We then added code so that the AFB Quick Employee Time Clock app checked for either the new paid permission or the AFB e-commerce permission. We also added it to the chooser as a default homepage option. Last of all, we tweaked the redirect option to make sure we could get out of the time clock app. It has limited page navigation. Good session. Russell and his guys are making headway and making good waves. Good stuff.

	Shop 3236		Brandon out of the office all day	12/8/2017

	Shop 3307		Transfer of info to Calvin for Caisson Labs	12/8/2017	On a phone call with Calvin. We were talking about the Caisson Labs project. I scanned a few pages and put them up on this element of time. We talked about needs and wants and I volunteered to help with this project. Calvin will come by my home and pick up the other hard copy pages that I have to date. After that, Calvin and I talked about ideas and concepts for the texting and emailing options that we want to build into adilas. Lots of ideas spinning around, we are just too busy to really nail everything down. That will come. We are making progress on all fronts.

	Shop 3275		Adilas Time	12/11/2017	On the morning GoToMeeting with Steve, Alan, and Calvin. Most of the session was us working on individual projects. We did get together at the end to bring everybody up to speed. I was mostly doing emails, answering questions here and there, and writing a review for Alan on his projects and internship stuff for USU. This is his last semester of school. See attached for the review that I wrote for Alan. He is doing a great job. Very impressed.

	Shop 3286		Lunch	12/11/2017

	Shop 3265		Russell Moore	12/11/2017	On a Zoom session with Russell. We went over a number of small changes. We worked on some navigation buttons for tables and mobile platforms. We worked on some CSS and display settings for the AFB quick employee time clock app. We also looked into the underlying details behind the ecommerce photos and scans. We decided that we need to educate the client vs. changing code on that section. We merged and pushed up the code and did some testing.

	Shop 3308		Registration PDF	12/11/2017	On a GoToMeeting session with Bryan. We started out going over a PDF paperwork form for stock/unit (trailers and vehicles) in Texas. We have a new version and we need to be able to populate it. As a fun side note, the Texas 130U form was one of the first PDF forms that we built into the system. This project is a newer version of the same form. After we reviewed some of the ins and outs of the PDF form, we switched gears and talked about 3rd party API socket connections and what changes are coming down the pipeline (setting the from id to help with one-to-many relationships). Lots of drawing and trying to show Bryan how these things are going to play into the mix.

	Shop 3309		General	12/11/2017	Paying bills, recording notes, and writing a letter to Dave Forbis to say thank you. Today, we were able to write out the final payment for monies owed to Dave from clear back in the shop era. That is awesome.

	Shop 3276		Adilas Time	12/12/2017	Working with Steve on the morning GoToMeeting session. We touched base at the beginning and I helped him with a custom bulk move PO's and plants page. He is planning on getting into sub phases and sub locations (subs of time) to help some of his growers move plants and track where things are at. After that, we both worked on different projects. I did some email, tech support, and read over some code that Will was working on to refactor the adilas API from a one-to-one relationship to a one-to-many relationship (API sockets and assignments per socket). At the end of the session, Steve and I were talking about tracking data for PO's, plants, seeds, trees, items, etc. We were thinking about options to combine the sub flags and tags tables (sub phases, sub groups, sub locations) with the any assignment tables for elements of time. The any assignment table was originally going to connect any person, place, or thing. Well, what if combined some of the options? That might be cool.

	Shop 3287		Lunch	12/12/2017

	Shop 3310		Combining sub phases and sub locations with the any assignments table	12/12/2017	sub flags and tags, sub phases, sub locations, and then mix it with any assignments (any person, place, or thing) - fill in some more notes here... great idea... where could it go... play with ideas of one-to-one for detailed tracking... play with ideas for one-to-many for group tracking of sorts... what options might we have? what about main_id, app_type_id, sub_id, table_name fields? what could that do? think and expand on the ideas.

	Shop 3297		Adilas Time	12/12/2017	Working on reviewing and getting code ready for merging in master. Working on the adilas API refactor project that was started and coded by Will. At the end of the session, I spoke with Calvin for a bit and got an update from him.

	Shop 3311		PDF and Third Party	12/12/2017	On a GoToMeeting session with Bryan. We started working on a number formatting bug. The number was formatted with commas and thus became a string vs. a real number. Once we got that fixed, everything went better. After that, we spent the rest of the time working on the Texas 130U PDF form. This is a pretty big form that helps dealers in Texas do there title paperwork. Going over different parts of the project and doing some testing.

	Shop 3317		General	12/12/2017	Helping to get Tanner set up to help me record tons of older post-it notes from back in 2016. I had a huge pile and they were just sitting around. Light training to help him get going. Recording notes from the day and working on the adilas API refactor project from Will.

	Shop 3321		General	12/12/2017	Code review and working on the adilas API refactor project coded by Will.

	Shop 3277		Adilas Time	12/13/2017	Normal GoToMeeting session in the morning. My computer was acting up so I had to restart and reboot in order to connect. Once I got on, I met briefly with both Alan and Calvin and we played a little catch-up on the sales tax expansion project. Later on around 10 am, I got on a GoToMeeting session with Megan Carr and Steve Blood from Columbia Care. They were asking questions about getting access to raw data. We presented a number of simple options going from easiest to more complex and custom. These were options such as: 1. Add new users and use system as is 2. Use existing exports, reports, and API sockets 3. Go custom - dream it up and we build it 4. Dedicated servers and remote access They then asked a number of questions and I gave them a quick little demo and showed them some tables and light raw data. We did a small sample query and talked about exports to MS Excel, CSV, XML, and/or JSON. We also talked about direct access to a remote datasource once they get a dedicated server in place. I referred them to Steve and his quote on the dedicated boxes and prices. After they left, I was working on the code review for Will and the adilas API refactor project. Towards the end of the session, Calvin got back on and asked some questions and reported on where he is at with testing on the sales tax expansion project. He also recommended that we stick to some kind of a web-based interface to serve up the raw data requested above. He recommended an API type interface so that we could monitor things, validate entries, and limit access to certain areas. I fully agree and will try to push things towards normal export features and/or internal API socket connections. Great idea.

	Shop 3288		Lunch	12/13/2017

	Shop 3266		Russell Moore	12/13/2017	On a Zoom session with Russell. We spent most of the day planning out what is needed for a project that will add a due date to the invoices. See attached for our notes and scratch document. We did some light brainstorming, set some variables, and went page to page and took some notes. We then started working on the database update. I was coding and Russell was watching and being a second pair of eyes.

	Shop 3322		Trailer PDF	12/13/2017	On a GoToMeeting session with Bryan. We looked into an API bug. We then merged in the Texas 130U PDF form and did some testing both local and live. We then went over a huge email from a client with super technical questions about numbers for a client. The client was comparing the main adilas.biz system (data 5 server) to data passed through a custom API socket. We were looking for discrepancies and making small tweaks to provide the same results. On a different note, Tanner is working and recording old post-it notes from 2016. He has a huge pile to go through. I was helping him and interpreting some of the notes and scribbles. He is doing a good job.

	Shop 3278		Adilas Time	12/14/2017	Morning GoToMeeting session. Mostly working by myself. Working on the adilas API socket code for Will. Touched base with Steve, Calvin, and Alan on different projects. As a fun side note, Calvin met with a client and will be proposing a mixed solution between a Window's desktop application using adilas API sockets and normal web-based adilas. That will be pretty cool. In a way, it is using the API sockets more than the normal application and existing flow. A full rewire job done on an external code set but still tapping into the power of the adilas platform. Pretty cool. Towards the end of the session, Mrs. Shari O. got on with Steve and I and we went over how to do assignments to custom paperwork. This uses the "Document Management" section. Shari O. needed to help setup some new clients on other servers to get access to the Texas 130U form and PDF document. Sometimes it is fun to look back and see some of the power and potential that we have built into the system. Tons and tons of dynamics. It just helps us play better in the custom realm.

	Shop 3289		Lunch	12/14/2017

	Shop 3298		Adilas Time	12/14/2017	Nothing happened here. Originally we had some time scheduled but we used it for other things.

	Shop 3312		Beaver Mountain	12/14/2017	Went into the Beaver Mountain, Logan office. I met with Debbie and Bri (Brhianna Malcolm) and we did an adilas training session on the custom interface stuff for the Beaver Mountain Ski School. Bri is the new office manager and Debbie is the Ski School Director. Good session and they were both quite proficient at the program. Bri seemed to pick things up quickly and Debbie has used it for a while no (a couple of seasons). They did give me a list of things that they wanted done and/or that I noticed as they were working. See attached for a scanned copy of my scribbles and notes. I will also list there out here. Notes from a meeting with Beaver Mountain: - On the calendar (time homepage), they want the arrows to keep going for next and previous. Currently, they only do the current month, the previous month, and the next month. They don't keep going in either direction. They would like that. - They would really like the abiltity to flip the lesson (time) templates. I too have had a need for that. The problem is that gets into settings and flip/flopping things. Maybe our idea of setting up time template overrides would work in that case. Just an idea. As a side note, the time template overrides are having the system update the template settings vs. having the user (code or interface) pass the settings in. That way, they would always be correct and controlled on the system level. - We found a bug when setting up the reoccurring elements of time (sub dates and times). If the element of time was unassigned, it only picked up the lesson (element of time) on the initial day. Once a valid instructor (payee/user) was setup, the reoccurring lesson dates showed up on the horizontal time view page. Otherwise, they did not. Small little bug. - They, Beaver Mountain Ski School, would love to have a drag and drop type interface where they could do bulk assignments of both instructors and students. Imagine a list of possible lessons (main elements of time), a list of available instructors (payee/users), and a list of students (either real customers or simple person flex grid records - quick assignments without a real person being attached). What if you could pull in the student that have the same levels, match them with an instructor, and assign all of those pieces to an element of time. It would also be cool if you could even create a new element of time and make the assignments from there as well. Think of drag and drop, pools, and a one-pager that does it all. That would be pretty cool. Maybe an HTML 5, JQuery, AJAX, or Flash app. Lots of options. - When editing a flex grid record, the ability to change the main id was not present when clicking on an edit link from a specific page. We need that to be present at basically all times or a quick way to get to it. The page in question was the print student list page. The important thing is making sure that the ability to change the main flex grid id (who is the host) is the important thing here. - On the flex grid... we have started a project called the limited flex grid, where the users could order and put the fields where they wanted them. They could show/hide fields, setup custom aliases, set defaults, and somewhat customize the 40+ flex grid fields. Well, that project is only part way done. They would like to see the project get finished and be able to help control both the normal add and edit pages as well as the limited add page. If I had my way, we would allow for the limited (ultra control) settings to cascade into the normal add/edit flex grid page. I would also love for an easy toggle to go between the simple or limited view and the full or expanded view (show everything). That would be super cool. Just to help with documentation, here are a couple of the page names that help deal with this project: flex_grid_home.cfm add_edit_flex_titles.cfm add_limited_flex_grid_settings.cfm search_additional_tieins.cfm add_limited_flex_grid.cfm add_edit_flex_grid.cfm - Setup and finish the duplicate elements of time page and functionality. They, Beaver Mountain would also like to be able to duplicate elements of time with their flex grid tie-ins and assignments. Beaver used elements of time mixed with flex grid tie-ins to handle their rosters and/or who is signed up to teach each day. Lots of that information doesn't change very often and it would be awesome if they could copy and/or duplicate records over and over again. It would save time and make it easier. This could be as easy as adding in a checkbox saying, copy/duplicate flex grid records. This is more of a general question, but what about other subs of time? Do those play into the copy/duplicate process? Just curious. - On the horizontal time view page, if an instructor is chosen, make sure that their payee/user id gets passed along and across. We added in some code to help set things to unassigned, but we may need to be able to overwrite that. - They would also love to get more involved in the payroll and sub payroll process (see element of time # 3197 for some light planning). That would really help them out as they already have tons of the data tied to the elements of time. They have the dates (main and sub dates), the instructors (payee/users), the lesson types (time templates), the students (customers or flex grid tie-ins), etc. It sure would be cool to get everything tied in and reporting back to help with sub payroll and such. It also sounds like Debbie is interested in working with us to build some of that out. That would be awesome to have someone to help prototype things and give feedback and suggestions. Good stuff. Once again, see attached for a quick scan of the notes. The actual notes here on this page have more details, but sometimes it helps to see the original notes.

	Shop 3237		Brandon out of the office all day	12/15/2017

	Shop 3352		General	12/15/2017	Bug fixes, emails, and recording notes.

	Shop 3353		General	12/16/2017	Emails, tech support, bug fixes, and recording notes. I then went back in and worked more on the authorization process for the adilas API sockets. This is part of a web/API refactor project that Will has been working on. I am rewriting the main authorization process for checking to see if we have a valid match with usernames, passwords, web page id's, payee/user id's, corporations, and status (open/closed) values. It gets pretty deep. We are building out from a perfect one-to-one relationship into a multi or one-to-many relationship. Just trying to keep everything straight.

	Shop 3279		Adilas Time	12/18/2017	Started out the morning talking to Steve on the GoToMeeting session. We were talking about developments that happened over the weekend. Steve was talking about an analogy - pay to play - and how that somewhat relates to what we are trying to do. We have a bunch of people who want things for free or want us to foot the bill. We just can't do that all the time. It comes down to if you really want it, you need to pay for it. Steve and I then talked about some business funding, his home refinance loan, and possible places where we could use and/or stash the monies. We have a couple different accounts and we may want to put money into some of the other accounts so that it does all get sucked up and used. Kinda like budgeting, but actually moving the monies out of the main account so that it won't accidently get used. We had all of the guys check in on different projects. We had Eric pop in. He had some questions on black box stuff and ecommerce. Alan popped in from California (on vacation) and Calvin popped in just to report and check in. Steve and I lightly talked about some budgeting and how we want to roll things out this next year. Good conversation stuff and we are all trying to push things forward. We then flipped into working on individual projects. I was working on the Adilas API refactor project that Will coded. Started getting into some testing and actual database changes. I had to fix a few bugs to make sure that everything went well.

	Shop 3290		Lunch	12/18/2017

	Shop 3267		Russell Moore	12/18/2017	On a Zoom session with Russell. We spent the entire time working on the invoice due date project. I was coding it and Russell was watching and doing little side things. We talked and chatted as we worked. At the end, he showed me some of his concept ideas on a new one page shopping cart that is super simple. Good session.

	Shop 3350		3rd Party code check	12/18/2017	On a GoToMeeting session with Bryan. We looked into his project for tracking invoice line item edits. He is working on a new history table or sorts to keep track of what changes have been made. After that, we went through a number of other projects. We merged some code into master and pushed it up to all servers. It is some special validation on the add/edit customer side for our clients if they have a 3rd party solution called Shield Pay turned on. Basically, Shield wanted to make sure that all new customers added to the system have certain fields filled in. Once we were done with those questions, we went back to some other projects and worked on small tweaks, changes, and ideas. We worked on math questions, where to get what values from what fields in the database, how to connect over https on the adilas API, etc. All kinds of smaller random questions.

	Shop 3280		Adilas Time	12/19/2017	On the morning GoToMeeting session. Steve and I chatted briefly and then just jumped in and started working. I finished up the Adilas API socket refactor project. I did some small changes, testing, and pushed files up and online. Once I was done with all of the database updates and merging stuff, I sent an email to the guys letting them know that some changes were launched and pushed. Eric jumped on part way through. He had a question about how to flag a certain customer/client/patient/student with certain attributes. He said that he would love to see parent attributes on customers. He loves how it works on parts and items. He would love to see it on customers and customer types. The deeper we get, the more custom of a solution we really need and want. All of us kinda get addicted to data and custom options. Towards the end of the session, I jumped back on the sales tax expansion project.

	Shop 3291		Lunch	12/19/2017

	Shop 3299		Adilas Time	12/19/2017	Working on merging in code that Calvin had been working on in the main branch for the sales tax expansion project.

	Shop 3355		Helios 3rd Party Page	12/19/2017	On a GoToMeeting session with Bryan. We were working on some of his custom projects. We went over how to hardcode a URL to start a new shopping cart by passing in URL values and basically shortcutting the normal system flow. After that, we jumped into some new projects and changes he needed help with. We did some merging of files and pushed a few things.

	Shop 3356		Beaver Demo for Will	12/19/2017	On a quick demo with Steve and Will going over some of the custom code for Beaver Mountain and their ski school reservation system. They are working on some campground reservations and trying to do a similar type interface. Light intro and showed some light functionality.

	Shop 3281		Adilas Time	12/20/2017	On the morning GoToMeeting session with Steve. We were talking and chatting about our developers and guys. We've got some great guys and gals that are working with us. In the background, I was merging in code from Alan and Calvin and the sales tax expansion project. I got a call from Calvin and we spent some good time talking on the phone. He was basically sharing where he is at and how things (life in general) were going. I told him we wanted him on the team and consider him an asset with his skills, talents, and personality. After I got off the phone with Calvin, I chatted with Steve once he came back on the meeting. He had a small school Christmas program to go to. We made some plans and really want to help keep Calvin going in a good direction. Good stuff.

	Shop 3292		Lunch	12/20/2017

	Shop 3268		Russell Moore	12/20/2017	Working on a small bug fix for Shari O. for stock/units on data 6. Then on a Zoom session with Russell. We merged in two code branches and uploaded code to the servers. One of them introduced a predictive text search for adding a new customer to a shopping cart.

	Shop 3357		SHAWN	12/20/2017	Shawn came over and dropped off some year end documents such as 1099's and W-2's off for me to test and do some printing. We met and chatted and I got him a check. Both before and after that, I was prepping files to help with merges between master and the sales tax expansion code branch.

	Shop 3282		Adilas Time	12/21/2017	GoToMeeting session - Steve and I chatted about new updates and things that are happening. Calvin jumped on and we talked about options of building up the internal build process inside of adilas, recipe/builds, sub inventory, mini conversion, and hybrid products (desktop apps mixed with API access to data with backend cloud storage options). Pretty good conversation and some good ideas. I spent most of the time merging code between branches. Alan popped in and reported. He is finished with school and is now getting back in the grove of the adilas projects. Good stuff. Started into the sales tax updates for stock/units. Working on the database update file for stock/units (serialized inventory).

	Shop 3293		Lunch	12/21/2017

	Shop 3300		Adilas Time	12/21/2017	Paying bills and reading through emails. Back on the sales tax expansion project. Trying to focus on the stock/unit changes, tables, and new fields.

	Shop 3358		Bryan	12/21/2017	GoToMeeting with Bryan... fixing a dynamic data problem... then working on the new special update history for invoice and PO line items (super deep before and after history stuff).

	Shop 3361		Tech support for Shannon	12/21/2017	On the phone with Steve going over all kinds of stuff. Topics included: Canada, developers and their strengths, adilas packages and pro pricing, funding, growing and maturing as a company, etc. Good conversation and all areas are progressing and developing.

	Shop 3238		Brandon out of the office all day	12/22/2017

	Shop 3252		Christmas - Enjoy with your family	12/25/2017

	Shop 3283		Adilas Time	12/26/2017	Brainstorming with Steve on the morning GoToMeeting session. We were talking about using elements of time and expanding the sub flags and tags table (time_sub_special_flags) to tie to outside pieces. By outside pieces, we were talking about main player objects within the system (PO's, invoices, items, customers, etc.) and/or even sub line items or sub details. We did a lot of drawings and talked about options. Mostly on the theory level or concept level. See attached for some drawings and sketches. We determined that we would be adding some new fields to the sub flags and tags tables to help with the outside connections. They are things like app type id, main id, sub id, table name, and total time calculations. Good little session. Calvin came on and we got him setup with some files and code to help with a data migration project from corp to corp on a single server. After that, we each started working on our own projects. I was recording notes and bouncing between projects and small to do list stuff. I also was able to get back into the sales tax expansion project and started working on the new stock/unit changes.

	Shop 3294		Lunch	12/26/2017

	Shop 3301		Adilas Time	12/26/2017	For the afternoon, I jumped on the GoToMeeting session and started working. At first, I was by myself working on the sales tax expansion project for stock/units. I then had to go in and I fixed a bug with the web/API assignments. I worked on cascading the from web page id's to all internal pages that call the web/API assignments. Lots of small tweaks and small filters were added to help things be tighter and return better results. Both Steve and Calvin came onto the session later on. Small little chit chat back and forth as all of us were working. I also helped Calvin with his data migration project. I am grateful that he was on that project. He had to do tons of clicks to make things happen. I could tell that his mind was running and he was thinking of ways to limit the number of clicks we have to do to make those data migrations happen. Good stuff.

	Shop 3359		Shawn - Year end stuff	12/26/2017	I was on a different project. No work or action was done here.

	Shop 3284		Adilas Time	12/27/2017	Working with Steve on the morning GoToMeeting session. I was finishing up the web/API assignment fixes and Steve was working on some custom code pages. Once I finished my project, I merged in some code and pushed up about 70 new files with changes. I then switched and started back on the sales tax expansion project.

	Shop 3295		Lunch	12/27/2017

	Shop 3270		Russell Moore	12/27/2017	Met up with Russell on a Zoom session. We were going to be working on the invoice due date project, but got derailed and ended up talking the entire session about the "any" assignments section for elements of time. This deals with simple assignments of main players, generic assignments, rentals, reservations, and other sub assignments to time. We talked about three different options. They were the existing pools and any assignments, the sub flags and tags table (expanding it), and using flex grid to help track things. We went over pros and cons of each option. That conversation sprung a sub topic about funding and getting paid for the work that we do. Also dealing with timing and mixing between wants, needs, goals, and dreams. This topic cluster put me into a tail spin and Russell had to ask some questions to get me back on track. I finally calmed down and we talked through a few things. I think I was just feeling some pressures from other places and it ended up boiling over onto Russell. Anyways, we chatted, made some plans, and I feel, we really tried to understand each other. Good meeting.

	Shop 3363		Out of the office	12/27/2017	Brandon out of the office for a family Christmas party.

	Shop 3285		Adilas Time	12/28/2017	Talking with Steve on the morning GoToMeeting. - Concepts of a trust and who owns what... -- What about founders, co-founders, dependables, etc. -- How do we bring people into the family or inter circle? -- How do we let people go? -- How do we pay people? -- Defining the model - Being a business solution like playing in social media - come learn about what adilas does - The use of the word dependables - Outside parties need to build on the main core platform - We are all standing on the shoulders of giants - We are working on a dynamic working model - we want to keep pushing that thing forward - What about multiple people trying to do similar projects at the same time? How does that play out. - Like landing an airplane... if you can hit the correct pattern, great, hit it. If not, just circle back around and try to line it up again. Basically, if you miss a pass, just do it again until it lines up. It is ok to make multiple passes. - Eric and his pricing engine - Russell and Chris Johnnie on their AFB stuff - Calvin and his email and text messaging stuff - There are a number of huge pieces that need to be nailed down and pulled in... they are things like adilas world, adilas market, and adilas university. - We want to keep pushing the adilas monthly up so that we could push more monies around to our dependables and other outside 3rd parties. - We may need to talk with some of our outside parties and figure out how to structure things. How can we join up and roll things together. - On the billing, we need to setup some standards for who bills, what percentages get kept and/or paid back - Put the monies into the payables and then allow some of our guys to go in and print their own checks. - If their payables go over a certain amount or certain age, we move it to the balance sheet - Define the core of adilas a little bit deeper - What are the ground rules and how to play the game. - We are seeing that our people want a level of trust and/or consistency - expectations and such - Like a volcano, inside the circle, outside the circle, how do people move between things, how do we manage complacency and/or lack of motivation - How can we help them (our players) see the bigger vision - Danny Shuford - We are a business solution for solution minded people - The Adilas API sockets will be coming more into the main picture. If we really push this out, we could harness so many more developers. We could really define what is available and what is possible. This is part of the Adilas platform and how it could work. - We can help steer the ship - The code is one of a thousand possible options. The concepts we are built upon are really worth way more than the actual code. - Steps to success - telling and catching the story - allocate some time to this project - what have we learned and applied along the way

	Shop 3296		Lunch	12/28/2017

	Shop 3364		recording edits	12/28/2017	Meeting with Bryan via GoToMeeting. We were talking about using the Adilas API sockets and then pulling and/or exporting data for a 3rd party solution that will eventually push the data into an outside software system like QuickBooks. We also talked about eventually moving internal page flow code into the API sockets to make things more standard. Lots of ways to skip around if someone is just using API's vs. our existing steps and page flow.

	Shop 3269		Russell Moore	12/28/2017	Working with Russell over a Zoom session. We spent quite a bit of time talking about the adilas any assignment features. Clear down to the database planning level. We chatted about options and possible extensions. Lots of fun ideas and progress.

	Shop 3360		General	12/28/2017	Spent some more time working on the add unit to cart process for the sales tax expansion project. Trying to chip away at this huge project. I've got to get this done so that I can move on.

	Shop 3239		Brandon out of the office all day	12/29/2017

	Shop 3436		Meeting with Shawn - Year end stuff	12/30/2017	Shawn came over to my house. We were working on the year end 1099 and W-2 forms. Shawn gave me some new code and we did a number of print tests. I also spent some time merging in code and reading over emails.

	Shop 3437		General	12/30/2017	Chatted on the phone with Wayne Andersen about a data upload and migration project. Then back working on the year end forms and such. Pushed up new forms and did some testing. I then made a couple small changes for Beaver Mountain and opened up the duplicate time or setup reoccurring time pages and looked over code. I would love to get back on that project.

What's New

Products

Find Us