Adilas.biz Developer's Notebook Homepage

[reset this page] . [historical web outline - entries by month] . [adilas community funded projects] . [contact adilas.biz support - email form] . [help]

Search The Adilas.biz Developer's Notebook
Time Period:	Daily (enter the day you want to see) Monthly Custom Date Range to
Template Filter:
Color Code:
General Text Filter:	(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:

Adilas.biz Developer's Notebook Report - 11/1/2008 to 11/30/2008 - (30)
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	AU 2661		Daily Tasks	11/3/2008	• On the phone with Steve going over things. • Working on new adilas web services conversion process. • Working on a 2nd round banner for a client.

	AU 2684		Daily Ideas	11/3/2008	Game plan for web services and load balancing: 0. Restore old ones for time being… 1. Move as many external, non-mission critical operations, over to the adilaswebservices.biz server 2. Create a small home page or landing page for adilas on the new server 3. Re-enable inventory pages, even if active link (to real data) is not fully intact. 4. On the adilas server. Show a redirect page with a physical link - this way search engines can find the link and path ok. 5. Create active links from adilas to adilas web services and vice-versa. 6. Set up new web services or adilas web services to handle all external calls. 7. Create a fake data base (very limited) on the adilas web services side only hold the important info. Nothing specific as far as SSN, customers, phone numbers, addresses, etc. 8. Need to make a list of what is needed on the remote side and then create web services that push the data over as changes are made. -Pre-check the first line item on e/r -Internal tickets – must be paid – preload it – on payment page -On deposit – hide the admin option or make it harder to get to -Default payments made - no user specific – keep store -3 on I.S. (Revenue, COGS, Expenses), and 3 on B.S. (Assets, Liabilities, Owner’s Equity) keep it that simple -Change the error message on deposit and expense type total reports. Prompt for a location.

	AU 2414		Note - Web Services Tables & Values	11/4/2008	Tech – Web Services: Tables & Values Used by Web Services - Corporations - Inventory types - Corp to inventory types - Makes - Sub inventory types - Store location - All inv - Models - Stock photos - Payee - Payee permission list - Payee permission categories - All inv subs

	AU 2662		Daily Tasks	11/4/2008	• Working on the adilas web services conversion. • On the phone with Steve going over things for clients. • Converted the parts catalog page into a field called parts bin number. • Posted files online

	AU 2663		Daily Tasks	11/5/2008	• Working on the adilas web services conversion.

	AU 2664		Daily Tasks	11/6/2008	• Working on adilas web services.

	AU 2665		Daily Tasks	11/7/2008	• Working on the inventory section of the remote web services. • Units and sub line items for units.

	AU 2666		Daily Tasks	11/10/2008	• Working on web services for sub items and stock photos. • Also worked on small changes from tick list. • Pulled down the database, uploaded new files, and reported changed database to work with web services.

	AU 2415		Brainstorming - Questions & Known Issues with Balance Sheet	11/11/2008	Questions & Known Issues with Balance Sheet 1. Things must balance. That can get tricky and hard. Every penny needs to be counted and assigned to the correct can. 2. Some things are real monies and some are book figures (not an actual cash values). Real monies need to be tied to a bank, investment, cash on hand, etc. Items such as depreciation may not actually translate into cash. This creates a disconnect. 3. Things (monies) can change hands, status, and destinations very quickly. What kinds of events trigger a move from an expense to a balance sheet item? Or vice versa? Say you have a customer who owes you money (A/R). You decide to write it off (clear the books). How does it change from A/R to expense or whatever? 4. Quite often you will have items changing status within their own group. Say cash (bank A/R) to inventory which is also an asset. 5. I’m worries about showing things multiple times on the same report. This has been a fear because I wasn’t sure how to show things. Originally, I was going to use expense types and deposit types. Those items would be shown by themselves plus be reflected in the cash or bank balance. The other problem is that some of the expense and deposit types don’t need to be shown on their own and should only be shown in the final bank balance. An example might be bank transfers or reimbursements paid. 6. What about internal repairs (internal invoices), bad debt, credits, NSF on checks, update P.O.’s, shrinkage, pre-paid items, capitalized items, refunds, monies over and short, due bills, breach of contract? And the list goes on…. 7. What about selling or renting a B.S. item? What happens if fully depreciated and still sold for profit? What happens if sold for a lost (loss)? What about gifts or receiving gifts? How do you record values if real money doesn’t change hands. Random note – all deposits require a bank – that might create a disconnect. 8. How do we automate payments (coming in and going out)? Is this required on the first round or sometime later? Along the same lines – what happens if we are ahead or behind the pay cycle (pre-paid or under paid)? 9. I need to set up a number of watchers or flaggers that can work over time. How do I do that so they can keep running totals and also be able to drill-down to details (in the past). I don’t see a problem if running on current data. What happens if the user wants a snap shot of days and time past? Random thought – if you use a snapshot analogy – a true snap shot is taken at the current time and then you look at it later on. In the digital world – I imagine that a user would like to virtually go back in time and see the snap shot of how it was even though things have changed and continued. This is where it gets tricky. 10. Classic model vs. new adilas model – The classic model is Assets, Liabilities, and Equity. The new model would be similar but show real , where am I values, with how much is owned, how much is still owed, and current value. An example might be: classic model – an asset (van) for $10,000 and long term A/P (loan) for $10,000. I would like to show it as an asset (van) valued at $10,000, paid $6,000, owe $4,000 and long term A/P (loan) value of $10,000, paid %6,000, and only owe $4,000. Paper doesn’t do it justice. Basically, I want to include real-time values to give a cleaner look at where we are. 11. How are we going to handle starting values? Say you know that at the end of last year you owed xyz. How do you keep things straight without having all of the details (or do we need all of the details)? This could get tough if we start signing up existing businesses that have years and years of history. Another thing to consider is the starting bank balance and the starting bank date. These are already included on the add/edit bank pages. 12. How do I maintain a duality (at least two offsetting accounts)? Not every transaction is processed in the exact same way. Plus, it may require a transfer within the same type or a 1-many relationship that could be any number. 13. I’m hoping to use an item called a “balance sheet item”. Each item would have its own name, destination, starting value, running value, sort, etc. We can tie in photos, sub, tables, etc. to each item. Basically, each item will be a special “can” with a name. The basic info will be ongoing and the details of what happened to it (baggage) will be carried by each item. We will record history info and possibly “snap shot” history. I’m not exactly sure on the snap shot history (what that means or how we will do that) but it might help with look backs. 14. The above item (B.S. Items) are a great idea but how do you deal with things the system is doing on its own (short term A/R’s, short term A/P’s, bank balances, inventory counts, P&L net profit, etc.). Maybe these things keep going in the background until the user “takes a picture” and thus create a snap shot history. 15. One of my main goals is to have the system be functioning and the balance sheet show up as an “effect” of good data. A number of other software systems require a post or physically recording where things are at. I want the numbers to just flow through as a result of normal usage. Let operations dictate to accounting what is happening. This takes the word “adjustment” out of the picture. It is what it is… 16. Speed vs. flexibility vs. server load vs. dynamic vs. static vs. frequency – This will be a full on balancing act. What is the most important? What is the easiest/hardest to maintain? What do our customer and users want? How easy/complex is this report going to be? 17. Because we are not doing traditional double entry accounting, how do we incorporate cross checking and dynamic multi checking? Instead of 1 to 1 (standard double entry) – what about multi-cross checking. How do we empower the users (corps) to set up their own cross checks that the system can monitor? If we can figure this out, it would help the users know where the problems are. This would be worth tons and would end up saving tons of time looking for the problems. 18. The good thing about B.S. Items is they are changed less frequently than normal day-to-day items. Maybe weekly, monthly, quarterly, or annually. Usually not daily. This is the outer loop (inter loop being daily business transactions) 19. What happens if the balance sheet won’t balance? Do we provide a force balance or do we require the users to check the cross checks and really make the data correct? It would be so cool if there was no way to trick it. That will be tough. 20. What prep steps do we need do? Maybe create watchers, flaggers, history points, etc. What about parts and running off or part-id instead of vendor and part number? 21. Maybe we need to have the B.S. report be dynamic. This means we only show things that are active and have a value. Maybe we allow the users to rename a system generated category (default to what we think but give them some flexibility on what to call it). Maybe we only provide drill-downs on current date. B.S. reports. Archived “snap shots” won’t have drill-downs, just numbers and text values. Current is crunch on the fly and archived is just a saved report. 22. Maybe we allow users to look up small sections of the balance sheet (in the current time or in the past) but we limit it to just a certain section at a time. This would lessen the server load and allow for special code and lops or smaller groups of data. These more detailed looks would crash the server if done as a whole.

	AU 2667		Daily Tasks	11/11/2008	• Emailed an update to Steve and associates. • Testing web service calls. • Changed the web services to work as either add or edits on every call. • Brainstorming on balance sheet items. • On the phone with an associate at Crystal Tech. Problem with JDBC driver.

	AU 2685		Daily Ideas	11/11/2008	-On paying splits – check for 1 checked item and send to edit or add payment. -Change all of the web service methods to be generic and able to handle adds or edits regardless of modes.

	AU 2416		Brainstorming - Balance Sheet Groupings	11/12/2008	On Balance Sheet Groupings: Use Category: unchangeable (required) - Assets - Liabilities - Equity Use Groups: allow dynamic naming (required) Defaults: (instead of creating all of these maybe just provide a special help file with the values) - Assets: o Cash o Bank Account(s) o Accounts Receivable o Other Current Assets o Fixed Assets o Other Assets o Accumulated Depreciation - Liabilities: o Accounts Payable o Other Current Liabilities o Long Term Liabilities - Equity o Capital o Other Equity Allow for an optional sub group: allow dynamic naming this is not required but may be used. I will need to create a system wide blank value or hidden sub group. (optional) Show B.S. report in the following levels: (same as P&L) 1. Quick look only (basic) 2. Show main groups (small) 3. Show main and sub groups (medium) 4. Show everything fully expanded (large)

	AU 2668		Daily Tasks	11/12/2008	• Testing the application and web services. • Emailing Steve some info on Crystal Tech. • Brainstorming on balance sheet items. • On the phone with Steve going over bank statements and verifying receipts and deposits. • Made some small updates on receipt payments. • Called and talked with a client about the flash banner.

	AU 2669		Daily Tasks	11/13/2008	• Working on the bulk verify receipt page. • Talked with Steve on the phone and decided to add a new payment verified field to each receipt payment. • Original verified (on the main) will remain intact. • Working on an update page for new receipt payment fields.

	AU 2686		Daily Ideas	11/13/2008	-Create a bank registry report – default to 30 days and add pagination to each page. -Status link per page (on the edit line items page) show what is needed, pending or missing -Deposit photo gallery -Change to part id # instead of vendor and part number -Mass verify on deposits and receipts – add date and show 25 per page -Check splits that have been verified – showing up on verified bank statements. -Add a check box to help put things “on account” on the add_edit_receipt page. -Add a name to the my hours page. -Split or add a new verified and flag to the e/r payments. This will also require a logic change on verify banks and posting final numbers. Check main verify page and every other method that verifies e/r’s. Add new options to payment search. -Change the web inventory link on web_application_prep.cfm page. -Print status stuff to check/payment search -Add vendor/customer names to advanced line and payment searching -Add a numeric check value to receipt payments -Do a major check on mark as payable, receipt paid, splits, rei’s, PO’s, check reqs, normal, negative #’s, subs, etc. Problems with negatives in the past. -Charts – see with your eyes – add some visual candy!

	AU 2670		Daily Tasks	11/14/2008	• Working on allowing negative splits.

	AU 2671		Daily Tasks	11/15/2008	• On the phone with Steve going over things. We talked about successes and short comings. We went over current plans and tick list.

	AU 2672		Daily Tasks	11/17/2008	• Added a logo to a company’s site. Added a buy online now link and uploaded files. Invoiced. • Working on a company’s flash banner. Added a number of images, took off the color flicker, added the head for branding, and posted file online. Emailed them with details. Invoiced on 11/20/08 for 13.25 hours. • On the phone with a client about payroll and dealing with IRA’s and how to calc taxes.

	AU 2687		Daily Ideas	11/17/2008	-On receive multiple invoices – add money type as a search criteria. -Change the lock permission to basic around the board -Create the automate invoice section. Reoccurring invoices and payments. -Create the history look-up section “activity per corp” -Add anchor tags to the permissions page -Balance sheet items and balance sheet report -Report and form builder -Payroll IRA calcs – no federal but full ss and medicare -On verify bank reports. Allow a check range (numeric) and show only deposits or expenses. -On reports – convert day, month, year look-ups to text entries. -Check the math on the payables page under splits when dates are used. Is shows all payments not just satisfying pmts. Doubles the “split” pmts. -At some point, it might be nice to record verify bank history; include date/time and person.

	AU 2673		Daily Tasks	11/18/2008	• Fixing a payroll calc for simple IRA’s. They require a pretax deduction but not a full deduction. They are federal exempt but require full social security and Medicare. Made changes and posted files. • Working on the new verify receipt payment fields and converting to real numeric check numbers.

	AU 2674		Daily Tasks	11/19/2008	• Posted a few new changes online. • Emailed Steve an update. • Fixed the PDF scale or invoices for a client. • Emailed an associate for help on sales taxes. • Worked on the check and payment searches. • Worked on verifying expense/receipt payments.

	AU 2675		Daily Tasks	11/20/2008	• Working through expense/receipt validation and trying to standardize output and options. • Added anchor tags and links on permission pages.

	AU 2676		Daily Tasks	11/21/2008	• Working on following e/r’s through the system process.

	AU 2677		Daily Tasks	11/22/2008	• Working on consistency between pages. • Following e/r logic. • Changed the lock permission from admin to basic. • Allowed verified items to be verified with prior locking. • Started on the verify bank report.

	AU 2678		Daily Tasks	11/24/2008	• Went in to a business and worked with a client on flash photo viewer application. Teaching, consulting, and working one-on-one with him. 10 miles. • Working on Flash tweens. Finished up the code for this client.

	AU 2679		Daily Tasks	11/25/2008	• Small changes to the photo viewer. Emailed a client a copy of the .Fla file with instructions. Invoiced on 11/29/08 for 5.5 hrs. • Working on the verify bank and final post sections. • Worked on the bulk verify section for expense/receipts. • Posted new files. • Updated all old receipt payments.

	AU 2680		Daily Tasks	11/26/2008	• Quick surgery on ColdFusion component. It actually shut down a number of sections. • Worked on help files and small tweaks to new pages. • Checked code and signed off on pages. • Worked on the bulk receipt verify page.

	AU 2681		Daily Tasks	11/27/2008	• Working on the bulk receipt verify pages. • Finished up the pages and launched the pages.

	AU 2682		Daily Tasks	11/28/2008	• Followed up with Crystal Tech on a random .jar file on the server. • Appears to be part of web services??? • Signed off on pages and started on the bulk verify section for deposits.

	AU 2683		Daily Tasks	11/29/2008	• Went in to Steve’s house to sit in on an interview for an adilas helper person. I did not bill for this interview time. 10 miles.

What's New

Products

Find Us