Paying bills and checking code for changes made last night. Ran a couple of sample transactions through the system. Light debugging and pushed up a new file. Sent an email to the client to have them do some testing.

Multiple sessions working on custom cart logic. Back on the logic for the golf tournament and how many participant records to show at checkout. They have donations, singles, foursomes, sponsors, etc. Testing counters and logic to show the correct number of participation and contact info records. Started working on saving that data to the cart memory object out in ecommerce land. Recording the contact info records and advancing the page on to the web make payment page. Also, at the client's request, made the ecommerce custom header non sticky, meaning it stays in one spot and the whole page scrolls down. Recording the flex grid tie-ins for the dynamic contact info and golf team registration

Helping Steve with a quick merge conflict resolution for a file. He also showed me some of the efforts that he and Josh are working on to do voice automation bots through AI agents. They are playing around with a company out of California that Josh knows.

Working with Steve on a custom ecommerce shopping cart. He is working on selling sub inventory by choosing a sub package to purchase. He had a bunch of code from Grok (AI stuff), and we had to back most of it out. We did it the old fashion way and got it all working. Not that the code was bad from AI but it didn't fit into our page flow. Anyways, we got it all fixed up and good to go. Steve is going to keep tweaking on his code, but we got the main task done and accomplished. Good work session.

Working with Shannon on content for the adilas master plan. Finished up the enterprise level content (see below). We then reread the whole value add-on core model page.

Here is the content we came up with for the Enterprise level:

Level five of the value add-on core is what we are calling enterprise, or the enterprise level. Not every client or corporation needs this level of interaction and functionality. That is why this level is the top most level of the value add-on core model. For those who do need it, it becomes the unlimited top end and allows for all kinds of functionality between multiple locations or multiple corporations. Enterprise could be a number of different things, but essentially you start getting into a scenario where you have one master corporation that controls smaller entities. Think Sci-Fi (science fiction), top level control or dominance. You always have the aliens with a master ship that controls all of the sub ships and sub armies attacking the planet. Below we will paint a small picture of how this may look. Once again, this is not required but has huge potential for those who want and need it.

Back to the business Sci-Fi levels... In a world building analogy, imagine a universe level. You have multiple planets, solar systems, clusters, all kinds of things that are interacting together. Normally, most of your transactions that happen inside of adilas are on a single world, or on a single planet type level. That is what we would call a corporation or business entity. In the enterprise realm, you are starting to mix and blend worlds and/or corporations. This is great for all kinds of businesses where you have either franchises, mother/daughter type corporations, vendor/distributor, or entities that are somewhat connected and have either shared financials or shared ownership.

Inside of the enterprise level, we have already defined a number of pieces with data flow going both up and down the chain, big to small or small to big. Data flow is really important and helps with communications and reporting. The real value of that communication channel is too broad for this discussion, but it is essential for enterprise level transactions. You could also add any amount of custom code to create rules, automations, functionality, special relationships, or define any other need for the flow of data. Custom code at this enterprise level is how you fine tune your processes and cater the software application to your business needs.

One of the goals of an enterprise level system is normalization, meaning normalizing or standardizing your data. You can have multiple different businesses, all running on adilas, and they can all use the same terminology and the same type of accounts or landing places for your data. This allows data to flow up and down and in between worlds to help with reporting and business intelligence. It then allows you to pull standardized reports so much easier than pulling individual reports and trying to blend them together with spreadsheets or other methods. Depending on the size of the company, some of this normalization can be very cost intensive and even painful. Sometimes there are even teams setup specifically for the purpose of extracting and normalizing data from multiple software systems. The adilas enterprise level has incredible value and helps to overcome some big pain points for traditional companies. Think business intelligence on an enterprise or universe type level.

Here are some other benefits of the enterprise level:
- Master lists or libraries of data - items, vendors, customers, photo galleries, etc.
- Shared loyalty points and gift cards
- Multi-locational or multi-corporational
- Bulk tools, rules, processes, and scheduled tasks
- Consolidated banking and financials
- Consolidated reporting and business intelligence
- Permission levels and security
- Automated routines and processes
- Options for custom code

Amazing potential in the enterprise level! This is the top most level of the value add-on core. You get to mix, blend, and use any of these sub pieces to create your perfect dream business, track and record your story, ease your pain, and have the necessary pieces to help your business thrive!

