Steve was out all week, last week. He gave us all a report on some of his outings and adventures. Good stuff and Steve is excited to be back in the saddle. Alan reported on his reoccurring payment stuff. We talked about more charts, eye candy, and other reports. Alan and I also talked about working on some code sign-off and trying to get back to some of those other projects.

I helped Steve with some code merging and pushed up some new files. I then got on a call with Eric and we touched base on his sub special account tracking project (loyalty points and gift cards). I told him that I was going to be pushing more on that this week. We also talked about an upcoming project to look at the adilas look and feel (over arching look and feel). This doesn't exist yet, but I was just talking with Eric about looking for ideas and making a plan. Anyways, he is interested in helping us out there.

I setup a time with Shawn to work with him. I recorded some bills, did some email stuff, and recorded some notes. Trying to push the ball forward.

Steve was on with Cory (an adilas rep) and they were going over some production and cultivation processes. Cory is going to be helping with some news and updates. After that, Wayne joined the meeting and we briefly went over the transition progress between Newtek servers (existing dedicated models) and upcoming AWS (amazon web services) stuff.

This has been a known need... We need an ongoing date range feature for the saved reports. Say something like: today, yesterday, this week, last week, this month, last month, current day, current week, current month, ect. We have some of those settings, but it would make some of the saved reports even more flexible. Currently, most of our dates are set and very specific and they have to change the dates if they are running off of saved report settings.

Long story made short, we need a way to save a dynamic (somewhat moving) date range for some of the custom reports. That way, the dates keep moving as needed, but all of the other saved search or filter criteria stays in place.

On the balance sheet, we currently only do a report per date (single date). We would love to get it out to hours, minutes, and even seconds. Eventually we would love to get it to the 3D time calendar level, but there is a need there. All of the reports would be cool if we could take it out to hours and minutes as well.

Along with that, we have had requests to allow the transitional invoices and transitional PO's to go clear out to the hours and minute level. Currently, those invoices and/or PO's are set to a physical date (single day).

As a side note, everything is breaking into subs and fracturing into smaller and smaller levels. Even reports and date/times, etc. Pretty crazy.

Working with Shawn to get his system up to date with new code.

Bryan jumped on and we went over some new possible corp-wide settings for showing email addresses on invoices and quotes. We talked about allowing options for showing emails per salesperson (payee/user), per corporation (per business entity), or per location (per store/location - all invoices are tied to a specific store/location). All he needed was a little bit of direction.

Merged in some new payroll withholding updates from Shawn. Ran the new updates on all servers.

Wayne pretty much ran the morning meeting today. As soon as I joined, Wayne, Steve, and Dustin were already on. Once we got started, the entire session was dealing with updates and upcoming changes that are available to us out in AWS (amazon web services) land. Kinda interesting.

We started the morning talking about photos, scans, and images and how those are stored currently. We moved to media/content (outside files) and then talked about ways of doing that kind of storage in the new environment.

