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 - 8/1/2014 to 8/31/2014 - (47)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 2763 |
|
Daily Tasks | 8/1/2014 |
• Emails. • An intern came over and we worked together on some simple MDI projects. We added 30 random Captcha images (graphics with random text characters) to a client’s site. We added a date code and the security images. Posted files online and invoiced. • Invoicing a client and showing the intern around adilas a bit. • He and I worked on a small contract tweak for a client. • Finished up the contract changes. Posted files online and billed the client. • Working with the intern on new IFTA (gas tax stuff for truckers) tables for a developer in Salida. This is part of the trucker interface pages for a client. • Working on visual menus for the invoice line items page. • Working on visual icon menu for the add/edit invoice page. |
|
|
AU 2872 |
|
August 2014 Monthly Recap | 8/1/2014 |
The majority of time this month was spent on a huge database copy project. This is a really exciting project for adilas as it will allow greater flexibility and options for clients. This project included hours and hours spent prepping tables for copy, creating new database structures, planning, scripting database table levels, and more. With the ability to copy, move, and start new databases, it will be like the difference of allowing clients to have their seat on the bus (current shared model) or have their own motorcycle or agile vehicle (future individual model). Allowing clients to work in their own adilas environment, instead of a shared environment, will greatly increase the speed and agility of their adilas. Other exciting new projects were started this month such as, working with a cash kiosk system to provide integration for users between adilas and cash kiosks. Adilas now has an expanded chooser section with over 20 new options available to all users. Initial tables and code for the in-line discount project were started as well as a custom behavior tracking project for a school. After attending a copyright and patent workshop we continue to feel an ever-increasing need to get more information out about the core concepts which adilas has been built on and functions by. We want these core concepts and ideas to be freely known, available, and used by people all throughout the business world. For more information on this entry specifically, please see element of time #2774 here in adilas university. *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 3700 |
|
Brainstorming & Tech - Elements of Time | 8/1/2014 |
Adilas Versions: - 12 years of progress - 8th version - Info graphics per year – 2001-2014 (See scan in photo gallery for sketches) Versions: 1. Inventory tracking system – Locations, employee/users, and stock/units (serialized inventory) – big ticket items 2. 3. 4. 5. 6. 7. 8. World Building -Base Camp -Anchors Versions: - Description/Features - Time 1. Version 1: 2001-2002 (?) - Inventory Tracking - Stock/Units or Serialized Inventory - Multiple Locations - Employee/Users - Role Based Permissions - Digital time clock 2. Version 2: 2002-2003 (?) - Full & General Inventory - Parts Department – General Items - Basic Inventory Point of Sale - Vendors, Purchase Orders (PO’s), parts, items, services, quotes, tax settings, invoices, and customers 3. Version 3: 2004-2006 - Payroll Reports, Commission Reports, & Withholdings - Stock Units - Floorplan app - Photo Management for Stock/Units - Web Presence for Stock/Units 4. Version 4: 2006-2007 – Full Rewrite - Full Rewrite with a New Base of Permissions & Settings - Changed from MS Access databases to MySQL server database - Banks, Expenses, Check Write System, Deposits - Invoice Rewrite to Open to Both Stock/Units, Parts, & Services 5. Version 5: 2007-2009 - Accounts Payable - Accounts Receivable - P&L – Income Statement - Balance Sheet - Officially Started Up Adilas (6/2008) 6. Version 6: 2009 - Merchant processing for credit cards - Recipe/Builds - Introduced corp-wide settings (custom naming conventions) - Web presence for parts & general inventories - CRM functionality & customer logs - Flex grid tie ins - Customer paperwork & PDF’s - Reoccurring invoices 7. Version 7: 2010 - Major work on corp-wide settings - Security settings tightened - Lots of new POS (Point of Sale) features such as o Barcode printing o Receipt printer invoices o Inventory ordering process o Dewy decimal – up to 5 levels of decimal accuracy o My cart favorite buttons – custom o Units of measure o Sales & profit reports o Advanced add to cart 8. Version 8: 2011-2012 - Elements of time – Calendaring & Scheduling - System designing & layout pieces and how they all worked together - Interactive map layout - More work on my cart favorites and other POS functions - System refinement - Customer queue - Smart groups and tiered pricing structure - Enhanced barcode search capacity - Duplicate PO - Choose interface options - New custom homepages 9. Version 9: 2013-2014 - Custom code & custom interfaces - Industry specific tweaks & charges - Built-in eCommerce and full web presence - Tons of new settings & permissions - Tons of training both online and live classes - Introduced World Building concepts - Lots of new flyers and graphics - Hired college interns to help with custom code projects - Over 100+ hours of training captured and edited - Lots of new YouTube videos - More icons & buttons - Added additional photo galleries for all 12 main system player groups - Migrated to multiple servers and further defined world building levels and definitions - Added full media/content (file management stuff for PDF, spreadsheets, word processing, graphics, images, video, and audio files - API sockets - 3rd party vendors - Custom code Update note: this was lightly recorded into the database on 9/20/14. See elements of time #873 in adilas or #2777 in the adilas university site. Recorded on 9/20/14. Elements of Time Homepage Params FORM – URL – Defaults - Action status id o Action status • 1 - Assigned to id o Assigned to • Normal id = x + 0 = all, 1 = unassigned, 1,id = unassigned plus me - Block size o Block size o C-W • “ “ - Color value o Color value • “all” - Created by id o Created by id • 1 - Customer filter o Customer • “All” - Daily date, FORM time period = 1 o Lots of if statements to refigure FORM o Me period = 1 • “ “ - From date o From date • “ “ - General title o Title • “All” - Monthly date – 1-12, FORM time period = 3 o If blank set to current • “ “ - Monthly year – FORM time period = 3 o If blank set to current • “ “ - Quick jump date • “ “ - Quick jump frequency • “ “ - Quick jump value • “ “ - Report type o Group o Calendar o Details o Time slot o Type – required if going URL o C-W • “ “ - Show group subs o 1 = show o 0 = hide o Show subs o C-W • “ “ - Show logs o Yes = show o No = hide o Show logs o Run extra cfc • “yes” - Time block end o Sample – “5:00 pm” o To time o C-W • “ “ - Time block frequency id o 2 = sec o 3 = min o 4 = hours o Block frequency o C-W • “ “ - Time block size o Block frequency size o C-W • “ “ - Time block start o Sample “8:00 am” o From time o C-W • “ “ - Time period o 1 = daily o 2 = weekly o 3 = monthly o 4 = custom o Defaults are 1 & 4 o C-W • “ “ - Time template id o 1 = all numeric o Template • 1 - To date o Used with from date o To date o FROM time period = 4 • “ “ - Weekly dates o Filled if blank o “start date, end date” • “ “ Time #2773 |
|
|
AU 2764 |
|
Daily Tasks | 8/2/2014 |
• Working on the icon menu for invoice line items and the add/edit main invoice page. Posted files online and light testing. • Working on showing all help files “as is”. Trying to get the pieces we have done out and about. • Working on showing all adilas university elements of time. This deals with the developer’s notebook. My sister has been working on this project for months. Good stuff! • On the phone with Steve going over our current game plan. We talked projects, funding, direction, and vision. Lots of good stuff coming down the pipeline. • Working on a time related interface project. • Writing a long email about free adilas API code and documentation. Included the existing stuff and also included the futuristic stuff that we are developing for our new JSON API socket connections. • Reworking a custom interface page that shows the time slot functionality on the time homepage. Cleaning up code and figuring out what params are needed for the mini time project. |
|
|
AU 2769 |
|
Daily Ideas | 8/2/2014 |
-We have had a number of requests to be able to search invoices and sales based on customer types. That may be a good thing to include in the PO/Invoice line items table. Just an idea. -Future note for help files… Each help file would be really cool if it had a graphic of the page, what it does, and how it is used. -On help files… Maybe even have layers or levels. Help them use at their level. -Start getting things out there… AS IS! |
|
|
AU 2765 |
|
Daily Tasks | 8/4/2014 |
• Prep for icon menu for all invoice section pages. Planned out buttons and icon menus. Created small screen captures and icons for over 20 pages. • An intern came over and we installed an instance of adilas on his laptop. We updated files and set up databases. We then started working on icon menus. He will be working on icon menus to help with a general face lift for adilas. Good stuff. • Helping the intern with his first solo project for adilas. • Working on the limited retail dashboard with scheduling options. Reworking an interface with a time slot (elements of time) piece built-in to the page. Lots of line by line testing and checking off on code. Also helped our intern as he had questions. |
|
|
AU 2766 |
|
Daily Tasks | 8/5/2014 |
• File review with the intern. We signed off on 4 new files that have icon menus. • Posting new files online to different servers. • On the phone with our developer from Salida. We were going over his IFTA stuff for the trucking industry. • Phone calls, emails, and tech support. • Prep for new files for an intern. He is cruising through the icon menus. • More file prep for the intern. Wrote up the next couple pages that need buttons and icon menus. • Working on IFTA stuff for a developer. Looking over code and making comments on his pages. • File review with the intern. We signed off on another set of files. He is doing a great job. • Posting new files online. Light testing. |
|
|
AU 2770 |
|
Daily Ideas | 8/5/2014 | -Allow companies to purchase full or whole servers from us. We could do $2,000 a month or $20,000 for an annual service contract. Just an idea but it may help us get some bigger clients. | |
|
AU 2767 |
|
Daily Tasks | 8/6/2014 |
• Reading over a developer’s IFTA trucker code for pulling data out of a CSV file and inserting it into the database. • File review with an intern on new pages with icon menus. Working on first stock field updates, IFTA stuff, and going over pages to sign-off on code. • Writing a longer email about updating inventory counts from an external digital source or file. Gave a small quote for the custom code. • Testing code on the IFTA trucking stuff. The process is a file gets uploaded. We run code on the files, pull things into the database and then push it where it needs to go. |
|
|
AU 2771 |
|
Daily Ideas | 8/6/2014 | -On the icon menus… we have tons to do… Focus on the main player groups first and we’ll go from there. Homepages, advanced search options, sub reports, data and individual level stuff. | |
|
AU 2768 |
|
Daily Tasks | 8/7/2014 |
• Lots of work on signing off on the IFTA trucker code stuff. Prepped some files for an intern for icon menus. Worked with the intern on some of the code stuff for the pages and menus. • Quite a few emails and phone calls for tech support and training stuff. Posted new files online and did some light testing. Ran into a problem with the new IFTA code on the live servers. I think it is a firewall or database admin thing. Anyway, lots of emails, phone calls, and tech support stuff. • Emails on 2D barcode scanners. • Setup a new corporation, logo, colors, and user account for a new client. |
|
|
AU 2772 |
|
Daily Ideas | 8/7/2014 | -We have received a request to include the opt in/out fields as part of the main customer search options. These fields were added to the database but have not yet been fully populated to all of the reports. | |
|
AU 2785 |
|
Daily Tasks | 8/9/2014 |
|
|
|
AU 2808 |
|
Daily Ideas | 8/9/2014 |
-Steve wanted me to record that some people may want the option of keeping the icon menus open on a per page basis. Basically, instead of auto closing or hiding the icon menus every time, some of the users want them expanded and/or show by default. -One of the places that we could really gain some ground inside of adilas would be with custom personal settings per page. This includes custom links, navigation, personalizing, and even saved report criteria. All of these things exist. We just need to let our users get at those pieces and harness the existing power of adilas. |
|
|
AU 2790 |
|
Daily Tasks | 8/11/2014 |
|
|
|
AU 2791 |
|
Daily Tasks | 8/12/2014 |
|
|
|
AU 2792 |
|
Daily Tasks | 8/13/2014 |
|
|
|
AU 2793 |
|
Daily Tasks | 8/14/2014 |
|
|
|
AU 2809 |
|
Daily Ideas | 8/14/2014 |
-On error messages for permissions, maybe include the name of the permission that is being requested. Also include the id number as a reference. -We had a request to add a bulk tool for invoices to update RFID tag numbers. The idea came from a consultant in Colorado. She might have more information and/or ideas. Look-up her company for her contact information. -On the bulk edit tool above, it seems that the tool needs to be two fold: 1. the invoice line items in bulk. 2. the actual item or part number based off of usage. This second one seems to hold a bigger weight right now. Interesting! Also, if we did do this, we might want to create a red admin permission that could be assigned as needed. |
|
|
AU 2773 |
|
Progress on the dream it up - your data, your world, your way! | 8/15/2014 |
This entry has a small history on the adilas slogans and graphics for the dream it up concept. See the gallery for details. 9/19/13 - Got original car and truck graphics from Russell Moore. This was part of the skin your engine stuff. 9/28/13 - Made a ink pen sketch in my notebook of how the layout might work. 10/31/13 - Got a first round mock-up from Tanya Bagley with graphics and text. 8/14/14 to 8/15/14 - Tweaked Tanya's graphic and added some new adilas slogans such as: "Dream it up, we'll help you wire it up!" and also included, "Your Data, Your World, Your Way!" |
|
|
AU 2794 |
|
Daily Tasks | 8/15/2014 |
|
|
|
AU 2810 |
|
Daily Ideas | 8/15/2014 |
-On the adilas GPS core layout, when the very center hub is clicked, show all of the different homepages with links to each homepage. Maybe set it up like the expanded chooser page with icons for the different homepages. (Or maybe it shows the map when the center hub is clicked.) -When we circle back around on help files, it might be nice to put a graphic of each page as part of the help file. A good example is the help file for the teacher/student interface (help id = 435). Notes on making full database copies: -We need to make a choice – add to an existing database or create a new standalone database. Our world building concept for databases is “solar systems” inside a “cluster” (box or domain name). -We need to be able to go both ways – new solar system or add to an existing solar system? -When copying, we need a master. A copy only works from a shared environment to a new environment. A copy may fail, due to id conflicts, from a shared environment to another shared environment. For this first round, shared to shared copies won't be allowed. Only shared to new will work for round one. -When checking between a master and a new solar system, do a query, check id's, and either insert or update depending on what we need. -Make it reusable for other corps. -I can see a future need for copying and moving from an existing shared environment to another shared environment. I wanted to avoid this crazy mapping and relationship stuff, but we may have to do it. Bummer! -We had a request to use the default invoice setting (print options) on quotes. Basically, the people want to go right to the mini quote once a shopping cart is saved. -On all new solar systems (new databases and database copies), add date indexing to all dates. This should really help with query speed. |
|
|
AU 3701 |
|
Brainstorming - In-Line Discounts | 8/15/2014 |
In-Line Discounts: - The root problem is deeper than the discount. It shows up in the taxes. - All existing math and reports use the “item price” times the “line quantity” to get the “item price extended”. This value is huge and is part of revenue and other reports. I would recommend not changing that field, due to how deep it is already entrenched. - We could add new columns such as: o Original list price o Original list price extended o Use in-line discount o In-line discount per line o In-line discount extended o In-line discount percentage o Discount campaign (added 10/22) In-Line Discounts per line item continued: Think about: - Stock/units - eCommerce - Restore to cart - Cart - Invoices - Quotes - What about removing a line item? - What about voiding things out? - Remember advanced add & edit to cart - Recipe/builds? - What about my cart favorite buttons? - What about discounts per line item? - What about discounts, cart as a whole? - What about returns & exchanges? - Hidden lines - Reports - Profit per line – invoices, quotes, and cart - Discount calculator - Edits - Bulk edits - Discounts on discounts - Update existing records - Servers - Add new corp - Script updates - Special code for “discounts” hardcoded - Discounts by customer type - Bulk updates per customer type - Steve’s idea to help cascade the discount campaign to existing customer types - Discount rate per customer - Help files - News & updates - Training - Settings - Exports to Excel - Icons - Validations - Flags for applied o 0 = no o 1 = % off o 2 = $ off total o 3 - $ off per - Converting old line by line to in-line per line (lots of lines) - Wholesale - Custom reports - Timelines??? - PO’s - PDF’s In-Line Discounts per Line Item: (See scans in photo gallery) Math for calculating discounts: % off: - Get # ____(given) %, take list price ($___ given) per times ____% = discount per $ ___ (calc), take the discount per $___ (calc) times the quantity (given), get the extended discount $___ (calc). - Do a second check using the extended list price $___(calc) times ___% = the extended discount $___ (calc). Compare the results extended discount / extended calc to extended discount/per calc. The rounding error goes in favor of the extended calc bigger value times the %. Discount $ off total: - Start with the total $’s off $___(given) – reverse the math, take the total $’s off and divide by the quantity: total $ off (given)/quantity. Check for division by zero, this gives you the discount per $___(calc). If you wanted, you could compare discount per to extended discount (simple math to compare). Next you take the total $’s off $___(given) and divide by the extended list price: total $ off / extended list $ (calc/given). Get calc___ number as a decimal. Times that number by 100 to get the percentage: decimal(calc) x 100 = ___% Discount $ off per: - Start with the $ off per $___(given) – Take that number times the quantity to get the total extended discount: $ discount per (given) x qty (given) = $ extended discount (calc). Next take the total $’s off – $ extended discount (calc) and divide by the extended list price: $ total off / $ extended list = get decimal – take this decimal (calc) times 100 to get the %: decimal x 100 = ___% In-Line Discounts per Line Item: (Math calculations table – See scan in photo gallery) - Qty (either sign) – given - Cost per (positive) – given - Extended (either sign) – simple math - List price per (positive) – variable but given - List extended (either sign) – simple math - Discount $ per (positive) – 3 way - Discount extended (either sign) – 3 way - Discount % (positive) – 3 way - Item price after discount per (positive) – simple math - Extended after discount (either sign) – simple math Examples – numbers – see scan in photo gallery Discounts are a 3-way decision: • Discount $ off per? • Discount $ off total? • Discount % off? • Might need a rounding error – see line #2 |
|
|
AU 2795 |
|
Daily Tasks | 8/16/2014 |
|
|
|
AU 2796 |
|
Daily Tasks | 8/18/2014 |
|
|
|
AU 2797 |
|
Daily Tasks | 8/19/2014 |
|
|
|
AU 2798 |
|
Daily Tasks | 8/20/2014 |
|
|
|
AU 2811 |
|
Daily Ideas | 8/20/2014 |
-Idea from my sister: As we start making adilas more and more a self-serve model, include the reps and consultants as the next level of automation and permissions. Let them get in and setup things. It is already headed in that direction, help feed things that way. -Maybe allow a request from a cluster to the upper galaxy and universe levels. That might be a cool option. Think of going up and down the chain of command. -On this new database copy project... Level 4 database or create new solar system project... Maybe use the analogy of a bus (older shared table structure) as compared with a motorcycle (newer, smaller, quicker table structure). Another one might be a raft vs. a kayak or a space ship vs. a smaller speeder or something. We are hoping that it will make that big of a difference. That would be cool! -”Teach them correct principles and let them govern themselves.” -Joseph Smith. Great council and advice. -We had a request to record shopping cart history. This is virtual memory. I can see a need for start, stop, save, create invoice (checkout), or clear. All other actions get into a micro management issue. It has got to come back to good principles... -When ready, we need to index main dates to numeric values. We also need to push date/time stamps out to hours, minutes, and seconds. Once we start to index that, it will be awesome! As a note, look-up numeric dates on adilas university for more info including numeric day of the week values. |
|
|
Adi 866 |
|
Intellectual Property Workshop | 8/21/2014 |
Brandon Moore, Wayne Moore, Cheryl Moore, Shannon Moore, and Dave Forbis attended a workshop on intellectual property in Logan, UT. The workshop was put on by the Small Business Development Center, Cooperative Extension of USU. The presenters were a law firm that dealt with patents, trademarks, copyrights, etc. See attached for my notes. What I got out of the workshop was basic information, timelines, ball park figures, and what is required. My favorite part of the workshop was dealing with how patents, trademarks, and copyrights can be denied and/or rejected. This might sound random, but I think that our goal is not to secure a patent on every little feature. Our goal is to defend patents being put on to core concepts. We need the model to be open and free. If not, it will swing power potentially in the wrong direction. So, in a nutshell, by us talking about things, publishing things, teaching, instructing, and building with openness in mind, we are helping to keep the patents out of the core of the ideas and concepts. Let people patent smaller pieces of the puzzle, that is no problem. However, we need to protect and educate people on the core of what we are doing. I have said this in private before, but I would bet that the core concepts that adilas.biz is built on are 100 times more valuable than the code that we have written over the years. There could be thousands of possible code angles on these same concepts. That is well and fine and a known fact. The important piece is protecting the core concepts and principles of what we are doing. We kinda fell into this... this wasn't our original goal. However, I do feel that we have some super important things that we are developing such as:
Anyways, those are some of the pieces that I see that we are doing and developing that could potentially be patented and/or copyrighted. They are listed here to start the process. |
|
|
AU 2774 |
|
Intellectual Property Workshop | 8/21/2014 |
Brandon Moore, Wayne Moore, Cheryl Moore, Shannon Moore, and Dave Forbis attended a workshop on intellectual property in Logan, UT. The workshop was put on by the Small Business Development Center, Cooperative Extension of USU. The presenters were a law firm that dealt with patents, trademarks, copyrights, etc. See attached for my notes. What I got out of the workshop was basic information, timelines, ball park figures, and what is required. My favorite part of the workshop was dealing with how patents, trademarks, and copyrights can be denied and/or rejected. This might sound random, but I think that our goal is not to secure a patent on every little feature. Our goal is to defend patents being put on to core concepts. We need the model to be open and free. If not, it will swing power potentially in the wrong direction. So, in a nutshell, by us talking about things, publishing things, teaching, instructing, and building with openness in mind, we are helping to keep the patents out of the core ideas and concepts. Let people patent smaller pieces of the puzzle, that is no problem. However, we need to protect and educate people on the core of what we are doing. I have said this in private before, but I would bet that the core concepts that adilas.biz is built on are 100 times more valuable than the code that we have written over the years. There could be thousands of possible code angles on these same concepts. That is well and fine and a known fact. The important piece is protecting the core concepts and principles of what we are doing. We kinda fell into this... this wasn't our original goal. However, I do feel that we have some super important things that we are developing such as:
Anyway, those are some of the pieces that I see that we are doing and developing that could potentially be patented and/or copyrighted. They are listed here to start the process. |
|
|
AU 2799 |
|
Daily Tasks | 8/21/2014 |
|
|
|
AU 2813 |
|
Daily Ideas | 8/21/2014 |
-Flood the market with ideas and concepts. Instead of trying to secure a patent on business world building concepts and practices, the goal may actually be to prevent patents on core pieces that are needed by businesses so they can go and do. -You have to give to get! Give people a taste... of what you've got. -You have to make things repeatable. Think, can anybody else do this? Can I put another actor in my place and have it succeed? If not, you need to get it to that level. Think of a play... Is it planned out enough that someone else could play that role? -You have to standardize things to a specific level. It doesn't have to be dry and boring, it can be super fun, but it does need at least a level of standardization. -Our clients are _________ (fill in the blank). Can I do this? If yes, what is the answer? Do I know who I am serving? Do they know what I'm offering? How does this interaction take place? Great questions. |
|
|
AU 2816 |
|
Notes from an Intellectual Property Workshop | 8/21/2014 |
INTELLECTUAL PROPERTY WORKSHOP Conference on Patents, Copyrights, and Trademarks -Creative act of the mind Copyrights: www.copyright.gov -Literary, musical, and artistic works -Physical, it has a life span, only covers the expression of the idea – not the idea Trade Secrets: -Formulas, practices, processes, designs, instruments, patters, or compilations of information – Have to have controls in place to keep it a secret Trade Dress: -Visual appearance of a product, its packaging, retail environment -Aesthetics - Look and feel Patents: www.uspto.gov -The concept, inventions, designs, plant, functional -Termed or time based – 20 years from date of filing -Utility and design – utility means useful -”Fair use” doctrine – make sure and site your sources. Trademarks & Service Marks: -Symbols, words, phrases -Be careful – if it becomes a generic term it could be over -Make sure and search first -Cost benefits and cost of protecting your intellectual property -Be proactive and do training on intellectual property -Patents – use a professional to help you -Patents – usually take between 3-5 years to be fully done Patents & rejected patents: -Prior art -Already printed publication -In public use -On sale or for sale -Or otherwise available to the public -Obvious or too general -These are things that we could do to protect future patents on stuff we are doing Trademarks: -Possible problems with consumer confusion – too close to another existing trademark -Instead of trying to help everyone... We need to focus in on our customers that are using our system. Keep them good and happy. Other customers will come. Focus on what we've got! -If you want to get something fixed... Have the person who built it use it for awhile. It will most likely get fixed pretty quickly. Kind of funny! Nobody likes to use something that is broken or hard. If the builder can see those issues, they will most likely fix it! |
|
|
AU 2800 |
|
Daily Tasks | 8/22/2014 |
|
|
|
AU 2801 |
|
Daily Tasks | 8/23/2014 |
|
|
|
AU 2802 |
|
Daily Tasks | 8/25/2014 |
|
|
|
AU 2814 |
|
Daily Ideas | 8/25/2014 | -Allowing people to do their own css (cascading style sheets) doesn't hurt adilas any. It only makes it more flexible. There is a lot of power in css. We only use it moderately inside of adilas right now. It could be a whole new avenue to help with look and feel. | |
|
AU 3702 |
|
Tech - Code & Database Questions & Table Relationships | 8/25/2014 |
Questions & Known Issues with Code & Databases: - It has got to start at the login level. This needs to include the corp id… That will help it know where to go. - What about application wide variables and queries such as locations – maybe move from application to session scope… - It might be nice to get away from domain (cluster) specific code and have the cluster databases hold that code. Thinking of the top secret application cfm pages. There are also other pages that might be able to be controlled by a database vs. a hard coded page value. What about storing all cluster settings in a single table as a JSON object – or – do we just need to script a new table? Or do we just stay with custom code pages. - We need to kill all the old web service feeds. If we do this, we may also want to change all of the references to the web service as far as links. Remember the main link on the root index cfm page. - Known holes: o In line taxes & discounts o Image folders – need to add o Web services to older server o We could do any of these as later projects - What about back doors? - aka test page stuff. This may need a data source setting in order to play. - What about user clock in/out between corporations. This could get lost very easily with multiple database or it could be easier. Just worry about what it can find… Let the user take care of the rest. - Anything that has crop specific stuff, needs to be held at the corp or world level. Think about moving corps… it all needs to go. - WE need to figure out the payee to corp access stuff. This will include a new history record of when and how long each person visits, views, and/or does anything from inside of the world or corporation level. Most likely, this will require a new history table per corp. - Leave a footprint for every corp switch and switch back… as a note, this may be able to be accomplished by using the payee login history table and just adding a corp id to the table. Just a thought. - What about cluster specific help files? We need to put the cluster specific stuff on the actual help file page, not in the database… That will help with updates & syncs. - What about controlling last updates statuses on cluster tables. This will also help with mass updates. Think about updates from the universe and galaxy levels. Table Relationships: - Payee permission list & payee permission categories - Payee permission list & payee to corp to permissions - Additional customer types & additional customers - Adjustment pos & purchase orders - Allinv, inventory types, makes, models, sub inventory types, title accounts, allinv history, payee, invoices, payroll status, allinv subs, store location, allinv final numbers, allinv asset types, allinv floorplan, customers, customer types, purchase by types, web price settings - Allinv ages, store location - Allinv floorplan, title accounts - App types, tie in flex grid, payee, tie in flex grid history, time sub assignments, cms media main, tie in flex grid titles, custom documents, balance sheet items, financial categories, financial groups, financial group subs, store location, balance sheet subs, balance sheet photos, payee, balance sheet history - Banks, deposits, receipt payments - Check request types, receipt types, receipt, payee - Country, banks, corporations, store location Key id’s that are specific: - Allinv payments: o Ties to floorplan id, receipt number, receipt line id - All inv subs o Allinv subs rec inv - Receipt line id o All inv sub line o All inv sub type extra o 2 – receipt o 3 = invoice |
|
|
AU 2803 |
|
Daily Tasks | 8/26/2014 |
|
|
|
AU 3703 |
|
Brainstorming - Developers & Remote Installs | 8/26/2014 |
- Corp id’s are huge - User or payee ids exist at a level 4 (solar system) level. - What about inter-world id #’s & outer-world id #’s for users. - It would be cool to be able to remotely update any look-up table via API/web service connections. Just thinking about developers & remote installs. |
|
|
AU 2804 |
|
Daily Tasks | 8/27/2014 |
|
|
|
AU 3705 |
|
Planning - Behavior Tracking School Project | 8/27/2014 |
Project for the teacher site: - Pull up the kids - Prep it - Cycle & see current data - School year start date: - School year end date: - Pull data year to date on sub dates & line Behavior is the main topic with: - Attending - Following commands - Following routines - Transitions - Others Layout & planning: See scan in photo gallery |
|
|
AU 2805 |
|
Daily Tasks | 8/28/2014 |
|
|
|
AU 2815 |
|
Daily Ideas | 8/28/2014 |
-Compare the adilas shared environment to a bus or large train. Basically, we have been selling seats on a bus or box cars attached to the train. With our new database work, we will be able to offer individual vehicles to companies. We may have some companies that choose to ride the train, but we anticipate quite a few companies wanting their own system – freedom! -On the updates and database copy... what if we could do that based off a date or date range. Originally, the copy was going to be all of the data from a shared environment to a new standalone system. If we could play with dates and date ranges, that could be very powerful. I'm thinking about options for all data, all data before a certain date, data between a date range, and all data after a certain date. I think that could be really cool and a great service. |
|
|
AU 2806 |
|
Daily Tasks | 8/29/2014 |
|
|
|
AU 2807 |
|
Daily Tasks | 8/30/2014 |
|
|
|
AU 3706 |
|
Planning - Behavior Tracking School Project | 8/30/2014 |
Behavior Tracking for school project: - Tracking behavior for students - We need both a one by one basis and a bulk or group basis - Maybe use session vars to hold groups - Maybe limit the custom buttons to a specific page URL. Do this for both core data points and Behavioral Tracking. Use a URL filter on each page. - Stay in a cycle - Really easy! - Limit time events to custom date range. On links & drill/downs - Set the time template as a setting - Use the elements of time title as the task - On the sub dates and times – record both the score and the behavior on the sub title field - Maybe use java script to help select values (buttons, images, and radio groups) - Show the latest results at the top of the page for behavior tracking Form & Layout Planning: - Name: - Date: - Behavior: - Score: - Selected Score: Form Planning: - Name: - Date: - Task: o Task list from main elements of time or be able to create a new one o Make room for the task section o Or create a new one by tying below - Behavior: o Attending o Following commands o Following routines o Transitions o Other - Score: o Positive o Negative o Other - Notes: - Submit: Notes Continued: - On paperwork… create one that has buttons or links to all data points, calendar, terms, logs, & follow-ups. This is a mini feeder report to help them get at the data really quickly. - Ask other people – my sister-in-law, my mom, the teacher, my wife, etc. Got ideas and stick to what they currently use. - Be able to get to the underlying data as quick as possible. - Maybe record the time template as part of the settings or tie it to the custom document assignment. Whichever is easier. - Allow the user (teacher) to add to the last main element of time or user a new element of time. Limited Student List: - First – Last o Log notes o Follow-up o Data points o Behavior details - Letter type: o Starting letter type of 5 o Customer name filter o Customer name - Pull the limited customer list - Pull in the custom settings date range and template id - Loop over the customers & pass the dynamics to pre-build pages |
|