all data is live and searchable
[reset this page] .
[historical web outline - entries by month] .
[adilas community funded projects] .
[contact adilas.biz support - email form] .
[help]
|
Adilas.biz Developer's Notebook Report - 10/1/2014 to 10/31/2014 - (74)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 2855 |
|
Daily Tasks | 10/1/2014 |
|
|
|
AU 2864 |
|
Daily Ideas | 10/1/2014 | -Use session variables to help with image folder paths. This will help as we add additional security. | |
|
AU 2923 |
|
October 2014 Monthly Recap | 10/1/2014 |
This was an especially exciting month for adilas in regards to brainstorming new concepts, ideas, and future direction. There are pages upon pages of documentation containing ideas and graphics about 3D tracking and accounting dealing with time, money, and space, sub inventory and cost controls (packaging & sub inventory tracking), sub locations and in-line extensions, and much more! Many exciting things are continuing to come and these projects will be developed and implemented in the coming months and years. An adilas rep sponsored the development of some additional Microsoft Excel exports including the P&L, balance sheet items, deposits, and subs of elements of time. Over 100+ changes of code were uploaded for images and security enhancements to my cart favorite buttons, photo buttons, and eCommerce aspects. Adilas sponsored a paid training event this month in Denver called “New System Updates and Advanced Backend Office and Accounting”. Project work continues on in-line discounts, bulk applying discounts, and continuing custom label and API projects. *We hope you are enjoying the adilas developer's notebook! Please utilize and explore the vast search capabilities of adilas to find more information throughout the developer's notebook. For further questions, or help, please feel free to contact us at: support@adilas.biz. |
|
|
AU 2856 |
|
Daily Tasks | 10/2/2014 |
|
|
|
AU 2865 |
|
Daily Ideas | 10/2/2014 |
Myself and an associate were talking in the car, going down and back to Orem. These are a few things we learned and were talking about today: -Seeking and bringing “truth” to what you are doing. Truth tends to radiate light and is recognizable when seen and spoken. If we base our actions, words, and presentations on truth, others will see and recognize those things. Sometimes that can be like hunting for gems in the rough. -Compound concepts – This was a topic that he was talking about. I loved the idea of compound or multiple concepts working together. The reason he was talking about “compound” was certain concepts have inter-relationships between pieces. If you take them apart, they fail or don't work. However, if you use them in combination, they flourish, prosper, and grow. We talked about tons of things both spiritual, gospel, and business. Lots of fun things here. -Be considerate of other people's time. In a way, how you treat their time or interact with people has some underlying tones about your love or care for that person. Granted, that may not be a perfect model, but it was fun to think about time as a gift. Then how we respect that gift of time and how that can relate back to love. This was a fun compound concept – time and love. -Just for fun, here were a couple other topics we had fun with... Compound Concepts – The God Head (The Father, the Son, and the Holy Ghost), Faith, hope, and charity; revelations, obedience, and intelligence; Tasks, goals, and dreams (the big picture), relationships, between things (objects and data) over time – how does time play into relationships? We also talked tons about inter-dependencies inside of the business world, systems, adilas, etc. Fun topics! The key was going back to the idea of a compound concept.... by itself, it needed something else. Together or in combination, it grew, thrived, and flourished. Pretty cool! -Different Business models: Separated Model vs Systemized Model We are seeing more and more need for the following – notes from an on-site setup – no specific order: 1. External alternate id numbers to link between different systems – see possible notes on application flex grid, normal flex grid, and more in-line database fields and options. Search adilas university – developer's notebook entries. 2. Certain line item tables even need external alternate id's. This is true for PO line items, invoice line items, quote line items, expense/receipt line items, and even deposit line items. [External alternate id's for line items] 2.1. Quick note – flex grid tie-ins only tie to main groups. Currently nothing exists for line items that need subs or special data fields. 2.2. We had an instance today (during the setup) that we needed potentially more fields per line items. We were transferring items from area to area (locations) and needed to record lot numbers, external PO numbers, and packaging slip numbers all on the same transfer invoice. These pieces of data related to the line items not the main invoice. 2.3. Some of the external alternate id's come from other systems, but need to be tracked as things happen and take place. Here is an example: Say we got in multiple batches (lots) of product for different PO's. We then want to move the pieces that have been okayed for production but the different pieces come from different external PO's, each with different batch or lot numbers. Right now, I only have one field that can hold an external id number such as an RFID tag number or a batch number. I don't have enough fields to also record external PO numbers per line item. (Think chain of custody or chaining things together to show a relationship or an ongoing relationship...) 2.4. Being able to add both one-to-one and one-to-many relationships to line items would be cool. We are already planning this as part of the sub inventory and cost controls (packaging) feature that is coming up. Our plan is to use a sub of elements of time to hold the sub inventory pieces. What other options are available? Think simple to more complex or dynamic. 2.5. It might be possible to expand the existing flex grid to allow for dynamic connections between main player groups and their line items. We could do this by adding a new column called special_line_id. This would be a temporary patch. However, this would cause us to rethink naming conventions, flex grid titles, and even queries on existing flex grid pieces. 2.6. As long as we are talking about the flex grid and flex grid tie-ins, what about special data types. Currently,the flex grid can extend and connect pieces in the system. We can name different fields and set up light properties such as open entry, drop-down menus, or both open entry and a drop-down. What about dates, date/time stamps, numbers, decimals, and bigger text fields? Currently, all flex grid fields are text based and can only hold up to 100 characters for both titles (alias names and actual data columns. The flex grid tie-in system is awesome, but it may be time for a custom system or custom upgrade option. This doesn't mean the flex grid will go away, but it may mean that a new dynamic system may be needed. Something even bigger or more robust that can be configured and setup as needed. I'd like to make the new feature as light, flexible, and dynamic as possible. Instead of a preset and coded database – existing flex grid tie-in system – what if we allowed each corporation to build extensions. 2.7. Real extensions – Currently, the flex grid tie-in system allows for new data points to be virtually added to a single individual player inside of a player group. The records are added independent of the main individual record. We also show the flex grid tie-in records in a separate spot on the associated sub pages. What if, we allowed new fields to be actual extensions of the main and/or line databases? I'm talking about new fields that appear to be in-line or fully connected at the hip with the original tables, entries, and queries. For example: Say I wanted a packaging slip number, an external customer PO number, and an expiration date to be assigned on every invoice. I only have a couple fields that are built-in to the invoices table. I would have to use flex grid (after the fact) to tie things together. What if I could set up any number of new data fields, assign them a name, sort order (where and how they show up), a real data type (date, time, numeric, decimal, text, etc.), and even have them show up as in-line options? That would be so cool! When I do my invoice, I would literally see those fields as options on the view cart page, edit main invoice page, printable invoice page, etc. The extensions could then be shown back to the user in-line or in-place. (Real In-line Extensions) 2.7.1. Quick note on these extensions.... we also need a field that helps us know instructions, relationships, required/not required, defaults, ranges, and expectations. If these fields are really going to play, we need them to be more rigid as far as what goes in them as opposed to an open entry text field that doesn't have any rules. 2.7.2. If we use real in-line extensions, we could also show and use them as part of the normal query and/or search filters or search criteria. Extension means an extension (dynamic one to one relationship). These values will be held in a special table, but will be treated as if they are part of the original table. This includes searching and filtering data. If a user is looking for a specific value, we could check the extensions and then use the results to filter the main core or existing tables. If no extensions are being searched or filtered, we could reverse the process by searching the main table and then filtering the extensions table base on the results of the main search. Extensions means an extension... 2.7.3. Real In-line extensions could be used on both the main group levels and the line item levels. That would be really cool! This could solve a number of custom field requests at almost any level. 2.7.4. What other tables besides main groups and line items? What about payments? What about subs of time? What about extensions of the flex grid tie-ins table? What about extensions of photos or media/content tables? What about extensions for time cards, payroll, etc. If we are talking about table extensions.... where do we draw the lines? Or do we draw lines? This could be a great way to extend any table... I know that means more code all around the site, but think of the potential. 2.7.5. Table extensions would have to be corporation or world specific but could technically be applied to almost any other main or sub table. This would allow us to keep the core engine virtually the same but it would allow types and functions to be applied like legos to any part of the system. That could be really cool and would make our product super flexible. 2.7.6. I see at least two new tables that are needed. They are the extension names and settings and the extension data points. The names and settings will hold all assignments, names, instructions, data types, defaults, rules, etc. The actual extension data point table will hold a number of pre-configured fields that just hold the data. In a nutshell, the actual extension data points table will be a plain white (vanilla) container. It will be general fields that can hold specific data. It will be the names and settings table that will help the general data points table know what to do. There may be some other supporting tables that go along with this, but these two main tables will be the core of the real in-line extensions. 2.7.6.1. Tech specs for the extension names and settings table: (General 1st round planning): please see scans in photo gallery for details 2.7.6.2. Tech specs for the extension data point table: please see the scans in photo gallery for details 3. Front-end and backend programmers – we are seeing a bigger need for tools for both front-end programmers (point and click interfaces and settings) and backend programmers (people who build the features and pages). The backend programmers are the hard core adilas developers that work in code all of the time. The front-end developers are the reps and consultants who help end users and companies to set up their corporations or worlds. Front-end programmers use existing tools to configure and tweak permissions and/or settings to get the desired outcome. We are seeing a need for both types of programmers. More and more tools are going to be developed for the front-end programmers. This seems to be the current trend. 4. While on the on-site setup, we were asked about moving product between bins and pallet docs (sub locations). Basically, in a warehouse type scenario moving inventory within a defined area. For most retail facilities we use the normal bin # field for the items. There is a need for tracking things on a sub level within a certain bigger area. Currently that option doesn't really exist. This could be a sub of time and I think a good fit there. It may also require the role call page to be built. What are my connections? I think that a flex grid solution could also be used on the transfer invoices after the fact. This entry has been all over the place but I do think that we have a couple of options. 5. Possible combo pack between the normal flex grid tie-ins and the future proposed application flex grid tie-in application. What if we used the real in-line extensions (see item 2 in this list) and extended the flex grid with in-line extensions. That could be pretty cool. That could be the best of both worlds in a fully customize-able level. That could be the application flex grid. Capable of connecting even outside systems together with special mapping, etc. Lots of options. 6. We had a request to be able to track hours worked (labor hours) per job or per Customer PO. This seems like a job for elements of time. It sure would be cool if we could attach sub time elements to any object without having to go to the main elements of time section. Here is one way it can work... A main element of time could connect to a single individual data object, and that could create a link to time. Then the subs could be added at will from the individual data object (a PO, an invoice, a customer, a stock/unit, etc.) This could be done very easily. Just add a new template setting called individual data connection. We could then use sub dates and time very easily. Basically, add an app_type_id and main_id field just like media/content and there you have the needed relationship between time and the single data object or player. It could be that easy. That would be super cool. 7. We really need round two of elements of time. It has so much potential. 7.1. Prepped but unfinished subs or functions of time: Additional Sign-Off's – Subs Additional GPS or RFID Tag Tracking – Subs Additional Payroll/Time Sheets – Subs Additional Notification/Reminders – Subs Additional Tie-In's/Assignments/Pools (“any” person, place, or thing) 7.2. See this URL for help and definitions of proposed pieces of the elements of time section: - https://data0.adilas.biz/top_secret/help.cfm?id=391&pwd=sub. This whole page talks about subs or functions of time 8. We are seeing more and more needs to be able to copy existing pieces in the system. This could be recipe/builds, users and permission settings, and even transfer invoices between locations. Each of these sections need their own features but basically people want to set things up once and then copy and paste or be able to see the next one up quicker or make almost an exact duplicate with only minor tweaks. Here are some other pieces that would be cool if we could copy them... 8.1. Be able to copy expense/receipts 8.2. Be able to copy balance sheet items 8.3. Part or items 8.4. Stock/units 8.5. Be able to copy users and permissions 8.6. Be able to copy locations and tax settings 8.7. Be able to copy Recipe/Builds 8.8. Be able to copy elements of time 8.9. Be able to copy smart group rules and assignments 9. Be able to point and click and create your own invoice and quote templates. Imagine an invoice template that you could set what to show/use, what to hide, what order to show things in, and what placement for the different pieces. Be able to turn features on, off, name the templates, and other options. As a note, elements of time already use custom templates – unlimited with point and click options to name the types of time and control the subs or functions of time. It already exists, just not for invoices yet. 10. We had a request to be able to speed up transfers and be able to carry over batches, lots, and RFID tag numbers. People want things tracked in detail but they also want speed. -Side note: This session has been more of a brainstorming session than just recording the notes from the setup... I got home late and just scribbled some quick notes on a post-it note. It is now 10/4/14 (two days later) and I'm trying to record the notes in my notebook. It's the little tiny note on my post-it note that is sending me off on this brainstorming session. I am so grateful for tiny little notes and the ability to write things down. Without that, we would skip and forget a lot of stuff. Anyway, just a small side note. |
|
|
Adi 883 |
|
Custom Code - Metrc Home for Kindman | 10/3/2014 |
Completed a custom page that replaces the current metrc page so that the weight field will multiply the quantity field to return the correct values. custom_kindman_metrc_home.cfm |
|
|
AU 2857 |
|
Daily Tasks | 10/3/2014 |
|
|
|
AU 2866 |
|
Daily Ideas | 10/3/2014 | -See other notebook for some good notes from General Conference. Lots of notes on compound concepts. | |
|
|
Adi 884 |
|
Custom Code - New Age - Expanded P&L | 10/4/2014 |
Hi Steve, Hope you are well. I left you a vm on Thursday regarding New Age & the reporting they are wanting. I was wondering if its possible to get a report for the P/L that can include all details of every account. It would be a very lengthy report but Dallas said they are willing to pay for it. Also, I've been sick so I haven't called the attorney but I will call her on Monday. Thanks & have a good weekend! Kath --- Contacted Dallas at New Age. They would like for all of the sub details to be entered into the reports. Quoted him at $500. Got approval the same day. Set the due date to 10/31/14. May have to ask for an extension as we don't have the in-line discount section done yet. Note added by Brandon on 10/29/14. Contact info for Dallas at New Age Medical. Phone: 303-233-1322 and newagemedicaldallas@gmail.com |
|
|
|
Adi 885 |
|
Custom Code - Cannamart | 10/4/2014 |
Steve, This is from Alex. These are the reports he would like to run from Adilas...there are some parameters unique that I am not sure how to find? E.g. They are interested in time/date stamp invoice data to track trends in sales flow to plan marketing/advertising. The other is sales data by user, but all in one export rather than by user. Also, is there a way to make a custom reporting page (maybe on their dashboard) that with one click will run common parameters rather than having to sort/filter through 'adv' function each time? Brevity via iPhone Begin forwarded message: From: Aleksander Murakhovskiy Date: October 3, 2014 at 10:59:39 AM MDT To: HH Gmail Subject: samples of MJ Freeway reports Here you go. also.. If customers get rang out after 7pm is there some way to change the time & date stamp on the receipt? I realized this in non-compliant.....apparently MJ Freeway allows ;) |
|
|
|
Adi 886 |
|
Custom Code - Dacono Meds | 10/4/2014 |
Hi Stephen, Well, Brandon is very busy and hasn't had time to address the label issue. But I can't even print the first one, I talked with him and he was unable to assist me in getting it to print. Is there any other center using Adilas, that is also using a Zebra LP 2824 Label Printer that could give me some help in getting this running. Right now I am hand writing all of the labels for each container as they are sold. Labor intensive and not very professional looking, but the only option I have at the moment. Thank you, Karen Nab Dacono Meds |
|
|
AU 2858 |
|
Daily Tasks | 10/6/2014 |
|
|
|
AU 2859 |
|
Daily Tasks | 10/7/2014 |
|
|
|
AU 2867 |
|
Daily Ideas | 10/7/2014 | -Show me... don't tell me... | |
|
Shop 3810 |
|
Virtual Post-It Note | 10/7/2014 |
Spiders and Wind Head first puts you at risk Then add wind. Butt first may then be a better option. Hang on and connect with whatever-then play once things get connected. Insert Scan Here. |
|
|
AU 2860 |
|
Daily Tasks | 10/8/2014 |
|
|
|
Adi 887 |
|
Custom Code - Developers NDA & Compete | 10/9/2014 | ||
|
AU 2861 |
|
Daily Tasks | 10/9/2014 |
|
|
|
AU 2868 |
|
Daily Ideas | 10/9/2014 |
Just for fun.... Think about sub locations per system player groups.... Just showing 4 of the 12 main system player groups: Invoices: 1. Pending 2. Work in progress 3. Layaway 4. Shipping 5. Archived 6. Etc. Items: 1. Bin # 2. Pallet # 3. Bay # 4. Floor # 5. Area 6. Section 7. Room 8. Etc. Stock/Units: 1. Lot 2. Show room 3. Front line 4. Repair 5. Rental fleet 6. Etc. Employee/Users: 1. Department 2. Office # 3. Area 4. Team 5. Committee 6. Task Force 7. Probation 8. Etc. -Thoughts on sub locations.... What if we made a section under elements of time for sub locations. (Think of sub locations per main player group) We could allow each main system player group to have virtual sub locations. This is kind of new... Instead of a single set of sub locations, what if we could specify subs per group... For example, say subs for a stock/unit could be Montrose Colorado (main location), North Lot (sub location). The item still exists in Montrose but we also know a sub of the main. Where the new piece comes in is by main player group. Let's say we are doing some parts (general inventory) movement, we may not want North Lot as a sub location. What if we only wanted Basement or Storage? Basically allow sub locations per main system player group. A PO might want sub locations of pending, filed, to be paid, shredded, etc. (Different subs for invoice, PO's, products, employees, etc.) -I'm seeing an increased need to cross tie a single data object (invoice #777, PO #251, E/R #555, stock/unit #101) to subs of the elements of time features. This could allow for sub phases, movement, sub tracking, sub locations, sub assignments, etc. We could add time elements to each of the main system player groups. The other part of this new need is where the action takes place. Traditionally, all subs of elements of time happen from the main element of time. What if we stored the data under the main element of time but showed or allowed access to the subs from the host or parent data object. For example: Let's say that invoice #37 (host or parent data object) wanted to track how long it took to build something... We could use sub dates and times (sub of time) but have it show up and be editable from invoice #37. The person could be interacting with time without ever leaving the invoice environment. That could be really cool and has a lot of potential. Here is what it might look like: (Sketch – please see scan in photo gallery – Main system player groups who need to access subs of time... There are actually 12 main player groups – just added a few of them for this drawing: Customers, invoices, quotes, parts, stock/units, vendor, PO's, expenses... Elements of time as a wrapper or pass through to the subs or functions of time – some of the subs or functions of time: sub dates & times, sub locations, sub comments, sub sign-offs, sub payroll, sub reminders, sub GPS & RFID tracking, sub assignments... Basically, use the main elements of time as a wrapper or pass through to access any of the subs or functions of time. Gain access to anything using time as a wrapper. -Wow, I didn't know time and time functionality (subs of time) were so important. Basically, if we used time as the wrapper or pass through media, medium, vehicle, or channel... We could add additional functionality to all existing player groups and individual players. That could be so powerful! I'm excited! -Instead of making time a key player, in this instance or event, it will be almost transparent but will allow main data objects and groups to access additional functionality. -What if... we could create templates for each main player group (all 12). We could then allow access to subs of time based on settings per template. It gets back to “Types” and “Functions”. Both types and functions of time were major topics while we were developing the system section called elements of time. I'm seeing a potential to take those same concepts to all main player groups and even let main player groups connect to sub functions of functionality of time or other player groups. This could get deep, but basically defining different types and functions for the different players and player groups. -Once we define the subs or functions, we could allow cross tying or cross usage as needed. Basically, make everything part of a bigger interactive system or data sphere. Bring it all together into one bigger system. -Things would still have a home or default usage, but we could open up cross overs and functionality to meet the demands of a flexible and complete world. True world building. Taking custom to a new level. -A couple days back I was writing about real in-line extensions. Well today I was explaining the concepts to the adilas interns. I used a couple of small drawings to show them what we were trying to do and come up with. Here are some rough sketches of how I was trying to explain things... (Please see sketches on scans in photo galleries): new in-line extensions, pretend an existing database table, core system with possible extensions, flow chart or relationship model with some extensions, throw things in the bucket, predefined levels, bucket or main data object with subs... -Imagine a one-to-many relationship (main boxes and lines) -Then imagine the flexibility if you could virtually extend and control other needs and wants on almost any table or relationship. Look at the dotted lines. Think options and custom business or data solution. -Imagine a bucket with certain predefined sections or sub containers (how the bucket is organized). Then imagine extending or adding custom containers as needed. -Small fix is needed on creating an internal-repair ticket from a URL web link. If no prior location is selected, it drops the URL.stock value and the user has to re-enter it. Help them out by keeping the known stock/unit value going forward. |
|
|
AU 2862 |
|
Daily Tasks | 10/10/2014 |
|
|
|
AU 2869 |
|
Daily Ideas | 10/10/2014 |
We need to setup pieces and small template options for invoices. This is not a full template level, just an intermediate step. These are things like: -Show/hide line item images -Show/hide RFID tag numbers -Show/hide Descriptions -Show/hide Elements of Time Eventually we'll get to the templates but we need to help along the way until we get there. -We had a request from a client to duplicate PO's in bulk. The ideal solution will be to use the duplicate PO page and just add a counter to help them duplicate in bulk. That way, we have a master and then we just loop over the master to get the PO's. -When doing sub inventory and cost controls (packaging), make sure and allow for some auto numbering on things. Say for instance... Duplicate this info from 10,001 to 10,500. We need the system to be able to dynamically assign those serial numbers or whatever in order making each one unique. This may require two pieces... One would be any standard pieces and the other would be the range. Say we had a serial number like PX-75-0010 to PX-75-0104. The standard part would be PX-75-0 and the looping range would be 010 to 104. We may also need length arguments or 0(zero) padding options. Just ideas. -Be your own style! |
|
|
AU 2863 |
|
Daily Tasks | 10/11/2014 |
|
|
|
AU 2870 |
|
Daily Ideas | 10/11/2014 |
-Using in-line extensions will give us the flexibility of Microsoft Excel with the power of a relational database and cloud based infrastructure. That will be awesome. -The key pieces are: 1. Centralize the data 2. Be able to collect and store the data 3. How to interact with the data 3.1. Interface 3.2. Flow & Processes 3.3. Analytics & Reporting 3.4. BI (Business Intelligence) & Big Data Space & Time Brainstorming: -Brainstorming on project phases and sub locations... Theses are subs of elements of time (and space). These pieces position or arrange how and where and what is happening or has happened or will happen. I think that we need to keep them subs or functions of time and space. However, I also think that we need to record the current state or status on the main. This allows it to be searched and referenced quicker. -We already store the action status value on the main elements of time table. These sub locations or projects phases would be the same way. We would hold an unlimited list of sub locations or project phases on or in the sub tables... but we would also make the current sub location or current project phase be part of the main element of time. -I'm really excited to see “space” or organization of time start playing into the mix. This is exciting! -If we are talking about subs showing up on the main individual data items or data objects, there are other pieces that want to be counted or accounted for. For example: Say a person was adding sub dates and times (virtual timecards) to a project. It sure would be nice if the total amount of time (sum of the subs) could show up on the main. All of the details are still held in the subs, but the current value becomes part of main. This is also true for things like action status logs, sub dates and times, project phases, sub locations, etc. -Elements of time and space need to be a foundational wrapper for all functionality for adilas. We already do this in a very light way. Invoices are assigned to locations and dated; PO's are assigned to locations and dates; deposits and expense/receipts are assigned to a date and one or more locations at a time. Inventory is tracked per location and by date (sometimes multiple dates). Almost everything we do has a component of space (locations and layering) and time (dates and date/time stamps). We already play this game... What if we just take it to the next level and allow the users to virtually wrap the system, the groups, and the individuals in both time and space? That would be awesome! -Time and space is ok (still works) but space and time sounds better. What about elements of space and time? -What if we add the word “space” into all of our pieces of documentation, literature, notes, quick search, etc. It may be made fun of at first but I think it could gain some ground especially if we start teaching and using those concepts together. -On the quick search – I would like options to search time or elements of time. I would also like a quick search option for space and time or elements of space and time. The space and time options could search much more and find all instances of things in both main and sub tables and database fields. If you searched space and time it could be the global adilas or all adilas searchable. -Locations and dates are a general way of saying space and time. We already knew that dates and times were important but we didn't know how deep locations or layering pieces would be (organizing your data). We've got to include space... It adds to and increases what dates and time can do by itself... It is a compound concept that needs both space and time! Think of our little assembly line graphic for our world building concepts... (Please see sketch on scan in photo gallery): -Space is how we organize over time -Pretend that the dots are checkpoints or key phases (dates/times) -Pretend that the top line is operations and the bottom line is accounting -Time goes both directions -Pretend that the vertical lines show permissions or access levels. Who gets to play at what level? -Pretend that the pods are areas or sub locations or departments (space) -In between checkpoints we have to allow some flex in the model -Lately I've been toying with the idea of a wrapper or a way to combine core concepts. I want them (core concepts) to interact and play together. I've been headed towards a wrapper of time (see entries from 5/22/14 and 6/3/14 in adilas university – developer's notebook). Anyway, my new direction is a wrapper or foundation of both space and time. You've got to have them both. -The bottom level (number 10) of the world building concepts currently says... Run all levels over “Time”. I think it needs to read – Run all levels through “Space” and “Time”. The word “through” may be a good general term for a wrapper, media, medium, or channel. We'll try that and see how it goes. |
|
|
AU 2871 |
|
Daily Ideas | 10/13/2014 |
When showing elements of time online, maybe use a format that looks something like this... (Please see sketch on scan in photo gallery) -Media/content links if any... maybe even just the folder icons full or empty with a counter -Main info and dates -Main notes and info -Photos and scans -Possible subs – if any -It has now been a couple of days since my last entries on space and time. I still think that they need to go together but I'm thinking it may need to be played out softer for the time being. I'm not sure if we want to jump that hard and in your face. We may just keep it soft and as under tones for now... -One of the interesting things that happens is how long things need to cook and actually be on the stove before they happen... It takes years and years sometimes... For example, elements of time project started in 2011, we are just now circling back around on what we are calling round two of elements of time. Another one is the content server, now called the media/content server. That was a project that started back in February and March of 2011 as well. The first round of that project was just barely launched fully in late July of 2014. It takes years sometimes and so projects will still take years and years and thousands and thousands of dollars... -One of the future projects, that is still a long way out, deals with 3D accounting and a 3D model of how the data and pieces all play together. Some of these ideas came clear back in late October 2010. That's four years ago... We are making great progress towards those goals, but it will most likely still be years out before we are there. I guess that is why you call them dreams and goals... They are out there a ways. Attainable, but still out there. Good stuff! |
|
|
AU 2877 |
|
Daily Tasks | 10/13/2014 |
• Recording notes and concepts on space and time and 3D objects and 3D data models. Kind of dreaming. • Reviewing notes and logic for in-line discounts. Checking math to make sure that the calculations were correct. Started going through code pages one at a time to add the new pieces. Working on the add to cart page. • Email to a client about a custom invoice. Created a quote and logged some notes. Apparently, there had been some verbal promises made but nothing was in writing. I officially started the ball in motion. • Emails and tech support stuff. • Helping an intern with his new barcode and label project for a client out of Texas. Called and talked with the client to see how things needed to be done. • Working on logic for in-line discounts. Light tech support for a client out of Arizona. • On the phone with the Colorado developer talking about extensions and flex fields. We also lightly talked about space and time as a wrapper of sorts. Just basic concept level stuff, nothing too deep. • More discount and flow logic. An intern came over and we worked on his web/API documentation project. • Getting notebook scans ready to send to my sister to enter into the online Developer’s Notebook on adilas university. |
|
|
AU 3718 |
|
Tech - In-Line Discounts Sessions & Cart Values | 10/13/2014 |
New session & cart values for in-line discounts: - My invoice info st. cart as a whole discount - Local page var = variables use cart discount - My invoice info st. show discount columns = “yes” or “no”, default = “no” - My invoice info st. cart as a whole discount approved = 0 - Temp st. original list price - Temp st. original list price extended - Temp st. use in line discount - Temp st. in-line discount per line - Temp st. in-line discount extended - Temp st. in-line discount campaign - Temp st. in-line discount price per - Temp st. line tax total - Item price - Extended line total - My invoice info st. total savings amount = 0.00 - My invoice info st. original cart sub total - Pre-existing value search for sub invoice amount - Temp st. line tax total - Update cart 2 cfm - Cart = “discount” - Use discount = 0.00 - On the discount searches… create a between filter to get discounts between the different levels. Filter discount between: ___% and ___% - We may be able to use the discount field on the customer record once we got the in-line discount piece done and in place. That would be really cool! - It may also be nice to help the customer tax categories pass all the way through the system by defaults. - On 10/17/14 we had a request to pass customer discount & tax rates clear out to eCommerce after a valid login. Kind of a new twist. |
|
|
|
Adi 892 |
|
Brainstorming notes from Steve and Brandon on sub inventory & cost controls (packaging) | 10/14/2014 | See attached for brainstorming notes and ideas on sub inventory & cost controls (packaging). | |
|
AU 2783 |
|
Brainstorming on 3D Operations and 3D Acconting | 10/14/2014 |
This morning, Tuesday, 10/14/14, Brandon and Wayne Moore were on a morning trail run. The subject was what goes with time? Brandon came up with space and Wayne came up with money. When you put all three pieces together, you can actually get 3D Operations and 3D Accounting. In Wayne's direct words... (written in an email to his friend) "I think you will like his 3-D approach to Operations and Accounting. X = Time, Y = $'s, and Z = Space." Great early morning conversation - done while running and hiking in the mountains of Northern Utah. |
|
|
AU 2786 |
|
Brainstorming between Brandon and Steve on sub inventory & cost controls (packaging) | 10/14/2014 | Brandon and Steve had a 3-hour GoToMeeting session talking about next phases of the project and where we are headed. These are some of the notes from part of the conversation. The notes cover sub inventory & cost controls, units of measure, pricing matrix options, attributes, extensions, and wrapping things together using space, time, and money. | |
|
AU 2878 |
|
Daily Tasks | 10/14/2014 |
• Emails on new permissions for invoices and limiting invoices to a specific salesperson. Also helping an intern with some css placement for a custom label job. • On the phone with Steve going over direction for the sub inventory and cost controls (packaging) section. The first hour was basically a pitch to head towards round two of elements of time as a virtual wrapper for all main system player groups. We did a GoToMeeting session and were drawing and talking concepts for over an hour. Really fun session. We used the graphics from 10/9/14 as a basis of our discussion. We also used the interactive map and the GPS core layout graphic to show flow and concepts. I had a lot of fun. 3D or three dimensional pieces were brought into the discussion. As a note, the 3D elements are: x=Time, y=Money, and z=Space. (Please see sketch on scan in photo gallery) o X – Time is on the bottom – it keeps running and may be broken down into years, months, weeks, days, hours, minutes, seconds, etc. o Y – Money flows upward or downwards – In business a point or trend that is flowing upwards is often a good thing (not always). Also, we want all monies to be tracked clear to the bank and financial level. Think of cream rising to the top. As a historical note… My dad is the one who came up with money as the y axis. That came from a walk earlier this morning. o Z – Space provided the depth structure of the items as they relate to time and money. Space allows for organizing, stacking, layering, packaging, combining, and separating. There are tons of things or attributes that may be applied to space. o Anyway, back to the telephone meeting, we used the last hour and a half talking about requirements for sub inventory and cost controls. See elements of time #892 in adilas or time #2786 in adilas university (developer’s notebook) for the actual brainstorming document. We spent a lot of time dreaming and talking about subs of subs, extensions, matrix, rules, and assignments, sub attributes, packaging, barcodes, space, etc. Great session. • An intern came over to work on the web/API documentation project. I helped him out a bit and tried to get organized. I started entering subs and elements of time to help us monitor custom code projects. We really need to do this. • Recording custom code projects into adilas – using elements of time. |
|
|
AU 2894 |
|
Daily Ideas | 10/14/2014 |
-On all real in-line extensions… on all dates and times.. include a used flag (yes/no value). If used, put a 1 (one). If not used, put a real date and use a 0 (zero) in the used flag field. -We have a good and stable set of code and functions for main groups and system player groups. The new and developing need seems to be in the sub or subs of subs level. Everything seems to be headed in that direction… Sub permissions, sub settings, sub inventory, sub tracking, sub groups, sub categories, sub functions, sub locations, sub phases, sub payroll, sub accounting, etc. Whole new levels to explore and figure out. Flat 2D objects vs. multi-dimensional 3D objects… (Please see sketches on scans in photo gallery) - Flat file with rows and columns - Three dimensional data objects built with properties of time, money, and space - X=Time, Y=Money, Z=Space Flat 2D models to compare operations and accounting along with 3D models to compare operations and accounting. The progression! - Operations on top and accounting on the bottom. Perfectly in balance. Ideal in a perfect world. - Operations on top and accounting on the bottom. Real world example, sometimes these things need to flex and then come back together. This happens in real life all the time. - Same as above with multiple instances where things flex and then come back together. Real life mixed with time. - Flexing model over time with dates and checkpoints at certain places. Dates and times now playing into the model. - Flexing model over time with: 1. Operations on the top 2. Accounting on the bottom 3. Process over time – multi bubbles or pods 4. Checkpoints as things come back together (dots) – Dates & Times 5. Permissions (user permissions) to limit access to the process (vertical lines) - Flexing 3D model that includes space. Depth, layers, stacking, wrapping, etc. - Add space to get a 3D model of how operations and accounting could work together. - 3D concepts – x=time, y=money, z=space -Another huge piece of the puzzle deals with being able to both add and subtract elements. We need to be able to go in both directions. For example: We may need more dates, more checkpoints, and more permissions. Other times we may need to short cut, streamline, or dummy things down. It (the elements of time, money, and space) need to flex as needed. -Steve and I talked a lot about attributes or pre-set pools (proposed subs of time). These could include rules, assignments, matrix or grids, sub players, options, sub locations, sub phases, etc. We kept switching between the word attributes and pools. The phrase attributes seemed to fit slightly better than pools just because you didn’t have to define it every time. This deals with verbage and terminology vs. the actual holding piece or data group. |
|
|
AU 3719 |
|
Brainstorming - Sub Inventory & Cost Controls | 10/14/2014 |
Brainstorming meeting between Brandon & Steve on 10/14/14: as a note this file was modified 10/22/14 - Sub inventory & cost controls (packaging) – sub of time – another function - Play in bulk or play in individuals – let the users decide - Limits (quantity limits) – yes limits or no limits (unlimited) - Attributes – the ability to have additional options, fields, settings, etc. - Pools – pre-defined rules to help with conversions o 1/8 oz = x g o ¼ oz = x g - Units of measurement for the package… unchangeable - Sub inventory items with special values… (for example) o Labor – mommy objects • Sub labor – child options - Price – variable prices and variable quantity to price levels - Barcode – we can use a unique number and it will pop up the package details - Package of packages (mini price and quantity matrix for or per the package) – copy and paste from other rules or matrix… think one-to-many - Currently we have a 1 to 1 on price and unit of measurement – we need to extend that… - Controlled groups – each package is individual - Pre-packaging - Scales and integrating with scales - Pricing matrix per item… without smart group buttons. This could be on a group level or on an individual item level. - Think subs and subs of subs – attributes (individual – micro level) - Be able to package, re-package, and re-package again. Unlimited number of layers or wrappers (how are we applying space) - By default a perfect 1 to 1 on price, quantity, cost, description, unit of measure o If they want, they could connect to a pre-defined matrix • Prices, start/end qty’s, descriptions, and unit of measure • Sub packaging to get to that level - On pricing we need price per, and total prices… just like smart group buttons - Borrow the logic of the smart groups without forcing things to the button level - Attributes – Allow them! – Empower the users! Both ways in and out (adding fields and subtracting fields). o Colors, descriptions, sizes, weights, o Sub matrix of other options… o Flex grid at any level… think any attribute - Packages are very defined… packages may not be as big, but think of a lot full of cars and trucks. Each one is very unique and we need to record that data. The uniqueness, good or bad, may also affect the cost and price (money or the y scale) - Part categories and sub categories of categories – stack as needed - Real In-Line Extensions – we need them – see notes from 10/2/14 - Go as deep as we need - Think of attributes on a per item basis…. Shoes, balls, t-shirts, sizes, colors, etc. The categories need to be main… The attributes need to be on the sub category or sub level. - Pattern after the makes and models section (any attribute and make it searchable). Do this on a group level or an individual level. - The goal is bulk or generic to specific or individual. Use the stock/units as a model. They are serialized units… tons of micro details that may be assigned and applied per item or per package… - Searching space… pretty vase and broad - All of the pieces play in this same realm – all 12 main players, sub line items, payments, sub tables, attributes, and any other sub functionality. Make it even more of a system. |
|
|
|
Adi 889 |
|
New Limited Invoice Permission | 10/14/2014 |
This is a custom code job for a new system wide permission. The client has employees (sales reps) that need to be able to look at invoices but only invoices that they have made. We have similar code for my quote vs. the general all quotes permission (all salespersons). The invoice permission will get a little bit tricky in that the permission needs to be cascaded out to all invoice sub reports as well. The goal of this new permission is to allow the user (sales rep) the full invoicing options and power but limit them to what other invoices may be seen. Ideally, if they have this permission we will automatically switch things in the background to limit reports to their name in the salesperson columns (2 columns - main and other salesperson). Along with that, we also need to limit access to an invoice if they (the current user) is not the main salesperson or the other salesperson. Basically, we pull the data, check the permissions, and then if needed we also check to make sure that they have access to view and/or add/edit details. Finished by Brandon Moore on 4/7/15. |
|
|
Adi 893 |
|
Adilas.biz 3D Word Building - Graphic | 10/15/2014 |
This is a first round graphic dealing with adilas.biz 3d world building concepts. The graphic shows all three dimensions: x = time, y = money, and z = space. The graphic also shows some of the features that adilas.biz offers to their uses. These include: - Sales & Inventory - POS (Point of Sale) - CRM (Customer Relationship Management) - ecommerce - Calendar & Scheduling - Payroll & Timecards - Document Management - BI (Business Intelligence) - Backend Office & Accounting The graphic ends with the question... What does your World look like? |
|
|
AU 2787 |
|
Adilas.biz 3D World Building - Graphic | 10/15/2014 |
This is a first round graphic dealing with adilas.biz 3d world building concepts. The graphic shows all three dimensions: x = time, y = money, and z = space. The graphic also shows some of the features that adilas.biz offers to their users. These include: - Sales & Inventory - POS (Point of Sale) - CRM (Customer Relationship Management) - eCommerce - Calendar & Scheduling - Payroll & Timecards - Document Management - BI (Business Intelligence) - Backend Office & Accounting The graphic ends with the question... What does your World look like? |
|
|
AU 2879 |
|
Daily Tasks | 10/15/2014 |
• Recording notes and pushing up brainstorming docs to elements of time. • Research on barcodes in Adobe PDF documents. Reinstalling Adobe Acrobat Pro. • Drawing pictures comparing 2D and 3D objects in my notebook. This is basically the history of how our vision of the assembly line for data came about. Steve originally came up with the concept of the assembly line for data in 2008. As some of our meetings progressed, a number of questions came up about how to handle different scenarios. See elements of time in adilas university from January 2008 to December 2008. Search for the words “balance sheet” between those dates. Around November of 2008 we were getting pretty deep. It was then that Steve had to help explain that our job was to just show the data back to the user vs. forcing a perfect balance. He drew the original analogy of... Operations & accounting: Ideal in a perfect world or controlled environment vs. Real world requires flex and possible variables (please see sketches on scans in photo galleries). Original model or analogy done by Steve in 2008. • As of now, 10/15/14, that model has grown and developed into a full 3D (three dimensional) model using time, money, and space (depth) to track user’s actions and reactions. Basically a 3D cause and effect model. We call it an assembly line for data. See a couple pages back for a visual evolution of our model. • I couldn't help it... I was so excited about taking our data assembly line concept to 3D that I spent a couple of hours creating some adilas.biz 3D world building graphics. • Adding new 3D world building graphics to a new 3D world building help file. See the following web address – https://data0.adilas.biz/top_secret/help.cfm?id=483&pwd=building • On the phone with Steve talking about projects. • Worked on the show all help files page. Small tweak on the add/edit media/content page to allow a direct data drill-down link to occur or point to the underlying data or main tie-in. • Added the vendor as an output option on the grouped PO line items. Posted files online and did some testing. |
|
|
AU 2895 |
|
Daily Ideas | 10/15/2014 |
Everything is headed to sub levels: - G – groups - I – Individuals - D – Subs or data level - Not sure how to draw it – but subs start dealing with space... organizations, layers, wrappers, stacking order, etc. Basically, the data level. (3D or add depth to the model) -We are even seeing needs for subs on both permission (users) and settings. Everything seems to be headed that way. -Idea from Steve… Be able to bulk update discount rates based on customer types. Idea came while Steve and I were talking about activating the customer discount rate field on the main customer table. The field already exists, it just wasn’t fully wired up. |
|
|
AU 2880 |
|
Daily Tasks | 10/16/2014 |
• Working with an intern on pulling barcodes into PDF files. Lots of back and forth testing and research. On the phone with Steve and a new Colorado developer getting his system setup and ready. • Research on an advanced quote to extend the P&L. Phone calls and tech support. • Writing the quote and doing emails. • On a GoToMeeting session with a developer. Going over page flow and even started into some light ColdFusion code and having him write it. Good session. |
|
|
AU 2896 |
|
Daily Ideas | 10/16/2014 |
-Idea from my dad while we were out walking… “Play at the wall.” – This deals with how we will allow outside developers to interact with adilas code and database. They will virtually play at the wall. This deals with API (application programming interface) sockets. -Other ideas from my dad… Treat the application like an electric wiring or circuit. All of the major wiring is done by the master electrician (programmer in our world). Once it is setup, a normal Joe is able to plug into the wall or power outlet. -When my dad and I were talking about electric circuits and playing at the wall, a couple other topics were: blue print reading or print reading (does the person understand the design or default flow). What standards are used? How does one read or interpret existing logic and wiring? Are there standard procedures or processes? If so, what are they and how can I get to them? -It is very tough to code to moving targets… Help out our future clients and developers by defining existing flow, wiring, output, and even code. -We need to fix the forgot password section. It should run great over our new API sockets. Currently it is built on older technology. Remember the glove analogy by an intern for handling custom code: - Same glove or page name - Any hand could go in the glove – any code could go into the page - I’d like to take this analogy to the next level… What is that level? I have needs to allow custom code, processes, and even custom output… - The glove thing, or whatever we come up with, will be used over and over again… Figure out a good solution! -On custom code includes... maybe define areas or sections and then allow those spots (places in the code) to be changed. This could be full page, navigation, headers, footers, body, sub body, etc. Basically, define the points where we allow custom. |
|
|
AU 2881 |
|
Daily Tasks | 10/17/2014 |
• Paying bills. • Working on the Denver training flyer for the end of October. The course was called new system updates and advanced backend office and accounting. Reformatted the flyer and added the 3D world building graphic on it. Sent it to Steve for approval. • Purchased a number of new domains. They are: 3DWorldBuilding.com, BusinessZipper.com, NewSchoolAccounting.com, RollCallAccounting.com, BusinessWorldBuilding.com, AdilasUniverse.com, and AdilasUniverse.biz. I’m really excited about some of those domain names! • Went with my dad down to Salt Lake City to meet with a potential client. They are an emergency preparedness company that wanted to see what we could do for them. On the drive down, I browsed their website using my dad’s hotspot while my dad drove. Once we got there, we met them at Village Inn for brunch. I used the interactive map graphic and the adilas GPS core graphic to explain core concepts. A gentleman and his web developer were at the meeting. They both had great questions and kept me hopping. I barely got to eat my meal. After the brunch they wanted a live demo. We then went to the web developer’s house to play with adilas. They kept throwing out questions and I would respond. They (combined) basically drove the demo by throwing question after question. Great session. As we were driving away, we got a call from him with some other questions. He had some excellent questions and you could tell that he was a very sharp cookie. 200 miles. |
|
|
AU 2897 |
|
Daily Ideas | 10/17/2014 |
Notes from a meeting with a potential client in Salt Lake City: - Extend the discount settings to both secured environments and customer facing eCommerce. Idea came from this potential client. - They (the potential client and his web developer) wanted to use quick css (cascading style sheets) templates to put a wrapper around the adilas backend engine. - Lots of talk about wrappers, skins, and getting things exposed as quick as possible. There was a definite element of speed to market. - They wanted options for both wholesale and retail simultaneously - They had questions about contracts and protection. Most of it was to cover them. - They wanted to know the quickest way to get up to speed. Once again speed to market and shortening learning curves was a big deal to them. - My dad and I talked tons about API sockets and mobile consumption of data (building apps). - We wanted to put my sister on this project. They asked for our best consultant and trainer. My dad and I both thought that my sister was our top pick for skills and availability. - While doing brunch, we had some pancakes on the table. We used the pancakes as a stackable object and then related to elements of time, phases, and even accounting. My dad wanted me to record that pancakes may be a good training image or object. Almost everybody knows what pancakes are and what they can do, be, have, etc. Fun stuff… (please see sketches in photo gallery) - Pancake sketches: Order, Cook, Serve, Top, Eat - Track objects and data over time (time, money, space, 3D elements) |
|
|
AU 2882 |
|
Daily Tasks | 10/18/2014 |
• Phone call with Steve. Lots of talk about custom projects, new and existing developers, and internal needs. We talked a lot about basecamps and what we need to do to get there. • Emails and light tech support. • On the phone with Steve trying to get his computer up to date with new files, database values, and what not. • Emails, phone calls, and tech support. • Working on in-line discounts and applying a custom discount on each item in bulk. Basically, looping over an existing shopping cart and updating values. • On the phone with my dad… He is recruiting other developers and other connections and contacts. I sent an introduction email to a new client to introduce him to Steve. Sent him some adilas reading as well. More in-line discount code work. Working on the bulk apply discount page. • Putting the advanced backend accounting flyer up online for the training seminar at the end of the month. |
|
|
AU 2898 |
|
Daily Ideas | 10/18/2014 |
-I’ve been thinking about the rewards cards, customer credits, and gift cards… I think we need to get on to that project pretty soon… Maybe think more dynamic than just a gift card. It could be a lunch card, a loyalty card, a pre-paid punch card, a vendor credit (they owe us), a customer credit (we owe them), a points system per item, employee/user points or credits, etc. Don’t stop there… think broad and dynamic. -What about rules, assignments, financial roll calls, values over time and through space. Help those rewards cards stretch the gamut. What about auto id’s, user assigned id’s, quick searches, homepages, flow? |
|
|
AU 3720 |
|
Tech - In-Line Discounts | 10/18/2014 |
- We’ve also had requests to think up different discount settings for secure, eCommerce, limiting, and manager’s sign-off. Needed variables: in-line discounts - Use in line discount - In line discount percentage - In line discount extended - Original list price extended - In line discount per line - Line quantity - Item price - Original list price - Extended line total - Inventory type id - Part category id - Store id - Tax category id - Line tax total Options for cart as a whole: - Discount Type: o In-line discount(s) – id=1 o Standalone Discounts – id=2 - Discount: o Percentage – id=1 o Dollars off – id=2 - Discount campaign: Fields: - Campaign - # - Quantity - Price - Discount - Discounted price - Item - UofM - Description - Line - Tax - Extended Old Discount Stuff: - Old: o FORM apply discount – default 0 - Both: o FORM apply discount type – 1=%, 2=$ off - New: o FORM default discount type – 1=in-line, 2=standalone o FORM campaign |
|
|
AU 2883 |
|
Daily Tasks | 10/20/2014 |
• Working bulk in-line discounts. • Working with an intern on PDF barcodes. Also working with my brother on beginner HTML, tables, and links. • Went into Smithfield to give a demo to a prospective client, a manufacturer for inlaid glass in cement, tiles, and flooring. My dad set up the demo. He went with me. The lady had a number of questions all written up and went right down her list. I was impressed with how organized she was. The things I took away were: o The importance of eCommerce!!! o Templates for eCommerce o Product matrix or attributes – colors, sizes, etc. o A pay portal for customers o Automated credits and credit memos • At the end of the demo, they asked for a demo login. Not that this was the main point, but the deeper we go, the more we see that companies want easy to use, full features, and speed to market type features. Lots of requirements. 20 miles. • Working more with my brother on beginner HTML stuff. More tables, links, and light formatting. |
|
|
AU 2899 |
|
Daily Ideas | 10/20/2014 |
-Main and subs of time… Add these fields: app_type_id, main_id, table_name, and sub_id. Help each table be more usable and versatile. Think along these lines… You tell me where to go (meaning the subs of time or main tie-in) and I’ll help you connect the dots. Think anything. -Expand the time templates a bit. Push the sub and main option lists to 255 characters. Also add the any tie-ins (app type, main id, subs, and table name). -What about pre-built extensions – known or commonly used functionality. -What about adding phases, check points, and financial flags to subs of time. Maybe look deeper into this option. Think custom reuse. |
|
|
|
Adi 897 |
|
Custom code - Setting for Quotes | 10/21/2014 |
Setting for quotes that will allow the salesperson to be the user id that restores the quote. As a note, a new corp-wide setting was added to the ecommerce settings to allow this to happen. The new setting was added as part of the in-line discount process. In-line discounts took over for about 3-4 months and the new setting was never pushed all the way through. Talk to Brandon for more details. This should be fairly quick once we get a developer on it. |
|
|
AU 2884 |
|
Daily Tasks | 10/21/2014 |
• Installing barcode files on the different servers to help with custom PDF label options. • In-line discounts and showing values in the view cart page. • New business cards for myself. • Working with an intern on barcode files for a client. On a long phone call with Steve (10-1pm). Lots of brainstorming on flow for sub inventory tracking. Lots of work in Microsoft Excel going over the subs and subs of subs (attributes) for packaging stuff). • Phone call with my sister. She called from Ireland. We talked about training, sales, and consulting. We are going to be feeding her more training and consulting work. • Other emails and tech support stuff. • Working with an intern and my brother on their different projects. The intern was recording web/API histories and doing small SQL table joins. My brother was building his first multi-page website with tables, graphics, and links. I helped the guys and did more emails and tech support. |
|
|
AU 2900 |
|
Daily Ideas | 10/21/2014 | -Add a discount type or reason. Idea came from a developer. We need to track – what is the discount for? What program? What coupon code? What marketing campaign? | |
|
AU 3721 |
|
Brainstorming - Sub Inventory & Cost Controls | 10/21/2014 |
Notes form a phone call between Brandon & Steve on 10/21/14: Recorded on a Word Doc for Sub Inventory & Cost Controls used for Brainstorming - Go to the very beginning. Where does it start? - On multi RFID & serial #’s o Standard – XYZ-7 o Auto increment from 003 to 7000 - Stock/Units – tons of 1-many - Attributes – tons of 1-many - Auto packages – LIFO or FIFO o Order of selling or think a vending machine – next, next, next - Setting – how do they want to play over rides – possible - Possible group invoices o Real details…. Behind the scenes o Show in bulk (to the customer) according to the price and description - Track in details but show in bulk |
|
|
|
Adi 895 |
|
Brainstorming session between Steve and Brandon | 10/22/2014 | See attached for brainstorming documents dealing with sub inventory and cost controls (packaging), recipe/builds (extending functionality), 3D world building (creating the whole system), etc. | |
|
AU 2885 |
|
Daily Tasks | 10/22/2014 |
• On the phone with a friend talking about projects and upcoming possible work options. He is a friend and full time web developer down in Salt Lake City. We’ve been good friends for years and years. • Working with an intern on getting his custom label layouts to show up correctly. • On the phone with Steve and a new developer going over sub inventory and cost controls. We talked a lot about recipe/builds, processes, pools, etc. Lots of new brainstorming notes on a Microsoft Word document from our phone call. See that word doc for details. • Emails and tech support. • On the phone with Steve going deeper into needs of the system and 3D world building – Everything is somewhat interconnected in a 3D system or 3D model of sorts. It is a system! • Recording notes and light phone support. • Back on in-line discounts. Working on new settings to help with discounts on the world or corporation level. New eCommerce settings, discount settings, and discount campaign options. • New logo for a company. • Working with my brother on his first ColdFusion training lesson. Working with variables. • Emails and phone calls about custom code, product uploads, product syncs, and custom exports from adilas to different software packages. • Working on new discount corp-wide settings. |
|
|
AU 2901 |
|
Daily Ideas | 10/22/2014 |
-On my cart favorites… Add more verbage on options 2, option 2. This deals with showing the user the view item details page. Lots of power! -Quote from an adilas rep and trainer – “Sell in bulk and train in bulk.” He was talking about focused group demos and training business owners. -Quote from Steve – “It’s a system! Help everything play together on the same team!” |
|
|
AU 3722 |
|
Brainstorming - Possible New Settings & Permissions | 10/22/2014 |
- Another discount request goes clear out to the type or campaign level. Think about a specific sale, a discount per customer type, a discount per part category, a discount per item. Tons of different levels to play at. Note made on 11/24/14: - We may need be show the total savings somewhere on the cart. Possible New Permissions: - My invoices – id = 141 o System Basics – limit the invoice options - Discount approver – id = 140 o System Assets – who can approve a discount Methods to Update: - Cart cfc: (checked & tested) o Add quote line item – all 7 fields – updated all occurrences o Update quote line item – all 7 fields – updated all occurrences o Add invoice line items – all 7 fields – updated all occurrences - Liabilities 4 cfc o Add PO line item o Get PO invoice line info - Assets 6 o Update invoice line item Possible discount, invoice, & quote settings: - Expose these settings to normal admin users - eCommerce settings: o Restore quote to cart setting • 1 = same as original (default) • 2 = assign who restored it o Quote apply discounts to eCommerce • 1 = yes • 0 = no default - Default discount type o 1 = use in-line discounts o 2 = use standalone discounts - Discount requires manager approval o 0 = no (default) o 1 = yes - Discount approval password o Required if discount requires manager approval - Discount campaign settings o “10::Member, 25::Employee, 15::In State, (%::Name) - Add some new default invoice settings to printable invoice options o With photos o With RFID tags On the Customers Table: - Add opt in/out email & text to reports & excel output - Add new field o Discount campaign On Quote Line Items: - Add new fields - Discount campaign On PO Invoice Line Items: - Add new fields - Discount campaign |
|
|
|
Adi 896 |
|
Report Builder or Page Settings | 10/23/2014 |
Patrick Campbell via adilas.biz 1:08 PM (17 hours ago) to Stephen I was discussing with our METRC officer, it would be awesome to be able to change the default selections and save a new default when doing advanced patient searches. e.g. : When I select "Patient", and type "adv", it brings up all of the different patient search option check boxes, and by default, a certain number of them are selected. I would like to change which of these check boxes are selected by default, as this would help us do patient audits that much quicker. This is of course nothing urgent, just another idea that we were thinking about. |
|
|
AU 2886 |
|
Daily Tasks | 10/23/2014 |
• Working with an intern to help make custom document assignments. Reskinning pieces to allow customers and clients to get to custom code. • Demo with prospective clients. We covered eCommerce, CRM, flash demo, education module using flex grid, and talk about API sockets. They had questions about multi-level websites, duplicating pages and code, marketing and commissions, tracking promotions and referrals, and multi-level direct sales and commissions. • Setting up an intern with PDF’s and custom documents. • Phone call with Steve. See new brainstorming notes on the Microsoft Word document for sub inventory and cost controls (packaging). Lots of direction, depth, goals, and vision. Great session! • Emails and phone calls. Helping an intern with his web/API documentation project. • Working on the new database update page for discount settings. Also on the phone with another developer going over options on custom code, rules, and assignments. We talked a lot about the glove analogy or the black box analogy for handling custom code. Basically, each page has or will need a way of allowing custom code, logic, or custom output without hurting the main page or underlying structure. (Sketches – Black box analogy – page hooks or page sockets. Black box at the top & another black box just before the output.) The black box is a way of saying… Do you need to add something? It could be code, processes, or even output. We could do a simple include or pass through (no abort just a simple include) or we could run standalone code that would or could virtually take over. This could be done by adding an abort command at the end of the custom include page.) • Working with an intern on some vision of the future. Lots of small drawings and chatting back and forth. • New logo for a client. • On the phone with a developer. We were going over the adilas main login procedure and how the different pieces play into the mix. Good session. |
|
|
AU 2902 |
|
Daily Ideas | 10/23/2014 |
-We had a request to be able to save advanced customer search options for custom reports. We are going to get more and more of these types of request. Users want to cut steps and save settings and search criteria. We already have the tools… we just need to implement them. -Quote from a developer – “The lines contain the data.” Basically, let the line items (the details) contain and hold the data. This will help later on with look-ups and reports. On sub dividing pieces into smaller sections… The goal is to add granular level controls. Having said that, it would also be very nice if we had pre-built bigger sections if we want to run fast or want to run in bulk. Think of bread as an example…. (please see sketches in photo gallery) - Loaf – (large or bulk) general - Slice – (medium) some control - Cubes or sections – (small) fine level control - Mixed or different options – (variable) -It sure would be nice if we could control things at whatever level we needed it to be. That would be awesome! -The best solution is a mixed or variable option that fits your needs. Granular control is awesome but sometimes you need quick, bulk, grouped, or even generic. Think pre-set pieces, tools, and output. |
|
|
AU 3723 |
|
Notes for New Client | 10/23/2014 |
Notes for a new client: - eCommerce - Multi-level website duplicate - Instruction level - Marketing & commissions - Promotions & referrals - Multi-level direct sales & commissions Ideas from Colorado Developer: - Black box o Include as a pass through (no abort) o Run standalone page (include an abort at the end of the page) - Dumbed down o The lines contain the data |
|
|
AU 2887 |
|
Daily Tasks | 10/24/2014 |
• Wiring up dynamic labels with an intern. Custom documents, database look-ups, and dynamic options. • Demo with a new client and his web developer. Light Flash intro and then showing them mock-ups and ways we will tweak the system based off of what they have right now. Also, eventually down the line, a full custom job for what they want. • Working with an intern on tying in flex grid pieces to his custom barcode PDF labels. Helped him get the files online, did some testing, and invoiced the client. • Emails and light tech support stuff. • Back on the discount settings. Added code to allow normal corp admin users access to advanced eCommerce settings. We’ve wanted to do that for a while now. |
|
|
AU 2903 |
|
Daily Ideas | 10/24/2014 |
-I really want to help with the developer’s notebook project and adilas university for videos and training. I’d love to budget an hour or so each day per project. I think that would be fun. -Just wanted to record this. I had a client call me today and ask why we are soliciting their employees to come to work for us. I heard her out, but basically said we are looking for people with skills. All work is independent and may be done on the side, as moon lighting, or as an independent. The lady said that we are stealing her employees. I tried to say that our goal is not to steal an employee but we do openly solicit people who have skills and want to help. That is part of our model. As a side note, I personally don’t even know the person who is in question or who has been solicited. The client was basically calling to complain about what was happening. As a follow-up, I did send out an email to the core adilas players reminding them to be kind and tactful if they are soliciting skills and talents. |
|
|
AU 2888 |
|
Daily Tasks | 10/25/2014 |
• Working on help files and prep for a meeting with a developer. Made some small needed changes to help files with documentation about login resets. Trying to make things more dynamic. • The developer came over and we worked on getting him started with the API socket or API parts (connections). We are going to call his project “wiring up the wall” so that we can let any outside party or parties “play at the wall.” The phrase “play at the wall” was mentioned by my dad as we were on a morning walk. We’ve used that phrase a number of times since then when trying to explain API socket connections (virtual data ports) to different people. See notes on other page for graphics that the developer and I drew to describe the process or concepts of play at the wall. • Working on help files for API socket connections or data ports. Lots of reading and writing. Trying to explain the process using analogies. • Writing up a help file to help explain 3D world building and business world building concepts. Included: x=time, y=money, and z=space levels and dimensions. Also included all 12 main adilas core concepts. I can’t wait to put graphics with the new help files. Help to both tell and show the story. That is the goal! |
|
|
AU 2904 |
|
Daily Ideas | 10/25/2014 |
On the API socket pages… I would like to provide samples in different languages on how to connect...: - ColdFusion - ASP.net - PHP - Ruby - Java - C++ - Java Script -Maybe have a super simple method that outputs a person’s name or does some simple math. Kind of a “Hello world” method, just for testing. Help people get connected. -A developer came over and we worked on the adilas API socket project. We are calling it “wiring up the wall”. Here are some graphics that we used to explain the process: hard coded pages and database queries. This is a one-time plug-in. We don’t want that. That is a one-to-one ratio and can’t be reused unless you copy and paste. Then if changes are needed, you have to update every page. -Internal use of API socket connections (API socket calls – good – use many, database) OR External use of API sockets, ports, gateways, etc. (“wire up the wall”) More drawings on how the API works… Brandon and a developer: This is the developers’ project of wiring up the wall with different ports and sockets. Many sketches – please see scans in photo galleries - External clients: laptop, phone or mobile, tablet, desktop - Normal Internal structure: internal API socket, adilas database - Other programs, apps, pages, etc. - Custom or 3rd party solutions Connection Process – Plugging in: 1. Knock, knock, who is there? 2. What do you want? Which method or function? 3. Pass in requirements. 4. Make the connection. 5. We pass back the results. - 500+ options Internal data ports and sockets |
|
|
AU 3724 |
|
Sketches & Planning - API Socket Project - "Wiring up the wall" | 10/25/2014 |
Developer’s Project: API Socket Project – “Wiring up the wall: (Please see sketches on scans in photo gallery) - Page – db = custom 1 time plugin - User, ports, sockets, gateways - Page 1, page 2, page 3 – API Call – DB = use many --- Good! Here is how the API Works… - Internal Structure: o Normal adilas o Adilas db - Clients: o Laptop o Phone o Tablet o Desktop - Other programs or pages - Developer’s project & wiring up the wall with different ports & sockets Connection Process – plugging in 1. Knock, knock, who is there? 2. What do you want? a. Method or function – 500+ options – black box 3. Pass in requirements 4. Make the connection 5. We pass back the results |
|
|
AU 2889 |
|
Daily Tasks | 10/27/2014 |
• Adding 3D world building graphics and adilas GPS core layout graphics to help files. Posted new files online. • Working on new corp-wide settings for discounts and in-line discounts. • Working on custom discount setting for customers. Adding the discount campaign fields for customer. • Adding the customer discount campaign to different pages. • Adding fields to the advanced customer search page. |
|
|
AU 2890 |
|
Daily Tasks | 10/28/2014 |
• Paying bills and doing email. • Emails to a graphic designer about doing small banner sites to point to adilas. A banner site is kind of like a banner ad but it is an entire website that is devoted and focused on a single subject. Kind of like a billboard on the side of the road… only these banner sites or billboard sites will have links, pages, graphics, etc. • On the phone with Steve. Going over code, projects, direction, and progress on in-line discounts. We talked API socket flow, custom code black box stuff, and did a little bit of show and tell on different projects we were working on. The last half an hour, Steve just watched me work on code over GoToMeeting and I narrated it as I went. Hopefully that helped him get some ideas. • An intern came over and we worked on loops within loops (nested loops). I kept working on the discount campaign settings while the intern was working on his projects. • Phone calls and emails. Trying to help out for the advanced training session that will be in Denver tomorrow. Sending some information over to Shari. • Working on new shopping cart logic for in-line discounts. • Starting on discount campaign fields for invoice and quote line items. |
|
|
AU 2891 |
|
Daily Tasks | 10/29/2014 |
• Emails. • Working with an intern and my brother. The intern was working on a custom PDF invoice and my brother was working on an intro to ColdFusion page. He was working with basic math and variables. • Working with my brother on variables. Working on adding two new system permissions. They are for my invoices – limited view per user and a new permission for a discount approver. This is a manager level permission to help with discounts. • Went in to Bridgerland to meet with a graphic designer about billboard and banner sites. Great meeting. We talked concepts and plans for just over an hour. Lots of little sketches about 3D world building, the data assembly line, API sockets and data ports. 30 miles. • Went to Preston, ID, with my dad to go to a meeting for the radio guys that helped with the Bear 100. Took a bunch of notes in my little green notebook. We then went to an ice cream Shoppe and talked about GPS event and race tracking using adilas as a backend engine with a cool and simple GPS app on the front end. Really good stuff and both my dad and I were really excited. |
|
|
AU 2905 |
|
Daily Ideas | 10/29/2014 |
Small sketch from a meeting with the graphic designer about billboard sites. (Please see scan in photo gallery) - Think of billboards along the side of a road (electronic or digital) - Simple, focused sites on a single topic - Notebook look and feel - Capture the story - Show systems and compound concepts -Get some of the ideas from the little green notebook. Lots of good stuff. Lots of late night and early morning brainstorming. |
|
|
AU 2892 |
|
Daily Tasks | 10/30/2014 |
• New 3D domain names. Email to the graphic designer, my dad, and Steve about digital billboard sites. Purchased these new domain names: 3dassemblyline.com, 3ddataassemblyline.com, playatthewall.com, 3deventtracking.com, and 3dracetracking.com. • On the phone with Steve, an intern, developer, and myself. The first part of the call was talking about sub categories for parts. See notes later on. After the developer left, we did a session on custom labels and showed Steve how to tweak the label settings. An intern then gave Steve a demo on the custom labels and barcodes that he did for a client. After that, Steve and I worked together on in-line discounts. We spent the rest of the time coding and building while doing some teaching. Great session. • Emails and tech support. • On the phone with a marketing contact going over a new custom project dealing with electronic billboards and menu boards. The client wants to interface between his menus and our point of sale system. • Helping an intern with his web/API documentation project. Reworking 2 new banners for Steve. The banners are for a trade show in November. • Finished up the 2 new banner graphics and sent some proofs to Steve. • Reviewing feedback from the advanced accounting training class. A rep sent me a recap of the surveys that were turned in. • New logo for client. • A developer came over and we got his laptop up to speed and all updated. He will be working on the adilas API socket project and wiring up the wall. |
|
|
AU 2906 |
|
Daily Ideas | 10/30/2014 |
Notes from a phone call between Steve, a developer, an intern, and myself: - We need to allow sub categories for parts. This could be called Nth level categories where N (letter N) is the variable. These categories need to create a self-identity or virtual stacking order. - It would be nice to add a photo per part or item category. This could really help with eCommerce and visual navigation. - Weights are going to be coming more into play. - We may need to create a cart or shopping cart alert system. - Small graphic to explain the difference between backend programmers and frontend programmers. (Please see sketch in photo gallery) - Clients – our users; API, Permissions, Settings – consultants, reps, and frontend programmers; ColdFusion, Code, Database, Java Script, SQL, … Backend – backend adilas developers, interns, techs, etc. - Pages – nuts and bolts - Subs… That seems to be the new direction. Subs deal with stacking, layering, categorizing, wrapping, and other spatial (space) elements. - Conversion - Little black boxes on the shopping cart page. - User defined rules and assignments. - True generics and homogeneous products - Units of measure or units of measurement. - We need a mini blog of what’s new, new updates, and upcoming features. - We talked about class and training attendance at our advanced accounting class (30+ people). We need more training. - We also talked about controlling and managing our time lines. That is a tough subject. - Custom labels - Backend developers – (write and develop the settings, permissions, and API sockets) vs. Frontend developers – (setup, use, and interact with settings, permissions, and API socket calls and connections) Small graphics while talking to an intern about filling in the subs or sub pieces of the puzzle…: (Please see sketches in photo gallery) - Start here – fill in the subs – key pieces or main general structure – goal - We got a very good base level structure built and ready - The next phase is filling in the sub pieces of the puzzle - 2D spreadsheet or table (rows & columns) - 3D model – Time (x), Money (y), Space (z) - Pretend this is a bridge – main supports, subs, “zipper it” – one cog at a time |
|
|
AU 3725 |
|
Brainstorming - Call with Steve & Developers | 10/30/2014 |
Conference call with Steve & 2 Developers: - Sub categories for parts - N level categories - Self-identity - Photos on part categories - Cart alert - Weights - Subs – it is the new direction – special elements - Weights - Conversions - Little black box on the shopping cart stuff - User-defined: rules & assignments - True generics and homogenous products - Units of measurement - Mini blog of what’s new o New updates - 30+ people in the advanced accounting class - Do logos - Controlling and managing out timelines - Custom labels |
|
|
Adi 901 |
|
New adilas banners | 10/31/2014 |
Here are two new adilas banners that will be printed and used at the upcoming trade show. Banner 1 - PDF - 11MB - https://data0.adilas.biz/public/adilas_banner.pdf Banner 2 - PDF - 12MB - https://data0.adilas.biz/public/adilas_banner_2.pdf The banner design was originally created by Steve using CSS (cascading style sheets) and graphics. We then had to convert the ideas to Adobe Photoshop in order to get the resolution high enough. Brandon did the Photoshop work and pushed the files up online. A lady by the name of Katrina Skinner helped with some of the data points and verbage. Banner 2 includes information and data about 3D World Building as well as other key concepts such as: assembly line for data, custom data engine, custom dashboards, and real-time data portal. |
|
|
AU 2788 |
|
New Banners for the Las Vegas trade show | 10/31/2014 |
Here are two new adilas banners that will be printed and used at the upcoming trade show in Las Vegas. Banner 1 - PDF - 11MB - https://data0.adilas.biz/public/adilas_banner.pdf Banner 2 - PDF - 12MB - https://data0.adilas.biz/public/adilas_banner_2.pdf The banner design was originally created by Steve using CSS (cascading style sheets) and graphics. We then had to convert the ideas to Adobe Photoshop in order to get the resolution high enough. Brandon did the Photoshop work and pushed the files up online. A lady by the name of Katrina Skinner helped with some of the data points and verbage. Banner 2 includes information and data about 3D World Building as well as other key concepts such as: assembly line for data, custom data engine, custom dashboards, and real-time data portal. |
|
|
AU 2893 |
|
Daily Tasks | 10/31/2014 |
• Swapped out the training flyer on the login page with a new banner ad. • On the phone with Steve. We went over some code questions and talked about upcoming projects. Trying to catch and communicate about the vision of where we are headed. • Working with an intern on graphics. Got him started on building his own icon menus for pages. While he was doing that, I was reworking some banner graphics. • Added 3D world building concepts to the banners. Purchased a couple new domain names for assembly line for data. • Finalized the new banners and put the high resolution PDF's online. I also added new elements of time with graphics and links to the new banners. The second banner has verbage and graphics dealing with 3D world building, assembly line for data, custom data engine, and real-time data portal. See elements of time #2788 in adilas university site or #901 in the main adilas site. Trying to start recording as we go vs. waiting until the end. |
|
|
AU 3726 |
|
Sketching & Sharing Future Vision with a Developer | 10/31/2014 |
Working with a developer on where we are headed: (See sketches on scans in photo gallery) - GUI - Money (y), Space (z), Time (x) - Consultants FE - Clients/users - API Permissions Settings - BE - CF, Java Script, SQL - Graphic - Custom - Subs - Start here - Goal - Links - Text - Body of page - 5 main buttons - Icon menus - Touch screen |
|