Wayne was showing us how quickly he was able to copy whole servers (existing dedicated boxes at Newtek) over to the AWS environment. He was also showing us how some of the resource management (CPU's, memory, and load balancing) were working as he spun up other instances. Very quick and very powerful. We are going to be able to speed up our time to market by leaps and bounds. Lots of talk about current model, options, and needs vs upcoming/future model, options, and new needs.

There was quite a bit of time spent talking about existing flow, hot fixes, FTP (file transfer protocol), and code repositories and deployment options. Lots of talk about the advantages of building a testing library and running tests and unit tests to increase the level of comfort, efficiency, and confidence for the developers and the clients (system users).

Wayne was using the term "tooling" and using the new tools and/or tooling environment to help standardize environments, processes, and expectations.

We went over some possible problems with incomplete data and who is going to help mange and/or watch what pieces of the system. It really will be, and currently is, a giant team effort. We need all of the players to keep pulling their weight and doing what they do and how they do it. More and more talks about teams and cross training those teams.

Got on to work with Shawn. He was working on payroll stuff so I ended up on a tech support call with Pat and Shari O. We spent about 1.5 hours working on getting those two, Pat and Shari O., setup and using the adilas label builder wizard that Calvin Chipman created. They got a pretty good taste of what it can do and we did some light playing and training. Lots of potential there. After that, I worked on some other emails and notes.

Ideas for a balanced approach... imagine a plate on a pivot point or a fulcrum - how much of each section could you load up without tipping things over or what is the virtual balance point? Good questions. We are seeing needs in the following areas. There may be more... System development, number of clients, and education

 -System development (look and feel, new functions, logic, database, and basic functionality)
 - Number of clients (sales and number of system users - feedback, funding, and ideas)
 - Education (how, when, why, where, how much, etc. - videos, graphics, text, verbage, flow processes, industry specific, trends)

- Here is a good question, how do you manage the demands? What about funding? What about skilled people power (skilled talent)? Those are resources that need to be managed and balanced as well. Interesting.

- We talked about possibly stopping development (system development). There are pro and cons to this. We also talked about - can we even stop that? It seems to keep going on for as far as we can see.

- We talked about how good reps and consultants are filling in the gap between new clients and education and new clients and new system development. They, the reps and consultants, become a virtual motor or engine to help people keep going, train others to do what is needed, and push things forward. There is no standard training material that is provided by adilas right now. The good reps and consultants provide those missing pieces. They are a super valuable piece of the puzzle.

- If we keep building, how to do we support (education) that new development?

- If we made a full on system user manual, would anybody actually read that? There might be a few, but most would like to know that one exists, but they want their information and training quick and on demand. Almost the "google it" - type mentality. A quick YouTube search, looking for videos that are 2 - 5 minutes (max). What would help us be the most successful in that realm?

- What if we put in small videos and started using the small little gear on the side of the snow owl look and feel theme (additional page settings)? Put some small videos in place and help the education process by putting assets in the right place.

- Shannon and I will be turning and going back to filling in some more content on the user guide. We will be turning all of the content into different elements of time in the adilas university site. We are then able to show/hide content, edit things, add photos, show user threads (sub notes and comments and/or forum type discussions), add videos, add other media (Excel, Word, PDF, images, etc.). Turn it into our own content management system (CMS). Making these changes will be a game changer for us. That will really help. Exciting.

Met up with Bryan to go over the new invoice/quote settings for show/hiding different contact email addresses. This is a new corp-wide setting that displays different invoices on the printable quote/orders and printable invoices. The different options are: show the salesperson's contact email address, a location specific email address, or a corp-specific email address. We made a few changes and Bryan is going to be finishing things up and we'll launch it tomorrow.

Steve and I had to do some quick checking on the data 7 server. It was having some problems and issues. Steve also reported on a meeting he had with Eric and talking about putting Eric on some of the look and feel pieces of adilas. Lots of good things going on and happening all around us.

Reading notes and recording notes from the day. Busy times but lot of good things going on.

Working on code sign-off for Eric's sub special account tracking project (loyalty points, gift cards, etc.).

Josh joined the meeting and we worked through a few small things. He has 5 files that needed to be looked at. We talked about a few things and he will be reporting back in tomorrow for the final sign-off.

Wayne jumped in and had some questions about where and how we are storing images. We talked about what it would take to get all of those images pushed out and stored on the adilas content server. As part of our conversation, we did a quick search to see how many pages may need to be updated. We got a number around 340 pages that deal with images and/or image paths. All of those files would need to be updated.

Back on the code review project for Eric and the sub special account tracking stuff - sub of the balance sheet for things like loyalty points, gift cards, in-store credit, etc.

Back working on Eric's sub special account tracking project and code sign-off. Working on the corp-specific rules portion.

Reviewing a news and update (still in draft mode) for viewing customer history. Cory has been working on it and it looks good.

Got on with Bryan and went over the new show/hide email contact settings for printable invoices and quotes. We merged in new code, ran updates, and did some testing. Towards the end, we had to do a light little bit of bug checking and testing out in ecommerce land.

Meeting notes. Steve, Brandon, Wayne, and Dustin were on the meeting. Wayne was showing Steve and I about some cool image manipulation options. The site and tools are called Thumbor - image manipulation. It was capable of pushing up an image and then running all kinds of cool tweaks to the image, on the fly. Things like cropping, scaling, specific file sizes, grayscale, colorizing filters, etc. Pretty cool. Our goal there was to talk about ways of using existing tools to eliminate how much processing we make our ColdFusion servers do. Currently, we do all of our own image manipulation and storage on a per server basis. Just some ideas and concepts at this time in the game.

After Wayne and Dustin left, Steve and I had a good discussion about where are things at and where are we headed. Both positive and potential dangerous and/or scary. Open conversation, no specific takeaways. Here are some of our notes:

- Defining strengths and weaknesses and then working on both

- Talking about the new AWS stuff - pros and cons

- The skill level difference between an adilas user who is a developer and a normal or non adilas user computer developer - there is a difference. A lot of our stuff has a culture and all kinds of cause and effect relationships attached to single decisions, setting changes, and/or wants and needs. Interesting.

- Your eductaion and expierence help you on your approach and/or your angle of attack

- Revenue is not what you get to spend

- We have a bunch of things that are partially done - finishers wanted

- We talked about the scary pieces... These are mostly the unknowns... this could be on complexity of the AWS side of things and/or the unknowns on normal operational costs (speaking of AWS stuff).

- Steve and I spent quite a bit of time on - Let's make a plan - this is huge. We really need to see what and where we are doing and going. We know that the plan changes from time to time, but we need something to help us direct this thing as we move forward.

- Scratch built vs pre-fab or mash-up options. We have been pretty spoiled and have built our own scratch built pieces for years... we can't keep up with demands if we keep that same mentality. We are being somewhat forced to start using pre-fabricated pieces, outside code libraries, and outside products to create a mash-up of sorts. As a side note, even through we like scratch built features and options, one of the adilas goals is to become an API socket option (aka a mash-up option) for other companies. We want to build out the tools and then let others (individuals, companies, and even outside 3rd parties) consume the adilas API sockets as needed.

- One of our concerns is, we spend hours and hours of our time on meetings and talking about possibilities. Technically, this is just R&D (research and development/design) stuff but it takes us away from other tasks (opportunity costs). We love it and we still need it. It comes down to a balance and a plan.

- Talking about business and the different balances needed to keep things going and in check. Steve and I talked about an emerging 3-way balance between clients, systems, and education. Each of those main topics branch into sub topics. For example: Clients may branch into sales, funding, shear numbers (how many clients), and market demands. The system side of things seems to branch into user interface, functionality, features, settings, permissions, development, and tech. The education side seems to open into documentation, ease of use, instructions, guard rails (don't let people fall off), just in time learning, and the need for good reps and consultants and other trained individuals. Very interesting. Shannon and I had a similar conversation the other day. See this link for more information: https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4506

Working with Josh on some code review for the discount engine stuff. We spent some time reviewing code and making small fixes to the database updates. Josh gave me a demo and we got some things prepped. We broke for lunch and re-hit things around 1:15 pm.

Back on with Josh. We worked on help files, final code merge, and pushing new permissions and help files to all servers. Josh went in and did some live testing.

Helping Dustin with a code merge and light clean-up. We had to do some manual cross checking, but got the files merged in and uploaded to the servers. Spent the rest of the time doing clean-up, recording notes, and writing an email to Wayne requesting that we get a plan in place for the transition over to the AWS (amazon) stuff.

It must be Monday... We started out on the morning meeting and only Steve and I were on at first. We chatted about the transition over to the AWS (amazon) stuff. We have a number of questions and aren't really sure which way to turn. Steve needs to provide some of our clients with an answer, can we service them or not, and we need to know how long it will take to get the AWS stuff fully up and running. Lots of unknowns, but some great potential. Part of us wants to return to what we know (older stable ground) and the other part of us wants to keep pushing forward (new and uncharted but promising ground). It creates an emotional battle of sorts.

We switched gears and Steve had some questions about a project where he is tying in balance sheet numbers to vendors. As part of his project, he was trying to come up with a switch that we could flip to help us know if a vendor was an inventory (parts or items) vendor or just a normal vendor. As we talked about it, we decided to take it out to an app type level (the 12 main system players). We talked about that and Steve liked that idea. I got him some code to help him get started. It is amazing how much, as we keep going, that the system keeps organizing itself into main player groups and what kind of relationships are needed per system or main player group. Very interesting. Almost like it likes to be organized into groups and related functions. We sure have learned a lot along the way.

Alan joined the meeting and we were talking about some of his projects. He is still working on automating some of the reoccurring invoice stuff. We also talked about having Bryan work on the dynamic field names and settings per main player group. That is pretty deep and we may keep it tabled for now. Also, as we were talking about it, we were talking about how an object oriented programming approach may be a better solution for some of these new settings and defaults. Currently, we build and break, build and break (speaking about pulling and accessing settings). It may be nice to keep and hold some of the persistent or permanent settings and features. An object oriented model may be better equipped for that type of transaction. Currently, we look things up just in time. In the future, we may need to catch and hold those settings and maintain them in the user's session (stored in memory) options.

Eric popped in and we did some check in and follow-up with his code review on the sub special account tracking project. This project is a sub of the balance sheet and deals with special accounts (mini bank account type objects) like customer loyalty points, gift cards, in-store credit, etc. That project is promised by next Monday. I will be trying to focus on the code sign-off this week.

After that, Eric and Steve and I started talking about some of the new look and feel, CSS, and user interface stuff that Eric is wanting to help with. Both Steve and Eric were talking about a virtual "Adilas Cafe" or a global landing spot for the adilas users. This all goes back to separating the users from the main application code. There will still be a tie-in, but we are seeing a bigger need to keep users on the outside as a single entity and then allow them to go in and work or be a part of a corporation. We have many users that  have and/or will need access to multiple corporations, and even be able to bridge across physical servers. Currently, our model is based on users per server and then tied to corporations based on active permissions to those corporations. We are seeing a need to break that down even further and have a master or global user id (virtual pool of users) and then allow them to be bridged to different corporations on a more global scale vs just per server (physical box) vs the possibilities of dynamic cloud networks.

As we got deeper into the conversation about the potential of the Adilas café type model, we were talking about doing mock-ups, flow charts, etc. Eric had some questions about authentication servers and how that would all roll into the mix. We told him that he would need to get with Wayne to get more details. As we talked, we decided that Eric and Wayne should work together in a mini team type environment. As we explored the options, some of Steve and I's concerns (listed at the top of this entry) started to go away. We ended up somewhat asking Eric to be a project manager type role for this transition project between Newtek and AWS. That little tweak in the plan and how the developers were paired up, made a ton of difference and some of the anxiety started to go away.

We need to crate a list of specs for Wayne and what we want the application to do. Plan and play as if for years. We also talked about in-house coordination and communication. That is a huge key and helps all parties involved. Steve was talking about skating to where the puck (pretend we are playing hockey) is going to be. He and Eric were talking about the existing login pages and the corporation chooser page as being the beginning of the adilas café (landing spot or centralized common ground area). Good discussion.

We would really like to keep pushing the ball forward and making each system its own entity. This means having a centralized database controlling users and access to different corporations and/or entities and then having the individual entities having their own database or system for just their stuff. Currently, there are a number of tables that are shared between parties. For speed and efficiency, we really need to split things up more. This may also affect how we are able to bill for storage and processing vs a set monthly system fee. Anyways, as the conversation progresses, Steve and Eric were talking about using the choose corporation page as the starting common spot or commons area. Steve was also saying that he would like the users to be able to go to work (assigned or authorized corporations) as well as go play (demo sites, play grounds, or play sites). Basically, anybody could have an adilas account, and then they could either go into a real site (aka work) or a play site (aka play and testing). Fun ideas.

One of Eric's and Wayne's first item of business will be to do a virtual inventory check of where things are at on the project and what will still be needed and/or stands in the way. That will be awesome. It really was an mini answer to prayers that we decided to team up Eric and Wayne. It helped us let go and be willing to embrace some of the unknowns. As part of that, we are hoping that having the guys work together in mini teams helps us prioritize what really needs to be done and when. Sometimes, by yourself, it is hard to know what needs attention first, especially if it feels like everything is vying or trying to get the input, attention, and/or priority. Crazy stuff, I'm been there before and will be back again.

Steve and I talked about cycling through hardware and how that is just part of the line of work we are in. Later this year, we will need to buy some new laptops and upgrade some of our development environments.

One of the breakthroughs for today was the mini team concept. We have Steve and I, Steve and Dustin and Josh, Brandon and Alan, Wayne and Eric, Shari O. and Pat and Drea, etc. There are starting to be all kinds of little teams. That is awesome.

Shawn popped in and reported on some payroll updates and changes. We scheduled a time to meet again tomorrow. He is also willing to help me out with some of my projects and such. After that, I spent the rest of the session recording notes and trying to get caught up (as good as I could).

Emails and recording more notes. Added some additional notes (sub comments) to the element of time # 4506 dealing with a balanced approach and how to mix the different pieces. See this link for more info about number of clients, sales, system development, education, training, output, needs, byproducts, talent pool, services, and the adilas marketplace.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4506

Bryan and I spent some time looking around on the adilas community user group site. This is live but not yet made publically available. We were talking about flow, CSS, look and feel, and how to force certain system elements. We ended up comparing some pages and then trying to get the desired output. Bryan is going to wrap things up and leave some notes on where we jumped off. We'll have to pick it up again in a little while. That is no fun, to leave a project, but it part of life.

I told Bryan that the term adilas community and optional services had come up already multiple times today. We are trying to prep this piece so that when we are ready, we can pick it up and use it with minimal changes.

Paying bills and recording notes from a couple of days ago. I had some unrecorded post-it notes from back on 4/4/19. Filling in the gaps.

On the morning meeting with Steve and Dustin. Steve had some questions on a page he was working on. We looked at a query and made a couple of changes. We then chased down a small bug that ended up being a user error, not a bug. We pulled some data and Steve took some notes to let the client know. Towards the end of the meeting, both Steve and I helped Dustin with a small fix on his local environment.

Shawn joined the GoToMeeting session and we worked on payroll updates and changes. He was testing the new changes and had a question every once in a while for me. While he was doing that, I was updating an adilas sales flyer with new contact information. The original flyer was dated back in 2014. Lots of water under the bridge since then. Kinda fun.

Code review for Shawn. Pushed a couple of payroll updates to all servers.

See notes from last week - https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4506

Shannon and I reread the notes from last week (including the sub comments or new comments since our last meeting). We went over those ideas and concepts and went in and setup some new master time templates. The new time templates were for the adilas user guide in the adilas university site. No real content was added, but we prepped a bunch and Shannon will try to go in and do some uploading and filling in content before our next meeting. Progress is being made.

Bryan has a project that needs some advanced computing and data manipulation. The client is on the data 2 server. They want a report generated every night and saved as a PDF (mini report of sorts). They then want that PDF auto sent as an email attachment to a specific person. By themselves, all of those things are possible. Our model gets a little bit more complicated due to the different servers. The server that sends the email doesn't have access to the data that is needed. The server that does have the data has to communicate through an API socket connection to the email server. Bryan and I went over some options and did some light drawings of what we could do.

The easiest way would be to send an auto email with a link that has a date range or specific day coded into the link. Then the user would get the report as soon as they click the link. Basically, generate the report on demand or just in time. If we start physically creating files, you deal with storage, eventual clean-up, and then transferring files from place to place in order to email or send as an attachment. We talked about converting the physical file into a base64 (code subset protocol) and then sending to the other server. We could also use FTP (file transfer protocol) to send the file to the other server. It may be a series of smaller requests to prep and make sure that other steps have been performed and are ready to go. Anyways, it gets kinda complicated due to how the email server is setup as compared to all of the individual data servers.

Bryan had a good attitude and enjoys learning some of the deeper and/or more complicated options and workarounds.

Dustin and I worked on his cultivation phases and getting some of the queries and filters a little bit tighter. He already had them in place, we just helped get things a little bit tighter. After doing the phases and phase counters, we switched and worked on the location counters section. All of these pieces are in a section called cultivation that he and Steve have been working on for months and months. It is really looking good.

Eric joined the meeting and had a couple of questions. I really appreciate that fact that he tries to look global or general adilas before just making a one-off custom report. His questions were dealing with showing discounts, discount ranges, min/max discounts, etc. He also had another request for some sub inventory and RFID tag reports. We talked about options and also talked about custom dashboards that have prebuilt buttons that allow our users to get to the reports that they need and want within a single click (precode the buttons and/or page links to contain the filters and search criteria.)

Working with Shawn and getting him setup on a new branch. Shawn and I also talked about two new projects that are coming up. He will be doing Oklahoma taxes and withholdings and the two of us will be working on the invoice due date project (old one that Russell and I were working on middle of last year). We need to pick that project back up. Called and talked with Calvin.

We have had numerous requests for better search options for discounts. It really needs to be on the advanced invoice line item search, the super invoice line items search, and other sales and invoice searches. Steve did make a discount search page but it somewhat limited and needs to be fleshed out a bit. See the top_secret/custom/sales_salesperson_specific_discounts.cfm for more details. Another thing that we really want to do is build out the advanced invoice line items search (and super line item search) to allow for checkboxes (build your own report). That way we could show taxes, categories, prices, costs, locations, discounts, etc.

Reviewing code on Eric's sub special accounts (sub of the balance sheet for customer loyalty points, gift cards, and other special accounts). Also working with Shawn to get him started on the invoice due date project. Trying to circle back around and get that project going again.

Facing some legacy issues... validation length on certain characters and strings. Also a conversation between old legacy code (adilas classic) vs the new fancy code (adilas snow owl) and updated features. We talked about even having some different pages and allow the users to choose between generation one, two, three, etc. (page versions and compatibility levels). We may end up using the corp chooser pages (special links and pages per corp) and point people to different files or different versions. On the code side, it becomes harder and harder to maintain and update multiple pages that provide different levels of functionality.

Steve and Dustin were working on some changes and restoring and creating some page variations (legacy code issues discussed above). Meanwhile, I was working on lowering the validation limit on PO and invoice line items. The old code required the line item description to be at least 3 characters in length. However, an item number or part number only had to be a minimum of 1 character. We were having problems with users creating a 1 character item and then not putting a 3 character description. The normal pages stopped any of that from happening, but we have some code that auto builds certain things and fills in default values (makes it quicker). The new auto build code didn't have the same validation. In order to help standardize, we actually lowered the required characters on the line description to allow both sets of code to work without any issues. Constantly refining piece by piece.

Jumping back on the invoice due date project with Shawn. It is amazing how much time it takes to transition back into an older project. Shawn is going to be helping and working on merging in current master files to the old project branch files, to help get things up to date.

Working on the special account transaction homepage. This is part of Eric's special account tracking project (sub of the balance sheet and deals with customer loyalty points, gift cards, and in-store credit type stuff). Made some headway on the special account transaction search and homepage (what are the individual recorded details).

Also helped Shawn with getting back into the invoice due date project.

Paying bills and working on code review for Eric's special account tracking project. Also did a verbage update on some default customer field settings. Altered the master verbage for the default tax category for customers. This field got some new functionality a few months back, but we never updated the main settings. It, meaning the new functionality will be highlighted in a news and update post dealing with cascading the default customer tax category clear through the shopping cart. The old setting was just a reminder of sorts (there but not fully working). Now it has additional functionality and actually tries to cascade the default tax category clear through the cart. This is huge for customers/clients that are say resale, wholesale, or government (non taxed). The new setting helps to make sure that the cart does not try to apply tax to non taxed clients. Anyways, a small update.

Alan came on to the morning meeting and gave Steve and I a small demo of the new merchant customer homepage. This is for reoccurring credit card payments and tracking some customer information that are scheduled as a reoccurring and/or subscription type payments or reoccurring invoices.

Steve and Dustin were working on some Metrc changes and fixes. I was working on a list of topics and questions for Wayne and Eric dealing with the transition between Newtek and AWS (amazon web services) stuff. See attached for a starting list for our conversation.

Wayne actually joined the meeting and we went for over an hour and half going over some of the topics dealing with the transition between Newtek and AWS. See the other attachment for a current working document with tons more details.

Emails and working on code review.

Working with Bryan on options to search sub inventory and filter ecommerce searches based off of sub inventory attributes and sub inventory search filters. We went over some code, started making some changes, and ran into a number of questions. We ended up talking about some existing options (selling options in the ecommerce settings - show and sell parents, show parents sell subs, or show and sell subs). We also talked about ways of doing some custom searches or reverse searches (starting with the subs and then going into matching parents). We went in circles a few times but hopefully came away with at least some ideas and better questions to ask the client.

Part way through our meeting, I got a call from an outside consultant that does some integration between Sage and QuickBooks. They are trying to help an adilas client and trying to get a good picture of how the client uses adilas on the inventory tracking side (PO's, sub inventory, sales orders, fulfilling orders, and shipping).

Recording notes and cleaning up for the day.

Dustin and I met up on the morning meeting. We touched base and setup a meeting for Thursday afternoon to work on his cultivation stuff. He is doing great and has been a good team player.

I started working on some code review. Didn't get very far. Both Alan and Wayne popped in.

We went through a whole new section where Wayne was explaining and showing us what was going on out in the AWS land. Wayne was the presenter and was showing lots of things. Alan was asking questions and I was taking notes. See attached for the latest notes.

Steve and Eric popped in later on to listen and chime in. Wayne was showing some of the Docker image stuff. He was also helping Steve look at a server and find out what was going on. Good stuff.

Need - drop shipping and special tax tables for that drop shipping

We also had a client express that they wanted to be integrated with a number of other outside ecommerce type systems. Steve was using the analogy of having multiple fishing poles in the water (this ecomm package, this other ecomm package, and this other one - get more clients from different sources and areas).

At the end of the session, Eric and I went over the progress on the code sign-off project for special accounts and special account tracking (customer loyalty points, gift cards, etc.). Still working on things, but making progress.

4 - Meet the players

-A lot of these keys pieces are based off of the map.... We want people to read this brief overview, basically concepts and what someone would need/want to use it for and have them feel like, "Oh that makes sense. I get it." That is what we want!

4.1 - General Overview

-Is it easier to say what we can't do, b/c we can do so much

-A whole package

-Interconnected,

-Buffet - pick & choose, can play at any level you want - imagine a buffet with 100 items, say you want 2, 3 or 50, you get to pick and choose what you want, it's great!

-Customizable

-All data is live & searchable, serviceable, sustainable, .... etc. Joe’s thing

-Tanya's graphic: choose your flavor, pick your tools, skin your engine, ....world

4.1 - General Overview

Understanding the Basics:

Welcome to adilas! Adilas is a buffet of user-oriented options, and you can play in a style that suits your needs and wants. It’s a whole, interconnected package that allows you to streamline your business functions through one customizable program. From vendors and customers to expense/receipts and payroll, adilas will track your data in a way that allows you to follow the entire process without having to change from program to program.

At adilas, you choose your flavor, pick your tools, skin your engine, and build your world. Adilas is a powerful data engine and a dynamic and adaptable business model.  In the following sections you will learn more about the pieces and how they interact with one another.

Getting Started:

This User Guide is a great resource as you start using adilas.  Every subsection here in “Meet The Players” begins with “Understanding the Basics” and “Getting Started”.  Each subject also includes suggestions for some basic and admin permissions or settings for that section of adilas.  There are also multiple links to help files for pages associated with each subject.   

Make sure to get in and start using the adilas system.   This is really how you will gain the confidence and experience you want.  Use the play sites, utilize this user guide, check out help files, click on links, explore, see how it all fits together and you will begin navigating the adilas system far more quickly.  We hope this User Guide will be a helpful tool as you start to use adilas.biz!

Suggested Permissions and Settings:

Settings and permissions are foundational pieces of adilas.  Settings help create the specialized work flow and the look and feel of your adilas.  Permissions dictate who is allowed to view, or work, in every area of the system.

This section of the user guide will give you a basic idea of some of the associated permissions or potential settings that could be used.  The general format for the permissions section is to give the section name where the permission is found, the permission name, and a brief description.  If applicable, the settings section gives you the setting’s name and a brief description.  This is not all inclusive, but meant to help you get started understanding and using permissions and settings in adilas.  

Related Pages & Help File Links:

This section will contain brief descriptions of related pages in adilas and links to the help file associated with that page.

Understanding the Basics: This help file explains some of the basic theories and concepts that adilas uses.

https://data0.adilas.biz/top_secret/steps_basics.cfm

Adilas.biz System Overview: With adilas – you get it all!  This map shows aspects of adilas grouped together to show business functions.  These subgroupings are representative of things you may find in varied business system packages.  But the most powerful part of adilas is, that here, you get it all together in one interworking system!

https://data0.adilas.biz/adilas_system_overview_map.pdf

Additional Content:

-Have some of the adilas graphics – like the GPS World Building Graphic

https://data0.adilas.biz/top_secret/images/help/adilas_gps_layout_big.jpg

-And the Adilas.biz System Overview: Map – With adilas, you get it all! (This link is listed above, but we could potentially even show the graphic here.)

https://data0.adilas.biz/adilas_system_overview_map.pdf

4.2 - Admin

-Dealing with some of your high end user features, accounting, histories, HR stuff

-Permissionable to whatever level you would like - user with extra permissions (additional responsibilities)

4.2 - Admin

Understanding the Basics:

Admin refers to the management or administration of your business or organization.  Adilas is built on a foundation of permissions and settings.  Settings help create the specialized work flow of your adilas, as well as the look and feel.   Permissions allow administrators the ability to grant or limit access for other users throughout the company’s adilas application.  In other words administrators assign, by permissions, how other users view and use the system.

Admin is used throughout the system to denote the higher-end user features which are accessible to those with the higher administrative permissions.  These are features that allow more power and accessibility to work in the system and with the data.  The flexibility of adilas is that you can give each individual the permissions they need to access the relevant pages and information necessary to do their job.  

Getting Started:

Admin functionality is based on assigned permissions.  To setup new users in the system or to edit information/permissions for any user, go to the Payee Permission Home page.  Either search and add for a new user, or click on the name of an existing user to edit info or permissions.  This takes you to the Add/Edit Employee/User Permissions page, which is an incredibly powerful page.  This is where you setup how that user is able to work in the adilas system.  For more information on permissions and settings please check out these sections of the user guide.

Reach the Payee Permission Homepage from the Classic Homepage under System Management – Add/Edit Payees and Permissions; My Favorites Homepage under Other Homepages – Payees & Permissions; or on the Interactive Map under the users button.

Suggested Permissions and Settings:

Admin: The ultimate administrator in a corporation has 2 key permissions that allow them to work with all other user’s permissions and the corporation-wide settings.  These are ultra-admin permissions and should not be given out to anyone but the highest administrators.  These permissions are found under the System Management section and are called “Add/Edit Payees & Permissions” and “Manage Corp Info & Permissions”.  These two permissions allow you to add users to the system, assign permissions for any user, and manage all of the corp-wide settings.  

We recommend that administrators check out both the settings and permissions pages within adilas.  Both are important to the management of your adilas.  There is an incredible amount of customization available right from the start. If you have any questions about permissions or settings, check out that section of the user guide, search through the permissions or settings - they all have associated descriptions, or contact your rep or adilas support to find your answers.

Related Pages & Help File Links:

Add/Edit Employee/User Permissions: This is the critical page for setting up users in adilas.  Come here to assign or edit permissions for users and to read descriptions for the permissions.  

https://data0.adilas.biz/top_secret/help.cfm?id=106&pwd=permissions

Manage Corporation Info and Permissions: This page in adilas is your hub for accessing your corporation management links.

https://data0.adilas.biz/top_secret/help.cfm?id=216&pwd=corp_admin

Corporation Wide Settings and Defaults: This is the page in adilas where you adjust all of your corp-wide settings.  The help file, whose link is provided below, contains additional details for all the descriptions associated with each setting.

https://data0.adilas.biz/top_secret/help.cfm?id=336&pwd=settings

Login, Passwords, & Permissions:  This is the section of the User Guide that covers logins, passwords, and permissions.  There is some great information here especially regarding the concepts and theory behind these adilas functions.

https://data0.adilas.biz/top_secret/steps_logins.cfm

Additional Content:

 -It would be great to come up with a useful graphical illustration to really illustrate permissions and settings… which should obviously go with permissions and settings but is also applicable here.

4.3 - API Sockets & Communications (application programming interface - send & receive data remotely)

-This allows computers to talk to computer - adilas accounts talking to other adilas accounts, or adilas accounts talking to other outside parties, or vice versa

-API is almost like computer to computer telepathy, you can’t see anything of the data per say - just the communications

-We use standard formats like JSON or XML to pass the data, standard way of communicating

-You can have data in a database, crunch it down, send it across the wire, and it can be reinflated on the other side - stuff that is automated on demand or request or create your own custom application that feeds or draws from the main application - you can create secondary apps that can play that way

4.4 - A/P - Accounts Payable (vendor waiting room)

-Time element (all time is stamped & tracked) - aging

-Fed by PO actions, etc. or inputs (partial paid or still due)

-Catch all for monies still owed

4.4 - Accounts Payable (Vendor waiting room)

Understanding the Basics:

Accounts payable are monies owed by your company for products or services you have received or will receive.  This page is a virtual vendor waiting room called the Payables Homepage and is a great place to start for seeing money still owed by your company.  It shows you amounts paid and/or owed to specific vendors and payees.

The Payables Homepage is fed by PO’s (Purchase Orders), unpaid or partially paid expense/receipts called splits (payments on account), reimbursements (REI’s) – expenses checked for a reimbursement, and serialized stock/units.  This page is full of active links so that you can directly access those objects to manage payment efficiently.  

Getting Started:

We recommend starting at the Payables Homepage for managing the process of paying off any PO’s, splits, REI’s or serialized inventories.  Use the active links in their respective columns to begin the expense/receipt process for these items.  This will eventually create a new expense/receipt where you will pay off, or partially pay for, the associated items you linked from.  To filter the data for this page, click the show/hide search criteria button and adjust your settings to the report type and parameters you want.

Get to the Payables Homepage from the Classic Homepage under System Liabilities – Payables Homepage; My Favorites Homepage under Expense/Receipts – Payables Homepage; or the Interactive Map Homepage under the a/p – vendor waiting room button.

Suggested Permissions and Settings:

Permissions:

Basic Use:

System Liabilities Section: “Basic Expenses/Receipts” – this allows a user to add/edit, view, search, and print basic expense/receipts.  Maintains a limited view of any private expense/receipts.  

System Liabilities Section: “Basic Payables” – this allows the user to view but not edit data on the Payables Homepage.   

These 2 permissions work well together for users who are creating expense/receipts for limited items such as PO’s.

Admin Use:

System Liabilities Section: “Admin Payables” – as the admin level for payables this allows the user to create split payment receipts, reimbursements, and contains admin feature options for PO’s and stock/units.   This permission should be given to the person in charge of making payments for your corporation or your accounts payable person.

Related Pages & Help File Links:

Payables Homepage: Come here to see the vendors/payees your company owes money to and manage payment for these expenses.   

https://data0.adilas.biz/top_secret/help.cfm?id=239&pwd=payables

Start PO Payment Receipt: This is the page that starts to build a new expense/receipt for PO’s by linking from the Payables Homepage.  This is the most efficient route for paying off PO’s because it automatically connects your expense/receipt information with the specific vendor and the PO’s that are being paid for.

https://data0.adilas.biz/top_secret/help.cfm?id=247&pwd=payment

Start Split Receipt (payments on account): This starts the expense/receipt building process for payments on account.  This occurs by linking from a split payment from the Payables Homepage.

https://data0.adilas.biz/top_secret/help.cfm?id=241&pwd=split

Start Reimbursement Receipt: This starts building an expense/receipt for reimbursements owed.  

https://data0.adilas.biz/top_secret/help.cfm?id=114&pwd=start

Additional Content:

 -Views or screen shots of the Payables Homepage

4.5 - A/R - Accounts Receivable (customer waiting room)

-Tied to A/P - one's outgoing, one's incoming - so very much like A/P but what people owe you

-Comes in through invoices & sometimes also through time.... charging people for time

-Monies received during the day but not deposited yet.... staging area, like your cash register, vault, bank bag, etc.

4.5 - Accounts Receivable (customer waiting room)

Understanding the Basics:

Accounts receivable are monies that people owe you.  This page is a virtual customer waiting room or cash register, called the Receivables Homepage, and is where you can go to see who still owes you money and invoices that have not been deposited yet.  

The Receivables Homepage is fed from invoices.  This page contains multiple links for efficiently managing and navigating your receivables.  These links allow you to view/search all your receivables, manage customer receivables, apply payments to customer accounts, view customer logs, histories, create statements, and more.

Getting Started:

From the Receivables Homepage the initial information displayed depends on the “Report Type” that has been selected.  Click the show/hide search criteria button to change your report type or filter data and set parameters you are interested in viewing.  Explore other active links to search customer accounts, apply payments or create a statement.

Get to the Receivables Homepage from the Classic Homepage under System Assets – Receivables Homepage; My Favorites Homepage under Deposits – Receivables Homepage; or the Interactive Map Homepage under the a/r – customer waiting room button.

Suggested Permissions and Settings:

Permissions:

Basic Use:

System Assets Section: “Basic Receivables” – this allows a user to look up accounts receivable, this is a view only permission and does not allow any editing of data.

Admin Use:

System Assets Section: “Admin Receivables” – this allows a user to modify the deposit status on receivables.

For admin users, and even for a basic user, to effectively use the Receivables section, other permissions would be helpful such as basic customer permissions, statement permissions, and other related actions.

Related Pages & Help File Links:

Receivables Homepage:  Your hub for managing accounts receivable information.

https://data0.adilas.biz/top_secret/secure/receivable_home.cfm

Customer Invoice Report:  This is a special invoice/payment search page for individual customers and is a pre-filtered search when you link from their totals or what they owe on the receivables homepage.

https://data0.adilas.biz/top_secret/help.cfm?id=263&pwd=invoice

Apply Payments to Invoices: This page helps you apply payments to multiple invoices for a customer from a single page.

https://data0.adilas.biz/top_secret/help.cfm?id=262&pwd=payments

Invoice Homepage: This is where all of your invoice sales show up whether they are paid, unpaid or partially paid.

https://data0.adilas.biz/top_secret/secure/invoice_home.cfm

Additional Content:

 -Screen shot of the Receivables Homepage, possibly even some of its differing views.

4.6 - Attributes (parent & child inventory flags and tags)

-If you need more ways to search things or ways to flag and tag things you need attriubtes.

-There is no possible way that we can know all of the data points that you want to filter, search by, etc. So this allows you to sort of build your own database to flag and tag your data.

-Another important thing is that a lot of this is external as to how you want to present these things to your clients. How can they filter, show it, sort it, etc. To your clients.

-Technical side - attributes are tied to a data type - a number, a string, a toggle switch, a list, a date/time

-Unlimited - you can have as many of these as you want. Set up your own database, collect your data points, then filter & search by them.

-These are usually tied to inventory or item categories. 

4.7 - Balance Sheet

-A snapshot in time.... where are things at right now

-It's buddy is the P&L (P&L - is over time), the P&L (the income statement) feeds into the balance sheet through net profit, which ends up being an equity item

-Roll call, ask the items where are you, where have you been, where are things at

-Tells you your story (kind of a day by day specific)

-3 main pieces: assets (have), liabilities (owe), & equity (gained over time)

-System maintained pieces (about 75% automated) & user-maintained pieces (specialized things you need to track)

4.7 Balance Sheet

Drafting…

Understanding the Basics:

The balance sheet is like a snapshot in time, a summary of where things stand at a particular point in time. The Balance Sheet has 3 main pieces: assets (what you have), liabilities (what you owe), and equity(what is gained over time).

It is fed by the P&L (income statement) page, through net profit.

Capital – financial assets, or the financial value of assets owned – wealth in the form of money or assets  contributed for a specific purpose like to start a company or to invest

1. A financial statement that summarizes a company's assets, liabilities and shareholders' equity at a specific point in time. These three balance sheet segments ...

2. 

3. a statement of the assets, liabilities, and capital of a business or other organization at a particular point in time, detailing the balance of income and expenditure over the preceding period.

Equity: The term's meaning depends very much on the context. In finance, in general, you can think of equity as ownership in any asset after all debts associated with that asset are paid off. For example, a car or house with no outstanding debt is considered the owner's equity because he or she can readily sell the item for cash. Stocks are equity because they represent ownership in a company.

Assets, liabilities and equity

Concept-

Use- The Balance Sheet is used as a roll call, a report on where each item is and where it has been. It tells the overall story of what has been happening, broken down into day by day specifics. It is 75% automated, but requires several user-maintained pieces (specialized things you need to track)

Getting Started:

Suggested Permission and Settings:

Permissions:

Basic Use:

Section: Permission

Admin Use:

Related Pages & Help File Links:

Title of Page:

Link: https://data0.adilas.biz/top_secret/help.cfm?id=318&pwd=log

Additional Content:

 -Graphics

-Screen Shots

-Etc.

4.8 - Banks

-In order to create deposits or expenses you need to have a bank setup.... they are technically outside of the adilas system

-So external, you can have as many as you want, the expenses & deposits require this... but one step farther.... your deposits often come from invoices, expenses from inventories and expenses for processes

4.8 - Banks

Understanding the Basics:

The banks section of adilas is used to represent your actual banking entities, which are external to adilas.  Setting up a bank is required to work with the Deposits and Expense/Receipts sections of adilas.  You may set up as many banks as you need.

These tools allow you to track everything coming in and going out of your bank.  As deposits typically come from invoices, and expense/receipts typically come from inventories and other businesses expenses, you can maintain accurate running bank balances with great underlying details.  This allows you to reconcile bank statements and manage your financial records with a great depth of underlying data.  

Getting Started:

To add a new bank, go to the Bank Homepage.  There is a link in the center to add a new bank.  The Bank Homepage is full of active links to help reconcile your bank, view your register, see bank balances, create reports or link to other pages that feed, or are related to, your running bank balance.

Get to the Bank Homepage from the Classic Homepage under System Maintenance – Bank Homepage; My Favorites Homepage under Other Homepages – Bank Homepage; or the Interactive Map under the bank(s) button (this actually takes you directly to the Running Bank Balances page but there is a link to the actual Bank Homepage).

Suggested Permission and Settings:

Permissions:

Basic Use: When you begin dealing with banks and many of the other financial tools, these are typically considered admin use areas.  

Admin Use:

System Reports Section: “Running Bank Balance(s)” – this allows the user to search all running bank balances.  This is view only but will show all banks and all totals.  This is also how you get to the bank deposit and check registers and link to outstanding deposits and expense/receipts.

System Maintenance: “Add/Edit Bank” – allows you to add or edit banks in your corporation.  Shows running bank balances for all banks in your corporation.  Banks can be configured to use the adilas.biz check write system.  

Related Pages & Help File Links:

Bank Homepage:  Add a new bank here and link to associated banking reports and functions.  https://data0.adilas.biz/top_secret/help.cfm?id=18&pwd=banks

Running Bank Balances: This page is used to show running bank balances and totals.  This page is highly used when dealing with banks.

https://data0.adilas.biz/top_secret/help.cfm?id=244&pwd=bank

Reconcile Bank Report: All verified deposits and expense/receipts will show up here to help you reconcile with your bank statements.

https://data0.adilas.biz/top_secret/help.cfm?id=110&pwd=reconcile

Bank Deposit/Check Register: This is a special report to help show banking activity.

https://data0.adilas.biz/top_secret/help.cfm?id=339&pwd=register

Additional Content:

 -Bank page screen shots, different report formats, etc.

4.9 - Barcodes & QR Codes

-Be default this is usually an inventorty type tool but technically can be used anywhere across the system for anything.

-Have many internal barcode creators/makers, can scan, we have direct links.

-Really it is just a way of getting somewhere/something quickly that you don’t have to type it out.

-We allow interactions through a HID (human interface device) - I.e. a scanner, which can speed up the process if we know what you are looking for.

-All of our barcodes allow for alphas, numerics, special characters, you can create your own, you can use existing ones, or we can autogenerate them for you.

-Bunch of cool help files on barcodes. We have not seen the end of what is possible with QR & barcodes.

-Think of the possibilities to get invoice, customer records, medications, reservations, rentals, etc., etc.

4.10 - Black Box Page Technology (custom code options)

-What happens here is we have to give you a starting stop which is what we call our classic interface.  If you need something changed, added, altered, edited, etc. You will need somehting changed - enter the black box - custom code.

-This is done per corporation, per page, or it can be done in bulk and used more as a general theme change or a multi-use custom code. This could be a corporation specific need or an industry specific change.

-Important to know that if you go custom it is a two-edged sword. You get what you want but it could potentially cut you off from other standard features that keep being developed.

-On a technical note, we actually have up to 8 different spots per page that we can interject custom code. Such as logic, headers, footers, bodies, full take-over, etc.  

-Usually this is ran as a custom job between you and the developer. You say what you need and the developer tries to accomplish that for you. These are all outside projects from the main adilas core.

-Quote(ish) from Steve, “Choose your solution, then invest in that solution.”

-Available internally as well as in eCommerce. Anything that you see may be changed including shopping carts, dashboards, interfaces, etc.

4.11 - Check Requests (sub type of the normal expense/receipts)

-Requires an additional approval process

-Vendor & items known, but a delayed payment and the need for approval on that payment aspect

-Main, line items, & then this one has a special approval process for payments, so it is short paid or gets sent back and reworked and has to pass through the approval process again.... it is trying to become an expense/receipt

4.11 - Check Requests

Understanding the Basics:

A check request is a special expense/receipt that does not receive any payment until it is approved.  The vendors and the items are known but the payment is delayed until it obtains the required approval.  This feature is not generally recommended unless you are in a multi-location type environment where all of the checks are authorized by a central office.   

Once a check request is submitted an administrator will have to approve the check request.  When it is approved, the user will then be able to print the check (if using the adilas.biz check write system).  If the check request is declined it can go back to be reworked and then resubmitted for approval.

Getting Started:

Because creating a check request is creating an expense/receipt that’s waiting for payment approval, we recommend checking out the expense/receipt section as well.  To create a new check request you could begin by going to the Check Request Homepage or to the Expense/Receipt Homepage.  When the permissions are turned on there are “create new check request” buttons on both pages.

Get to the Check Request Homepage from the Classic Homepage under System Time & Requests – Check Request Homepage; My Favorites Homepage under Checks – Check Request Home or New Check Request; or the Interactive Map Homepage under the expense/receipts button.

Permissions Needed/Suggested:

Permissions:

Basic Use:

System Time & Requests Section: “Basic Check Requests” – this is a silver permission, which may be limiting and is not recommended unless you are dealing with a multi-step approval process for Expense/Receipts.  This allows a user to submit a request for approval and once approved by an admin the user can print out the check.  The user also needs the “Basic Expense/Receipts” permission in the System Liabilities section to fully be able to use this permission.

Admin Use:

System Time & Requests Section: “Admin Check Request” – If you are using the check request feature, an administrator will need to have this permission so that they may approve or decline check requests.

Related Pages & Help File Links:

Check Request Homepage: Begin creating your check request form this Homepage or the Expense/Receipt Homepage if you have the check request permissions.

https://data0.adilas.biz/top_secret/help.cfm?id=24&pwd=check

Start New Check Request – Search Page: This is actually the Vendor/Payee Homepage which allows you to search payees to create expense/receipts or in this case check requests.  

https://data0.adilas.biz/top_secret/help.cfm?id=94&pwd=receipt

Add/Edit Check Request: This is where you add the main information for you check request.  In subsequent pages you will add the line items and other information.  Add as much information as possible to aid the approval process.

https://data0.adilas.biz/top_secret/help.cfm?id=230&pwd=check

Additional Content:

 -Graphics

 -Screen shots

 -Etc.

4.12 - Check Writing

-This is not required but is an option. We can generate computer, printer based checks.

-We allow for you to setup each bank with different kind of checks - check on the top, bottom, center, multi, or handwritten.

-If you choose one of the computer setups, we have a whole setup widget that helps you customize exactly where all of the key fields print. This is specific per bank so you can have multiple different checks and their specs set up.

-The checkwriting system has potential flags and ties. You can capture all of those histories and major auditing trail, who printed it, touched it, etc.

-As far as the filing system, it holds all of the important information on the check stubs, the E/R number, the payee, the amount, the notes, the memo, external reference numbers, etc. Makes filing super easy.

-This is very handy if you are paying bills, inventory, payroll, etc. It fulfills and ties together the whole expense circle nicely.

4.13 - Chooser (custom interface chooser)

-Similar to how a painter might have lots and lots of paints and options, but they select the best tools and options for a specific job. What the chooser helps with is allowing you to preset your home page to the set of tools that will best suit the tasks you most commonly do and need to access.

-The chooser allows you to get to a number of preset pages that may be homepages or high traffic areas. The goal was to create default landing pages that work for you instead of what we had originally created.

-As of now there are 7 global homepages or different views including classic homepage, button favorites, interactive map, core layout, and three flash interfaces. You can set all of these as your default homepage.  

-We also have another 30+ pages available in the chooser that you can also set as your home page default.

-There are also ways through your corp-wide settings where custom pages can be designed and developed and made into available pages for your corporation to have as default options. These can be custom homepages, custom reports, custom dashboards, industry specific pages, etc.  

4.14 - Corporations (worlds)

-At the world level, what is your world, what is your business... individual business entities - the giant umbrella that all of the groups fit under

-What are your flavors, what do you do, what do you need?

-You can technically have multiple corporations and switch between them... so a user can be bigger than individual worlds

-Can custom name your corporation, LLC., INC., entity,.... name your world

4.14 - Corporations

Understanding the Basics:

Your Corporation is essentially your world.  What you do in your industry, your look and feel, your terminology and what tools you use to accomplish your work.  All of these are specific to your organization and many are customizable in adilas to reflect your organization in the creation of your adilas world.  

You can have multiple locations and for some, potentially multiple corporations.  A user is technically bigger than a corporation, because one user can have access to multiple corporations.  Since users are assigned permissions per corporation they can flip between corporations and do the work they have been permissioned to do in that corporation.  Everything you do in adilas is tracked and takes place under the umbrella of your corporation or within that world.

Getting Started:

Setting up a corporation is one of the highest administrative functions.  This is the person who has the power to change corporation-wide settings and defaults that will cascade throughout your entire adilas world.  The Manage Corporation Info and Permissions page is where you can access all necessary links for managing corporation settings.  One especially important link on this page is the “[edit corp-wide settings and defaults]”.  This link takes you to the Corporation-Wide Settings and Defaults page with over 70 different settings to help customize your adilas world.

Get to the Manage Corporation Info and Permission page from the Classic Homepage under System Management – Manage Corp Info & Permissions; My Favorites Homepage under Other Homepages – Corp Home; or the Interactive Map Homepage under the settings button.

Suggested Permission and Settings:

Permissions:

Setting up corporations is considered an administrative function and requires high admin permissions.

Admin Use:

System Management Section: “Manage Corp Info & Permissions” – this is one of the highest admin permissions and should only be given to your ultimate administrators.  This permission allows the user to adjust any corporation-wide settings.

System Management Section: “Add Edit Payees & Permissions” – this is another one of the highest admin permissions.  This permission allows you to add/edit and assign permissions to yourself and any other user.  

Settings:

As mentioned previously, setting your corporation defaults and flow is where you use the settings section of adilas more than anywhere else. There are over 70 different settings.  Have fun checking out the different options to see what you can do with your adilas world!

Related Pages & Help File Links:

Manage Corporation Info and Permissions: This page is your hub for accessing your corporation management links.

https://data0.adilas.biz/top_secret/help.cfm?id=216&pwd=corp_admin

Corporation-Wide Settings and Defaults: This is where you setup or adjust your corporation-wide settings or your adilas world.  Come here to setup terminology, work flow and special options to best reflect your corporation.

https://data0.adilas.biz/top_secret/help.cfm?id=336&pwd=settings

Add/Edit Corporation: This is the page where your corporation information will originally be added.  This page also holds look and feel information such as you corporation logo and the color schemes for your adilas.  This information can be updated or edited by going to this page in adilas.  The link for this page is called “edit main corp info – look and feel”.

https://data0.adilas.biz/top_secret/help.cfm?id=16&pwd=corps

Additional Content:

-It might be fun here to show some world building graphics here.

-I think it would also be fun to have some graphics of some different corporations or “worlds”…. Give a little idea of the flavors already out there – there are so many and it is so exciting!

4.15 - Coupons & Sales Campaigns

-This gets into marketing and how you sell your products. We have some plans to build some engines that will allow you to start creating, automating, and monitoring these sales campaign activities. We are currently building in this area on tools that will allow you to manage and interact more with your marketing endeavors.

-You can currently track a sales campaign based on discounts that are given. You can also search and create reports based on that. It is not tied in directly to coupons at this point.  

-Eventually Adilas would like to be able to handle internal coupons directly through the system. It currently can track sales campaigns that are tied to discounts. There are some existing 3^rd party providers who do some sales campaigns and some coupons.

-Eventually this will also deal with marketing campaigns via text messaging and email blasting. 

4.16 - Customers/Clients

-People you want to track something one, whether contact info, who owes you what - that is a big one -, histories,

-You can custom call this one whatever you need/want for your industry: clients, patrons, patients, students,

-Customers can deal with eCommerce, invoices, A/R waiting room, .... refer to the map, all the stuff that is around it

-(Possible graphics showing how items connect with other things on the map)

ADD A CUSTOMER

• To quickly add a customer, locate the quick search in the top right or left corner on any page.
• Type in part of the customer's name, email, or phone number to see if they already exist in the database.
• If they already exist you have access to any of the customer links and options on the right side of the returned records for whatever next step you are needing to do (i.e. log, new cart, edit, history, etc.). 
• If your customer is not in the database, click the add new customer button on the top of the page.
• Fill out the required form information fields with an asterisk (*) and any other information you want to collect for your customer.
• Click the add customer button.
• You now have a new customer in your database to perform any further action.
1. 
   

4.16 - Customers

Understanding the Basics:

Customers are the people you service or sell to.  Think broader than a traditional customer here, this is customizable to your information needs and what you call your people: clients, patients, contacts, members, patrons, students, etc.  Whether your customers buy goods/services from you or you just need to track data, the customer section is a powerful tool for managing your customer relations and information.

Customers are one of the 12 Main Players in adilas and they connect with many other pieces in adilas.  A great deal of information can be held on a customer’s record, including unlimited customer log notes, additional contacts, ties to elements of time, how much they owe you and much more.  Customers are generally associated with invoices for selling products or services.  From there they tie into Accounts Receivable – what money you are bringing in and who still owes you.  Customers can interact through eCommerce, be quoted, receive statements, hold custom data through flex grid, and much more.  

Getting Started:

The Customer Homepage is a good place to start for adding or searching your customers. You are always prompted to first search, so as to not add a duplicate customer.  The Customer/Contact Log page is your central point for customer information.  This page holds all of their information, log notes, additional contacts, flex grid tie-ins, and many active links to quickly access any information you are interested in finding about your customer.  Start here to add/edit or view your customer’s information.  

One of the fastest ways to get to customer information is to use the Quick Search for “Customer” (the drop-down search at the top of every page in adilas).  Lots of information can be used to quickly search for a customer, like any part of their name, phone numbers, email and more.  When customer searches return, link directly their log, start a new shopping cart, apply payments, or a number of other options.  Check out the Quick Search help file below for more tips on using the Quick Search (available from any help page).

To change the corporation-wide naming of your “customers” see the settings section below.  Get to the Customer Homepage from the Classic Homepage under System Maintenance – Customer Homepage; My Favorites Homepage under Customer – Customer Home; or the Interactive Map Homepage under the customers button.  

Suggested Permissions and Settings:

Permissions:

Basic Use:

System Search Section: “Customer” – this permission populates your quick search with the customer option.  This is one of the best tools for quickly searching customers and quickly getting to customer information from any page in adilas.  The user must also have at least the “Add/Edit Customer” permission to use the customer quick search function.

System Basics Section: “Customer Logs” – this permission provides a quick link to search the customer logs section.

System Maintenance Section: “Add/Edit Customer” – this permission is required for 3 main customer functions.  First it allows the user to add/edit any customers, customer information, log files, follow-up records, and customer images/scans (if user has photo management permission).  It is required to create “customer” invoices, quotes and shopping cart function for basic customer sales.  If your corporation uses the queue, this permission is also required for a user to queue a customer.

Admin Use:

System Maintenance Section: “Customer Admin” – as the admin permission for customers, this allows the user to manage customer types, credit limits, exporting customer data to Excel and other settings.

Settings:

Settings play a large role in the customers section.  This is where you name your “customers”, name/turn on your customer queue, and adapt and name information fields to record the data you need.  To adjust corporation-wide settings you must have the administrative permissions to do so.  For more information on settings, please see that section of the user guide.

Once you get to the Corporation-Wide Settings and Defaults page there are at least 10 settings that can be adjusted for customer info (currently near the top).   Every setting has a description to help give you an idea of what this setting effects and a couple ideas of how it could be used.   The “Default Customer Title Name:” and “Abbreviated Customer Title Name:” are the settings for naming what you call your “customers”.   The “Customer Tax ID Title:” is another great setting to know as it has a lot of flexibility and can be renamed and adjusted for something specific you may want to track for every customer.  It is also searchable as one of the customer fields in the quick search and can even be barcode generated.

Related Pages & Help File Links:

Customer Homepage: This is your main homepage for all of your customers.  From this page you can search and add new customers and link to other customer related pages in adilas.

https://data0.adilas.biz/top_secret/help.cfm?id=70&pwd=customer

Customer/Contact Search Results: This page shows the results of your customer search, from here you have the “add new customer” button, or you can link to any of the existing customer’s information you searched for.

https://data0.adilas.biz/top_secret/help.cfm?id=71&pwd=customer

Customer/Contact Log: This is the main hub page for an individual customer.  This is the page where you add/edit/view all of your customer data.  From here you can add log notes, check the customer’s history, add contacts, add flex grid, check payment history, invoice history, and more.

https://data0.adilas.biz/top_secret/help.cfm?id=318&pwd=log

Add/Edit Customer/Contact:  This is the customer’s main information page and the form you fill in when creating a new customer or when editing an existing customer.  Below the customer’s information are fields for additional contacts, these can also be added from the customer’s log page.  

https://data0.adilas.biz/top_secret/help.cfm?id=72&pwd=customer

Adilas Quick Search Help: The quick search help file is accessible from any help file page anywhere in adilas by clicking the link “[adilas “quick search” help]”.  This help file is useful for learning the quick search options and key words for each search category.

https://data0.adilas.biz/top_secret/help.cfm?id=376&pwd=quick

Additional Content:

 -Graphics

-Screen Shots

-Etc.

4.17 - Customer Logs

-User maintained history - anything you want to track or add to your customers, notes, follow-ups

-These are unlimited in length & number

-You can also use follow-ups, etc. A date sensitive history log, helps tell the story, who talked to them, when, what was said, etc. (this is what happens)

-Your CRM (Customer Relationship Management) scenario

4.17 - Customer Logs

Understanding the Basics:

Customer logs are a central Customer Relationship Management (CRM) tool.  They are a user maintained history of what occurs with your customers or any data you want to record and track.  

Customer logs are unlimited in length and number.  Everything is date and time stamped, which helps to tell the story over time.  You can categorize how the contact was made, use follow ups, search the customer logs and really use this tool to your benefit.  

Getting Started:

To add a customer log entry, first find your customer.  Whether you search your customers from the Quick Search or the Customer Homepage, every returned search result has a direct link to the customer log if you have the permissions.  Click on their “[log]” link and then click the “[add new log entry]” link under the User-Maintained Customer Log Section.  From the Customer Homepage and your main adilas homepage there are also links to directly search customer logs or check today’s logs or follow-ups.  

There is also a detailed search option for searching customer logs from the advanced customer search page.  This allows many options for adjusting the parameters to search your customer logs.  If more help is needed finding or adding customers, please see the Customer section of the User Guide.

Suggested Permissions and Settings:

Permissions:

Basic Use:

System Search Section: “Customer” – this permission populates your quick search with the customer option.  This is one of the best tools for quickly searching customers and getting to customer information from any page in adilas.  The user must also have at least the “Add/Edit Customer” permission to use the customer quick search function.

System Basics Section: “Customer Logs” – this permission provides a quick link to search the customer logs section.

System Maintenance Section: “Add/Edit Customer” – this permission is required for 3 main customer functions.  First it allows the user to add/edit any customers, customer information, log files, follow-up records, and customer images/scans (if user has photo management permission).  It is required to create “customer” invoices, quotes and shopping cart function for basic customer sales.  If your corporation uses the queue, this permission is also required for a user to queue a customer.

Admin Use:

System Maintenance Section: “Customer Admin” – as the admin permission for customers this allows the user to manage customer types, credit limits, exporting customer data to Excel and other settings.

Related Pages & Help File Links:

Customer/Contact Log: This is the main hub page for a customer and where you go to add customer log notes.  This allows you to add/edit/view all of your customer data.  From here click the link to “[add new log entry]” for adding customer logs, check the customer’s history, add contacts, add flex grid, check payment history, invoice history, and much more.

https://data0.adilas.biz/top_secret/help.cfm?id=318&pwd=log

Add/Edit Customer Log:  This is the actual page where you record the log entry.  It is automatically date and time stamped or you can change that if needed.  This page allows for unlimited log notes and the option to use follow-up fields.

https://data0.adilas.biz/top_secret/help.cfm?id=320&pwd=log

Advanced Customer Search Results: Whether you just want to search the customer logs or really detail out your customer search, this is where you’ll come.  When you click on the “customer logs” link it is actually just a filtered view of the advanced customer search page.  The full page also has its own customer log search section.

https://data0.adilas.biz/top_secret/help.cfm?id=321&pwd=results

Additional Content:

 -Graphics

-Screen Shot

-Etc.

4.18 - Customer Queue (check in/out)

-"Who's next?", who is ready to be serviced next.... lines, queues, service center that needs some kind of ordering, very hand for service type businesses with any kind of a waiting room or waiting process (great for servicing time sensitive independent interactions)

-Can be generic with notes to help you know who it was, can tie to customers, can be used as a plain numbering system

-You can custom name this as well

4.18 - Customer Queue (check in/out)

Understanding the Basics:

“Who’s next?”  The customer queue is a line up for who needs to be serviced next.  If you deal with an industry that has a waiting room or a waiting process and need some kind of ordering, the customer queue is a great tool for servicing time sensitive, independent interactions.

The customer queue can be tied to customers, used generically with notes for reference, or as a plain numbering system.   Custom name your queue and use it to suit your needs.  The customer queue is turned on or off in the corp wide settings.  Once the queue is working there are many links and ways to add customers to the queue and a queue icon in the top right corner of every page for quick access from anywhere in adilas.

Getting Started:

After your customer queue is turned on by an administrator (which is done in the settings section) the customer queue can be accessed a number of ways.  You can link directly from the queue icon in the top right corner of every page and search for a customer from the queue page or add generic customers.  If you search for your customer first there is a link on returned customer searches to add directly to the queue.  If you go to the customer’s log page there is also an easy button to add the customer to the queue.  

Suggested Permissions:

Permissions:

Turn on the customer queue in the corp-wide settings.  This is also where you can name your customer queue. Once on, you can use the customer queue with the basic customer permissions turned on.

Basic Use:

System Search Section: “Customer” – this permission populates your quick search with the customer option.  This is one of the best tools for quickly searching customers and quickly getting to customer information from any page in adilas.  The user must also have at least the “Add/Edit Customer” permission to use the customer quick search function.

System Basics Section: “Customer Logs” – this permission provides a quick link to search the customer logs section.

System Maintenance Section: “Add/Edit Customer” – this permission is required for 3 main customer functions.  First it allows the user to add/edit any customers, customer information, log files, follow-up records, and customer images/scans (if user has photo management permission).  It is required to create “customer” invoices, quotes and shopping cart function for basic customer sales.  If your corporation uses the queue, this permission is also required for a user to queue a customer.

Admin Use:

System Maintenance Section: “Customer Admin” – as the admin permission for customers, this allows the user to manage customer types, credit limits, exporting customer data to Excel and other settings.

Settings:

The Customer Queue can be turned on and renamed by editing your corp-wide settings.   Get to your “Manage Corporation Info and Permissions” page, accessible from any homepage when you have the administrative “Mange Corp Info & Permissions” permission.  Click the “[edit corp-wide settings & defaults link]”.  On you corporation settings and defaults page, the Customer Queue setting is with the other customer settings, currently near the beginning.  Choose to “Show/Use” your queue here, also rename your queue as you desire and set the auto clean up times.

See the Admin section of the User Guide if more instruction is needed on how to access these administrative pages.

Related Pages & Help File Links:

Customer Queue:  This page is where you manage your customer queue.  You can search for customers to add to the queue, add generic non-customers to the queue (it can be helpful to add notes to reference these customers), and overall search and manage your customer queue.

https://data0.adilas.biz/top_secret/help.cfm?id=400&pwd=queue

Additional Content:

 -Show what the customer queue icon looks like & the customer queue page.

4.19 - Data Imports & Exports

-Histories, reports, access to all of your data

-Deals more with an admin level

-Getting your data back out of the system.... pdf's, web, Excel, build your own reports, etc.

4.19 - Data Exports

Understanding the Basics:

Data exports are generally used at the administrative level and are a way for you to retrieve data from your adilas system.  There are innumerable ways to search data in adilas, build your own reports, or track important indicators for your organization. All Data Is Live And Searchable = ADILAS.

Many of the advanced searches in the adilas system have an option for the data to be exported to Excel, under the “Report Type” field.  Other reports and searches in the system can be printed directly from the print link on the header and footer of every page or copied, pasted, and reformatted to fit your needs.  Other pieces of adilas are printable as pdf’s.  More and more options are coming to further assist you in formatting and retrieving your data for your needs.   

Getting Started:  

A great resource for data searches and exports is the “All Advanced Searches & Exports” page.  This is considered an admin page and is a centralized access point for all advanced searches, information currently exportable to Excel, and other special reports and data exports.  Another highly recommended page is the History Homepage which shows everything done in adilas for the time you specify and provides drill-downs to the underlying data.  

Get to the All Advanced Searches & Exports page from the Classic Homepage under System Reports – All Advanced Searches & Exports; My Favorites Homepage under Other Homepages – All Exports to Excel; and from the Interactive Map Homepage click the history & reports button and then the “all advanced searches & exports” link on the history homepage.  The History Homepage is also found under all the same sections from the main adilas homepages as the advanced searches and exports page.  There are also quick links to history reports on the bottom of the Interactive Map Homepage.

Suggested Permissions and Settings:

Permissions:

Basic Use: 

To generally print or search data, this can be done with any page in adilas that you have permission to access.

Admin Use:  

Data searching, copying/pasting, and printing can be done in general from any page you have permissions to access.  For exporting directly to Excel, look for the “Report Type” field on your advanced search or go to the “All Advanced Searches & Exports” page.

System Reports: “Corp/User History” – this gives you access to the History Homepage which has lots of power and is one of the quickest ways to see everything done in adilas for the time parameters you choose.  It allows you to see and drill-down to all of the underlying data to show you what was done and who did what.

System Reports: “All Advanced Searches & Exports” – this allows you to access this concise page for all searches and data exports.

Related Pages & Help File Links:

All Advanced Searches & Exports: A great hub for searches, reports and data exports.

https://data0.adilas.biz/top_secret/help.cfm?id=406&pwd=advanced

History Homepage: An incredibly useful page for checking out what has been going on in your adilas with drill-downs to all the underlying data.  This is great for seeing what has been happening and any data you are interested in.  This is a great page to check out every day.

https://data0.adilas.biz/top_secret/help.cfm?id=329&pwd=history

Additional Content:

 -Show some different formats of reports in adilas…. I really think with a lot of these things, people really want to have an idea of their options.  

4.20 - Departments

-Internal organization - conceptual setup and organization, organization of people

-A backbone of payroll

-Deals hugely with payroll, deals with time cards, payroll, manager - not necessarily physical locations but departments are required to be setup for payroll - who's the admin, manager, who is in that department (then you can set up pay rates, payroll taxes for specific people in various places)

4.20 - Departments

Understanding the Basics:

Departments represent the setup and internal organization of your company.  These do not have to be physical locations but can reflect any organizational distinctions.  Use them to virtually reflect your company’s organization.

Departments must be setup to use the timecard and payroll features of adilas.  Departments are the backbone for payroll.  A user is first assigned to a department and then they can be set up with payroll settings.  This provides great flexibility in assigning a user to one or potentially multiple departments to track different settings or pay rates.  Managers and administrators can be assigned and permissioned to oversee departmental management.

Getting Started:  

To set up departments go to the Department Homepage and add a new department.  This is also where you come to edit existing departments.  After a department is created, users can be assigned to the department and user payroll settings can be setup.   

The Department Homepage can be found from the Classic Homepage under the System Maintenance – Department Homepage; My Favorites under the Other Homepages – Department Home; or from the Interactive Map click on Users and then there is a link at the top of the page for the “department homepage”.

Suggested Permissions & Settings:

Permissions:

Basic Use:

Department setup and maintenance is considered an administrative function.

Admin Use:

System Liabilities: “Manager’s Time Clock” – this allows the manager (user) to add, edit, view and manage all of the timecards for users assigned to their department.

System Liabilities: “Admin Time Clock” – this is the admin permission over all the time cards for all users in all departments.

System Maintenance: “Add/Edit Department” – this allows admin to setup and manage departments.

Related Pages & Help File Links:

Department Homepage: Go here to add, edit, or manage your departments.

https://data0.adilas.biz/top_secret/help.cfm?id=27&pwd=dept

Add/Edit Department: This is where you can add or edit a department or even inactivate or reactivate an old department.

https://data0.adilas.biz/top_secret/help.cfm?id=28&pwd=dept

Assign Users to Department: This is where you assign users to their department.

https://data0.adilas.biz/top_secret/help.cfm?id=29&pwd=dept

Additional Content:

 -???

4.21 - Deposits (monies coming in)

-Any money coming in.... ideally, the standard flow comes from invoices, ends up in the A/R waiting room until you come to the end of the day or how often you deposit and pull in the money you have to deposit

-There are other flows, though standard is through invoices, but you could have investments, credit paid for a customer, bank to bank transfers, etc.

4.21 - Deposits

Understanding the Basics:

Deposits track monies coming into your business.  Deposits are one of the 12 Main Players in adilas.  The standard deposit is made up of money from invoice payments, which is the general flow for almost all deposits.  Occasionally other deposits may come from bank transfers or monies that are invested or loaned to your business.

The Deposit and Receivables Homepages both have ways to see monies that still need to be deposited.  From the Deposit Homepage there is a quick link for “[payments not yet deposited]”.  On the Receivables Homepage use the show/hide search criteria and change the report type to show invoice payments not yet deposited.  The Deposit Homepage is where you go to create, edit, search, and manage deposits.

Getting Started:

Create a deposit by going to the Deposit Homepage, which also shows your recent deposits, and click the “create new deposit” button.  If you do not know the amount of your deposit, put in 0 or any amount and move forward.  The next step then has you add the invoice payments that make up your deposit.  If you put in 0 or did not know the actual deposit amount, circle back around and edit the main deposit information to match the sum of monies that end up being contributed to that deposit.   

Reach the Deposit Homepage from the Classic Homepage under System Assets; My Favorites Homepage under the Deposits section; or the Interactive Map from the “deposits” button.  One quick way to add a new deposit is to select “deposit “from the quick search menu, type in “new” and click go.

Suggested Permissions & Settings:

Permissions:

Basic Use:

System Search: “Deposit” – allows use of the quick search for deposits.

System Assets: “Basic Deposits” – this allows a user to view deposits and deposit history.

System Assets: “Sales Deposits” – combined with the Basic Deposits permission, this allows a user to build deposits from invoice payments only.

Admin Use:

System Assets: “Admin Deposits” – combine this with the basic deposit permissions and this user will have full access to deposits so that they can add, edit, verify and manage any deposit needs.

System Maintenance: “Add/Edit Deposit Type” – this is an accounting level permission and allows you to add/edit your deposit categories to define what you are depositing the money for.

System Management: “Deposit & Receipt Final Post” – this is a high admin permission which allows this user to put a final lock on deposits and expense/receipts.

Related Pages & Help File Links:

Deposit Homepage:  This is where you can see recent deposits or start a new deposit.

https://data0.adilas.biz/top_secret/help.cfm?id=81&pwd=deposit

Add/Edit Main Deposit:  This is the main deposit information page.

https://data0.adilas.biz/top_secret/help.cfm?id=82&pwd=deposit

Add/Edit Deposit Line Items:  This is where you add items to build your deposit.  This page is also where you will find the admin add/edit deposit line item form for special deposits that are not sales generated.  

https://data0.adilas.biz/top_secret/help.cfm?id=83&pwd=line

Additional Content:

 -???

4.22 - Discounts & Discount Rules

-First off you have to realize that price is a variable that you can play with, cost is fixed. Price can be manipulated. Some people choose to change prices & others choose to use discounts to “change” the price. Discounts - A visual price change.

-In line discounts: these are per line item in percentages, dollars off, or mixed. Occur per line. Huge level of control and your taxes are spot on.

-Standalone discounts: these are a new line item that just holds the discounted amount. These are more general and depending on your industry may or may not be allowed. The hard part about this one is if you have advanced tax stuff it is hard to back out all of the taxes correctly. That is why in-line discounts are more detailed on the taxes.

-There are ways of setting up discounts through corp-wide settings, campaigns, based off of customer types, can tie discounts to buttons (my cart favorites), and there are other global rules & settings being developed including date & time based discounts. (i.e. happy hour, double Tuesday’s, etc.)

-There are also settings per item that you can say include or exclude on discounts. So this can be taken out to the individual item level.

-There are also some discount calculators that deal with cart as a whole, individual lines, or just sample data so that you can figure discounts.

4.23 - Display Options & Interface Choices

-Settings & permissions

-How do you organize your space? Your work space?

-Chooser - what do you want your interface to look like? Adilas has many available out of the box but this piece is entirely customizable and a lot more will be coming.... you can request or design your own which can then be quoted, individually charged/billed for & built out

-Very customizable - what do you use? What do you need? What is important? What do you want to see? What do you not want to see? 

4.23 - Display & Interface

Understanding the Basics:

Adilas is built for you, the user, and right from the start adilas allows customization to help set the look, feel, and flow of your adilas.  We want using adilas to be easy and efficient.  To help accomplish this, we provide different interfaces so you can choose the one that is best for your needs and your style.   

The first way to customize your adilas is through Settings and Permissions.  Adilas is based off of these two concepts. Settings allow adilas to reflect your specific organization, such as what you call your “customers”, what you sell, or how your processes flow.  Permissions determine who can be where in the system and what information or actions are available to employees or admin.

Getting Started:

By using the “Chooser” link, found on every page, you can set your main default interface.  If you want a custom interface or have a request, contact adilas.  Custom interfaces, reports, or displays can be individually charged and built out to meet your specific needs.  This is one of the sides of adilas that has lots more coming!  Adilas is already very customizable and the future only holds more and more in the way of customizing your adilas to fit your needs.

Your corporation’s “corp-wide settings” are determined and adjusted by the ultimate administrators of your business entity.  They are accessed from the “Manage Corporation Info and Permissions” page.  From here click the link to “edit corp-wide settings and defaults”.  All of the settings have associated descriptions to help you understand what that setting controls.  Reach the Manage Corporation Info and Permissions page from the Classic Homepage under System Management; My Favorites under Other Homepages – Corp Home; and the Interactive Map under the settings buttons.  

Suggested Permissions & Settings:

Permissions:

Basic Use: 

Use your “Chooser” link to pick the interface you like working with.

Admin Use: 

Changing corporation-wide settings and permissions is done by your ultimate administrators.  There are permissions for each of these functions which should only be assigned to top administrators.  These permissions are found under the System Management Section:

System Management: “Add/Edit Payees & Permissions” – this permission allows you to add and edit any user and their permissions in your adilas system.

System Management “Manage Corp Info & Permissions” – this permission allows you to edit and set up all of your corporation’s settings and defaults.  There is a lot of power in this section.  This section allows you to set industry specific naming and terminology, adjust aspects of flow for various processes in your adilas application, determine default settings, and more.                   

Related Pages & Help File Links:

Manage Corporation Info & Permissions: This page is an administrative hub.  This is where you come to find the links for editing your corp-wide settings and defaults and your corporation’s look and feel.  There are also many other links at the top which allow quick access to a number of admin pages.

https://data0.adilas.biz/top_secret/help.cfm?id=216&pwd=corp_admin

Corporation-Wide Settings & Defaults: Here is where you set your corporation wide settings and defaults.  There are associated descriptions for each setting to help you understand its use and some potential options.  From the manage corporation info and permissions page the link to this page is “[edit corp-wide settings and defaults]”.

https://data0.adilas.biz/top_secret/help.cfm?id=336&pwd=settings

Add/Edit Corporations: This is where you set your main corporation info as well as color schemes and logo that cascade through the whole system.  From the manage corporation info and permissions page the link to this page is “[edit main corp info – look and feel]”.

https://data0.adilas.biz/top_secret/help.cfm?id=16&pwd=corps

Additional Content:

 -Definitely, definitely feature some of the varying custom interfaces here!  There are so many cool ones!

4.24 - eCommerce & Web Presence

-Another corner piece

-2 parts to this: Web presence: on the world level - do you want to show it yes or no? You can control this on the world level. You can control it even more on the item or stock level. A customer facing portion, outside secured environment - so basically a satellite or moon of your world (your retail storefront instead of your back office)

-Next part: eCommerce: goes a level deeper, controlled on the Universe level, allows virtual shopping carts to be used outside of the system. So the next level, instead of just showing the system you can sell, make payments, which will affect inventory and affect things within your world (the Adilas system). There is a whole other piece coming beyond the one by one transactions by creating to be a way for customer to log in to pay their bills, or view/print their histories, so almost give them a limited functionality to do their stuff

-Ways to hide the pricing in eCommerce and give wholesale pricing to your clients

4.25 - Elements of Time (calendar & scheduling)

-A tool for using time. Are you doing: reservations, rentals, reminder system, scheduling, forums, a history, calendar event .... which you can then attach to anything else, or tie it to other things in the system

-Mix & blend, connect things, standalone & have it show up on the calendaring & scheduling application, tie it to customers, to vendors, to users... an additional time and scheduling/organizing piece for any of the other pieces, players, or functions in the system

-You can name and create your own templates, bins, buckets; You can name your locations or separate time organization & track in various ways

4.25 - Elements of Time (Calendaring & Scheduling)

Understanding the Basics:

Elements of Time is a dynamic business tool for time.  However time is used in your organization, this feature of adilas has great depth and flexibility to adapt to your needs.  Elements of Time can be used as a standalone time tool or it can be connected and linked to customers, users, vendors and other players within your adilas system.  There are 3 rounds of development planned for Elements of Time and Round 1 is what you are currently working with.  It is already a powerful and functional tool for time, but there is a great deal more to come!

Elements of Time allows you to create your own master time templates.  These master time templates allow you to setup and determine what details and information you want recorded, or that you require for that “type” of time.  You can create as many time templates as you need and then use them over and over again for tracking time.  Whether you are doing reservations, rentals, scheduling, project management, appointments, forums, calendared events, reminder systems, servicing, etc., this tool is ready to be customized to suit your needs.

Getting Started:

Go to the Elements of Time Homepage to start working with elements of time.  From here you can access links to add/edit master time templates, create new elements of time, and search and change report formats to view and work with your time elements.  

The first step in using elements of time is to setup time templates.  Once you have created a template click the “create new element of time” button to start adding time.  These templates can be adjusted with a huge variety of settings to make this useable for your organization, or what you need to track, for that “type/kind” of time.  For help getting started with elements of time check out the associated help files, these can help you better understand the versatility of elements of time and setting up a template to use over and over again.

Get there from the Classic Homepage under System Time & Requests; My Favorites Homepage under Elements of Time – Time Homepage; and the Interactive Map Homepage – elements of time button.

Suggested Permissions & Settings:

Permissions:

Basic Use:

System Search: “Time” – this allows you to use the quick search to search any elements of time, very fast and helpful.

System Time & Requests: “Basic Elements of Time” – allows the user to add, edit, search, print and generally work with time.

System Time & Requests: “Time – View & Comment” – this is a limiting permission and allows a “view only” setting.  This is given if you don’t want the user to be able to work with elements of time but only to see them and add sub comments if your template allows it.

Admin Use:

System Time & Request: “Admin Elements of Time” – this allows you permission to setup, create and edit master time templates and have admin permission over Elements of Time.

Related Pages & Help File Links:

Elements of Time Homepage: Your main hub for all time.  Lot of navigation and links at the top, a search form for elements of time, and your time search results & display.

https://data0.adilas.biz/top_secret/help.cfm?id=381&pwd=time

View Master Time Templates – Admin: Where you view master time templates and link to add/edit them.

https://data0.adilas.biz/top_secret/help.cfm?id=382&pwd=admin

Add/Edit Master Time Template: This help file is highly recommended if you are setting up master time templates.  This helps you understand the options for master time templates, what each of the settings controls or does and how you can create them to fit your needs.

https://data0.adilas.biz/top_secret/help.cfm?id=383&pwd=template

Add/Edit Main Element of Time:  Once you’ve set up your templates, this is the actual process of creating elements of time, which will follow the pattern of the template you created.  These will show up on your calendar and become their own object, being able to flex, adjust and hold large amounts of information.

https://data0.adilas.biz/top_secret/help.cfm?id=384&pwd=time

Additional Content:

 -It would be really neat if you could visually show some different ways or uses for Elements of time…. Maybe even some different view of it: like scheduling, a forum, time for invoicing, etc.

4.26 - Email Settings

-By default you can automatically email quotes, statements, & invoices directly from the system.

-There are also ways that you can configure custom emails that allow for html coding (rich look & feel). These emails can also use data directly from the system.

-If you need a custom address, there are ways that we can implement a custom email address.

-Professional quality emails. There is an entire sub-section just for email settings.

-There are custom options available. So if you need reminders or certain triggers need to be set or monitored, we can send you email notifications directly through the system. 

4.27 - Employee/Users

-Permissions, individual settings

-Which keys - permissions - are you giving them? Where can they work, play and what can they do in the system.

-Can by bigger than a corporation... they can have access to multiple corps

-Over 100 permissions, but must have 1 active permission to be considered a user

-This is one of the Main 12

-Often connected with payroll

-Every single piece is eventually connected to "who" - which user - did it, the system history, the employees can walk down every hall and go in every room if you give them the keys for it

-Employees & vendors technically the same in the system, except that one has permissions in the system and the other is just an outside feeder - ties to the end goal of getting paid - expense/receipts 

4.27 - Employee/Users

Understanding the Basics:

Users are the people that have access and permissions to work inside your adilas system.  You must have one active permission to be considered a user, but there are over 100 permissions that allow you to dictate what users can access, view, edit, and how they work in the system.  Users are one of the 12 Main Players of adilas and can technically be bigger than a corporation, since a user can have access to multiple corporations.  

System history is tracked with every single piece of adilas telling you the “who” of the story, or what user was associated with every action done in the system.  Users (employees) and vendors are similar in the system because they both tie to the end goal of getting paid through expense/receipts.  The difference is that a user has permissions and access to use the system, where a vendor is an outside payee of your adilas system.

Getting Started:

Adding new payees with their associated permissions is a high administrative function.  With the admin permission to “add/edit payees & (their) permissions”, it is a straightforward search and add process from the Payee Permission Homepage.  When adding or editing user information or permissions, the personal information is at the top of the page and all of the permission options are below.  The add or edit payee button at the bottom of the page must be submitted for your changes to be active.  

If users are setup with a basic permission of password and profile, they can go back in themselves and change their username, password and personal information but not their permissions.  Permissions can only be changed by a user that has the “add/edit payees & permissions” permission, which should only be given to the highest administrators.   Get to the Payee Permission Home from the Classic Homepage under System Management – Add/Edit Payees & Permissions; My Favorites Homepage under Other Homepages – Payees & Permissions; or the Interactive Map – users button.

Suggested Permission & Settings:

Permissions:

Basic Use:

System Basics: “Password & Profile” – this allows users to change their own password and profile and edit their personal information.  

Admin Use:

System Management: “Add/Edit Payees & Permissions” – this is an ultra admin permission.  These are the keys to add and change any user’s permissions, it is strongly recommended you take some time to understand permissions and only assign the permissions the user needs to do their job.

***With over 100 permissions that can potentially be assigned to a user, this is really where an administrator decides what they want a user to be able to do in the system and then assigns permissions accordingly.  It is strongly recommended if you are an administrator setting up new users in the system to take some time to understand permissions.  You do not want all of your users having access and permissions to every part of your adilas application.

Related Pages & Help File Links:

Payee Permission Home: This is where you search and add new users in the system.  This is also where you go to edit user permissions or information for users already in the system by clicking on the user’s name.

https://data0.adilas.biz/top_secret/secure/payee_permission_home.cfm?sec=51

Search Payee/User: Basic search before you add a new user in the system, this is required so as not to duplicate user in the system.  The link is at the top left of the links section and is called, ”[search/add a payee in the database]”.

https://data0.adilas.biz/top_secret/help.cfm?id=11&pwd=search_user

Add/Edit Employee/User Permissions: Adding or editing employee information or permissions.  Each permission has an associated description to help you in assigning the appropriate permissions per user.

https://data0.adilas.biz/top_secret/help.cfm?id=106&pwd=permissions

Additional Content:

 -We might want some screen shots here of the permissions page.  Or maybe we would even want to give a couple sample packages, if you will, of basic user permissions.  Like a basic set of retail permissions, or basic inventory permissions, etc.  Not necessary since each different company will have people that operate so differently but it was just a little thought I had while typing so I thought I’d record it here.  It could be helpful?

-Link here to the hour permissions class we recorded for one of our adilas university classes.

Adilas is what we call a "business platform". What that means is there are tons of tools, functions, permissions, settings, and processes to help you run your business. This guide or manual will take you on a step by step journey in exploring and explaining some of the functions and tools that are available to you and your company. Not every tool or function will be used and that's ok. We want you to match the right tools with the right job. Some of the goals in providing this manual are helping you learn the system, apply the concepts in your own specific manner, help you track all your operational and accounting data, and help make you even more successful than you currently are! Let's get started!

Basic Outline - Feel Free to Jump to a Specific Section or Area
 
1 - Understanding The Basics
1.1 - What is adilas?
1.2 - How Does It Work?
1.3 - Enter Once - Use Many
1.4 - Database Basics
1.5 - Web Basics
1.6 - Standard Page Elements
1.7 - Navigation Tips & Tricks
1.8 - Vocabulary
1.9 - Adilas Theory

2 - Logins, Passwords & Permissions
2.1 - Main Website Features
2.2 - Username & Password
2.3 - Creating An Adilas Bookmark or Favorite
2.4 - User Permissions

3 - General System Settings
3.1 - Main Corporation Info & Settings
3.2 - Locations
3.3 - Sales Tax Settings
3.4 - Payroll Tax Settings
3.5 - Departments (tied to payroll)
3.6 - Assigning Employees to Departments
3.7 - Timecards (clock in/out)
3.8 - Master Time Templates (calendar & scheduling)
3.9 - Flex Grid Tie-Ins (custom data fields)

4 - Meet The Players
4.1 - General Overview
4.2 - Admin
4.3 - API Sockets & Communications (application programming interface - send & receive data remotely)
4.4 - A/P - Accounts Payable (vendor waiting room)
4.5 - A/R - Accounts Receivable (customer waiting room)
4.6 - Attributes (parent & child inventory flags and tags)
4.7 - Balance Sheet
4.8 - Banks
4.9 - Barcodes & QR Codes
4.10 - Black Box Page Technology (custom code options)
4.11 - Check Requests (sub type of the normal expense/receipts)
4.12 - Check Writing
4.13 - Chooser (custom interface chooser)
4.14 - Corporations (worlds)
4.15 - Coupons & Sales Campaigns
4.16 - Customers/Clients
4.17 - Customer Logs
4.18 - Customer Queue (check in/out)
4.19 - Data Imports & Exports
4.20 - Departments
4.21 - Deposits (monies coming in)
4.22 - Discounts & Discount Rules
4.23 - Display Options & Interface Choices
4.24 - eCommerce & Web Presence
4.25 - Elements of Time (calendar & scheduling)
4.26 - Email Settings
4.27 - Employee/Users
4.28 - Expense/Receipts (monies going out)
4.29 - Exports - MS Excel/CSV/PDF
4.30 - Flex Grid Tie-Ins
4.31 - Floorplan
4.32 - Gift Cards, Rewards, & Loyalty Points
4.33 - GPS & RFID Tag Tracking
4.34 - History & Reports
4.35 - Ideas & Sharing
4.36 - Interface Options, Dashboards & Choices
4.37 - Invoices
4.38 - Labels & Custom Paperwork
4.39 - Locations & Tax Settings
4.40 - Look & Feel (custom colors & navigation)
4.41 - Manufacturing (changing or modifying inventory)
4.42 - Marketing
4.43 - Media/Content/Files (physical file uploads and referencing)
4.44 - Merchant Processing - Credit Cards & Financial Solutions
4.45 - Mini Conversions (buying, selling, & tracking inventory - units of measure)
4.46 - My Cart Favorite Buttons
4.47 - My Stuff (personal settings & options)
4.48 - Objects & Data Over Time (theory & concepts)
4.49 - Orders
4.50 - P&L - Income Statement
4.51 - Parts/Items (general inventory pool)
4.52 - Payroll, Commissions, & Time Clocks
4.53 - Permissions
4.54 - Photos & Scans
4.55 - Purchase Orders (PO's)
4.56 - Quick Search
4.57 - Quotes
4.58 - Recipe/Builds
4.59 - Reimbursements (REI's)
4.60 - Reoccurring & Automated Options
4.61 - Sales & Promotions (see coupons & sales campaigns)
4.62 - Saved Reports (custom report favorites)
4.63 - Settings - Corp-Wide
4.64 - Settings - Group Level
4.65 - Settings - Page Level
4.66 - Settings - Personal
4.67 - Shopping Cart
4.68 - Special Line Items (system parts)
4.69 - Splits (payments made on account)
4.70 - Statements
4.71 - Stock/Units (serialized inventory)
4.72 - Sub Inventory (parent/child inventory)
4.73 - Support
4.74 - Texts, Emails, Reminders, & Communications
4.75 - Third Party Solutions
4.76 - Tiered Pricing & Pricing Engine
4.77 - Timecards (digital clock in/out)
4.78 - Tools & Maintenance

5 - Customers (in depth)
5.1 - Customer Settings (general)
5.2 - Customer Types
5.3 - Customer Logs
5.4 - Customer Additional Contacts
5.5 - Customers to Invoices & Quotes
5.6 - Customer To Elements of Time (scheduling)
5.7 - Customer Photos & Scans

6 - Inventory (in depth)
6.1 - General Inventory vs. Serialized Inventory
6.2 - Parts, Services, & General Inventories
6.3 - Vendor/Payees
6.4 - Part Categories
6.5 - Use PO's to Add Inventory
6.6 - Updating Inventory Counts
6.7 - Light Manufacturing
6.8 - Recipe/Builds
6.9 - Stock/Units (serialized inventory)
6.10 - Makes
6.11 - Models

7 - Sales (in depth)
7.1 - Shopping Cart
7.2 - Advanced Add To Cart
7.3 - My Cart Favorites & Smart Group Buttons
7.4 - Quotes
7.5 - Invoices
7.6 - Invoice Payments
7.7 - Transitional Invoices
7.8 - Reoccurring Invoices
7.9 - Discounts, Returns, Trades, & Refunds
7.10 - Statements
7.11 - Sales & Profit Reports
7.12 - Sales Tax Reports
7.13 - Merchant Processing (credit card payments)
7.14 - Transfer Invoices

8 - Deposits (monies coming in)
8.1 - Banks
8.2 - Deposits
8.3 - Deposit Types
8.4 - Deposits on Merchandise
8.5 - Depositing Invoice Payments
8.6 - Bank Transfers (deposit side)
8.7 - Special Deposits (balance sheet)

9 - Expenses (monies going out)
9.1 - Payables Homepage
9.2 - Expense/Receipts
9.3 - Expense Types
9.4 - Check Requests
9.5 - Reimbursements
9.6 - Splits or Payments On Account
9.7 - Pay Stubs (payroll and withholdings)
9.8 - Payroll Tax Liability
9.9 - Sales Tax Liability
9.10 - Special Payments - Credit Cards
9.11 - Bank Transfers (expense side)
9.12 - Special Expenses (balance sheet)
9.13 - Printing Checks
9.14 - Advanced Concepts & Usages

10 - Reports & Searching
10.1 - Report & Search Basics
10.2 - Adilas Quick Search
10.3 - Basic Application Type Searches
10.4 - Advanced Application Type Searches
10.5 - History Homepage
10.6 - Sales & Profit Reports
10.7 - P&L - Income Statement
10.8 - All Advanced Searches & Exports
10.9 - View Custom Code & Reports

11 - Financials & Accounting
11.1 - Bank Reconciliation
11.2 - P&L - Income Statement (logic and flow)
11.3 - Balance Sheet (logic and flow)
11.4 - User-Maintained Balance Sheet Items
11.5 - Adilas Theory on Accounting
11.6 - Roll Call Accounting Principles
11.7 - Old School Accounting vs. New School Accounting
11.8 - Vision for the Future

12 - Other Tools & Features
12.1 - Bridging Users Between Corporations
12.2 - Site Look & Feel (colors and logo)
12.3 - Corp-Wide Settings
12.4 - Training & Support
12.5 - Barcode & Label Generator
12.6 - Profit & Discount Calculator
12.7 - Finance Loan Calculator
12.8 - Financial Flow Calculator
12.9 - Global Parts Find & Replace
12.10 - Global Parts Mark-Up
12.11 - Global Stock/Unit Mark-Up
12.12 - Admin Time Clock
12.13 - Update Inventory Counts
12.14 - Managers Checkbook
12.15 - Wholesale - Cart Builder
12.16 - Cross-Corp Sales
12.17 - Custom Forms & Documents
12.18 - Custom Code & Reports
12.19 - Building Master Time Templates
12.20 - My Cart Favorite Buttons
12.21 - Smart Group Buttons (tiered pricing)
12.22 - Become an Adilas Rep

4.28 - Expense/Receipts (monies going out)

-Any monies going out of the bank.... opposites of deposits

-Used for many different things - paying off PO's, inventory, paying employees, paying business fees, services, utilities, reimbursements, etc., even one expense receipts can be used to pay off multiple subs

-One of the most flexible pieces for mixing & blending & has incredible potential for great depth

-This is one of the Main 12

-You can detail out and organize all of your expense categories

4.28 - Expense/Receipts

Understanding the Basics:

Expense/Receipts indicate the payment of any monies going out from your company.  This is one of the 12 Main Players in adilas and has great depth.  It can be used to pay off many different things such as PO’s – inventory, paying employees, business fees, utilities, reimbursements (rei’s), etc.  One expense/receipt can even be used to hold other expense/receipts as subs and pay them all off together.

Expense/Receipts allow for you to setup and detail out all of your expense categories to 5 levels deep.  This means that every expense receipt is mapped out to 5 levels and all of this information tracks to your financials, showing up on the Income Statement or the P&L.  

Getting Started:

The Payables Homepage is a great place to start for seeing who you owe money to and expenses that have been recorded and need to be paid.  This is where all of your PO payments, payments on account (splits), and reimbursements (rei’s) will show up, if they have been recorded as such, and where you start the process to pay them off.  Use the active links in their respective columns to begin the expense/receipt process for these items.  

For creating other expense/receipts or managing expense/receipt information, go to the Expense/Receipt Homepage.  This encompasses all of your expense/receipts, even those that bypass the accounts payables section (accounts payable indicates known monies owed – for things like PO’s or monies recorded and in process or needing to be paid – splits & rei’s).  Come to the Expense/Receipt Homepage to create a new expense/receipt.  This page also contains links for getting to the add/edit expense types for your classification of account types.  

Reach these pages from the Classic Homepage under System Liabilities – Expense/Receipt Homepage & Payables Homepage; My Favorites Homepage under the Expense/Receipts section – Expense/Receipt Home & Payables Homepage; or the Interactive Map Homepage under the expense/receipts or a/p vendor waiting room buttons.

Suggested Permission & Settings:

Permissions:

Basic Use:

System Search: “Expense/Receipt” – a user also needs the “Basic Expense/Receipt” permission to be able to search/view or add/edit expenses.

System Liabilities: “Basic Expenses/Receipts” – this allows a user to add/edit, view, search, and print basic expense/receipts.  Limited view of any private e/r’s.

System Liabilities: “Basic Payables” – this may be another possible combination with the “Basic Expense/Receipt” permission, this allows the user to view but not edit data on the Payables Homepage.

Admin Use:

System Liabilities: “Expenses/Receipts Admin” – allows for the ability to verify, alter line items, lock expense/receipts, and view all private expense/receipts and all admin rights to expense/receipts.

System Maintenance:  “Add/Edit Expense Type” – this allows permission to add and edit the expense types or payment categories.

System Management: “Deposit & Receipt Final Post” – this allows the final admin lock on all deposits and expense/receipts, no one can change data without this permission once it has been posted.

Related Pages & Help File Links:

Expense/Receipt Homepage: Create new expense/receipts here, view/search recent expense receipts, search and link to other associated pages.

https://data0.adilas.biz/top_secret/help.cfm?id=86&pwd=expenses

Payables Homepage: Come here to see monies owed, or in the process of being paid for.  View and begin paying off your PO’s, splits, and rei’s from this page.

https://data0.adilas.biz/top_secret/help.cfm?id=239&pwd=payables

Vendor/Payee Homepage – Search Payees: When starting a new expense/receipt from the Expense/Receipt Homepage you will come here and be asked to search for a vendor/payee.  Who is getting paid on this expense/receipt?

https://data0.adilas.biz/top_secret/help.cfm?id=94&pwd=receipt

Add/Edit Expense/Receipt: This is the page where you finish creating your actual expense/receipt.  Who is getting paid and how much – the main information, what the payment is for & how it is categorized  – line items, and how it was it paid – payments section.

https://data0.adilas.biz/top_secret/help.cfm?id=87&pwd=expense

Add/Edit Account Types: This is the page where you create and manage your account types or your payment categories.  What categories or account types do you need to track/categorize your financials for expenses.

https://data0.adilas.biz/top_secret/help.cfm?id=91&pwd=accounts

Additional Content:

 -???

4.29 - Exports - MS Excel/CSV/PDF

-Exports are important and we want you to get your data. We help you store & secure it but it is your data. If we provide you with data it is part of our back up plan. You get your data, your needs, in your way.

-Almost all of the main system reports have export options. Usually exports are tied to the admin permission. Once it is in Excel or CSV you can alter the data however you want.

-There is an entire page that deals with just export options. Also, a lot of the new data tables, which is technically the word for special web tables that have cool features, they automatically have export options directly from the tops of the data tables.

-The system automatically can generate PDFs for POs, invoices, statements, quotes, P&L, & balance sheet; all of those can be configured to specifically match your needs. 

4.30 - Flex Grid Tie-Ins

-Create data relationships, connect players together (tie things together), 15 custom fields per the 12 main players- create your own customized database, notes

-Can add log notes to any of the 12 main players, unlimited in quantity

-Virtual buddy system

4.30 - Flex Grid

Understanding the Basics:

The flex grid tie-in application is a standalone mini application or customizable database that rides on top of your entire adilas system.  Flex grid has 3 main uses.  It can be used as a virtual buddy system, tying things together and creating data relationships.  Flex grid also allows you to add additional notes or logs to any of the 12 main players.  Another use is to create your own customized database for each of the 12 Main players with up to 15 custom fields and unlimited subs per each main player, to track any special data needs.

Flex grid arches over the entire application because it can be used with, and between, any of the 12 Main players.  You can add an unlimited amount of flex grid to an object and flex grid is almost as unlimited in the ways it can be adapted to fit your needs.  

Getting Started:

Flex grid must be tied to a main or “host” object, one of the 12 main players.  To add flex grid, go to the individual object (Such as: Invoice #97, Employee - John Doe, Customer – Jane Smith, E/R # 65, etc.) where the flex grid needs to be attached, and add your flex grid tie in from there.  When you are on the main object and have the necessary permissions there will be a link that says “[add new flex grid tie-in]”, there is also a link to view other flex grid pieces already attached there.

To set up your own customized database, go to the flex grid tie in homepage to add and manage your custom fields.  With the admin permissions there is a button right in the middle of the Flex Grid Homepage that says “admin – manage custom fields”.  We would highly recommend taking some time to plan out what you need/want for your flex grid before going in to set it up.  You have 15 custom fields per Main Player Group but the 15 custom fields can contain subs in the form of dynamic drop-down lists, or a combination of a drop-down list and open entry field, it depends on your needs.

Get to the Flex Grid Homepage from the Classic Homepage under System Maintenance – Flex Grid Tie-In Homepage; My Favorites Homepage under Flex Grid Tie-Ins – Flex Grid Homepage; or the Interactive Map under the flex grid tie-ins button at the top.

Suggested Permissions & Settings:

Permissions:

Basic Use:

System Search: “Flex Grid” – this allows a user to search flex grid pieces from the quick search.

System Maintenance: “Add/Edit Flex Grid” – this is the basic flex grid permission and allows a user to add, edit, view and search flex grid pieces.  

***The 12 Main Players Groups: Though they may be named differently in your adilas application (i.e. if you call your customers – patients, clients, etc.; or your parts – items, services, etc.)

o Balance Sheet Items

o Customers

o Deposits

o Elements of Time

o Employee/Users

o Expense/Receipts

o Invoices

o Parts & General Inventory Items

o PO’s  or Purchase Orders

o Quotes

o Stock/Units – Serialized Inventory

o Vendors

Admin Use:

System Maintenance: “Admin Flex Grid” – the admin level for flex grid allows the user to setup the custom fields, essentially creating a miniature customized database for the information you need to track for that main player group. With 15 custom fields available for each of the 12 main players, and potentially unlimited subs this creates a very expandable and flexible mini application.

Related Pages & Help File Links:

Flex Grid Tie-In Homepage:  Helps with understanding flex grid, getting started with lots of good information and some examples for using flex grid.

https://data0.adilas.biz/top_secret/help.cfm?id=323&pwd=flex

Admin – Manage Custom Fields:  This page is where you set up your custom fields or your custom database.  There are a lot of options here, you can pre-set your subs or just leave it as an open entry field.

https://data0.adilas.biz/top_secret/help.cfm?id=324&pwd=flex

Add/Edit Flex Grid Tie-In:  This page is going through the actual process of adding new pieces of flex grid or editing existing pieces of flex grid.  This page comes up after you have linked from the “[add new flex grid tie-in]” from an individual object page.

https://data0.adilas.biz/top_secret/help.cfm?id=326&pwd=flex

Additional Content:

- Graphic:

o Where the 12 main players are in green & flex grid highlighted in yellow on the interactive map

- Lots of good videos on this --- but that can come later

- Or even showing some screen shots of some Flex Grid custom set up pages – this helps me have an idea of the organization – what it looks like to have all Open Entry – what it looks like when you have populated subs, etc.

- The Teacher site and The Seamstress both have some good flex grid pieces you can show… I’m sure there are others too.

4.31 - Floorplan

-For big ticket items - trading titles for working capitol - your credit line

-Deals with the bank, an outside entity, almost like a multi-note with the bank per specific big ticket items (so like a loan with lots of miniature pieces or subs under it)

-This categorizes and data tracks and helps to track things with your floorplan - data tracking on serialized units & inventory

4.31 - Floorplan

Understanding the Basics:

Floor plan is a form of financing often used in industries with serialized or big ticket items, such as the auto industry.   It is a means of inventory financing which allows an outside lender, often a bank, to extend credit lines for these specific items.  As these items sell, the borrower repays the lender.  This ends up being like a multi-note loan, or a loan containing individually tracked miniature or sub pieces under it.

This section of adilas helps you track and categorize all the serialized units and inventory associated with your floorplan.   It also helps you search floorplan information and details, print reports, and track aspects of managing a floorplan.  

Getting Started:

Suggested Permission & Settings:

Permissions:

Admin:

System Liabilities: “Floorplan”

Related Pages & Help File Links:

Floorplan Homepage:  

https://data0.adilas.biz/top_secret/help.cfm?id=43&pwd=floor

Search Units in Inventory:

https://data0.adilas.biz/top_secret/help.cfm?id=76&pwd=inventory

Inventory Groups:

https://data0.adilas.biz/top_secret/secure/balance_sheet_inventory_groups.cfm?useDate=12%2F4%2F13&parts=1&repairs=1

Grouped Floorplan Report:

https://data0.adilas.biz/top_secret/secure/balance_sheet_floorplan.cfm?useDate=12%2F4%2F13&mainType=1&reportType=grouped&make=1&subType=1&status=owe&titleId=1&storeId=

Search Sold Units:

https://data0.adilas.biz/top_secret/help.cfm?id=77&pwd=sold

Additional Content:

- ????

4.32 - Gift Cards, Rewards, & Loyalty Points

-Tons of custom options are available. Often these reward programs have some corporation specific flare.  

-The Adilas standards are still currently under construction. Expected release data first quarter of 2019. Some of the standards will include: loyalty/rewards, gift cards, punch cards, in-store credit, vendor credits, etc.

-Technically all of these special account types or payment types are subs of the balance sheet. Behind the scenes all of these accounts will be run under a general title called sub special account tracking. Within that we will allow you to name the special programs according to your needs. For example, if you want to call your gift cards XYZ Bucks, that is totally fine.

-All of the programs that get setup will automatically inherit a default set of rules. Then we will let you modify those rules to match your company. This may be custom naming, special ratios, values, redemption exceptions, all kinds of rules, etc.

4.33 - GPS & RFID Tag Tracking

-GPS stands for global positioning system and RFID tag stands for radio-frequency identification

-One of the differences between GPS (global positioning system - usually satellite based) and RFID Tracking (radio-frequency identification - usually small tags or chips) is dealing with the distance from a hub or known area. Both technologies deal with tracking items or things according to a specific location or coordinates. GPS usually covers more distance and is mobile and RFID is more local, fixed, or within a controlled environment.

-These technologies are capable of tracking an "x" coordinate (longitude or width), a "y" coordinate (latitude or height), a "z" coordinate (depth, height, altitude, or elevation).

-Currently we have all of these as a possible sub of time so they can be turned on and off.  The fields exist so that we can capture real data or we could have other third parties that could feed us data and we could capture that.

-Basically the field is set to play but it is not fully automated yet. There are tons of places that it could go but currently it still needs some further development for it to be fully automated. 

4.34 - History & Reports

-Usually checked and used by admin - get to the history & data in/from the system

-Historical, Effectual, & Financial - levels of history on the different pieces

-Lots of flexible ways to get your data - All Data Is Live And Searchable

4.34 - History & Reports

Understanding the Basics:

There are 3 main groups of history tracked in adilas:  Effectual – what shows up for roll call (where is an object at, with date & time stamps), Historical – who touched what (actions/histories), & Financial – what & where does this show up on the financials.  History and reports are usually checked and used by admin to monitor and see what is happening in the system.  There are many ways to view, print, export and get at data in adilas: All Data Is Live And Searchable (adilas).  

The history homepage is one of the best resources for checking daily histories, weekly histories, grouped history reports, etc.  The history report provides drill down links into the specific items done in the system.  Many reports can be printed, exported to Excel, copied and pasted, and so forth.  Each object in the system also has its own history as it is created and tracked through the system.  Look for the history link to see the history associated with that object.

Getting Started:

Suggested Permission & Settings:

Basic Use:

System Basics: My History

Admin Use:

System Reports: Corp/User History

Related Pages & Help File Links:

History Homepage:  One of the best resources for efficiently accessing what has occurred in the system

https://data0.adilas.biz/top_secret/help.cfm?id=329&pwd=history

All Advanced Searches & Exports: All of the links to advanced searches in one place

https://data0.adilas.biz/top_secret/help.cfm?id=406&pwd=advanced

Additional Content:

- Screen Capture:

o It might be helpful to have a graphic here that shows a substantial or average Daily History report, so they can see layout, drill-down links, etc.

o It might also be good to show a couple different layouts for the ways reports are displayed & in the caption explain where that is

4.35 - Ideas & Sharing

-We love ideas! As adilas can get to it, it will get to it. But if you have an urgent need, get with adilas and help pay for that feature to be developed and you will benefit and it helps to grow the overall functionality of adilas

-Piggy back system, ideas grow & feed on ideas, so it all helps build a better system in the end

-A lot of great ideas come for our users and we appreciate any submitting of ideas, improvements, or tips, tricks

-It is a huge asset to have so many users contribute to the growth of this project

-In the future we would like to have ideas & sharing as a sub piece of Elements of time so that we can have a more open forum and a way to share and improve together 

4.35 - Ideas & Sharing

Understanding the Basics:

Adilas loves ideas and input!  Much of what adilas already is has come because of user input and suggestions.  It is a huge asset to have so many users contributing to the growth of this project.

As adilas gets ideas and suggestions, we will get to it as we are able to get to it.  But if you have an urgent need, contact adilas and you can help pay for a feature to be developed.  This services individual needs but also helps adilas’ overall functionality and growth.  In the future we hope to have a more open forum, under Elements of Time, to share thoughts and ideas and grow together.

Getting Started:

Send Ideas and thoughts to:

info@adilas.biz

Suggested Permission & Settings:

Related Pages & Help File Links:

Additional Content:

4.36 - Interface Options, Dashboards & Choices

-Every user gets to select or specify what user interface they want to use. This is done through a thing called the chooser. By default there are seven global interfaces that you can use and there are over 30 other custom ones that may be used as well.

-There are also custom options that may be added and built in through your corp-wide settings. So once a custom page has been built you can actually add that to your chooser so that you could use that as your homepage.

-Any of the other sub- homepages could also be set as your default interface or landing page.

-There are also a number of themes which are pre-set color structures. You can modify your own or select from our pre-sets. Basically it is custom look and feel all the way around.

-Some of these presets include things like classic look, blue pastel, geometry, Snow Owl theme, etc. Some of the interfaces like Snow Owl have hundreds of sub-settings to dial in your look and feel.

-Because we allow color and theme changes there may be white label options that have their own, unique look and feel due to 3^rd party vendor white labeling.

-Currently custom dashboards are done on a per corporation basis. You come up with the different things you want to be displayed and shown. You work with a developer and they build it for you to your customized specifics.  

-More things to come! =D 

4.37 - Invoices

-Very flexible

-Must be created through the shopping cart (the building zone), once it is done & stamped as an invoice it is in the database, collect money (or money still owed, or partial payments), mapped to financials, deposited

-Invoice hold lots of info: COGS, customer info, payments, revenue

-Invoices feed P&L, they also feed inventory levels on Balance Sheet

-Potentially tied to payroll if you are doing commissions

-One of the most used pieces in the system

-Can by reoccurring as well

-This is one of the Main 12

-Internal parts ticket - taking products & services and moving them around - internal ticketing

-Also deal with sales taxes & accounts receivables - receivables mainly come from unpaid or partially paid invoices

4.37 - Invoices

Understanding the Basics:

Invoices are very flexible, one of the 12 main players and one of the most used pieces in the adilas system.  Invoices are the means to track products or services you are selling.  It contains a record of the goods you sold and the amount owed to you for your products or services.  A great deal of information is held on an invoice, such as: COGS, payments, revenue, items sold, customer information, etc.  

Invoices feed the P&L (Profit & Loss) as well as inventory levels on the balance sheet, they effect inventory counts and create your accounts receivable.  Whether money is fully collected, partially paid or still owed, this is mapped to your financials in adilas.  There are 6 invoice types that can be used in adilas: quote, counter sale, customer invoice, internal repair, transfer, and transition invoice.

Invoices are created in the shopping cart - this is the interface to build an invoice.  While in the shopping cart you are in a construction phase until you proceed to “checkout” when it then becomes an actual invoice in the system.  To create an invoice from the homepage click “Start New Cart”, or from the Invoice Homepage “Create New Cart”.

Getting Started:

Suggested Permission & Settings:

Permissions:

Basic Use:

System Search: “Invoice”

System Basics: “Start New Cart (Invoice)”

“My Cart Favorites”

“My Quotes”

System Reports: “Parts/Inventory”

System Assets: “Basic Quotes”

“Basic Invoices”

Admin Use:

System Reports: “Parts Admin”

System Assets: “Admin Invoices”

Related Pages & Help File Links:

Start New Shopping Cart (Invoice):

https://data0.adilas.biz/top_secret/help.cfm?id=144&pwd=cart

***View Cart Help File: Great help file if you are spending any amount of time creating invoices.  This will help you with things you need to know about the shopping cart.  This will teach you about how to get things in and out of your cart, this is where you can learn about the other invoice types, how to deal with aspects contained in invoices, cart logic, saving your carts, big ticket items, applying discounts, and much more.  You want to take the time to check this file out! ***

https://data0.adilas.biz/top_secret/help.cfm?id=143&pwd=cart

Add Item to Cart:

https://data0.adilas.biz/top_secret/help.cfm?id=146&pwd=cart

Invoice Homepage:

https://data0.adilas.biz/top_secret/help.cfm?id=147&pwd=invoice

Printable Invoice: (after it is now an invoice in the system)

https://data0.adilas.biz/top_secret/help.cfm?id=149&pwd=print

Add/Edit Invoice Line Items & Invoice Payments: (again, after you have an invoice in the system)

https://data0.adilas.biz/top_secret/help.cfm?id=155&pwd=line

Additional Content:

 -Graphics

 -Screen shots

 -Etc.

4.38 - Labels & Custom Paperwork

-Labels and custom paperwork usually deal with getting some sort of information out of the system and getting into a different format for printing and/or saving.

-We have a number of presets that are in the system that anyone can use. If you need anything custom, we can attach custom paperwork or label options to any part of the system. For example, if you needed contracts for invoices, or customer signatures for rentals or reservations, or labels for things like pharmaceuticals or chemicals, etc.

-There are a number of pre-built labeling systems inside the system that allow for direct labels for items, customer, invoices, elements of time, etc.  These labels may contain other output values such as: barcodes, descriptions, id numbers, names, date, quantities, locations, etc.  

-Custom labels and custom paperwork may be added to any section such as parts, items, shopping cart, invoices, customers, POs, vendor, employee (HR), etc.

-There are some corp-wide settings to help control some of the defaults for labeling.  

-Labels can be printed on an individual basis end to end, stacked, or custom layout. There are also options to print bulk-sheet labels. 

4.39 - Locations & Tax Settings

-The ability to customize your location specific tax settings

-Helps organize things by geographic regions or areas

-You can use virtual locations as well, which you can also name - example a retail side, a service side, etc.

-Corp-wide settings to custom name

-State, county, city and 5 customer additional ones per location so you can setup all your location specific tax settings

4.40 - Look & Feel (custom colors & navigation)

-We want your business to look and feel like you want it to. Some of this is done through settings so that we can speak your language. Some of it is done through visual interfaces and displays so we can make you feel more comfortable with using things and making things happen.

-The backend is like an engine but we can use function and form to help you get what you want and the look and feel that fits your needs.

-**Skin Your Engine Graphic - This has the motorcycle, van, sports car, semi-truck, UFO, all with the same engine.

-We have a number of presets. The one we first started on is called the classic - very simple, non-moving, but very powerful and dynamic. Some of the newer ones have more mobile, responsive ones, more sliding/moving menus, more modern technologies built in.

-We allow you to upload logos, alternate images, watermarks. You can change colors on virtually every single thing - backgrounds, roll-over colors, menu icons, buttons, link colors, messages, icons, etc.

-There are many different settings that you can setup for reports, navigation, and hundreds of settings that let you control feeders, footers, headers, custom navigation. Tons of options for corporation links, individual links, and other options for navigation that can be customized for your particular needs or setup for your corporation.

-Custom interfaces - we have thousands of pages which could be available to set as your homepage. If you need your own custom look/dashboard we can create that as well. Or we can blend those pieces together to get what you need.

More code review on the special accounts and special account tracking project.

Shannon and I got together over a Zoom meeting and worked on adding content to the adilas university elements of time for the adilas user guide. We were copying and pasting and chatting while doing that work. Mostly just a work session.

Analogies for defining deeper processes

Steve - Business is like a pirate ship - (who is the crew, are they good/bad, who is doing what)

Kelly - Business is like a body - (what is your tool to get to your goals)

- Goals and sub goals to get to the bigger goal. Adilas is just a tool. The people who use it are the ones making the goals.

- Talk is great, but we need to work on some implementations (getting out there and doing it).

- How do we implement the tool... this drives customer satisfaction.

- Adilas is so flexible that sometimes that is a problem

- Kelly was not saying don't be flexible... but we need a standard starting place

- There are new things that get launched all the time... without any training - this keeps deepening the need for good reps and consultants

- Unintended consequences

- Pressure and pain drives the current development cycle

- Everyone looks to a system to be "The" solution - systems can do a lot of things, but they can't save you from yourself

- Good physical control of the system is a huge key - stick to the plan and then go from there

- Many of the business owners don't even know what they are doing and then that translates to their business processes

- Helping to setup mini goals for the client... miniature options for success

- Addressing the physical before jumping into a digital realm

- Sometimes, a companies leadership will drive things right into a ditch

- Kelly has been doing some research on what other developers and companies do to help standardize things

- A good setup will make or break the whole deal... from there forward (what milestones are set and achieved and was there a good handoff between the software company and the rep/consultant)

- Accountability practices

- When a client has a question, have tech support use the user guide as their answer. As a side note, Shannon and Brandon are working on the adilas user guide.

- On numbering... instead of using a straight 1, 2, 3, 4... system (single numbers). Maybe think more along hundreds 100, 200, 300, 400... (lots of room to add and subtract as needed)

- Sub attributes - Kelly doesn't think that piece is fully "strong", yet we are building upon it. Steve thinks the concepts are pretty good. We just need to fix some of the coding pieces to help get reports, searches, and exports more up to speed.

- Steve was talking about the complexity of even servers - we had a meeting this morning that just dealt with servers (hours and hours). So many moving pieces and working with somewhat limited funding and talent options.

- Due to our current size, we almost have to say - in order to setup clients, you will need to setup an adilas specialist (in your company) and we will help train them. They will then help push that ball forward.

- Some of our squeeze points deal with persons who have the skills, talents, and time. We have masters like Steve, Brandon, Kelly, Daniel, etc.

- Start by defining the language that we are speaking - adilas is its own language - A good starting point - how do we communicate things, as a company

- People want organization and structure - being too thinly spread can be a big problem

- Allowing dreaming and custom options - we love it but that could be a problem - we may get in trouble by giving them too much or too many options.

- Maybe have them run with the standard options for 6 months and then talk about going into the custom realm - we have seen problems with people going into full on custom too quickly.

- Like an airplane - put the oxygen on yourself first and then help others around you - you end up selling what you do

- Setting clear expectations

- Maybe have some tools and education (training materials) about how to run a business and how to use the tools - Steve has had the ideas of putting on basic business seminars across the country. We could use the adilas tool as the backbone of the basic business training sections.

- We are seeing a bigger and bigger need for training, guided training, and even self training. This could be checked and/or quality assurance based on skills, tests, scenarios, sign-off's, etc. In traditional learning environments, there is standardization, testing, feedback, etc.

- What about using elements of time to help monitor the virtual checklist of what has been done and to what level?

- We do need a team, but at what level do we need to get to? That gets tough. People resources are always tough to manage.

- More training sessions - pros and cons to our current model - people want to learn in privacy - some of the training sessions get out of control (high jacked).

- Vocabulary and what things do and what we call things is a big part of the puzzle

- Some people don't want to know the why (that takes time)... they often just want to know how (show me quickly so I can do it)

- Education from gaming - 2 minutes or less - quick YouTube type mentality

- What kind of users are you? Do you like to self train? Do you want the easy button? Do you shoot from the hip (all the time) or are you a detailed oriented person who likes to organize and manage things? Great questions... help pre-qualify them in a way. The adilas system works best if the users want to put the things into the system (feed it) and play the whole game.

- Sadly, we can't fix everything... sometimes, we have to just go to the next person

- AI (artificial intelligence) and where things are going - automating setups and then automating tech support - keep going where things are going (skate to where the puck is going)

- Working on your company vs working in your company - focus on working on it and making it better

- What is the low hanging fruit and where can we start?

- How many touch points are needed to get someone setup? Who setups up the quote? Who turns things on? Who setups up things? Who does logos and watermarks? Who does labels? etc. - you get the idea - try to automate as much as possible.

- Somewhat of an internal bulletin board - who is doing what and what changes are going on in those shifts

- Just adding bodies doesn't always help things - events happen, how do you deal with that - there has to be an internal training process to take care of those things. It comes down to core things that are needed. Who is going to do those things (virtual checklist of what is needed)? Light talks about templates.

- Function vs fashion - where do you spend your time? We may not be able to solve everything but we can try to take the edge off of things. We want to show them what is possible. We want to present a nice package. We also want to make sure that things work (functionality) for them.

- Steve and I are trying to get out of the way. We are trying to fully get the process all setup and dialed in. Sometimes, if we are a pivotal part of the puzzle, it just doesn't happen, we are maxed out.

- Going back to consistency... We know we need it, we are trying to work through it and then actually using it. What can you expect every time? We also need a timing of those events... when should we do things, not just what should be done. There is a difference.

- Sustainability - We need to keep doing this (our business) for years to come... let's set ourselves up for success.

- Building our own processes to help with project management, task management, and to do list checkboxes before doing x (fill in the blank). Templates and automation processes. Help share the load.

- Things are changing super fast... nobody knows everything - we are currently letting different parties run with what they think needs to be done vs having one person giving orders and then getting a good return and report type process. Currently, it is somewhat of a community type effort.

- Why are we doing it and should we do it? Check this out before you jump in. Think of the consequences first.

- Kelly is going to help get a group together to help bring up the structure level and get the oars (some driving and direction) into Kelly's hands. We need a good driver who won't run us aground. We are going to let Kelly run with some things on the core management side of things.

- We are going to be starting at the very beginning and then going from there. A great place to start.

Pretty quiet morning. Dustin and I were on the meeting but mostly working on our own stuff. He did have me help push up a file to a server for testing, but other than that, just getting going and working on our own projects. I spent most of the morning working on the add/edit page for manual transactions for the corporation special accounts (things like customer loyalty points, gift cards, etc.).

- Parent items and fields vs sub inventory templates and sub attributes

- Browser issues - working in one and not in another

- Discount history and tracking all of those changes

- Styled cart and super limited

- Full Circle IM and using an API to create SMS (text messages). They would like to build out an API socket that would update Full Circle 365 on any client record changes. The best spot for this would be the add/edit customer action page. Of course, all of this would be contingent on the company/corporation having Full Circle turned on and mutual accounts on both sides.

As a side note, part way through the meeting, we had a guy from Florida join our meeting and gave us some information on their adilas account and some current and upcoming needs. I took some screen shots and got some contact info. I'll pass it along to the developer who will be working on this project.

Emails, tech support, and light project management and pushing info and details off to other developers. Back on code sign-off and building on the sub special account tracking project.

Bear 100 mile race meeting. They use adilas for tracking all of their runners and aid stations.

Went into town and had a meeting with the race committee. We went over a big to do list. Adilas will be tracking the runners again this coming fall. They, the Bear 100 folks, are also looking to redo their website and make it more mobile friendly. Another thing that may be coming down the pipeline is a trial version of 10 satellite GPS units and tracking the runners through the full course. That will be fun and exciting.

Talking with Josh and Steve. Josh has been focusing on the discount engine inside of adilas and the adilas shopping cart area. He has also been doing great on a high level tech support type role. He is actively helping and doing a developer level consulting for some of our clients. Very interesting twist. Sometimes our clients really need to speak with someone on a super techy level and Josh has been doing great there. I'm glad that he cares and is willing to help where needed.

Alan, Steve, Wayne, and I were talking about the transition to AWS. We took a bunch of new notes and added them to the attached document. Our goal for these meeting is just to flesh out and flake out some of the topics that need a little bit more information dealing with this transition from Newtek to AWS. For the record, there is nothing wrong with Newtek, they have been great. We are just trying to move to a bigger underlying platform and infrastructure. Good stuff and progress is being made. We set up another meeting for mid Monday morning of next week. Trying to get through our list of bullet points.

Working with Dustin. We were having a problem with submitting bulk form data and then the system not maintaining the correct sort order. It was still doing all the right stuff, it just needed some light refinement. We worked on submitting things in bulk, then resorting it, and then doing the normal actions. Good stuff and a great session.

See email from Ian on ideas. Maybe look into a new system wide tool vs a single custom page. The email has a date of 3/25/19.

- Who can help Kelly? She needs access to a developer.

- One of her main requests is getting data out of the system. One page that she would like is a full parent inventory with all flex grid fields. See the top_secret/custom/full_customer_list.cfm page for a sample that does the same thing but for customers and flex grid.

- Pieces of pie analogy - and who gets access to those developers and how do we get everything tied back together.

- Symptoms of the problem - a non whole-listic approach

- Kelly is having to take the information out of the system and run her own reports

- Two main parts that Kelly wants tracking money and tracking inventory

- What are the minimum levels for a code developer? Looking for talent. Kelly and I talked about beginners, intermediate, and advanced developers.

- Project management software for adilas

- We need money and funding to keep going

- We need to focus on our own system and get it across the finish line as a product

- The model of independent consultants and/or developers can get very scary - the scary part is the inconsistency of how the money comes in - somewhat of a feast or famine type feel

- Developers: Wayne, Alan, Eric, Calvin, Bryan, Shawn, Josh, Dustin, Brandon, Will, Steve

- People believe in the tool and like what they are doing

- In order for adilas to get bigger, we will have to change some things

- Revisiting the entire business model

- Investments - pros and cons - period for two year (funding numbers)

- Let's setup a whiteboarding time and come up with a new model

- Steve and I were talking about data normalization - reporting systems (data pushed to them) - display systems (data pulled to them) - push and pull type technologies - what is the outside company's purpose? Are they a reporting agency or a menu and display type agency?

- Steve had some questions that were dealing with the application type id flag and setting that on vendors. Basically, he is introducing a new variable to help flag certain vendor records as inventory only vendors vs normal expense/receipt or vendors for paying bills.

- Wayne jumped in and had some questions about out API sockets, rest API's, and helping to standardize things. We talked about the Swagger Editor and some of the different standards that should/should not be used. Internal and external API sockets. Wayne was also talking about using Amazon Lambda functions and doing some API socket stuff from there.

- Steve and I were talking about our goals and where we want to go. Good conversation.

- We also talked about white label options and how that could play out. Even options on internal and external white labels.

- Around 11 am, Alan, Eric, Wayne, Steve, and I had a meeting to talk more about the transition over to the AWS stuff. We were using a small Word Document as the outline for topics and questions to go over. I was scribing and the guys were giving their input and ideas. See attached for the latest working document. Lots of good notes. There is still a lot of work ahead of us, but the future looks bright.

- After the meeting, Alan and I spent about 1/2 hour looking over his current project. He is working on automating merchant settings and reoccurring invoicing. He showed me some of his code and we did a brief overview and looked at some of the new reports and functionality. It is getting pretty close. We also talked about custom black box code and where we want to go from here. It is super awesome to be able to do custom work, but there is a few hidden costs to it.

Met with Bryan and we went over some things. We did some code sign-off and merged in a branch of new code that dealt with exports for sub inventory. The new exports have two new fields. They are the sub barcode and the time id per sub inventory package. After that, we made a small fix to a cross crop page that helps create new items in the invoice to PO section. We also talked about an API socket error and brainstormed on ideas and possible fixes.

Paying bills, tech support, and recording notes. Also had to login to the data 0 server and call tech support about the server not responding. Not sure what was going on there.

Getting started and getting all caught up. Steve had some files that needed to be merged in. Wayne popped in and helped to answer some more questions on the transition to AWS. See attached for the latest notes. We are calling that transition document done, at least for now.

Working on merging in code for Steve. Also got a call from Calvin Chipman and we chatted about some things. Lots of moving pieces. Steve and I got back to the code merging and while we were working, we were chatting about some of the great people that we have and get to work with. That is awesome. We would love to do another training event, here soon. Even if it ends up just training our own team, it is worth it.

Dave Forbis called in and I chatted with him for bit. He is on the outside edge, but he could be a great asset when the time comes. He has a number of customer relationship and project management skills that could really play into the mix, if the conditions were right. Great potential.

4.41 - Manufacturing (changing or modifying inventory)

-Taking an original or raw product and making into something else, anything that you are altering & selling as a product

-Anything mixed, blended, bent, changed, tweaking or making pieces of inventory

-It is tied to inventory - so it gets pulled in on the PO side

-Can be manufacturing big ticket or small items

-Friends with recipe/builds

-A request PO - like a quasi PO, or a quote, on order - to make

4.42 - Marketing

-Once you have all of the data from your day to day operations and accounting - think of all the power you have. We can use the massive amounts of data in your system to connect with other companies that can help you manage your marketing in whatever ways you need.

-Presently we have all the data. We do not manage the marketing but can connect you to third parties who are focused in various marketing aspects. We provide you with great resources for business intelligence as you can access all of the data in the system.

-We have a number of reports, charts, graphs that can visually show you data. If you need something customized we can build that for you.  

-We have all the data. You can pull reports, trends, export things, and use your data to improve your work flow and your company. 

4.43 - Media/Content/Files (physical file uploads and referencing)

-A Library to organize content

-What are your files & media? Contracts, video, drafts, drawing

-Files on your local machine, on a network

-You can tie them to any of the 12 players or you can just categorize & organize them

-Can tie to individual items, to groups or to everything

-Cataloging, referencing, organizing, logging, tracking your pieces, pulling in & connecting any type of content that you want

4.44 - Merchant Processing - Credit Cards & Financial Solutions

-Merchant processing is a great addition to any business. This allows you to process any transaction with credit card or digital payments. This feature is not required to use our system, it is just an available option.

-You have to have at least 3 players with merchant processing. You have to have a POS (Adilas), a gateway or credit card processing company, and then you have your banking entity which is your merchant or banking entity. Some big companies actually fill multiple of those roles but all three of those components are required for merchant transactions.

-**Flow chart diagram for Merchant Processing

-We do not require that you deal with a certain merchant. We do have a number of merchant gateways that we have already coded to. So if your bank already deals with these gateways you can be very easily integrated.

-We also have a number of other closed circuit payment options. This is basically where you load money on to a card or account and then you can spend that money at participating stores.  

-If you have a specific gateway or banking entity that you would like us to work with. We need to be notified of that, we will do some research, get you a quote, and built the pathway to use that merchant processing option.

-Merchnat processing may be used in internal POS/shopping cart options, online bill pay, payments on account, external eCommerce, reoccurring invoicing/payments, etc. 

4.45 - Mini Conversions (buying, selling, & tracking inventory - units of measure)

-When you deal with parent/child inventory - this is usually a placeholder at the parent level. Then usually some sort of sub-batch or group to create the child inventory. Mini conversions are actually breaking that child inventory into different units of measure to either be used, consumed, or sold. Mini conversions is only at the sub inventory level, this is not available at the parent level.

-An example is water - how do you get it? How do you sell it? If I sell you a case, that may be 12 bottles of 1 liter per. Breaking things into smaller pieces. Technically the same water could be sold by the drop, the cup, the pint, the gallon, the liter, the case, etc.

-Part of the plan with mini conversions is also being able to track who has what and what is available so that we can go back and forth between conversions. Going back and forth between conversions. So this will allow you to create or destroy conversions so that you can go back and forth as needed.

-Another goal of mini conversions is being able to track the hard to track inventory pieces. Right now there are some known areas that are tough - what is real, what is committed, promised, what is ordered online, what is in the shop, someone else’s shopping cart, warehouse, what is requested, etc. It gets into a way of micromanaging your inventory in a way that you are going to buy and sell it.

-It goes deeper and deeper, you’ll be able to set prices, you will be able to also create some standard things that you can use over and over again. You will be able to setup how internally manipulate these items as well as prices, structures, and a whole chain of custody that is built into mini-conversions. Where did this product come from, what happened to it at every stage, what is it being used for and put into now, where is it sold, split, etc.  

4.46 - My Cart Favorite Buttons

-These are basically preset code that help you to sell things, organize things, or create visual checkout processes. You can tie them to existing searches, exactly to specific items to tie to the cart, you can tie them to recipe/builds, or even stack, group, or turn them into tiered pricing models.

-Originally they were designed to be user specific and they still can be. However many companies want them to be one master set for the company. Either way will work and you are also able to copy, view, and share buttons as needed.

-As far as organization goes, you can name them, add photos, stack them, group them, color-code them. You can tweak out your buttons to whatever fits your needs! For example say you wanted a certain group of items to be orange or purple, or if you were a deli you could have a button that said Desserts and nested under that button you could have pies, cakes, cookies, sodas, ice creams, etc.

-There are multiple different kinds of buttons - you can have Flash buttons or HTML buttons depending on your interface. Certain devices, operating systems, or browsers work better with certain kinds. For example an iPad does not allow Flash and would use HTML. Switching between button types is very quick and easy.

-Some companies even like to run their entire POS with just the buttons directly or something called a split cart mode that allows them to see and click on their buttons while viewing the shopping cart screen.

-One kind of button is called a smart group which allows you to setup your own tiered pricing structures. This can go as deep as you would like to go and one of the secrets behind it is rules and assignments. The rules are where your price breaks come in, typically based on a quantity type model. The assignments deal with which items or product are associated with that set of rules. All of those are one to many relationships and that button is able to hold all of the related functions you have set for that button.   

4.47 - My Stuff (personal settings & options)

-My stuff usually deals with things such as clocking in/out, checking your hours, updating your own username and password, setting your own user defaults and presets - so that you don’t have to make certain selections every time, etc.

-Personal settings are sometimes at the lowest, most detailed level. The highest level is the corporation or world setting, then a group or player level (like parts or invoices), then page level settings, and then one of the lowest things are personal settings. Things that you can set that can best help you out.

-Some of your personal settings deal with your own default homepages, a specific shopping cart type/style you use, cart favorite buttons you use, if you use the queue, if you’re tied to a specific location, etc.

-Also within your personal settings you can view your own history - what did you touch, work on, effect in the system, what were your logins, etc.  If your company is running payroll through Adilas you can also view your paychecks and paystubs.

4.48 - Objects & Data Over Time (theory & concepts)

-Creating the data as objects which are then able to be moved over time and mapped back to, because things are tracked as objects, they can be mapped, tracked through time, you can go back & see where things were at certain time

-Also everything that is tracked over time you can go back and see the story, it really helps to tell the story

-Objects allow for depth, diversity, detail

-Everything has a life cycle: it starts, things happen to it (depth), and then things can be mapped to it & it concludes its life cycle or 

4.49 - Orders

-On the quote side for customers (invoice side)

-On the request side for PO's

-Already started but no monies are owed, paid yet... partial, quasi status

4.50 - P&L - Income Statement

-Profit & Loss - a financial document

-Feeds the balance sheet

-2 calculations (Gross profit & net profit) & 3 main pieces (Revenue, COGS, Expenses) - (Revenue & COGS which then derive your gross profit, then after your expense you have your net profit)

-The P&L is fed by the line items from the invoices, deposits & expenses

-The P&L is 100% automated from the objects, so when you want to adjust something from the P&L you go back to the source and you can re-categorize or whatever you need to do with it so that it ends up in the right place

-Time range on it, can look at date ranges, by the end of year, it is your fiscal year

4.51 - Parts/Items (general inventory pool)

-What is your product? Is it actual product? Is it services? What are you putting on your invoices?

-Parts are generally tied with PO's (incoming - the way to get something into the system) & invoices (the way to get them out of the system) sold to customers

-A place holder is created in the system for the parts by bringing it in on the PO, (so the pipe analogy to track incoming and outgoing) by tracking this, then you can roll call on the pipe at any given time, this place holder holds your name & cost (which can also be adjusted) it becomes the unit, so that you can track and roll call the outgoing and incoming pieces

-This has a number of corp-wide settings attached so that you can name what you want to call these - parts, services, widgets, etc. name it what you want it

-Parts & inventory are eCommerce ready

4.52 - Payroll, Commissions, & Time Clocks

-Paying your employees

-Payroll tax settings, user tax settings

-Deals with people, so it is a buddy with employee/users, to time clock (clocking in/out), also ties with invoices if doing commissions, then it also ties to expenses for paying the employees

(From 4.13 Departments section: A user is assigned to a department and then set up for payroll where they can have pay rates assigned, personal tax settings and other settings saved for them in that department. This provides great flexibility, because you could have the same user assigned to different departments, receiving a different pay rate depending on what job or “department” they are working in for that period of time.)

4.53 - Permissions

-Wanting to control who can play where

-"You don't want the bull in the china shop."

-Making sure people have the ability to do what they need to do but not allowing them to work where it is not needed

-Can give temporary access and then turn it back off immediately

(-From admin file: The beauty of adilas is that you can give each individual the permissions they need to do their individual jobs, whatever that spectrum may be.

grant or deny access to your users as to how they are able to play and function in adilas based on the permissions that are assigned to them. (i.e. employees, members, etc.) other users in where they are able to work in adilas.

How access is permissionable, which allows them to maintain control and structure in their organization. It also allows them to access or permission access for various responsibilities and information.

The permissions are color coded, so that you can see visually as well as by reading the description which permissions are more basic and which are more admin oriented.)

Help File: to the permissions page

4.54 - Photos & Scans

-Can be attached to any of the objects (or individuals) for the 12 main players & can attach up to 100 per individual

-Tells your story, it's your evidence, your trail, document, story, picture, hand scribbled note, whatever you need it to be

-Selling tool

4.55 - Purchase Orders (PO's)

-Ways to get things into the system

-An inventory tool - an inventory manipulator tool, so you may use it internally just like you would use a PO to bring in product from a vendor

-PO's flow to the general inventory pool, often come from a vendor, but as mentioned before can be used internally

-Manufacturing all done through PO's

-Eventually moves to the A/P so that someone can eventually get paid (you can also have $0 PO's for internal uses or services & such things), buddies with vendors, parts & eventually expense/receipts

-One of the 12 main players

-PO's you can name as well - out of the 6 available you can name 4 of them

4.56 - Quick Search

-One of the quickest ways to move around the system or reference things, almost like teleporting

-Bounce & jump all over - once you learn the quick search it is your buddy, it is how you get around

-Two flavors: More expanded version on the classic homepage & then there is the smaller version on the top of every page 

4.57 - Quotes

-Related (brother or cousin) to an invoice -

-A saved shopping cart - so you can restore it back to the active cart or edit things before it is finalized for invoicing, you can send it out as a quote so you can still work with it... you aren't quite ready to finalize & commit it yet

-So it is a definite buddy with customers & invoices

-Quotes can hold stock units, elements or time... basically anything that an invoice can do, a quote can do, except progress through checkout, then you will have to restore that to the cart & finish out the process as an invoice

-Quotes a prep/holding spot or to quote a job/service

-If you are just learning adilas, this is a great spot to spend some time b/c you don't hurt anything at all. It doesn't alter any sort of financials or inventory or anything so it is a great resource for practicing! :)

4.58 - Recipe/Builds

-Great tool for any repetitive processes - almost like coding or prepping the system in a way - groups, kits, choices, options, things that go together (buddies, add-ons, accessories)

-Can almost create a virtual walk through list or a questionarre so you can cover everything with a customer

-Currently 2 flavors. Flavor 1: Build & Sell (Invoice/Quote side)

-Flavor 2: Build & Hold (PO side)- like miniature manufacturing

-Can be tied to buttons

-You create the recipe at your lowest common denominator (essentially) then you can use a yield multiplier to create as many recipes of that thing as you need

4.59 - Reimbursements (REI's)

-An expense/receipt with a special flag - it was already paid but not by your company. Someone else paid it but you need to pay them back. So this exists but you need to pay some else back.

-Reimbursements - each one you say that you are going to pay off (and you can pay off many at one time), has to be paid in it's entirety whereas splits will allow you to do partial payments

-Can pay back multiple reimbursements at a time - so you can stack multiple reimbursements with one check (or one form of payment)

-Depends how rigid paying it back is between here and splits

4.60 - Reoccurring & Automated Options

-We have a full section that allows you to do recurring invoices if needed. Basically you would setup a master invoice, setup a schedule of when that needs to happen, then it rolls itself into an ongoing queue that you are able to view and process. Currently this process does require light manual babysitting, We want to provide you the opportunity to make sure that everything is still as it needs to be. Oft times things need to be changed or adjusted, change of service levels, or products.

-Reoccurring expenses are fully automated. Once these are setup they will automatically run based on the scheduled date and time.

-Another thing that deals with recurring is recurring elements of time. This one is special, you create the original element of time and then you have the opportunity to duplicate on a bulk fashion up to one year out from it’s creation. It’s recurring format is based in a calendar format with easily select-able days, weeks, that you can click on and have that event duplicated and pushed into the future.

-There are also some automated options such as automatically emailing things, certain states require certain syncs or updates that function automatically, if there are certain tasks or reports that you need we can automate those, there are many options for custom options with automation. At times certain business processes need to trigger other things in the system, so we can specifically code things to happen just for your business. Eventually we will have automated texting options as well where you will be able to setup reminders and such. 

4.61 - Sales & Promotions (see coupons & sales campaigns)

-This deals with selling your inventory - whether it is live where the customer comes in, they order online, or they somehow respond to an ad.

-This is part of your marketing arm. Most of these transactions will take place on quotes, invoices, and online eCommerce.  

-A lot of the current tools deal with being able to set and control discounts and record which campaigns they are tied with.

-There are ways of doing discounts that are manual, in-line, automatic, pre-set buttons, etc. There are also reports to help you view and see these discounts that have been given.

-One of the big tools is something called the discount engine. This allows for discounts based on vendors, part categories, specific dates and times, you can exclude or include certain items, etc. After being setup these discounts occur automatically.

-Additional marketing and discount ideas are still in the works. 

4.62 - Saved Reports (custom report favorites)

-There are tons of reports and options straight out of Adilas. You can run these reports at anytime. If you have something you want to run all the time you can use the save report feature. These buttons are spread out through the whole system.

-Most of the advanced searches have save options. What this does is remembers all of your search criteria and then allows you to name and sort your reports. These can all be accessed from a special page called my saved favorites or favorites for short.

-Small technical note on each favorite - behind the scenes we actually store all the settings and search criteria in a database format. Once this happens it actually creates an id number and allows you to get to the same report by using the id number without re-specifying all of the criteria again.

-You can actually name your own reports, you can assign them to specific users, you can make them private, you can sort them, and you can view them at any point in time. There are no limits to how many different reports you can save.

-To edit the search criteria simply browse to your favorites, click to view, then look for a button or link that says refine your search. At this point it will take you back to the original form and populate it with the stored criteria. Simple change the criteria, resubmit it, and if it looks good simply find the save report settings button.   

-You can create a report, modify it, and then save it as a different report. So you are basically creating multiple reports off of an original report.

-You should be able to save reports for almost all of the 12 main system players.

4.63 - Settings - Corp-Wide

-Corporation look & feel, how you kind of set up your world; what do you buy, sell? What do you call things? What do you call customers?

-Foundation level of setup for look and feel, to speak your own language (to make you comfortable), to help accomplish the goals of your company or industry

-Change once, use many - from changing it in the corp-wide settings it cascades throughout your entire corporation

-We will continue adding more and more custom settings (History: we started out with 6 and now there are over 100)

4.64 - Settings - Group Level

-Basically the group level settings deal with our 12 main players:

l Customers

l Invoices

l Expense/Receipts

l Parts & Inventory

l Quotes

l Employees/Users

l Elements of Time

l Vendor/Payee

l Deposits

l Purchase Orders (PO’s)

l Stock/Units

l Balance Sheet Items

-These settings are things that help us set up custom naming and usage for these main players. Of these main groups how do you want to play, what do you want to call them?

-Many of these currently exist in the corp-wide settings: what do you want to call your customers? What naming conventions do you want to use? What options do you want to toggle on or off? What fields do you want to use? What special features do you want to use? What handling options? Rounding? What flow do you want to use?

-Currently some of these group settings are mixed between page level settings and corp-wide settings. Our goal is to eventually break them all out independently according to their group (i.e. invoices, customers, etc.).

4.65 - Settings - Page Level

-Settings that only deal with certain pages or sections. This is very common to help with defaults, mapping, decision making, and how expanded or contracted pages look, feel, and react.

-If there are page level setting you get to them through a gear icon or a button/link that says page settings. These are very common in the industry specific pages  or pages that can have custom industry specific options.

-As a technical note - most of the page level settings are stored as a JSON object. So technically we can add as many as we want in one single entry - this could be corp specific, user specific. This is efficient because we can store it as one single object so when that page is pulled we can pull it as a single object to use whatever settings have been assigned for that page. 

4.66 - Settings - Personal

-Choose and set your default settings. So your default interface, banks, PO's, payment types, etc., etc.

-This piece will be growing like crazy... to eventually set up buttons so you can control your space, your settings, how do you want things to work, what do you want to show, do you want certain reports, settings..... you personalizing the system for your specific needs

4.67 - Shopping Cart

-The interface with your customers. How you sell products and services.

-One of the most flexible and critical pieces of the entire system.

-Highly recommend that you read this help file (View Cart) - it shows you multiple ways to get items into your cart, how to apply discounts, payments,

-All virtual memory - so nothing hits the database until it is saved as a quote or you go through checkout - then it becomes an invoice and hits the database

-So what that means is that you could change price and all sorts of stuff in the shopping cart and that does not affect the actual details for the item

-Non-linear... because it is held in virtual memory, you can go anywhere else in the system and it is still held in virtual memory - in it's own little container

-There about 30 corp-wide settings that deal with shopping cart and invoices - clear to disclaimers, show/hide bin numbers and other features, units of measurement, check out options, barcode options, payment options

4.68 - Special Line Items (system parts)

-System parts - items you do not have to bring in through a PO

-So the system gives you between 15-20 pre-set items you are ready to use

-Items such as: labor, discount, freight

-Pre-set tubes or place holders - system standard, you can turn them on or off but they are there for every corporation, a hard-coded item

-These have special back-end connections and mapping to financials

-They are controlled through a sub-section of the corp-wide settings, they are all unlimited as well, so they can be used over and over again

-Basically without doing any sort of PO you could start doing invoices with all of these pre-set, out of the box, loaded items

-Non-editable, so you cannot switch vendors, change things... you can only turn them on or off through the corp-wide settings

4.69 - Splits (payments made on account)

-Define Splits: if you had a bigger payment to pay for littler things - so payments on account or partial paying stuff

-2 Basic Scenarios: 1 - paying multiple payments on one item or expense; 2 - paying one bigger payment that pays for multiple little pieces - so using an expense to pay other expenses (a 1-many-many) (A video tutorial might be helpful to add in this section)

-A type of expense/receipt - either short paid or partial paid, so it is not fully satisfied on the payment portion - b/c of that it automatically routes itself to the A/P waiting room

-You can apply payment after payment until it is satisfied or you can wrap multiple ones together.... probably the most flexible when it comes to the expenses/payment section

-More flexibility in paying it back... can pay it back in multiple times

4.70 - Statements

-A snapshot in time of lots of invoices

-One statement can hold many invoices - kind of like a summation

-As soon as you create it, it is dead or a dead end - it is just a snapshot in time - it is just a tool so you can get payment or tell someone where they are at

-You can send them as a pdf

-when someone does remit payment you actually go back and apply payments through the apply payments section (a sub of the A/R waiting room) or through the invoices themselves - statements are just a tool to help you get that money

4.71 - Stock/Units (serialized inventory)

-This is one of the original reasons this system was created - this is where we started! :) Pretty cool how adilas really grew and came from this area - this is where the history starts (give a plug here).

-One of the deepest sections of the system and one of the most powerful tools inside of adilas.

-They deal with makes and models - it has organization, (inventory type, sub inventory type, make, model - adding corp wide settings so that you will be able to change those names)

-One of the main 12

-These are items that need to be tracked on a one by one basis, they are usually serialized

-It is part of inventory, they automatically allow for subs to be connected, internal ticketing (tied to invoices and parts), external repairs (automatically ties to expense/receipts for those specific items)

-They allow for photos, we can track location, age changes, and location aging

-Allows for the manager's checkbook or slush fund accounts

-Floor-planning is tied to stock units

-They automatically create a payable out for that base price when entered

-Can be sold and mixed with other items all on one ticket or invoice (mixed tickets)

-Can attach multiple customers to it

-You can work deals and payment options on it. They allow for setting up multiple payments

-Can be tied to payroll, commissions

-There is a LOT of depth here

4.71 - Stock/Units

Understanding the Basics:

There are many levels and sub pieces which allow for some of the This is where adilas started from and this area holds some of the greatest depth and power for data tracking.  This are contains many levels and sub pieces and can be

Getting Started:

Suggested Permission & Settings:

Permissions:

Basic Use:

Section: “Permission”

Admin Use:

Related Pages & Help File Links:

Payables Homepage help file: