all data is live and searchable
[reset this page] .
[historical web outline - entries by month] .
[adilas community funded projects] .
[contact adilas.biz support - email form] .
[help]
|
Adilas.biz Developer's Notebook Report - 10/1/2009 to 10/31/2009 - (26)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 1510 |
|
Daily Tasks | 10/1/2009 |
• Got a new product key for Adobe Acrobat 9. Installed and started playing around. Created a new form and played around with populating it. Pretty cool! • On the phone with Steve going over updates, needs, and new breakthroughs. Things are cooking right now. • Working on a company’s site. Took off 3 styles, removed background image, added new verbage, added another row of dynamic photos to the homepage. Cropped a number of new houses for homepage photos. Upped the show count per page for 6 to 20, added nav and drill-down links. Tested and uploaded files. |
|
|
AU 1511 |
|
Daily Tasks | 10/2/2009 |
• Planning and prep for document management (pdf forms). • Brainstorming on tables and tie-ins. • Finished up the new quotes permissions and sign off on pages. • Added location and contact info on printable PO’s. • Created options to save PO’s as pdf’s • Posted files online and did some testing. |
|
|
AU 2388 |
|
Tech - Custom Documents | 10/2/2009 |
Docs to Corps 1. The document will be the one and corps will be the many 2. Certain docs will be sued by multiple corps 3. Certain docs will be corp specific and a single one to one relationship 4. There could end up being 100’s or 1,000’s of docs 5. Currently, the main doc type is adobe pdf. But there could be Word, Excel, html, swf, css, etc. I think for now I will assume that all docs will be pdf. I can change this later if needed. 6. The docs are currently assigned to invoices or sold units. It is possible that they may need to be assigned to different app types. Tech – Custom Documents Table (Please see scan in photo gallery) Tech - Custom Docs to Corps Table (Please see scan in photo gallery) |
|
|
AU 1512 |
|
Daily Tasks | 10/5/2009 |
• Working on help files, doing emails and phone calls. • Created new database tables for documents and custom forms. • Added a new document management permission. • On the phone with Steve going over game plan and options. Talked about education and training. Also talked about an adilas update log. • Added a quick fix for assigning any payee to any corp. • Created the document homepage and worked on corp-wide settings on flex grid dynamic output for parts and customers. |
|
|
AU 1531 |
|
Daily Ideas | 10/5/2009 |
-On credit card payments. Steve had the idea to match up the cc authorization #’s to help determine which deposit was which. That is a great idea and helps break a date disconnect and an amount disconnect. We may also be able to store custom fields like money_type_id, total_sale, date, payee_id, customer_id, etc. -We need to add an additional link from add/edit payee (system wide) to any payee to any corp. This will help Steve and I out with setting people up. -Flex grid on reoccurring invoices. |
|
|
AU 1513 |
|
Daily Tasks | 10/6/2009 |
• Working on the document management section and pages in adilas. • Fixed a small bug for switching corps with an open shopping cart. • On the phone with a client. • Added log to the system. |
|
|
AU 1514 |
|
Daily Tasks | 10/7/2009 |
• Working on the document management interface. • Added options for hardcoded values for documents. Added 10 dynamic fields that can hold corp specific data. • Working on the pdf side of the Texas 130-U form. Almost 100 fields. Testing and displaying data. |
|
|
AU 1515 |
|
Daily Tasks | 10/8/2009 |
• Finished up the 130-U for Texas trailers. Posted files and tested online. Let people know about it. • On the phone with Steve going over new changes and potential with new features. • Working on the Texas Farm and Ranch Form. Start to finish on the pdf form. Created the pdf, created the ColdFusion page to populate it, posted files online, and made assignments. • On the phone with a client going over flex grids, corp-wide settings, units, customer website, and scale options on pdf’s. |
|
|
AU 1532 |
|
Daily Ideas | 10/8/2009 |
-If user searches for a vendor from the quick search, hide the check requests links. -On pdf’s maybe include a background setting of bgcolor=yes or bgcolor=no or color=yes and color=no. This would allow for a black and white options or at least a white background. -On corp-wide settings. We need the ability to set up the defaults for internet system charge, pack, photo fees, basically, subs to stocks and where and how much to apply. Currently commented out the code. -Add a multi-stock filter to sold unit options. See units in inventory (comma delimited list) – special report builder. |
|
|
AU 1516 |
|
Daily Tasks | 10/9/2009 |
• On the phone with Steve going over a company’s requests/issues (items for an employee). • Research on USAePay. |
|
|
AU 1517 |
|
Daily Tasks | 10/13/2009 | • Working on the corp-wide settings on the adilas web services site. | |
|
AU 1518 |
|
Daily Tasks | 10/14/2009 | • Working on documentation for developers on the adilas web services site. | |
|
AU 1519 |
|
Daily Tasks | 10/19/2009 |
• On the phone with Steve going over game plan and setup/optimization needs for clients. • Need to check out Colorado used car paperwork and desking the deal application. • Added four new logos and colors. • Changed all of the front page images for a company’s website. Posted files and let them know. |
|
|
AU 1520 |
|
Daily Tasks | 10/20/2009 |
• Research and work on interfacing with USAePay through web services. • Set up pin codes, developer’s site, and sandbox server options. • On the phone with Steve and set up a username for a contact. • Created a test page to work with USAePay web services. • Getting code ready to migrate parts for a company. Migrated two different vendors and their parts. |
|
|
AU 1521 |
|
Daily Tasks | 10/21/2009 |
• Training for a client. This is billed in advance. Total invoice for 5.75 hours 9/28/09 to 10/21/09. Invoiced. • Migrating parts over for a client. • On the phone with Steve going over parts and processes. Talked about auto population vin #’s and credit card processing and transactions. • Planning new changes for merchant account processing. • On the phone with Steve going over the day’s activities. |
|
|
AU 2389 |
|
Brainstorming - Payment Options for Credit Card Processing | 10/21/2009 |
Payment Options for Credit Card Processing: 1. I want to encourage adilas users to get a USAePay merchant account. It is not required but highly encouraged. Especially if it is through us as the tech exec referral through Newtek. 2. I would like to make it a soft approach but show the advantages and benefits (on a different page) with links to sign up for a rate comparison (self-referral). 3. Show logos for Visa/Master Card/Discover/ & Amex 4. Show links and logos on all payment option pages a. Main cart page b. Apply payments page c. (Maybe just a link) – from invoice line item page 5. As long as I’m in the cart payment page, I would like to add a feature for multi payments (remember in session scope with round trip abilities). I would also like to add an option for making change. 6. We need a section that will show error or declined messages with options to try different payment types or options. 7. Change bottom verbage on cart payment page. 8. Allow a direct link to card processing or let them use the main form with a blank cc approval code. Once submitted, if they have the permission, reroute to cart processing page. If they don’t have the permissions, show the normal validation on cc approval codes. 9. Document new changes in help file. 10. Show invoice total in first value (amount field). Show remaining amount owed and change due to help users. 11. Even if the user doesn’t have a merchant account with us, show them the payment page but hide and/or disable the submit button. 12. Help use select the correct money type by comparing first numbers: 3=Amex, 4=Visa, 5=MC, 6=Discover. 13. Record the actual transaction # and provide a link from the reference # (cc approval) to the actual transaction. This is done behind the scenes and is un-editable. The drill-down link will show credit card transaction info. We won’t store it anywhere but we will look it up and show it. 14. Once the transaction has gone through add an option to void the transaction before the batch closes. This may require a check of the batch status or an error message stating it is already closed. 15. If the corp has multiple merchant accounts (with us) allow them to choose from the payment page. If only one account, hide the setting and pass it in the background. 16. Don’t allow any negative transactions, (by themselves). Maybe allow a credit or refund after the fact. Maybe we could require a valid pin number and an actual transaction number from behind the scenes. |
|
|
AU 1522 |
|
Daily Tasks | 10/22/2009 |
• New logo and colors for a client. • Writing and email to Steve and a client regarding potential adilas issues and concerns. Tried to keep it positive. • Signing off on code for pages. • On the phone with Steve going over green light requests from clients. • Working on new tables for merchant account settings. • Brainstorming on security and hash functions. • Research on options and web services for USAePay. |
|
|
AU 2390 |
|
Brainstorming & Tech - Merchant Processing | 10/22/2009 |
Merchant Processing available through adilas.biz: Database ideas for merchant accounts: 1. Are they tied to a corp, loc, or bank, or all these? 2. We are currently tied into USAePay and Newtek, do we want to allow for future growth or deal with it when we get there? 3. What about transactions and batches? These are key fields on the remote side. It might be ideal to capture and use them to help with reconciling bank deposits. 4. What if we allowed a feature where the user could view the current batch, pick and choose (create an internal tie between inv. Payment and transaction number), force the batch to close (only the records we want), record the batch number (on the deposit), and create the new deposit. This would be pretty cool. This would keep things all tied together. 5. What about security? The source key and pin key are very important keys to the user’s merchant account. How can I protect myself, adilas, the users, and the companies? This is a big responsibility. 6. Make sure all cc transactions and webservice calls are done over SSL connections. Force it SSL or send to logout. 7. I need to come up with a hash to conceal the source keys and pin values. See part of LTF for some ideas. Tech – Merchant Settings Table & Merchant Types Table (Please see scan in photo gallery) |
|
|
AU 1523 |
|
Daily Tasks | 10/23/2009 |
• Working on new credit card payment stuff. • Fixed a small bug dealing with reoccurring invoices. • Worked on Java Script for cart payment page and calculating sub totals and differences. • On the phone with Steve going over different options and paths for adilas. Kind of fun to talk about vision. |
|
|
AU 1524 |
|
Daily Tasks | 10/24/2009 | • Checking files and updating Java Script functions. | |
|
AU 1525 |
|
Daily Tasks | 10/26/2009 |
• Reviewing tick list in notebook and checking off completed items. This was a good review of what is needed. • Research on Snagit and Camtasia studio. • Working on signing off on code. • On the phone with a client going over a request for video marketing for his products. • Working on the Java Script for calculating change. • On the phone with Steve for over an hour talking about all sorts of things. He is going got help me figure out what the next couple of optimization projects will be. • Posted new files online and added new database fields for transaction and batch numbers. |
|
|
AU 1526 |
|
Daily Tasks | 10/27/2009 |
• Help files and working on merchant account homepage and the add/edit account setting page. • Worked on the new adilas encoder (hash) function. • Working on securing data with new encoder function. • Known problems with (backslash), ‘(single quote), “(double quote). |
|
|
AU 1527 |
|
Daily Tasks | 10/28/2009 |
• Working on the add/edit process for merchant account settings. • Encoding and decoding values. • Set up a store in adilas. Added a new logo and colors. |
|
|
AU 1528 |
|
Daily Tasks | 10/29/2009 | • Back and forth emails and phone calls to help an associate get set up again. | |
|
AU 1529 |
|
Daily Tasks | 10/30/2009 |
• Looking over a project that my dad sent to me. • Working on the add/edit process for merchant account settings. • Signing off on new pages. • Started to build interface on cart checkout and payment page. • Working on the actual add secure payment form for collecting credit card data. • Lots of time working on Java Script for that page. |
|
|
AU 1530 |
|
Daily Tasks | 10/31/2009 | • Working on the cart payment form and shopping cart flow with merchant processing. | |