Working on the dynamic flex grid tie-in logic for the golf tournament registration (custom ecommerce checkout process). Going over scenarios. Thinking about ways to remove records.

Dealing with multiple participants signing up for the golf tournament (singles, doubles, and foursomes). Tons of dynamic coding to setup multi flex grid tie-in options out in ecommerce land for gathering up the dynamic data. Deep looping logic stuff. Sent an email note to the client letting them know that it would be done by tomorrow afternoon.

Working on the custom cart logic for the Benning Construction checkout process. Building and checking the logic section by section. Uploading a small sample file and then testing the black box (custom code) live on the server.

Working with Russell. Jumping onto the chart stuff. We started out talking about life here and life after death (fun talking philosophy). Talking about limitations in our vision and outlook. So many good experiences here on this earth life. Take advantage of that.

Working with Russell on Adobe XD mock-ups. Going over plans for date pickers, date ranges, and advanced comparisons for dates and presets (day, week, month, quarter, year). We also want to build in jumper values for next and previous dates. Exploring navigation options, scenarios, pagination, and drill-downs.

Russell loves the full experience... for code projects - plan it and implement it - design, develop, and project management - mix all of those things together. That is fun to come up with it and then see it all the way through. Good stuff!

Bulk flex grid stuff for the Benning Construction golf tournament. Fixed some black box code for both internal tooling and external tooling out in ecommerce land. Both have to play along in the custom realm. Trying to collect names, contact info, shirt sizes, and dietary restrictions per participant and then tie everything back to invoices. Possible one-to-many relationship between invoices and how many contact records (golf team registration stuff).

Working on the Benning code to catch and gather the contact info per participant in the golf tournament. They opted not to setup a normal customer and are doing all of their invoices through a quest customer profile. We then have to catch a bunch of other data after the fact and tie it into the invoice. Also added in some bulk add and edit buttons to help with bulk flex grid tie-ins for internal pages (invoice line items and printable invoices). This will help later on, once they start getting some registrations.

Meeting with Bryan. Fixing some small bugs out in ecommerce. We made the changes and did some live testing. Once we got that finished, we switched gears and looked at Bryan's code for his Plaid API stuff (external banking API). We did some more testing and tracked down a number of different variables. Trying to make the whole process smoother.

Working on code changes for the Benning Construction ecommerce site. Working on some tweaks to the donation entry, had to hide the price and add some extra verbiage. Working on collecting contact information. We will be using some custom code to gather things like name, contact info, shirt sizes, and dietary restrictions. All part of the golf tournament registration stuff.

Work session for the Benning construction site. Added a new top header logo. They provided a nice flyer. Took a bunch of the images off of the flyer to rework the header graphic. Working on the custom code to help with the donations page. Had to open up the pricing field. Meeting with the construction company and Bryan and Suzi from the adilas team. Quick meeting. We are getting closer. After the meeting, then working on a small to do list of items. Small cosmetic stuff.

Working on content for the enterprise level of the value add-on core model. Smaller session today. I have some other things that have been promised. As Shannon and I were talking, we decided that adilas has a big appeal because it is so open... there are also a number of problems and challenges because it is so open. It's all part of the game we are playing. Part of the environment and real estate of the adilas application.

Paying bills and recording notes. Lots of internal tech support stuff today. Also, at two different times, we tried to jump on the GoToMeeting session but others were using the account. Steve was on earlier in a demo when Alan and I were going to use it. Then Alan was on later when Bryan and I were going to jump in. All is well. I'm glad that they were getting their stuff done as well. Busy day!

Phone calls with Bryan. He and I are working on the Benning Construction website. He passed me over some code via email. We also heard back from the client, and they are wanting a fancier looking site. Lots of lastminute changes. We'll see what we can come up with.

Internal tech support, helping Bryan with questions for a client. Multiple phone calls with questions. Lots of internal PO and inventory stuff. He needed to know how to switch vendors, mix vendors, convert between pounds and single packages (each). Also questions about printable invoices and forcing things to a certain size. Answering questions. Some of the topics I haven't done in years. It was stretching me a bit.

Texts, phone calls, and emails. We had to flush and make a small Cardpointe change for ecommerce checkout on data 0 (merchant processing stuff). We were having a hard time with the page clearing the cache and flushing the application scope variables. Working with Alan to get the fix in place for the client.