|
Adilas.biz Developer's Notebook Report - 10/30/2025 to 10/30/2025 - (4)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
| Shop 12429 |
|
Meeting with the Nxtlinq guys | 10/30/2025 |
Meeting with the Nxtlinq guys. They had a small agenda and we went over it. Nothing too crazy. They are using a crawler to go over the help files. They did have some questions about some of AI quick search prompts that did not have a help file and/or would go to some other site or external reference. We talked about it and they are going to use their web crawler and get what they can. Thomas from Nxtlinq was talking about their AI agent, they are calling NxtGPT (GPT stands for Generative Pre-trained Transformer - AI deep learning stuff). That seems like a cool name. I may put in writing some of our requests with regards to the AI agent. We just want to turn it on and not have to verify or set permissions. Our application has built-in error handling and user permission checks on every page. If we have to do settings inside the system and inside the AI agent, our customers or clients might say no. Too much setup... Anyways, I will put some stuff in writing and we'll go from there. Basically, I'm going to say that adilas, as client of NxtGPT and Nxtlinq, we don't want the AI agent to require permissions. The adilas.biz application will take care of the permissions at the user per corp per page level. They reported that they are ingesting the help files and pushing them over to the agent. That is awesome. There are over 500+ help files. That is awesome and will really help get the AI agent smarter on adilas stuff. Lastly, I really want to read over some feedback that they, Nxtlinq, gave us from the last meeting. I briefly saw it, but want to really give it a better look over. That is mostly for me. Anyways, good meeting. I sent Steve a quick text after the meeting. |
||
| Shop 12407 |
|
Meeting with Hamid | 10/30/2025 |
Meeting with Hamid. We did some reviewing of where we left off last time. After that, we then jumped back into the CSS course from Udemy that we were working on. Practicing and playing around with the commands and code. Went through a few chapters and videos. We are both trying to learn more about CSS. I already know some things and I've worked with it before, but never gone through an official course or class. It is surprising how many base level pieces I either thought that I knew or only mildly understood. I'm enjoying the learning process. |
||
| Shop 12427 |
|
General | 10/30/2025 |
Emails and reviewing a super cool video on Affinity Studio - It has some awesome custom menu options and is a well done promo video. I watched it and then sent it out to a number of our people to show that what they are doing. I would love to be at that level where we can push something like that out and create those kinds of tools, features, and razzle/dazzle. Pretty cool! Paying bills, phone call with Bryan about transitional invoices and options. We have the functions and functionality, but nobody knows how to use them... We need more training and easy ways to get at what is possible. I was explaining to Bryan how it all works. We also talked about moving away from sub inventory, depending on the scenario. Sometimes parent inventory tracking works better than subs, for certain scenarios. We also need to get to the ICC (internal cost corrections) project up and going. That has been a requested feature for years. Recording notes from yesterday and today. |
||
| Shop 12403 |
|
Working with Shannon | 10/30/2025 |
Working with Shannon. We stated out the session talking about building on what we have and filling in the gaps. We talked about building bridges vs building walls (one lets people in and the other keeps people out).
We talked about API's, sockets, endpoints, and how all these things play and flow together. I was drawing up a storm. We spent a bunch of time looking at some graphics in the teaching gallery and then drawing on top of those graphics. We then flipped over to work on content in the adilas lite and fracture plans. We were working in the API socket section of that page. So many potential benefits and ways to use it. One of my big takeaways was how this could tie-in to the value add-on core model. We, adilas, create the master road map for our product that is called the value add-on core. Adilas is going to build out the main transactional core (level 1 of 5). Any other level could be built out and/or added to with the API. We can't even fathom all of the possibilities. If you want more information about the value add-on core and all of the levels of the master plan, please see that section. Here is a quick overview of the adilas value add-on core model... Level 1 - Adilas Transactional Data Core Level 2 - Industry Specific Skins Level 3 - Custom Code Level 4 - Business Intelligence (BI) Level 5 - Enterprise (multi world) |
||