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 - 9/1/2010 to 9/30/2010 - (32)
Photos
Time Id Color Title/Caption Start Date   Notes
Click to view time photos.
AU 217 Daily Tasks 9/1/2010   • On the phone with a customer that had some questions on how to pay for stock units and other inventory related questions.
• Added a new buy now button to a company’s website. Customer wrote back and said they wanted it to “pop” more. So I reworked it and added some color. No charge for the rework. Invoiced them for 1.25 hours since 4/26 to 9/1.
• Working on a customer website. Converting the web mock-up graphic in to actual html code.
 
Click to view time photos.
AU 241 Daily Ideas 9/1/2010   -From post-it note: adilasbookkeeping.biz, .com. Loc’s, start and end date, sales tax containers, collected containers, bank’s start and end date.
 
Click to view time photos.
AU 218 Daily Tasks 9/2/2010   • Working on balance sheet request.
• Small brainstorming session giving adilas and the balance sheet a visual representation.
• Sent an email to Steve and others with a loose idea and concept.
• Added a VIN number to a balance sheet inventory report.
• Launched and tested new pages.
• Created a “For Sale Now” page for a company. It had a pdf floor plan, photos and specs. Posted the files online.
 
Click to view time photos.
AU 242 Daily Ideas 9/2/2010   -Along with these other ideas below – remember that one of the original ideas was a container or “Pringles cans”. Stuff things where they need to go and move things around as needed.
-This is a random funny idea – but wouldn’t it be fun to rewind a company and virtually watch it grow from nothing (some point) into what it is now or what it was at some prior date?
-On the balance sheet – think about the story and how different things would happen and unfold. How can I fit events into a time line and then map them back to where they need to be? Tell the story of what is or what has happened. That’s the accounting!
-At some point I may want to create an invoice type that does both a transfer and a sale. This would help with moving inventory between locations and could also speed up the time to do this process manually. “Transfer and sell” invoice type.
 
Click to view time photos.
AU 219 Daily Tasks 9/3/2010   • Working on a small website a customer. Sent them an email with the web mock-up graphic.
 
Click to view time photos.
AU 220 Daily Tasks 9/4/2010   • Finishing up the website and sent them an email update and left a voice mail.
 
Click to view time photos.
AU 221 Daily Tasks 9/6/2010   • Transferring files and getting things setup on godaddy.com for a customer. Email and domain name servers.
 
Click to view time photos.
AU 222 Daily Tasks 9/7/2010   • Added a new filed to the order sample floor plan for a customer. The field was a “how did you hear about us?” field. Posted and tested files online. Invoiced on 9/7 for 2.75 hours.
• Worked on another company’s website. Posted files online.
• On the phone with a customer going over banks, verifying banks, reconciling banks, bank transfers, credit card accounts, reports and adilas story and theory.
 
Click to view time photos.
AU 223 Daily Tasks 9/8/2010   • Starting the process of transferring the domain name for a company.
• Working on the specific unit name corp-wide setting.
• On the phone with a customer going over photos, scans and images.
• On the phone with a customer going over parts and updating inventory counts.
• Added a new session var to help with the payee type id when creating new expense/receipts.
 
Click to view time photos.
AU 224 Daily Tasks 9/9/2010   • Reviewing and checking off new changes for the specific unit name corp-wide setting that was launched last night.
• Worked on the mini sales report. Added the special line items to the output.
• Also sent an email update.
• Talked with a customer on the phone about PO’s and inventory. We spoke a couple of different times today.
• Also on the phone with another customer a couple of different times. We had a conference call between him, me and a GPS tech about his idea of integrity billing and capturing a GPS map and live printing. We decided that all we needed from the GPS side is a GPS unit (AKA service vehicle or driver), and their position for a date/time frame. We would get this info and hold it in a flex grid or some 1 to many relationship. The office staff could then get a prepared document ready behind the scenes and do a screen capture into a certain format or Word Doc. This could also be a graphic template. Anyway, once complete, they could upload the doc/image and the onsite technician would print it out and deliver it.
• Also added a new filter to the advanced customer search. It is for salespersons tie to customers.
 
