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 - 6/1/2011 to 6/30/2011 - (82)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 494 |
|
Daily Tasks | 6/1/2011 |
• Basic business stuff. • Reoccurring invoices and credit card payments. • Working on the sub comments and notes for elements of time. • Logo for a company. Posted new colors and logo. • Also posted new time files. • Uploaded code to do sub action status logs, sub date/times and sub comments or additional notes. • On the phone with Steve. Quick update on what both of us are doing. He needs some help and magic in the coming weeks. |
|
|
AU 495 |
|
Daily Tasks | 6/2/2011 |
• Added a new summer banner ad for a company. Posted files online. • Added a real product image to a company’s website. Reactivated the PayPal shopping cart, made some verbiage changes and posted files online. • On the phone with Steve going over direction and current needs. We are planning a meeting for tomorrow and I told him that I would do some prep work and prepare a list of what I felt needed to be done. • Basic business stuff and writing an email about where we are at. • Worked on some tweaks to elements of time that I needed. They were a new priority sort, a due date bypass switch and a general budget frequency setting. Posted files online. |
|
|
Adi 3 |
|
Meet The Players - General Categories - List | 6/3/2011 |
This is a list of general categories or system players [view help file]: 4.1 - General Overview 4.2 - Accounts Payable (vendor waiting room) 4.3 - Accounts Receivable (customer waiting room) 4.4 - Admin 4.5 - Balance Sheet 4.6 - Banks 4.7 - Check Requests (sub type of the normal expense/receipts) 4.8 - Corporations 4.9 - Customers 4.10 - Customer Logs 4.11 - Customer Queue (check in/out) 4.12 - Data Exports 4.13 - Departments 4.14 - Deposits (monies coming in) 4.15 - Display & Interface 4.16 - Elements of Time (calendar & scheduling) 4.17 - Expense/Receipts (monies going out) 4.18 - Flex Grid Tie-Ins 4.19 - Floorplan 4.20 - History & Reports 4.21 - Ideas & Sharing 4.22 - Invoices 4.23 - Locations & Tax Settings 4.24 - Manufacturing 4.25 - Objects & Data Over Time (theory & concepts) 4.26 - Orders 4.27 - P&L - Income Statement 4.28 - Parts (general inventory pool) 4.29 - Payroll 4.30 - Permissions 4.31 - Photos & Scans 4.32 - Purchase Orders (PO's) 4.33 - Quick Search 4.34 - Quotes 4.35 - Recipe/Builds 4.36 - Reimbursements 4.37 - Settings - Corp-Wide 4.38 - Settings - Personal 4.39 - Shopping Cart 4.40 - Special Line Items (system parts) 4.41 - Splits (payments made on account) 4.42 - Statements 4.43 - Stock/Units (serialized inventory) 4.44 - Timecards (clock in/out) 4.45 - Tools & Maintenance 4.46 - Training & Support 4.47 - Users 4.48 - Vendor/Payees 4.49 - Web Presence & eCommerce |
|
|
|
Adi 4 |
|
PO's - Items on-order and in-transit items | 6/3/2011 | What about a transition PO... Something that is kinda real but still in the "transition" like a transition invoice. If yes, we hold all of the info and payments on the balance sheet until it goes live or becomes real. We need to cover the pre-payment and not fully in play states of things. This could be order, items in transit, etc. | |
|
|
Adi 5 |
|
Time - round 1 for elements of time | 6/3/2011 | Finished and launched round one on 9/30/11. | |
|
|
Adi 6 |
|
Support - General email support | 6/3/2011 | We need a way for users to be able to quickly email us... We currently have a contact adilas support page but only the support email address is listed. It may be nice to show options for sales or other key players. | |
|
|
Adi 7 |
|
Web - Full eCommerce | 6/3/2011 |
Here are a number of ideas related to eCommerce... no specific order... just dumping... - Small time eCommerce is where we want to go with this thing (adilas). People will pay the monthly fee just so that they can sell things. - We have created a fun thing in the buttons and what they can do (my cart favorites)... What if we allowed a similar thing with eCommerce. - A customer sign-in could be the customer id number and the email associated for that customer. The customer id would be able to look up the corp id. - I want to have a customer bill pay section where they can pay their bills, look at their payables, print invoices, and histories. Maybe even their own statements with limited functionality. - One big challenge might be shipping and handling... They are separate but somewhat linked. We need free, set, dynamic, and variable options. - I will be building a cart on one server and then passing the whole cart to another server for payment and committing to the database. That could get a little bit tricky and making sure that both sites (send and receive) get updated correctly. - What about inventory levels and selling items that don't exist? How do we handle back orders? - What about custom or web service options... Do we want to use XML, ColdFusion web services, basic HTML, etc? We want to make it portable, yet flexible. We will provide a cookie cutter or pre-built cart and allow for custom options. - Building custom carts could be a great side gig and money maker for me and/or another development company. That may be a great spot for interns and college folk. Create the tools and then open up the road. - We may need some mass or bulk update tools to help with shopping cart stuff. Sales, hide/show, active/inactive, my cart favorites, etc. Special reports. - Make the process as easy as possible. Many of our clients will be in the under 10 items pool. We may have others who are in the 100-10,000+ item pool. Think small to big... - Add photo upload options for part categories, buttons, and promotional banners. The more we can put at our user's finger tips, the better! - Allow a customer to create and save their own quote. - What about merging customer info... We already have them on file but they get entered or created again. - There will need to be corp-wide settings setup and maintained just for the shopping cart... What location, what invoice type, what user (generic), what customer type, what taxes, what promotions, etc. - A flash shopping cart may also be a fun option. Kinda extra. - Emails and promotions, etc. - Quick reports and notifications. Email about new sales. - Ask customers and clients what they want. - We may need a page that has or shows specials. Key off of the web price settings. Maybe have a section for special web prices, best prices, etc. - The price setting per item will either allow a sale or not. - What about quantities on hand? How do we monitor that? Do we check the real site or do we just do it and sort things out later (like back order, credits, refunds, etc.). For the record, it is easier to check first and deny at the door rather than ask someone to leave that is already in and committed. - Our goal is to provide the service... however, wherever possible we should also help our users learn and use good practices. - Keep it ultra simple - show a crumb trail (where you are at and where you are going). - Use email and/or text messages. - Have special reports for web sales. - Treat all sales as either customer sales or transition invoices. - I want to provide some simple buttons that allow a customer to create basic things like a quote, restore to cart, save as... (new quote), statements, pay a bill, real cart checkout, check on outstanding invoices. - Allow custom HTML to be assigned to parts and stock/units. This could be links to movies, tables with rates, calendar graphics, virtual tours, sub navigation, additional verbage, headers, footers, special notes, etc. Think anything custom. It could be added before or after an item - or even both. It could be a one-to-many relationship between the custom sections and the items. We need to allow for sorting, spacing, etc. Basically, a mini snippet or wrapper. Other ideas... links to like products, promotions, ratings, testimonials, availability, reminders, colors, sizes, options, recommendations, waivers, forms, checklists, rosters, syllabus, course work, coupons for local businesses, updates, closures, etc. - Maybe pass back data in XML format instead of letting ColdFusion generate the data. This would make our methods more usable to other developers. Maybe a step further down the line would be to pass a param (coldfusion or xml) to the web services and then let the user decide how they want to deal with the results. If xml, convert and send back. If coldfusion, just process as normal. The XML could be a standalone function that takes a ColdFusion structure and creates the XML notes and pieces. Think reuse... - On the stock/unit photo galleries... we need the captions to show up like they do on the parts galleries. - eCommerce may also include custom pdf documents or other special paperwork or forms (pdf, word, excel, other). - On the corp-wide settings... Maybe have options for show only (default), quote only, or full eCommerce. Maybe instead of a choice (one or the other), maybe create a list of options and let the users select what they want people to do. This list may be extended to customer login, bill pay, reservations, statements, etc. Think options... To help with outside code (additional web services or custom eCommerce web sites), pass all incoming data through a verifier or validator or sorts. If the incoming data is missing one or more pieces, either ask for it or use a default value. That way all of the main code can run as needed. This allows us to update things (normal flow and values) and still allow for possible older outside code to function correctly. |
|
|
|
Adi 8 |
|
Customers & Web - Customer pay portal | 6/3/2011 |
See element of time # 7 for more details on full eCommerce. - A customer sign-in could be the customer id number and the email associated for that customer. The customer id would be able to look up the corp id. - I want to have a customer bill pay section where they can pay their bills, look at their payables, print invoices, and histories. Maybe even their own statements with limited functionality. |
|
|
|
Adi 9 |
|
Reports - All grouped reports | 6/3/2011 | This is partially done but we wanted to have each section have options to pull grouped reports. Most of adilas is based on details or individual items. Some people don't really care about the details unless they have a question. This is a pretty big project because it touches some many different application types and data groups. | |
|
|
Adi 10 |
|
Reports - Direct links to sub sections | 6/3/2011 | The goal here was to map out the system in such a way that we could jump to any page within the system at any time (including the sub pages). The trick here is to organize things and then also make sure that all of the sub pages are able to handle possible dynamic page params. To see a related topic... see elements of time # 412 (my favorite links and buttons). These sub link options would end up being part of the options that would be available to pick from. | |
|
|
Adi 11 |
|
Training & Web - adilasuniversity site | 6/3/2011 | The adilasuniversity.biz site is the future training ground for adilas clients. We have a bunch of things that will end up being there, but they are all currently under construction. One of the project will be a multi-media player of sorts (see time # 450). I have tons of loose brainstorming papers on ideas and subjects for the university and training site. | |
|
|
Adi 12 |
|
Photos - Secure images & use a content server | 6/3/2011 |
Random notes about the content server... - On the current thumbnails, take off the height attribute and re-do all thumbnails. This allows for square, portrait, and landscape images. - Maybe allow for other content to be saved... Create special images and icons for word docs, excel files, adobe pdf, and other generic files. Images would have their own icon (mini thumbnail) and other docs would use these custom graphics. - Set an upload size limit. Say like 2 MB and then let them upload whatever they want... We might need to be careful with things like web code, java-script, sql, etc. - What about virus protection? What do we do about that? Does that really matter? How would it affect us? What are the other possible threats? I do have a full sheet of notes that are dated 3/21/11 in my file at home with about 20 ideas and feature requirements. |
|
|
|
Adi 13 |
|
Look & Feel - My quick buttons & links (favorites) | 6/3/2011 |
See element of time # 412 for more info. It would be really cool if we could marry the my cart favorite buttons with the old mend and repair (build your own report) settings. The new buttons would then show up as standalone buttons and/or in the interactive map layout. Another idea is have a full list of every possible link in the system and then allow the users to pull up the links, name them, save them, and categorize them. The initial interface would be broken down into application types and then broken down into subs from there. Another idea is to have a link on each page (say like in the heading) that allows that page to be pulled in automatically to the favorites. Kinda like a bookmark or favorite inside a browser. If that page needs criteria, it would then prompt for any criteria. That way, the users would know where they were at before creating the favorite or link to that page or section. New idea added on 9/25/12 by Brandon - What if we just did a big one-to-many and allowed any existing report in the system to be saved (the settings). The main values would be a report id (dynamic key field), the report name, the page name (destination page), who it was assigned to, and a status field. Other values may be public/private or something like that. The many part would be the report id (tie-in value to the main report), a variable name (setting name), a value (setting value), and a status. We would then be able to pull the reports and then set the correct criteria or just run the reports and look-up the saved settings or values on the fly. This would be really cool... Instead of making a whole big brand new super report, we could just harness all of the existing reports and result pages. All we would have to do is pass a special saved report id number and then have the report pages look-up the values and play accordingly. That would be a huge time saver (not having to re-create this huge super report structure). Along those same ideas... We may need to add special date presets or hardcoded date keywords. We could then dynamically figure out those dates by having a global function that could interpret the keywords. This could be things like: today, yesterday, tomorrow, thisweek, lastweek, nextweek, thismonth, lastmonth, nextmonth, ytd, or a special value called "prompt" which would allow you to enter the custom date range on the fly. This whole system could be saved per user, shared between users (like public cart favorites), and dealt with in a controlled manner. As a side note, we may want some global functions or global responder pages that know what to do and then pass the data to the correct sub pages or sub reports. Just some ideas. |
|
|
|
Adi 14 |
|
Settings - Look & Feel - Graphics and icons | 6/3/2011 |
We know that at some point, the entire interface will need a graphic facelift... A couple thoughts are: 1. Allow the users to upload there own button graphics or icons (this allows for a custom look and feel). 2. Use our own standard buttons or icons (keep things consistent). We may end up having the icons be mini thumbnail images of the pages themselves. That would really save time and help show the users where they are headed... The other thought deals with a number of personal settings that are controlled and setup on a per user basis... let them tweak and customize things as needed. See element of time # 412 for a thing called my favorite links and buttons. |
|
|
|
Adi 15 |
|
Taxes - sales tax & collected fees | 6/3/2011 |
Note added on 7/19/12 by Brandon - Sales Tax - we need to start on the location homepage. We need to assign real vendors, real expense/types, and real user-maintained balance sheet items. The key is the locations... that is tied to the tax settings, that is how it is recorded and collected (on invoices), that is how it will be paid out, etc. A good resource is Jeff McCorvey who has 30 locations with 8 different states and tons of smaller entities that need to be paid and tracked. Small idea on the sales tax re-work... What if we added two more levels. The top level would be a quick - to the point - group for the date range. The next level down would be a breakdown by day, the last level would be the detail level. If a fourth level was needed, it could be level 3 as a invoice group and then level 4 as all of the details for that invoice (advanced invoice line item search). Just some ideas. The other thing that I want to do is take out the invoice total (with taxes). I just want to show the amounts that need taxes and the taxes. Don't worry about the amounts plus taxes (full invoice totals). New note added on 9/10/12 by Brandon - We just spent a whole week doing a rework on the sales tax page. We still need to automate flow between invoices and balance sheet item and balance sheet items and expenses but we did do a bunch of prep work and created the 4-level deep reporting system described above. Those files are up and online as of 9/8/12. |
|
|
|
Adi 16 |
|
B.S.I. - Balance sheet rework (round 4) | 6/3/2011 |
We need to circle back around and work on automating sales tax, collected fees, standalone declarations, watchers, feeders, hybrid callouts, etc. This is quite in depth and is what we would be calling round 4 of the balance sheet. As a note, on 7/4/13 we had another request from Kelly Whyman to add some sort of off the record type entry that a CPA makes. This would allow the owner or manager to see things as they really are and/or see things as they become adjusted according to specific entries. Kelly was requesting this show/hide option that could be turned on/off as needed. I (Brandon) replied to the email and mentioned the "standalone declarations" that are planned for adilas. Here is some info from the email. Kelly, Great ideas! We love it! Now if only we could find some time... :) I'm not sure if I've ever mentioned this before but have you ever heard of a thing called a "standalone declaration". This is a future adilas project that I think could help you out. A standalone declaration will be a physical entry that is mapped to a specific spot within the financials (income statement and/or balance sheet). It will be called a standalone declaration because it just exists or was created (kinda pulled out of the air if you will). It doesn't really have any backing or supporting documents other than it was an entry that was required or requested by a CPA. We are going to call these entries a standalone declaration to help them stand out or be their own little sub set. In order to help with the show/hide options, we could add a special show/hide flag or we could add an option for "real" or "taxes only". Another thing that we could do is allow the dates to be very general. Most of the dates inside of adilas are a physical date such as 7/4/13. However, if we needed to, we could allow for things like: In 2013 or in July or 2013 without going clear to the exact or physical date value. Anyways, just some ideas and food for thought. Enjoy your day and keep the ideas coming. Even if we can't jump on them yet, we can at least record them. That is at least a start in the right direction. Thanks, Brandon Moore 435.258.5504 (home/office) brandon@adilas.biz :: www.adilas.biz "all data is live and searchable" ----- Original Message ----- From: Kelly Whyman To: Brandon Moore - adilas.biz ; Stephen Berkenkotter Sent: Thursday, July 04, 2013 1:40 PM Subject: HUGE SUGGESTION - The need for an additional day on the Balance Sheet or Option for Adjustments to be seen or hidden Gentlemen - Happy July 4th, with it being independence day, I have a huge request for the Adilas System. Is it possible to add a day or some time of sub section to the system that allows adjustments to the P&L/Balance Sheet to be shown or hidden. So many CPAs adjust clients books and it takes away from the ability to see the business as it was prior to adjustments. Originally Steve had mentioned an extra day of the year. I would like to suggest you allow the adjusting entry mechanism (Invoice, Deposit, Expense, Balance Sheet Detail) to have the ability to be active or inactive when viewing P&L or Balance Sheet. Is this possible? It would be something that no other system is capable of doing. Best, Kelly |
|
|
|
Adi 17 |
|
Training & Reports - Roll call page for every major item | 6/3/2011 |
We need the "roll call" page for every major item in the database. Who are your buddies, your mom, your dad, your brothers, sisters, cousins, etc. Where else do you play? Who is connected to you? When and where do you show up in the financials? What are missing? What do you have? What are your next steps? How long have you been at your current state? You get the picture. Basically, how does each item play or get played with... :) See element of time # 27 for ideas on the reflexive side of the flex grid. These two items are somewhat related. |
|
|
|
Adi 18 |
|
Reports - User history reports | 6/3/2011 | This project is part way done... The current portion is located on the history homepage and is called the "Historical" report type. Currently, there is no way to search the user history records for specific data or by a specific person. It is fairly general and done on a system-wide basis. We do have a user specific report, but it is only done on a per user basis and is filtered by the current user that is logged in. Ideally, the full user history report would need to be searchable by type, description or notes, and by specific users for certain date/time ranges. It would be cool to be able to search for timeframes (smaller sections of time) as well. For example: What was done by Jimmy between 12:00 pm and 3:30 pm? | |
|
|
Adi 19 |
|
Reports - Financial roll call history report | 6/3/2011 |
The history homepage needs another history report for the financial roll call of the items. This would be what shows up for the financials according to the date range provided. This report would report on revenue, cost of goods sold, expenses, assets, bank stuff, inventory stuff, liabilities, and equity. In old school terminology "your entries". Kinda like an income statement (p&l) and balance sheet all rolled in to one report. Basically, what does the data do on a financial level according to the date range provided. This might be fun to experiment with different report types and show things in a cross between a calendar and a grid matrix. The report would have rows and columns. Each date could list any possible system pieces and how they play into the different financial categories or reports. Time (dates) would go across the top and players would go down the sides... All data would have drill-down links to the common advanced search page resutls so that more details could be seen. There might be a max of 31 days (a month) so that the page doesn't go on for ever in the sideways format... :) Another option would be to show this data in a calendar type view with what happens on each day... Kinda a calendar view of the system and who is playing and what is happening... Just ideas... :) |
|
|
|
Adi 21 |
|
Training - general user manual | 6/3/2011 | ||
|
|
Adi 22 |
|
Training - Adilas theory | 6/3/2011 |
There are tons of different adilas theory items... each one needs its own place to be talked about and shown how it plays into the process... No specific order, just brain dumping... Centralized data, empower the users, enter once - use many, go to the source (transactions and where the events take place), flexibility comes from settings and permissions that get interconnected, water droplets turned into slush then snow and then ice, business zipper (bring operations and accounting together one cog at a time), teach the why, track every penny in and every penny out, track objects and data over time, roll call accounting, accopps (mix and blend accounting with operations), linear checkpoints and data flow (pull), function over fashion, train and teach people not subjects, life cycle, pioneering the future of business, listen to our clients, under promise and over deliver, give to the people (there will be plenty left for us), education, train the upcoming generation(s), build a relational model, think add-on's and subs, all data is live and searchable, always up to date, no limits, your data... you cache & retrieve it... we secure it, we are one big data portal, community project and community effort, giant tool box - you get to match the tools with the jobs, 3D business model, always open and available, bridge the gap, trystorming vs. brainstorming, peace of mind, super user friendly, digital filing system, ongoing development, go mobile, touchscreen, business data sphere, play the game (rules, players, actions, goals, etc.), everything carries its own weight and luggage, return and report, users are bigger than corporations, one-to-many relationships, new school vs. old school, business platform, be your own style, catching the vision will inspire and guide you, business data mapping, start a revolution, customize your solution, put the horse in front of the cart (as compared with the cart leading the horse), see the whole picture! Anyways, here are some other words that I needed to record... Lean, just in time, continuous flow, eliminate waste, ease of entry, precision and accuracy, flexibility, pull... all good stuff! What if you look at things from a user's view... Does that change the "why"? "How"?... I was talking with a physical therapy guy (Sharik Peck) and we were talking about ergonomics and production (workplace safety stuff). What are the human components? If things are multiplied what does that do? Standardization helps flow. Teaching the "why" helps downstream customers and other employees. Distribute the work flow! Easy repetitive steps and processes. There is a guy by the name of Ammon (in the scriptures)... He was a master at serving and building on common ground and common beliefs (Alma chapter 18). When showing how we are different (old school vs. new school) build on common beliefs and reasons for doing what we are doing. Try to focus on the common threads. I've got a two page document in my notebook that goes over the progression of accounting and bookkeeping (dated 3/17/11)... Maybe instead of saying... Look what we have... Say something like "if this helps, great! If not, that's ok - we just wanted to share what we've learned." Help others help themselves. Another great quote is "Teach them correct doctrine and let them govern themselves" Joseph Smith. Sometimes the answer is a change of perspective... the situation may be the same but your view or understanding of it changes. |
|
|
|
Adi 23 |
|
Time & Web - Online reservations | 6/3/2011 |
See element of time # 427 for some ideas about rentals and reservations. Also, as a note, Brandon has a ton of brainstorming sheets that cover these topics in depth. It would be a good idea to review those documents when actually doing this project. |
|
|
|
Adi 24 |
|
Web - main adilas.biz face lift | 6/3/2011 | ||
|
|
Adi 25 |
|
Web - automation for new corp setup and payment | 6/3/2011 | ||
|
|
Adi 26 |
|
A/P & Reports - Full payables rework | 6/3/2011 |
We need to do a full payables rework... We need to break things into 0-30, 30-60, 60-90, 90-180, 180-360, and over 360+ for aging. The current code does not take into effect the paid date values. The payables needs to be modeled after the receivables section (a rework was done there back a couple of years). One of the problems deals with dates and date ranges. Currently, if a date range is used, it pulls everything. We want to be able to filter by the paid dates and paid status. Another known issue is the ability to manually update all of the paid status and payables stuff. We have had a few instances where the user paid for something but then can get it out of the payable because all of the manual checkboxes (admin side of the expense stuff) were not shown to them. We need a super admin page where all of the backend payables, paid date, paid switches, mark as payable, reimbursement stuff, and other verify, post, and admin options are available. As a side note, we would most likely have to really nail down the logic and validation, but there have been times when a super high admin type roll is needed, if anything goes wrong. |
|
|
|
Adi 27 |
|
Flex Grid - Reflexive side of the flex grid | 6/3/2011 | The flex grid is a user-maintained section or addition... The reflexive side of the flex grid is showing other associations without actually having to go to that item and create the link or new tie-in. It basically allows any connection to go both ways instead of just from main to sub. This would allow subs to report back that they are part of the main without specifically creating that link. Once a relationship between application items exists, the reflexive side shows up as being part of an existing relationship. See element of time # 17 for details on the "roll call" page for each item. These two items are somewhat related and deal with a system-wide roll call of sorts. "Who are your buddies?" | |
|
|
Adi 28 |
|
Photos - upload pdf | 6/3/2011 | ||
|
|
Adi 29 |
|
Invoices - interactive cart, quotes, and invoices | 6/3/2011 | ||
|
|
Adi 30 |
|
Payroll - payroll rework | 6/3/2011 | ||
|
|
Adi 31 |
|
Training - Map out entire system | 6/3/2011 |
When getting to a detailed level about what the system does... Go through the code and note all forks, decisions, assumptions, and normal flow logic. Put those values in to normal English and dummy things down a bit... :) This concept of mapping out the system started back in Sept./Oct. 2010, and let to the development of the interactive map concept. I have a number of loose pages with brainstorming ideas on the system mapping sections... see Brandon's adilas brainstorming folders. Also, here are some other random notes that I made in my notebook. These notes were part of a picture that was drawn in my notebook. The picture was of a globe or data sphere... Here are some of the notes... Not bound by walls, virtually jump to any place at any time, if you ever get lost... return to the main homepage or main hub, the quick search is like a little vehicle or transport pod to multiple parts of the system, it (the quick search) follows you to every page. Think interconnected levels, orbs, stations, functions, processes, jump points, cores, short-cuts, stages, key points or flag, full life cycles, waiting rooms, staging zones, traffic patterns, etc. Show permission levels and how they interact or overlay the data and life cycle of the objects and data. This is the adilas "data sphere" model. Learn how to play the game... relate the model to the game of golf with fairways, greens, roughs, sand traps, lakes, bunkers, etc. Help the users visually see where they are and where their data is (good to go or in the sand trap). |
|
|
|
Adi 32 |
|
Customers - Promotion codes & marketing | 6/3/2011 |
Random notes about promotion codes and marketing... no specific order... just dumping... - We also need a way to track sales and promotions. I have a great start done on LTF... It would need to be modified and beefed up a bit but a great start. Be able to pass promo codes in from the outside or from outside sources. This would then become trackable. - People want to track the source from where the codes come from and how often they are used. This could be for specific reps, specific items or products, for from specific places (sites, banners, ads, magazines, etc). Basically, they need a way to track their marketing. - The promotions and sales need to be able to tie to time, dates, and even small segments of time (for example a happy hour or block of time per day - very tiny or sub section of a date or dates). |
|
|
|
Adi 33 |
|
Maintenance & Reports - Import and export tools - data in/out | 6/3/2011 |
We need to get people access to their data... This actually helps us lower our liability in the case of disaster... If they have access to it and didn't ever use it, it falls on them not us. Giving people access to their data give them piece of mind as well... Let them get it how and when they want it (web, pdf, excel). Good stuff! Exports that need to be done: Invoices - done Customers - done Flex Grid - done PO's - done Parts - done Expense/Receipts - done Deposits Bank Registers or Bank Reconciliation Employees/Users Quotes Vendors Recipe/Builds Elements of Time Stock/Units P&L Balance Sheet Payroll Numbers On data imports... we are going to keep that on a custom level for right now. If we did provide a tool, we would need to allow for mapping or force everything to a standard data structure. The current vote is to keep the import of data on a custom (tech support) level. |
|
|
|
Adi 34 |
|
Reports - Build your own reports | 6/3/2011 | As a note... this may end up getting tied to a thing called my favorite buttons or links. This is not for sure, but just wanted to chime in. See elements of time # 13 and # 412. | |
|
|
Adi 35 |
|
B.S.I. - known issues report | 6/3/2011 | ||
|
|
Adi 36 |
|
E/R's & B.S.I. - Reoccurring expenses and balance sheet items | 6/3/2011 |
We have had tons of requests for reoccurring expense/receipts and the ability to duplicate an expense. Most of these are tied to user-maintained balance sheet items. It would be really cool to get the expense side of the balance sheet in place when we do this release. By way of an idea... When a balance sheet expense type is used... We had the idea to play a virtual game of tennis. What this means is that we show the amount on one side and then virtually ask who (on the other side - bs side) needs to get the ball. It could be one or multiple players. One of the hardcoded options would also be "Bank/Cash". |
|
|
|
Adi 37 |
|
Invoices & E/R's & Checks - Print multi interface | 6/3/2011 |
This feature has a number of different pieces. One is printing multiple invoices at a single time. The other pieces deal with either labels (invoice line items) or checks that are ready to print. There is already a page to help with invoices but you have to manually add the invoice numbers. There is a minimum of 10 per multi run. See the secure/print_simple_invoices.cfm page for details. Ideally we would have a point and click interface that would feed the multi print queue. You could click a certain number of items and then click one print button. It would then process all of the different pieces. The primary tool will be done in some form of HTML with css page breaks being added to the different pages. If more control is needed, we could send the info to flash and automatically hit the print button. It could even be done in a frameset with options on one side and commands being executed in the other window. Not exactly sure what direction to head in. Another multi print queue option might be to pass lists of info to the players and have them loop and print, loop and print. These multi-print queues are for things that need specific print sizes, specs, and exact placement needs. These are things like checks, labels, and multiple invoices. |
|
|
|
Adi 38 |
|
Customers - customer type - sales reports | 6/3/2011 | ||
|
|
Adi 39 |
|
Look & Feel - touch screen interface | 6/3/2011 | ||
|
|
Adi 40 |
|
Reports - run on grouped totals | 6/3/2011 | ||
|
|
Adi 41 |
|
Web - merchant processing - batches, deposits, tips, authorizations, etc. | 6/3/2011 | ||
|
|
Adi 42 |
|
E/R's & PO's & Vendors - searchable additional vendor tie-ins | 6/3/2011 | We need a second (or more) vendor/payee for the expense/receits and PO's. One would be the payable and the other (or more) would be a vendor look-up or additional tie-in. Only the first one would be required. | |
|
|
Adi 43 |
|
Photos - other photo galleries | 6/3/2011 | ||
|
|
Adi 44 |
|
Reports - dashboards, graphics, charts, eye candy | 6/3/2011 | ||
|
|
Adi 45 |
|
Photos - Be able to replace the mini thumbnail | 6/3/2011 | Finished on 3/27/12. | |
|
|
Adi 46 |
|
Bank Stuff - automatic ACH or EFT payments | 6/3/2011 | ||
|
AU 496 |
|
Daily Tasks | 6/3/2011 |
• Added two new sales sheets as PDF links to company’s site. Posted files online. Invoiced for 1.5 hours. • Ideas and to do list for meeting with Steve. Did some prep work for our meeting and added 40+ new elements of time to our ideas and virtual to do list. • Worked on commission checks for reps. • On the phone for 2.25 hours having a phone meeting and going over stuff. We had quite a talk about a number of different pieces and subjects. They mostly dealt with training customers and helping people get going on the system. It is getting hard to figure out which way to jump. We decided that I would help with some tech support stuff and start pushing towards light training and a richer and easier interface model. |
|
|
AU 2210 |
|
Brainstorming New Homepage Views | 6/3/2011 |
New Home Page Views: - Move all searches to a basic search page - Add a grouped report page - Take off current html add buttons and add a new button graphic - Think flow and logic - Dummy it way down, the back end will still be very sharp but make it simple - Add buttons to help get to the data easy - Once the button graphics are created… allow those same graphics to be used on the my favorite buttons section - Think sand bagging… getting ready for a flood mentality. We need to get done… - Make all graphics into jpegs so that we can use them over and over again. Make the buttons standard – meaning the my favorite buttons might look like the buttons used on the home pages. - Help via graphics… kid simple - Another idea for the button graphic is a mini version of the page itself - What if you spend a day creating a workable mock-up and posted it online. Lay it out like a plan with this will do that and this will do that. Show a couple of images etc. Buy some time, set a completion date in to fall. Update the to-do list. - Add a button for getting started with basics and printers and small tutorials. Do this right from the main home page. Maybe a door opening up to take a look inside. |
|
|
|
Adi 47 |
|
Invoices - Request from Craig | 6/4/2011 | Transfer invoice - he wants to be able to dupe and save as quote | |
|
|
Adi 48 |
|
Invoices - Request from Craig | 6/4/2011 | Quick add - Add discount as after the fact, as most invoices do. Add Freight as after the fact, as most invoices do. This is important to his type of work as most companies do not know until after the fact the freight amount or the discount because it is driven by the customer paying early and taking the % discount ......... short paying the invoice. | |
|
|
Adi 49 |
|
Invoices - Request from Craig | 6/4/2011 | Freight line at the bottom of the invoice. | |
|
|
Adi 50 |
|
Invoices - Request from Craig | 6/4/2011 | Weight line on invoice and total quantiy line on invoice. Corp wide setting? I have quite a few that want to see the total purchased amounts | |
|
AU 497 |
|
Daily Tasks | 6/4/2011 |
• Small logo fix for a company. They had virtually uploaded their own logo via an outside website and then used a full URL path to the logo. Pretty creative. • Worked on a customer migration problem for a company. • Worked on about 10 checks for adilas reps. • Lots of flex grid stuff. • On the phone with Steve going over things. We talked about the barcode generator and tweaking that a bit. We also talked about doing a small plan to roll out the new interface and what steps would be required. We also briefly talked about the state proposal and what possible liability that would be for us. I feel much better about everything and I’m excited to keep working on the master plan. • Bank work. • Small tweak on my cart favorites. • Made inactive buttons be hidden unless wanted for the bulk sort page. • Added a description field to the barcode generator flash widget application. |
|
|
AU 518 |
|
Daily Ideas | 6/4/2011 | -Add my own file upload and database utility. Use that for small things and then use the major deal (normal) for bigger projects. Add extra security to help who gets to use the special pages. Include https requirement, payee id, permissions, special password and an IP filter. | |
|
AU 498 |
|
Daily Tasks | 6/6/2011 |
• New logo for private investigator play site, • Worked on the barcode generator description option. Added a number of drill-down links to the label generator throughout the application. • On the phone with a guy from a merchant processing place gong over the adilas business plan. • New logo for a company. • Tech support. • Reoccurring invoices and posted all of the new barcode and description label changes. • Did some light testing. |
|
|
AU 499 |
|
Daily Tasks | 6/7/2011 |
• Working on a company’s website. Took off the made in the USA line and read over other content. Uploaded new pages. • Spent quite a bit of time writing a big email back to a customer about changes and requests. • Looking at some stuff for a company. They had some questions about inventory tracking. • Did some invoices and normal business stuff. • Added a new contact support page with an email form. • Uploaded the pages and did some testing. • Updated help files and pulled down a full database backup. |
|
|
AU 500 |
|
Daily Tasks | 6/8/2011 |
• Bank work. • Reviewed pages that as associate made to help with training. Sent an email back to them with feedback. • Worked on the interactive map mock-up page. |
|
|
AU 501 |
|
Daily Tasks | 6/9/2011 |
• More tweaks on the interactive map layout. • Added the word manufacturing to the on-order button. • Did some basic business stuff. • Worked on adding image map links and buttons to the interactive platform map. It is still just a graphic but it has tons of little links overlaid on top of it. |
|
|
AU 2211 |
|
Brainstorming What is still needed to roll everything out like we want to? | 6/9/2011 |
What is still needed to roll everything out like we want to? - Ecommerce and customer pay portals. Maybe online reservations. (2 weeks) - Help files (3 days) - Grouped reports (2 weeks) - My favorite buttons (2 weeks) - Graphical navigation and page flow (all sub homepages) (2 weeks) - My user history - Flash media player (2 weeks) - Roll call page with associative reports flex grid and other system ties (3 days) - New credit card gateways (Lucy and First Data) show groups then details (2 weeks) - Balance sheet rework – round 4 (1 month) o Feeders o Watchers o Known issues o Standalone declarations o Payables rework o Taxes and collected fees - Training manual and adilas university… Ongoing project (1 month) - User history reports (3days) - Financial history reports (1 week) - Small tweaks to current history reports (1 day) - New photo galleries and moving over to content server (2 weeks) - Payroll rework (1 week) o Gross sales o Elements of time (subs) o Reports - Ideas and sharing… global updates, global idea center, global forum, all elements of time (1 week) - Objects and data over time – adilasuniversity – theory and concepts (2 weeks) - On order and in transit tracking (1 week) - Sub locations and how they tie-in to things (1 week) - Elements of time (1 month) |
|
|
|
Adi 51 |
|
Training - adilasuniversity - Add a section with scans of old brainstorming files | 6/10/2011 | ||
|
AU 502 |
|
Daily Tasks | 6/10/2011 |
• Did some research on BB Flash Back (Blue Berry Software) screen capture software. • On the phone with a customer going over things. • Worked on a small sneak peek graphic for elements of time. • Added a couple of new pages to help with ideas and sharing objects and data over time. Both of the new pages deal with landing pages coming off of the interactive map. |
|
|
AU 503 |
|
Daily Tasks | 6/11/2011 |
• Basic business stuff. • Reoccurring invoices, payments and bank work. • Added some new history homepage tweaks and changes. • Added new URL date switches for values like today, yesterday, tomorrow, this week, last week, this month, last month and year-to-date. • Also worked on sorting application types with dynamics included. |
|
|
AU 504 |
|
Daily Tasks | 6/13/2011 |
• Worked on help files. New help files for the interactive map and documented all of the quick search options. • On the phone with a customer working on doing settings for their Authorize.net account. • Random phone calls and tech support. • Added elements of time and reoccurring invoices to the history homepage report. • New logo for a company. |
|
|
AU 519 |
|
Daily Ideas | 6/13/2011 |
-Sometimes the work “help file” may scare people. Maybe use the word “more…” or something like that, just an idea. -When doing time we need to record values that start on a specific date, get closed, are due, have subs, etc. We need to check a bunch of different things. |
|
|
AU 505 |
|
Daily Tasks | 6/14/2011 |
• Basic business stuff. • On the phone with contacts going over elements of time and what is where and how things work. • Checking credit card processing for a company, still having problems. • On the phone with Steve going over progress and needs. • On the phone with a customer, he needed some training and wanted a few new features on the advanced customer search report. • Looked at criteria for the Lucy gateway. • Also reviewing the PA-DSS compliance stuff, huge document. • New logo for a company. |
|
|
AU 506 |
|
Daily Tasks | 6/15/2011 |
• On the phone with a contact that had two main requests. One was to get the customer type to pull into the cart. The other was a dynamic one-to-many (1-many) on parts and prices. • Basic business stuff. • Banks and reoccurring payments. • Prep work on customer files for new company. Lots of stuff will need to be combed and filtered. • Added some new advanced customer search features. • On the phone with a customer going over their customer list and what is required for the migration to adilas. • Added the customer type to the shopping cart. • Four new logos. • Uploaded the advanced customer search options (show salesperson, filter by phone, address, email). • Uploaded new shopping cart pages. |
|
|
AU 520 |
|
Daily Ideas | 6/15/2011 |
-On users and their permissions – it might be nice to see a grid of all users and all permissions at the same time. General overview. -On banks – do we need options for liability and equity banks? B.S.I question. -Need a second vendor/payee for expense/receipt. One could be the payable and one would be the vendor look-up. Only the first one would be required. -We need to tie-in to each invoice for payroll. This helps show the underlying details of the numbers. This could be 1-many. -Pull in customer type to cart, quote, invoice and sales reports. Need a dynamic one to many on parts and prices. This could be in the cart mode, from buttons, as an extra step, done in bulk, etc. This may also need a time element, a customer type and other settings. |
|
|
AU 507 |
|
Daily Tasks | 6/16/2011 |
• On the phone with Steve going over things and what direction to take. We spent quite a bit of time talking about a one-to-many relationship between parts and customers and vendors. We know this is a need but it gets kind of deep quickly. • Small migration for a company. Migrated their salesperson info. • Did the customer migration for another company. • On the phone with a customer going over an old payroll issue from last year. • Worked on the adilas history page bio. • On the phone with a customer going over customers and patients and how to get them into the system. • On the phone with Steve going over things and what not, good stuff. • Working on the flex grid for a company. Forgot to migrate a mail out field for them. |
|
|
AU 508 |
|
Daily Tasks | 6/17/2011 |
• Finished up the flex grid mail out update for a company. Also did a quick flip of home phone and cell phone values. • On the phone with a customer going over update inventory counts and using an update PO. • Added an update inventory count link to the PO homepage. • On the phone with customers doing mass PDF upload and possible security hole. |
|
|
AU 2212 |
|
Brainstorming Tweaks to be made to the Flex Grid Tie-Ins | 6/17/2011 |
Tweaks to be made to the flex grid tie-ins: 1. Add quotes, Id = 13 (including pdf), my quotes (63), basic quotes (105), basic invoices (59), admin invoices (60) 2. Add elements of time, id = 12, basic time (123), view only (122), admin time (124) 3. On the search results – add more description (human readable parts) to the main and sub tie-ins. 4. Expand all of the 15 custom fields and their values. 5. Update help files to show new players and counts. 6. Add more links and be able to move around better. On the add/edit page show a link for other flex grid items and a more obvious link to the main. Make it human readable. 7. Create the roll call report. (7 & 8 kind of tied together) 8. Reflexive side of the flex grid. (7 & 8 kind of tied together) 9. Expand to association tie=ins instead of just direct tie=ins. 10. Be able to get the data back out of the flex grid easier… 11. Smooth as many corners as possible. 12. Think about interactive map connections and flow. 13. Be able to sub filter standalone flex grid results. Tie page to roll call as well. 14. Make sure that transparent and admin only options are protected and maintained. 15. Make the tool more friendly. 16. Be able to additionally filter results. (Main and general searches) 17. Once results are shown… be able to show just certain records… kind of extra. 18. Open up flex grid fields to 15 custom fields. (Request from a rep and a client) 19. Check time, quote, and E/R security and privacy options. 20. We may need an advanced flex grid search form that ties main details to flex grid search criteria. App Types: 1. = Dummy 2. = Deposit 3. = Invoice 4. = PO 5. = Expense/Receipt 6. = Balance Sheet Items 7. = Stock/Unit 8. = Customer 9. = Vendor/Payee 10. = Employee 11. = Part 12. = Element of Time 13. = Quote |
|
|
AU 509 |
|
Daily Tasks | 6/20/2011 |
• Basic business stuff. • Lots of emails and phone calls. • Lots of work on the flex grid. Went from 10 dynamic titles or custom fields to 15 custom fields. • Added a new function to check permissions in bulk. |
|
|
AU 2213 |
|
Testing on the Flex Grid Tie-Ins | 6/20/2011 |
Testing on the add/edit flex grid tie-in: A/E (both Add & Edit modes for all): The goal here is to breach security and force the system to show what it shouldn’t – this is just a test on security. - Expense/Receipts with privacy - Time with make private - Time with admin only - Quote with only my quote permission - Normal time - Normal quote Remember My Quotes and Basic Quotes: - Quote - Quote - Name or counter sale - Date - Amount - Notes - (tempExtraFour = salesperson id), (tempExtraFive = other salesperson id) Remember privacy and admin only: - Time - Template - Caption/title - Color - Start Date/Time - End Date/Time - (tempExtraFour = created by id, assigned to id, use single user assignment), (tempExtraFive = make private, admin only flag) |
|
|
AU 510 |
|
Daily Tasks | 6/21/2011 |
• On the phone with Steve going over the game plan and how best to help people do their accounting and inventory management. • Daily business stuff. • Worked on the add/edit flex grid page. • On the phone with a customer going over custom shipping options and how to interface with adilas. • Created a custom export of patients for a company. • Did some prep and research for using custom code inside the system. |
|
|
AU 511 |
|
Daily Tasks | 6/22/2011 |
• New logo for a company. • Prep for a customer upload. • Spent some time reading over an associates shortcuts and providing some feedback. • More add/edit stuff for the flex grid. • Added printable notes to the mini invoice. • Also added a customer log link to the view shopping cart page. |
|
|
AU 512 |
|
Daily Tasks | 6/23/2011 |
• Basic business stuff. • Did some domain renewals. • Added elements of time and quotes to the flex grid options. • On the phone with Steve going over white labeling and pros and cons of that. • New logo and colors for a company. |
|
|
AU 2214 |
|
Check Flex Grid Index Numbering | 6/23/2011 |
Check flex grid index numbering: 1. Sub dep 2. Bank 3. Sub inv 4. Inv-type 5. Sub po 6. Vendor 7. Sub e/r 8. Vendor/payee 9. Sub BSI 10. Item name 11. Sub unit 12. Make and model 13. Sub cust 14. Customer name 15. Sub vend 16. Vendor name 17. Sub emp 18. Employee name 19. Sub part 20. Part number 21. Sub time 22. Title/caption 23. Sub quote 24. Quote type 25. Other 1 26. Other 2 27. Other 3 28. Other 4 29. Other 5 30. Other 6 31. Other 7 32. Other 8 33. Other 9 34. Other 10 35. Other 11 36. Other 12 37. Other 13 38. Other 14 39. Other 15 40. Relation 41. Loc 42. Date 43. Amount 44. Modified 45. Visible (printable) 46. Admin 47. Notes 48. Drill-down link 49. Check flex grid index numbering: 1. App typ 2. Main id 3. Main info 4. Sub dep 5. Bank 6. Sub inv 7. Inv-type 8. Sub po 9. Vendor 10. Sub e/r 11. Vendor/payee 12. Sub BSI 13. Item name 14. Sub unit 15. Make and model 16. Sub cust 17. Customer name 18. Sub ven 19. Vendor name 20. Sub-emp 21. Employee name 22. Sub part 23. Part number 24. Sub time 25. Title/caption 26. Sub quote 27. Quote type 28. Other 1 29. Other 2 30. Other 3 31. Other 4 32. Other 5 33. Other 6 34. Other 7 35. Other 8 36. Other 9 37. Other 10 38. Other 11 39. Other 12 40. Other 13 41. Other 14 42. Other 15 43. Relation 44. Loc 45. Date 46. amount 47. modified 48. line status 49. notes 50. drill-down link |
|
|
AU 513 |
|
Daily Tasks | 6/24/2011 |
• Worked on a rework of the flex grid search results. Changed the entire flow. • On the phone with a customer going over payroll totals and what is needed. • On the phone with Steve going over a bunch of different things. We talked about flex grid, elements of time, new reports, interactive interface and custom requests. |
|
|
AU 514 |
|
Daily Tasks | 6/25/2011 |
• Basic business stuff. • Reoccurring payments. • Working on the flex grid search results. Broke the main flex grid search into two parts, added 5 new custom fields, added elements of time and quotes. Also made the output more readable. The old way would show the sub and main tie-in id numbers and that was it. The new way shows the tie-in ids plus human readable info to associate the tie-in. • Finished up and launched files. Did some testing. |
|
|
AU 515 |
|
Daily Tasks | 6/27/2011 |
• Basic business stuff. • New logo for a company. • Worked on help fields for the flex grid. • Also created a new graphic to help educate users on what the main application players are. • Added a small graphic to help users checkout the help file. • Read through the technical documents for automatic ACH bank transactions. • New logo for a company. |
|
|
AU 516 |
|
Daily Tasks | 6/28/2011 |
• Proofreading the adilas history bio. • New logo for a company. • On the phone with associates going over the plan for elements of time. • Basic business stuff. • Re-reading old brainstorming notes on system mapping and needs. • Working on personal financials for a company. • Working on automatic reoccurring ACH transactions. • On the phone with Steve going over general stuff. I told him about different phone conversations and bank stuff. |
|
|
AU 2215 |
|
Brainstorming Ideas for the Roll Call Page | 6/28/2011 |
Ideas for the roll call page: - Look at other mapping ideas. Eventually we want a visual model to help people understand what is going on. - What if we make a graphic per section that needs it and just reference the graphic instead of making it interactive. - This may need to be done in 2 or 3 stages. - Who, what, where, when, why, how much - Keep it super simple - Allow for drill-downs and sub reports. Maybe be able to pass a list of id #’s to a sub look-up page. Small form buttons - Think group, category, detail - Design it out on paper first - Re-read some of the earlier brainstorming ideas… some good stuff out there! - Start at the beginning - Search flags and dates instead of tables and tables and loops and subs. (see item #17 – dated 10/6/10 on automating sales tax and collected fees) - States and status, both required (solid lines) and optional (dotted lines) - Permission? B.S. and I.S. flags? Basic and advanced? - Map it out, tell the story, and help people follow the path. - Show different maps or scopes o Who? (map), Timeline? (map), Relationship? (map) |
|
|
AU 517 |
|
Daily Tasks | 6/30/2011 |
• New logo for a company. • On the phone with a customer. |
|
|
AU 2216 |
|
Brainstorming Backend Access | 6/30/2011 |
Backend access: FTP & uploads & SQL – quick & dirty On FTP - Check for payee id - Request FTP or SQL - Require a password - Limit to o Select, insert, update, alter table - Choose between dump or normal response - Browse - Destination - Success message On 11/29/11 dealing with a backend or backdoor: In talking with my mom, two sisters, and my wife: We came up with the following: 1. Track a full hidden history including full path and file name for uploads, full SQL for SQL statements, IP address, date/time stamps, payee id, mode/type, and corp id 2. Make it non-inviting 3. Maybe add some booby traps 4. Don’t leave a key under the floor mat 5. Don’t call it a back door 6. No windows 7. Low profile – don’t beat a path to it 8. Don’t talk about it |
|