Work session with Hamid. He finished up the 12 business functions and the see more features modals and bulleted lists. See below for a list of link (see the section titled see more features per page). We also checked and pushed up a bunch of the smaller PDF's that show the business functions in a printable format. Good work session.

Sales, Inventory & POS System
Customer Relationship Management (CRM)
Calendaring & Scheduling
eCommerce
Accounting & Backend Office
Expense Tracking
Payroll & Time Cards
Reports & Histories
Business Intelligence (BI)
Data Relationships
Content Management System (CMS)
Big Data

Going forward, he is going to be working on some training in CSS and JavaScript until Shannon and I can get him some new content for the presentation gallery site.

 Working on the Yogen Fruz special report page for Phillip. Working on really building out the page. Tied in the new form, the comparison, and started showing output values. Good work session.

Meeting with Shannon. Doing some light catch-up. It has been a while since I have worked with Shannon. Talking about patience and waiting on the Lord (His timing). I reported on my trip up to Canada and how things went up there. We talked about working on the presentation gallery, chipping away, at that big project. We talked about other content needs and how we can push the ball forward. I would like Shannon's help on plans, outlines, and helping me to make new content. She has been great on those levels. Super excited to get back to work with her. We also talked about letting go and not trying to micro control everything to a super tight level (obsessed with details or perfectionism). Let's just get it out there.

Working with Steve. Working with the inventory snapshot code/database and back figuring the data. We are planning on harnessing user clicks to help with catching up the rolling part/item quantity. We worked on adding in a threshold value and a quantity check to help us watch and monitor which items have been updated. Multi-hour building and work session.

Meeting with Bryan to go over some planning and building out a demo site with both flex attributes and flex grid tie-in (building forms and drop-downs). Spent the session actually building it out.

Clock in/out issue that Cory sent to me. Quick backend database change. Texted cory that it was fixed.

Meeting with Russell. Working with Russell to bring in small pieces of the layout that we made in Adobe XD. Building the form, the toggle to show hide the other part of the form, and working on custom CSS (cascading style sheets - layout and view code stuff).

Talking about making some UML diagrams for the adilas database. We spent a bunch of time talking about databases and all of the interconnected relationship (just for parts, PO's, invoices, and sub inventory). For me, send Cody all of my old database docs (take the time to get him the correct info - ended up finding a few back from 2016 and 2017 - they had been uploaded into the adilas shop media/content folder - do a description search by database and set the dates back to 2016 to 2017).

We also spent some time talking about banking hours and how that works (paid time off or future payout options). We then got into working on permissions inside of the label builder. We went through a bunch of stuff and added some light permissions to the label builder home page. Good work session.

Cody is wanting to help me get some of the older projects done that have been on my tick list for years and years. I'm excited about that.

They were busy doing some customer integration stuff so we will have to reschedule. Texting back and forth.

Emails, paying bills, internal tech support, and merged in some code for Bryan. Small change on the QuickBooks API stuff that he is working on. Pushed up files to all servers.

Meeting with Wayne and Alan to go over options for database configuration options (code words... datasource project or bus to motorcycle or world building project). Light catch-up. Wayne was going over options for running a base service to figure out the corp and datasource (what database to use). The old datasource is the default.

Talking about efficiency and combining corporations and servers. Going over scenarios. The idea is to make the code and the schema unaware (more open - able to connect to any database). For me, I have a bunch of older notes under clustering, solar systems, and galaxies (all kinds of cross-schema options).

For us, internally, database updates may get more crazy, especially for our developers. Talking about possible load balancing stuff. We were talking about master databases, sub databases, and efficiency questions.

- Wayne was recommending a more company related approach (which businesses are connected or have a relationship) vs corp related (single worlds, all by themselves). Widen it out a bit.

- Wayne's branch... WLA/DynamicDSN

- Alan was talking about a wish list to help update things from one spot (one page or one server) vs logging into each server to run it on each server (current process).

- Wayne already uses a script (test script) to run his database updates. He doesn't like to do things over and over again. He would rather build a script or make a tool to do that.

- Wayne wants Alan and I to help pitch it to Steve and Cory.

- We may need to look at and check the edge cases (on the datasource look-up project). They were talking about some known caching issues.

- Places that we need to check... (list of us, internally)
>> shop folder - there is some session stuff but it is different then the top_secret stuff.
>> web folder - API's - most pass in a corp key that we can figure out a corp id number from.
>> public folder - hardcoded per page or FORM or URL scoped controlled.
>> temp folder - hardcoded per page or FORM or URL scoped controlled.
>> database_updates folder - may need to query (get all known datasources), then loop and do updates per schema. basically, layer and nest things vs just plain doing a single update.
>> check the process to create a new corp - some questions there (we are currently using the main datasource and building tables and inputting values based on our create new corp routines).
>> caching - check the daos, services, and cfc's - make sure we do what we need to here to make this still function correctly.
>> search for corp_id IN (? whatever the list or arguments are) - multi corp queries. Maybe be able to set a temporary master/primary corp id where needed.

Working with Bryan. He was trying to setup flex grid and flex attributes for an upcoming demo. We did some planning and looking at the different pieces and what would need to go where. We were using simple notes, outlines, and even got into some table/data simulations in Microsoft Excel. Sometimes that really helps to show how the data will look and how it will be related, connected, and stored. You can even see how you would query and filter things as well. Great planning and mock-up tool.

Spent the last 15 minutes doing emails and cleaning up.

Emails. Quick meeting with Cody to look at his code. Ended up debugging a small database update to total up the sub date/times for all existing records. We pushed up the code and then talked about some of the next steps.

Meeting with Cody. Trying to figure out the next phase or part of the label builder project. We recorded some notes and plan on doing some security stuff on Wednesday morning. We talked about using the buddy system to get through certain projects and help with motivation. I sent him over a whole bunch of my little todo list items. I helped him get some small bugs fixed, that I knew how to fix (based on older files and custom includes). Small work session.