Click to view time photos.
AU 225 Daily Tasks 9/10/2010   • Modified the main homepage for a Twitter landing page for a company. Posted files online and let them know via email.
• Brainstorming on how to automate taxes and balance sheet items.
• General review of the to do list.
• On the phone with a customer going over balance sheet items and how to map to the expense/receipt side of a B.S. account. Also a small intro to the flex grid.
• On the phone with the manager for a company. He was very frustrated with tracking a vendor specific inventory. He had multiple items with the same name from different vendors. He also had multi vendors and had even doubled the problem.
• Wrote some emails and recorded customer logs about the day and where we are headed.
 
Click to view time photos.
AU 2164 Note 9/10/2010   Be your own style!
- Math can be done very quickly on the fly, but if individual math is needed for multi items, why not watch it at the source and pre sum it up or flag and do it right there. Basically, I was always taught to let the computer do the math on the fly… I’m finding that if the math doesn’t change (it has become hard like ice) it could go much faster if we sum up things (only hard unchanging things) and then run reports off of that.
- What I’m looking for is a watcher and a place to hold values and time frames (daily, weekly, monthly, quarterly, annual, etc.).
- What about locations, what about corporations? These are even bigger containers.
Find & Replace:
- Part numbers (dynamic)
1. Search and select a master (use this)
2. Search and select a value to replace (instead of this)
3. Run the clean-up function
- Vendor/Payees
- Customers (dynamic)
Special pricing and conversions all in one feature – may need a hidden #:
- Buy it how?
- Sell it how?
- Price it how?
 
Click to view time photos.
AU 226 Daily Tasks 9/11/2010   • Working on new global parts find and replace permission and function.
 
Click to view time photos.
AU 243 Daily Ideas 9/11/2010   -May need to add a security patch so that any outside form cannot submit to adilas. The user is required to login but that doesn’t stop homemade form submission.
-Need a global show/hide parts on the web feature. This would only flip the show on web status. See the global mark-up for fast code.
-Random idea on parts – I may need to create a set of pages to help people combine parts and make homogeneous or generic items. This will replace all other parts in PO’s and Invoices (line items) and will make those items go inactive. This may also require a PO type flip.
-You should be able to look at any day in time and see the overall picture of who is at what check point. In order to do that, we need to really decide what the checkpoints are and map it.
-Provide a digital, visual, interactive flow chart of how the system works. Main players, sub players, systems and sub systems. Think of the human body: Body as a whole, body parts, smaller parts, underlying systems, cause and effect relationships, clear down to cells. Map it out, show it and explain it!
 
Click to view time photos.
AU 227 Daily Tasks 9/13/2010   • Working on new global parts find and replace permission and function.
• Tons of time working on the find and replace parts sections.
• On the phone with Steve for 1.5 hours going over parts, inventories, price structures, customer needs and new developments.
 
Click to view time photos.
AU 228 Daily Tasks 9/14/2010   • Working on the find and replace parts section.
• On the phone with Steve.
• On the phone with a customer talking about PO’s and how to pay for them.
• On the phone with another customer going over my findings. Did some testing and learning about cfhttp, xml and web services. Testing and then contacting this customer about how I don’t think that he even needs web services.
• Lots of research about using ColdFusion and accessing XML and soap info.
 
Click to view time photos.
AU 229 Daily Tasks 9/15/2010   • On the phone with Steve going over game plan and new developments.
• On the phone with a customer going over invoice payments and how to tie them to deposits.
• Additional work on the find and replace parts and how inactive parts play into the mix.
• On the phone with Steve going over how to handle inactive parts.
 
Click to view time photos.
AU 230 Daily Tasks 9/16/2010   • Working on error messages for dealing with inactive part numbers.
• On the phone with a customer for an hour. They had a special balance sheet deal that required an equity item, a PO and an invoice sale of a balance sheet item. We also talked shop and then I took them into adilas corp-wide settings.
• Also did a little bit of research on Merchant One API interface. This is a merchant processor that we need to connect to through adilas. Small direct post-test. Playing with lists, arrays and loops to decode URL query string formats.
 
Click to view time photos.
AU 231 Daily Tasks 9/17/2010   • Added new help file and launched the find and replace toolset.
• Research on Merchant One (sounds a little sketchy) and also more research on using cfhttp and soap web services.
 
Click to view time photos.
AU 232 Daily Tasks 9/18/2010   • Research on USAePay and connecting to the web services via a cfhttp post. Ran into some problems. Submitted some support tickets. I want it to work because it will be faster, much faster. However, it is more complicated code work.
• Started on a new advanced add to cart permission and work flow.
 
Click to view time photos.
AU 233 Daily Tasks 9/20/2010   • On the phone with Steve going over the game plan. He also needs some credit card magic by Wednesday morning (Merchant One gateway).
• Follow up on USAePay and Merchant One documentation from different people.
• On the phone with a user going over reoccurring invoices.
• Working on the advanced add to cart page.
• Formatting output and started to add some Java Script to help the users.
 
Click to view time photos.
AU 234 Daily Tasks 9/21/2010   • Working on Java Script calcs and functions for the advanced add to cart functions.
• Lots of testing and working on an advanced edit cart line item page mode.
• Posted files online.
 
Click to view time photos.
AU 235 Daily Tasks 9/22/2010   • On the phone with Steve going over things. Gave him a quick update on new permission and where we are headed.
• Turned on some permissions for some customers for the advanced add to cart permission. Sent them an email with a brief explanation of the features.
• On the phone with a customer going over how to make generic quotes.
• Added new help files for new permission.
• Started working on merchant processing pages to connect to the Merchant One payment gateway.
 
Click to view time photos.
AU 244 Daily Ideas 9/22/2010   -At some point we may need a payee clean-up for payee ids. Say a person wants to be in multi-corps and didn’t use the any-payee-to-any corp permission; they may be in there twice and can’t jump from corp to corp. The update might get tricky with tons of different history tables.
-At some point it may be nice if we set the FORM focus to the correct form field on a per page basis. Not all pages apply….
 
Click to view time photos.
AU 236 Daily Tasks 9/23/2010   • Working on connecting to the Merchant One gateway. Basic sales transactions and then querying the transaction.
• Learning about XML and how to use it in ColdFusion.
• Additional work on void logic for Merchant One gateway.
• Posted files online.
• On the phone with Steve at different times throughout the day. Let him know that the credit card stuff was online. Spent 1.5 hours on the phone with Steve. We talked about the day and some of the new changes. We also had a wonderful recap session of the future of adilas and where we want to go. We covered a wide range and touched on a number of different subjects. Here is a rough outline of our future to do list:
- USAePay – rework web service calls
- Full e-commerce
- User side of the history report
- Sales tax and collected fees
- Rework on payables section
- Accrual call outs
- B.S. side of expenses and deposits
- Map out everything (all states, status and checkpoints)
- Roll call and watchers per item
- Known issues report – backwards balance sheet
- Visual – what is happening?
- Pdf – upload and secure images
- Reflexive side of the flex grid
- Special clean-up tools
- Build your own reports
- Download and save back-up files of your data
- 1-many on parts, prices, sales and discounts, customers and vendors
- Scheduling (person, place or thing)
 
Click to view time photos.
AU 2165 Brainstorming Merchant Processing 9/23/2010   Merchant Processing:
USAePay:
- Assigned to the transaction st
- Response Auth Code
- Details Clerk
- Customer Id
- Response – Batch Num
- Response – Batch Ref Num
- Details Amount
- Date Time
- Response Result
- Transaction Type
- Status
- Response Status Code
- Account Holder
- Credit Card Data – Card Type
- Credit Card Data – Card Number
- Credit Card Data – Card Present
- Details – Comments
Merchant One:
- Under nm response transaction
- Authorization code
- Shipping – address
- Shipping – last name
- Action amount
- Action date
- Action success
- Action – action type
- Condition
- Shipping – company
- Cc number – look at first letter and compare
- Cc number
- Shipping – first name
- Shipping – address
3rd Column:
- Cc authorization
- Payee id – who can run the card
- Customer id number
- Batch #
- Amount of transaction
- When it happened – date/time
- Like approved, decline, etc.
- Like sale, credit, void
- Pending, settled, etc. void
- Small code for the status above
- Name on card
- Visa, Master Card, Amex
- Cc number
- Swiped or not
- What mode – cart, invoice, payment, etc.
 
Click to view time photos.
AU 237 Daily Tasks 9/27/2010   • On the phone with Steve going over the game plan and where we are headed.
• Working on logos and colors for companies. Posted logos and colors online.
• Cleaning up code for the Merchant One gateway connections. Created a special test page for testing merchant account settings.
• Did some research on soap protocol for sending and receiving xml and web services.
 
Click to view time photos.
AU 238 Daily Tasks 9/28/2010   • On the phone with Steve going over credit cards and using credit card swipers.
• Paying bills and commissions, recording deposits and following up with clients that were struggling to pay.
• Working on the test connection page for merchant processing and account settings.
• Worked on the add credit card payment page.
• Had a need/request to handle card swipers that only passed track 2 data.
• Working on Java Script and code values.
• Added code to help manually create tracks 1 & 2 if needed for retail transactions. Posted files online and did some testing.
 
Click to view time photos.
AU 239 Daily Tasks 9/29/2010   • Started working on the rework of the USAePay web service calls. Changed from a .wsdl file and cfinvoke to a cfhttp post and raw soap xml. This should really speed up the process.
• Migrated parts for a company, 4,000+ for one area and 400+ for another. Also did some PO and part # clean-up.
• On the phone with Steve going over merchant processing stuff. We also talked about education and how to help people learn what tools are available and how they play in to the mix.
• On the phone with a company trying to make a deal.
• On the phone with a customer, he had some balance sheet questions. We talked about the need for a system-maintained balance sheet item called inventory in transit (paid for but not here yet). He would also like to see search options for any part of the customer or vendor searches (biz name, first and last name).
 
Click to view time photos.
AU 245 Daily Ideas 9/29/2010   From post-it note, 9/29/10
-Inventory in transit (ideas from a customer) – paid for before it hits your loc. This deals with PO’s, payment dates and received dates.
-On vendor and customer – have it search all section biz name, last name and first name)
-Instead of “all” make it an “any” or any part or any match.
 
Click to view time photos.
AU 240 Daily Tasks 9/30/2010   • Working on the USAePay soap web service calls.
• Went online and wrote a forum post on Crystal Tech’s website to help other people know how to better use the USAePay and ColdFusion mix using cfhttp post and xml vs. .wsdl and cfinvoke options.
• Added help files and made a small tweak on the new test merchant account connection page.
• Worked on hard coded SQL histories that needed some corp-wide settings.
• Posted new USAePay files online.
• Full database back-up.
 
Click to view time photos.
AU 246 Daily Ideas 9/30/2010   -On sales tax – create a special help file just to explain how it works and who the players are. Add a link to this page from loc home, bs home and add/edit locs.
-When I do figure out the back-up schedule… remember how fast things change (good and bad). Plan for change…
-What kind of back-up system do we need? How do we protect the data? The pages tie everything together but the data makes it mean something. Do we mirror, web service, scheduler, outsource, do it ourselves, let the customer do it, don’t touch it, hybrid solution, mix and match? Think strategically and simple…
-?’s – fixed location, slush piles, obscure, offsite, secure, remote, local, mixed, redundant, dead end, moving target, etc.
From Post-it notes:
-When dealing with flags and date (ranges) – if it is a one-time deal do a flag and a date, otherwise don’t be afraid to do a flag and a date range if needed. Tell the story, map back to what happened in time.
-Different states and status: match, mismatch, easy, straight forward, normal, split, pre, post, partial, void or canceled, hanging, pending, done or complete, special, unknown, stale, dead, fresh, new, short, over, foul, out of bounds, start over, redo, reset, suspended, time out, denied or rejected, needs attention, unfinished, clouded, independent, dependent, simple, complex, backwards, reversed or inverted, out of order – events, incomplete, waiting.
-Create a 1-many from loc to deal with difference or tax service fee (revenue from tax collection tax, revenue declarations)
-Penalty fees and other IS accounts. (Don’t really worry about this; this is more of a reminder about I.S. penalty fees may get mixed in with B.S. items.)