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 - 3/1/2011 to 3/31/2011 - (40)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 405 |
|
Daily Tasks | 3/1/2011 |
• Building and testing code for the Charge Anywhere gateway. • Posted files online. • On the phone with Steve going over updates and needs. • Updating the merchant flyer. • On the phone with a customer going over payroll and problems with a company. They needed some major clean-up. • Working on the scheduler application. • Brainstorming and reviewing notes. • Wrote an email to a customer about tracking inventory on a location specific method. • Small tweak to the main adilas.biz homepage. • Added a search date and changed the stats to a daily stats compared to the total stats. • Worked on a logo for a company. |
|
|
AU 406 |
|
Daily Tasks | 3/2/2011 |
• Commissions, checks and a server outage. • Brainstorming on the scheduler. • Wrote a follow-up email about using the customer PO# field for invoices as a searchable sub location field. • I also decided that I’m going to create a mini application for the “any” scheduler to get basic functionality down. |
|
|
AU 432 |
|
Daily Ideas | 3/2/2011 |
-What if the functions of time were a corp-wide setting. Only functions of time would be turned on if set by each crop. -On the scheduler, once known values are known, help speed up the flow and allow for multi’s to be entered in at the same time. This could be class times, work schedules, shift planning, etc. -We have a building need to help handle cash drawer – type transactions. Basically, cash comes in – does not get deposited and goes out the door towards something else. This throws off the deposit and leaves things flapping in the wind. |
|
|
AU 407 |
|
Daily Tasks | 3/3/2011 |
• Basic adilas stuff – invoices, deposits, statements and emails. • On the phone trying to talk to different people about getting the Charge Anywhere gateway up and running. • Email to a contact about merchant accounts and options. • Planning out the mini application and scheduler demo. |
|
|
AU 2187 |
|
Tech - Elements of Time Tables | 3/3/2011 |
Notes from the Tables & values for the element of time brainstorming: (Notes only recorded here, not table names, please see scans) - Set the templates up, set this up kind of like the corp-wide settings page. - Not all of these are needed on the same table… just trying to air out the scope and needs. - Need to add new titles to the tie_in_flex_grid_titles for other 11 & 12 - Need to add two new app types to the app-types table - Invoice Status Table Values: dummy, blank, no charge, only quotes (no invoice), needs to be invoiced, invoiced, N/A – other - Time Actions Table Values: dummy, blank (new), started, stopped, in progress, pending, completed, canceled, checked in, checked out, other - Time Frequency Types: dummy, seconds, minutes, hours, days, weeks, months, years - Maybe think about a payroll status of “paid” - If yes, go back through and update all that have been marked as paid (stock and invoices) - The element of time has a number of time stamps that are used. Make sure and remember them. - Keep it simple! - Maybe we could add a photo link to the flex grid search. The photo would be to the main. Be able to search notes as well. - Info on latitude and longitude o Latitude = vertical, up/down, or y coordinate o Longitude = horizontal, left/right, or x coordinate o Depth/space (Altitude) = stacking, front/back, or z coordinate (altitude), height |
|
|
AU 408 |
|
Daily Tasks | 3/4/2011 |
• On the phone with customers. • Small fix on the payroll reports. Took off the requirements for all monies, all paperwork, and all trade-in info. It should be a more flexible and open now. Called and told a customer I had been speaking to earlier that day. • Working on a bank report problem for a customer. Wrote an email asking for help to get things in order. • Working on the scheduler mini application – phase I. • Writing an email to help steer some customers in a good direction on adilas as far as banks and starting bank dates. Trying to help them make sure the outstanding’s get counted. • Planning out database tables for the element of time. • Did a full database back-up. |
|
|
AU 409 |
|
Daily Tasks | 3/5/2011 |
• On the phone with Steve going over the game plan and catching up on direction, needs and vision. Pretty busy and pretty crazy. • Writing an email to a customer on how to undo a bulk clean-up mistake that happened yesterday. • Email about commissions. • New logo for a company. • Working on the database backend of the elements of time. • Did some research on RFID tags and GPS coordinates. • Working on database table design and layout. • More brainstorming on flow and needs for the application as a whole. |
|
|
AU 2188 |
|
Current Problem Areas - Scheduler (Elements of Time) | 3/5/2011 |
Current problem area – Scheduler: 1. I’ve got some great tables and ideas… I’m missing the first and most basic parts – templates and what they include. Settings and presets… 2. I originally came up with the idea of categories… Now I’m not sure if I need them… at the same time it might be cool if you could assign multi (1-many) on categories. However, I’m not sure if it is needed. 3. Lots of my brainstorming is deep and all inclusive… kind of the dream… what needs to be done right now? What needs to wait? And what is just a dream? Maybe think in phases… plan for say three phases. 4. How long do I have and what is the goal as far as timeline, functionality, needs for other projects, complexity, etc.? 5. Where is the biggest pain? Education? Server-side and processing? User-side flow and functionality? Depth and bigness of the project? What is the goal? Are we being too broad? Where can I get the biggest bang for my back? 6. I had a dream about the server and it struggling to keep up with data demands. How does that play in to everything? We had a 15-20 minute reset this week… How does that play in? We have a need to secure the images and speed up the upload process. This is a known problem area… 7. What have I promised? What are the time lines and immediate needs? What can wait for a couple of days? Weeks? Months? Longer? 8. My first promise is to one of our clients (other than personal promises)… I promised a first round scheduler – first of next week. I need to focus in on that. 9. Just start digging in… things will open up as you go! 10. “A fox that chases two rabbits catches neither.” Old saying about setting your focus. |
|
|
AU 410 |
|
Daily Tasks | 3/7/2011 |
• Emails and general stuff. • Working on the scheduler. • Planning out database tables. |
|
|
AU 411 |
|
Daily Tasks | 3/8/2011 |
• Went up to Bear Lake to work with a company on web stuff. We made a few modifications and posted a number of new files. 90 miles. • Creating database tables. • Setting up an Authorize.net account for a company. • Posted the new time database tables online. • Spent some time on the phone talking to Steve about RFID tags and what is going on in his neck of the woods. |
|
|
AU 433 |
|
Daily Ideas | 3/8/2011 |
-I was reading in the scriptures about Ammon. He was a master at serving and building on common ground and common beliefs. (Alma 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. |
|
|
AU 412 |
|
Daily Tasks | 3/9/2011 |
• Writing an email to an associate to update them on progress on the scheduler. • Working on the scheduler. • Brainstorming on main application types. • New logo for a company. Posted logo and colors online. • Brainstorming on rentals and different levels of tracking things. |
|
|
AU 2189 |
|
Brainstorming Inventory Types - Rentals | 3/9/2011 |
Inventory Types – Rentals: 1. Randomly enough… the first page that I wanted to fix deals with inventory types. We already have an inventory type for “Rentals”. Currently it is somewhat “inactive” but is used at least once for the hardcoded part number “Rental” and assigned to the rental sales tax category. 2. What do we need to do to “reactivate” that inventory type? How will this effect things? Will it rock the boat? Will it make things better? I’m shooting for better! 3. I’m now getting to the point that we want to include rentals. 4. Currently, rentals are very basic and have no tie-ins. It is a hardcoded part that is controlled on the corp-wide settings page. There may be some value in keeping things simple to a point. 5. We also have an unused invoice type called “Rental ticket”. 6. We are introducing the element of time which ties in to rentals. 7. There is a difference between a rental and a sale… a rental may be used over and over again but a sale takes the item(s) out of inventory. We need to be able to track the quantities, costs, and prices… in everything… 8. The users will want to know how many times each item has been rented and what each unit (thing or rental) has produced by number of rentals and revenue compared with purchasing cost and/or up keep costs. 9. I would like to be able to allow rentals of stock/units, parts, users (people and salespersons), places, and general things. Virtually “any” thing including time and blue sky. We at adilas are virtually renting a web service. We may eventually rent or white label the entire application. 10. I really want our invoices to be able to rent and buy on the same invoice. Basically a “mixed” ticket. Put whatever you want on the invoice and we’ll figure it out. 11. How do I know what is a rental and what is for sale… How does each corp and location decide this? How do you pull an item out of inventory and make it become a rental? 12. What about renting 5 different things… 3 days on 3 of the items, 2 days for 1 item, and 1 day for another item. How do you keep it all straight and help the system keep track of things. And… of course… this all needs to be on the same ticket. 13. Not to mention a security deposit of $200 that will be paid back up on proper return. This could also be a cleaning deposit. This needs to be tracked as a liability back to the customer. Maybe we could have a flag on the payment that says flag as a liability. 14. What happens if some maintenance is needed… how does this get tied to the correct unit? Outside repairs, internal parts tickets, depreciation, unit buy down? 15. Stock/units already have a bunch of those features… however, they are the most cumbersome to sale… except for the wholesale cart builder. 16. What if you had a pool of rentals and you could add them really quick like the wholesale cart builder? What would happen if you could set an in/out date range for each item? This could tie into the elements of time. 17. What about the ski mountain I worked for and the rental shop… They have hundreds of boots, skis, boards, helmets, poles, etc. They could either use a hardcode scanner or select a general category and enter a number. This could be preset bins, tubs, pools, or categories. 18. How much time does this take? There might be a line between speed and accurate data. What if I have 35 or something, 50 of another, and 10 of another? Maybe I just want to know quantities and types… I many not want to know exact numbers. 19. What about taking things all the way to accounting? What about just a fast and effective operations tool? How do I accommodate both parties? What are the goals for both? Where do they combine or join up? 20. There are multiple pieces that need to be pulled together. How do you skip steps and jump without making things complicated? Would you design it different if no accounting was needed? How and why? 21. Rentals, reservations, and scheduling are very similar and share a number of different pieces. I’m hoping to tie them in to the element of time. 22. If I click a button and the system does 50 things… I’m cool with that. However, if I make a mistake and want to make a change… does the system change all 50 or do I have to do it manually… there is a difference. All of the sudden… I’m not so cool with that… meaning manual changes… keep things automated. 23. If I collect all of the details… can I shoe them back to the user in a grouped or simplified way? How many steps until I’m at the detail level? How many levels are above that? What do I want to see and how should it look? How many rental tickets am I doing per day? Volume? Complexity? 24. What are the different levels of tracking and what does that take? Each company may be so different…. a. Mental b. Paper c. Spreadsheet d. Software e. System level f. Mixture of above g. Mass or high volume h. Contract level 25. Sometimes rentals need a self service station that is really dummied down and open to the public. This could be just customer info or maybe even simple items… maybe a quote that will become an invoice. |
|
|
AU 413 |
|
Daily Tasks | 3/10/2011 |
• New logo for a company. • On the phone with Steve going over rentals and how to work on some of that stuff. We are going to need to rework the balance sheet and how things flow. • On the phone with a customer going over how to do a credit card transaction. • Working on a corp-wide setting to help control the auto calc switch on the advanced add to cart page. • Quick email to a customer about bank stuff. • Finished up on some advanced add to cart tweaks and started working on the cross-corp billing pages and permissions. • On the phone with Steve going over our days and what is going on. We talked about current needs and where we are headed. We need the cross-corp billing, the elements of time demo, etc. • Writing an email to a potential adilas consultant. • Did some ColdFusion research on the sleep ( ) function and image functions. • Posted new code and files online for the advanced add to cart – auto calc switch and corp-wide setting. |
|
|
AU 434 |
|
Daily Ideas | 3/10/2011 |
-Another known hole is the adilaswebservices.biz site. If that is down, the main site may appear to hang. -Be able to replace the mini thumbnail for image one. |
|
|
AU 414 |
|
Daily Tasks | 3/11/2011 |
• Working on the cross-corp billing page. • Added a new corp-wide setting for allowing cross-corp actions. |
|
|
AU 415 |
|
Daily Tasks | 3/12/2011 | • Working on the cross-corp billing page. | |
|
AU 416 |
|
Daily Tasks | 3/14/2011 |
• Working on the cross-corp billing page. • On the phone with a contact talking about GPS integration. Wrote a follow up email to an associate about the phone call. • Random adilas clean-up and work. • Fixed deposits, wrote off some bad debt, fixed some reoccurring invoices, etc. • Working on the cross-corp billing page. • Made a quick change to the location special line item page for stock/unity sales. Opened the tax categories a bit. • Working on validation and history messages for the cross-corp billing. |
|
|
AU 2190 |
|
Brainstorming System Needs & Cross-Corp Billing Ideas | 3/14/2011 |
System Needs: - Grouped reports – all app types - Detailed look (25) per page – all app types • Deposits, expense/receipts, PO’s, invoice, quotes, stock/units, balance sheet items, recipe/builds - Save as PDF - Custom reports - Show last N – where, N=a number - Normal searches – but limit data that gets pulled back - On advanced searches – be able to filter the results. Refine each search • Basics: - From date - To date - Location - Vendor/payee – name or id - Customer – name or id - Type or sub - Created by - App type - Date switch - Corp - Main id - Name type = 1 b.2, 2 las, 3 first, 4 any, 5 rd Cross Corp Billing Ideas Use the steps (500 or 1000) function – values in milliseconds Use image functions inside ColdFusion to tweak graphics 1. Start with corp – depending on permissions… either just certain corps or all corps if the any feature exists. 2. Check permissions 3. Choose a vendor 4. Show last 4 for that vendor 5. Created the new expense/receipt 6. Upload any photos - Be able to choose who the user is – only with the any corp permission - Be able to view past couple e/r’s - Be able to back up steps - Be able to assign photos - Add a special history message showing that action came from cross-corp pages and function - Maintain privacy security - Set up a corp-wide setting to allow cross-corp billing - Back tie to invoices (optional) - The corp-wide setting allow_cross_corp_billing should also be checked when selling items from one corp to the other. This will tighten things up. - Be able to handle Normal/E/R’s, on account pmts, REI’s, and check requests. |
|
|
AU 417 |
|
Daily Tasks | 3/15/2011 |
• Uploaded files and did some testing. • Updated the corp-wide settings help file. • Working on viewing cross-corp expense/receipts. • Brainstorming on system report needs. • Wrote an email to an associate. • Started working on statements. Added three new fields for invoice age, paid status and payment types. • Small photo fix for a customer. • Added some new Java Script to the add/edit statements page. • On the phone with Steve going over the day and what is happening. Good stuff, we are both quite busy. Steve is setting up a bunch of new clients. • Created and ran the global update on statements. • Added new database fields and posted files online. |
|
|
AU 418 |
|
Daily Tasks | 3/16/2011 |
• Working on the help file for the add/edit statement page. • Research on the cfx_htt5 and asynchronous execution. • Did some online blog reading and research on uploading files in ColdFusion. |
|
|
AU 419 |
|
Daily Tasks | 3/17/2011 |
• Brainstorming on the progression and needs of accounting over time (see notes below and pages in red notebook). • Ran some test scripts for certifying for the Charge Anywhere gateway. • Ran into a coding problem with my unique identifiers. Fixed code and sent off results. • On the phone with an associate going over database back-up and security. • Lots of research on the climate tag. Watched a video on the subject and took some notes. • Wrote an email to help this associate with security stuff. • On the phone with Steve going over progress and ideas for expanding the advanced add to cart page. Basically, we are looking at options to add a group button with subs that could be tied to other sub buttons. The subs could then be displayed as a physical button or an open matrix with pre-coded values and multi add to cart options. • A contact came over and helped me in audicity sound editing program. Went over a few small things and did some playing with my mic and recorder. |
|
|
AU 435 |
|
Daily Ideas | 3/17/2011 |
-Time based accounting, time line accounting, time accounting, adilas content, adilas content management. -Add a clean-up function for all temp files that get created – images, PDFs, xls, etc. Random outline on the progression and needs of accounting and book keeping: Build on common ground, keep it positive. Win more bees with honey than salt, keep it light and fun. Thinking about the progression of accounting: - Way back governments wanted to tax people and merchants. - Businesses had a staff of accountants and book keepers. - People expected it to take some time for a transaction. - Purchases were usually bigger orders – here is what I need for the next n (time frame). - Transactions were simpler – this for that, pretty cut and dry. - Everything was done on paper, entered into journals and then filed to create a paper trail. - Computers started to come on to the scene. - Processing and tracking improved. - Huge book keeping and accounting staffs started to go down. - People started making more complicated purchases instead of this for that – it became this, this, this, this, this and that for that price unless you can do this, then I’ll give you that for this minus 10%. - People started to expect a transaction to take less time. The drive up window and fast food mentality. - Business owners grew and diversified but kept the same size accounting departments or people. Increased the load. - Business owners are needing faster and faster reports and numbers. - More and more complicated tracking needs. - Somewhere along the way costs and price plays into the mix. - Somewhere along the way sheer volume plays a role. - Somewhere along the way cash flow, economic times, trends, supply and demand and customer service play in. - Marketing, promotions, loyalty, just in time inventories, credit cards, internet, mobile devices, cloud computing, push vs. pull, city, county, state, federal regulations and expectations. - Accounting staff is overworked and swamped, element of control, perfectionism and traditions. Business owners and accounting staff thoughts: - Limited resources, worried about a “new” or “unknowns”, mentality – I can do it best, pressure to produce more than you are able, getting tired, don’t have anybody trained with experience, element of pride, etc. - Worries about the future, your company, your customers, and your role in the company. - You almost get stuck and feel like you are in a rut…. It almost gets to the point where the straw will break the camel’s back. - Maybe you have a vision of the future or where you want to go and that gives you strength to hold on a little longer. - Good work ethic and a drive to succeed. -Somewhat unrelated but similar – think about myself working on adilas. More and more complicated demands, limited time and resources, no body trained to take on the load, more and more pressure, still have the drive to keep going, looking and hoping for the future… -Maybe instead of saying, look what we have, say something like “if this helps, great! If not, that’s okay – we just wanted to share what we’ve learned” -Build on common ground and keep an open positive flair! The glass is half full! |
|
|
AU 420 |
|
Daily Tasks | 3/18/2011 |
• General business stuff – invoices, credit card payments, bank stuff and light clean-up. • Research on storing images in a database. • Working on the photo management portion of the cross-corp billing process. • Sent an email to the cfx_http5 guy. |
|
|
AU 2191 |
|
Image Goal | 3/18/2011 |
Image Goal: - Simple form to upload a photo and a caption - Be able to send without stopping ColdFusion – hopefully through cfy_http5 – be cool if you could show some progress… - Be able to use different browsers - Once on the server, resize using cfimage - Show specs and help the user - Convert to binary and store in the database, store original file size - Be able to show the content through a drill-down |
|
|
AU 421 |
|
Daily Tasks | 3/19/2011 |
• Writing an email to Steve about what I have learned about images and uploading content. • Research on cfimage stuff. • Working on a photo mini app using cfimage tags and showing image specs and sizes. • Got stuck putting images into the database and then pulling them out. Encrypting for storage. |
|
|
AU 436 |
|
Daily Ideas | 3/19/2011 |
-Instead of using a location watcher, what if we just beefed up the line items tables so that we could just query them. Put all of the dates, typed and categories so that we could pull data from there. -On uploaded content – record the original file size. Maybe even implement a report that shows violators and/or warns the user if they go over a certain amount of big files. -It may be cool to monitor the file size for a week or two and see what is coming down the pipeline. -Help the user understand about images, sizes, resolution and compression stuff – help to educate them along the way. |
|
|
AU 422 |
|
Daily Tasks | 3/21/2011 |
• On the phone with Steve talking about where we are headed. We talked about images, content server, merchant processing and new my cart favorite button changes. We decided that we are going to be adding a new content server. • Ordered new domains and a new dedicated server. • Did some research on storing images in a database. • Finished up the mini photo app which included storage into the database. I had a problem with storing larger files. The problem was in the ColdFusion data source settings. The blob options needed to be expanded. |
|
|
AU 2194 |
|
Brainstorming Adding the adilas Content Management Server | 3/21/2011 |
Adding the adilas Content Management Server Spanning from March 21, 2011 – August 6, 2012 Adding the adilas Content Management Server (Sketches: see photo gallery) Content – main – web services – university Needs & Wants: 1. I will have at least three servers that may need to get content from the new adilas content management server. 2. Things are separated in order to help each section focus on the task at hand. Main is for working, content is for content and photos, university is for training, and web services is for customer sites and inventory (eCommerce). 3. Currently we have a mix of CF7, CF8, & CF9. That may need to be standardized. 4. All of the systems need to be able to talk to each other. 5. There are currently three different content sizes: (for the Images) o Thumbnail – 29x22 (ish) o Small – 160x120 (ish) o Large – 640x480 (ish) 6. I know that I want to store the big or large photo in the database. What about the smaller image? I’m going to say overkill for now. Just do the big image. This is a known security hole but I’m willing to leave the smaller images as free standing images. 7. Security is a big issue. I want to make is as secure as possible. A couple of ideas might be: a daily password (stored in a database), a daily date password, an encrypted corp-id and/or corp-key, encrypt the user id, check for permissions, have the big photo page look-up data instead of just showing passed in data. Hash and encrypt where needed. Maybe look-up logs on either side of the fence… play pass back and forth. 8. The remote server will need corp, payee, permissions, and photo info. 9. Stock and part # photos are needed on the web services server. These need to be visible by the general public. 10. My cart favorites (photo buttons) need to be local to the main adilas.biz server. This could make it a bit more challenging. Maybe don’t even put these images on the content server… maybe leave these where they are… not sure on this… 11. I will need Crystal Tech’s help in migrating images from old server to the new server. 12. We need to create a clean-up function that runs every night to check the temporary directories. Maybe every hour. We don’t want raw content sitting out there open to anybody. 13. What about check request pages… these files use the big photos and may have multiple images per page. Luckily, these pages are not used by tons of corporations. We might get away with showing the smaller (medium) sized files and allowing a click through if needed to the big files. 14. What about gallery pages? What about thumbnails? What about photo reports? Where does the data get pulled from? I would say the main. 15. When creating a new corp – we need to make sure that the correct folders and files have been copied on the content server. These servers need to be matched up and synced together. 16. Add other galleries (time, deposits, vendor/user) (bank, location, corporation, extra…) 17. Make a default image for MS Excel, MS Word, pdf, gif, video, etc. This needs to be a choice when uploading as well. It might also be determined on the server-side after a valid upload. Lean towards server-side categories. 18. See elements of time 19. Maybe start playing with WDDX (XML) files for passing data back and forth. See old CF books for info. Content Management & Content Server - It might be cool to see an upload status or graphic that says uploading… JQuery style - It might also be cool to help the users tune up their scanners and cameras to make faster downloads. Help the people. - On the current thumbnails, take off the height attribute and re-do all thumbnails. This allows for square, portrait, and landscape images to be used. Currently all thumbnails are forced to landscape and fixed height and width. - Set application vars for the content server. That way we could add more or duplicate our code without having to search for certain URLs over and over again. - Show the new image once uploaded. - Show the main id number on the photo action page. Ex: E/R #, Invoice #, PO #, BSI #, etc. - Show the compression levels and stats. Do some math for the users – once again try to help them. - Limit to 2.5 or 3.0 MB on the upload size. - Check the remote server before trying to go there… quick ping, if unavailable, make a soft response. - We may need to limit certain file types… code, web, java script, SQL, etc. We want it open but not too “loose”. - Check for a possible bug with small file names or unknown formats and characters. Prompt users to change file names and submit again. - Bounce back and forth between servers as if they were the same server. Try to make it seamless. - What about virus protections? What do we do about that? Does that really matter? How would it affect us? What are the other possible threats? - Make sure, that if an edit is done, that all files, including the thumbnail get replaced. We may also need to prompt the user for a page refresh (to help the users). Ended up using a time code to force the refresh. - On uploaded content… record the original file size. Maybe even implement a report that shows violators and/or warns the user if they go over a certain amount of big files. - Help the user understand about images, sizes, resolutions, and compression stuff – help to educate them along the way. - Plays pass back and forth… if something doesn’t get passed successfully, leave it hanging and pick it up on the next go around. Basically, an update flag and date… if not updated, then do the update later… keep both sets of data in sync as much as possible. Or just have one master… - What are the human elements? Time? Complexity? Processes? - We may need to use a flash uploader widget. This helps us determine size before the upload. It also shows upload status. - Our goal is to free up the main server. Don’t make it work too hard to make this new connection. The goal is to be modular. - One of the goals is storing the content. That way, the user has to use the system to get it out. We want to block (limit) direct access. Along with this… do we want to record who views the files and when. This would be hidden 9for now). Content access log… - Do we want to record a history note when a photo is added or edited to an item? Currently, nothing is recorded. - What do our users want? How can we help them? o Upload multiple o Quick & easy o Real thumbnail of their non-image content (way too hard currently with my knowledge) o They may want their data at some point for their own back-up or when terminating service. o Add more counters to let me know what to expect or what I have. o Maybe a break-down graphic or chart of what I have stored. - What about data retrieval? If I write a file to the server… How do I get rid of it? Does this create a problem? - Make sure and have a re-route index.cfm page in all remote folders. I don’t want any browsing of full directories or folders. - Changes need to be made to the web services server (customer sites)… The images need to point to the right place. We also need to change the documentation around a bit (on the customer web side). - Get in there and get dirty… roll-up your sleeves and get to work. Things to do or research: - Set up pings between both servers – standard web services. - Set up timeouts for both sides. This deals with the other server not responding or an error of some kind. - Force to SSC on the content server. - Figure out how to limit the upload size to 3 MB. - Figure out how to limit or figure out the file type. - Once uploaded, we need to store in the database. - Once stored… How do we rebuild and restore to original. - What is the share process (sync data) between servers? - What are the clean-up procedures? Adilas Content Server & Flow Quick copy of notes form mini notebook on 8/2/12 - You always start from the main. From there you get the who and the what. - Once you know the what, you need to check to see if the other player is ready. - If yes, pass to the other player. If no, show a soft error message. Help the people understand the logic. - The main needs to pass all of the key pieces. They may be hidden, scrambled, or otherwise… but they need to be there. - Do everything on the remote side and then either pass back to the main or prompt for more actions. This may keep the user in the content loop or release them at any time. - Record as soon as actions happen and then flag if both sides match. Check for mismatches and try to keep things in sync. - If the remote server can’t validate something… Help the user get back to where they are working. - Maybe it would help to list out tasks and then go through each one. o Add new content o Edit old content o General update (non-content related) o Retrieve and restore content o Sync or check for matching data o Global updates o My cart favorites - Try to keep it seamless and natural. - Each corporation needs their own database table for their actual content. - The goal is to transfer the load first. Then once it is transferred, then further develop the flow and functionality. Keep it simple at first. - There is a hidden photo function dealing with resetting the first stock/unit number. See update New Stock Number method in cfc/assets.cfc. |
|
|
AU 423 |
|
Daily Tasks | 3/22/2011 |
• Added some bullet points for a company’s site for dimensions. Also added new points to the godaddy.com shopping cart. Invoiced for 1.25 from 2/16/11 to 3/22/11. • Basic adilas stuff – invoices, payments and recording E/R’s. • Did some planning for the flow on the content server. • Made some calls to chase some receivables. • Spent a bunch of time working on a csv file to help feed stock/units to a company. |
|
|
AU 424 |
|
Daily Tasks | 3/23/2011 |
• Working on the csv file for the company. Ran into problems with the description field and funky characters like tab, commas, enters, quotes, etc. Finally posted a file online and emailed the customer. • Did some research on CFFTP. • Built a min app (new page) that creates the file and then uploads it via ftp. |
|
|
AU 425 |
|
Daily Tasks | 3/24/2011 |
• Emails and invoices and checking on CFFTP settings and options. • On the phone with a customer going over balance sheet stuff. • Watched an hour webinar on Sorenson 360 video compression and content management system. • Working on the group button options and the show as button or show as grid (advanced add to cart grid). • On the phone with Steve going over things. I gave him a rough overview of where we are headed with the my cart favorites. Worked on the flash part of the group buttons. |
|
|
AU 2192 |
|
Changes Needed for My Cart Favorites | 3/24/2011 |
Changes that are needed for the my cart favorites: 1. We need a way of grouping the buttons. Basically telling the system when to show the buttons. Essentially another filter that we call the group. 2. At least one level deep but allow for other levels. Sub of subs. 3. The main buttons can be tied to a group or be a standalone top level button. 4. Be able to change assignments in bulk. Only show top level (according to what is selected) on the bulk or show all with grouping and categories. 5. If setting up a group – allow for a view mode of show sub buttons actual buttons or show sub buttons in a grid 6. The grid made is a multi-advanced add to cart form that can be submitted as a bulk value. 7. Maybe put the group settings below the recipe settings. 8. Group-icons: This will either be show subs as buttons or show as grid. - add new fields to the my_cart_favorites_table - cart_group_id int(10)1 indexed - show_as_button tiny int(1)1 9. On the output grid – maybe show the “var” or variable. 10. Disable the submit button by default. 11. Allow for a link to do the same thing as the button. Basically a virtual by pass in case you are in a non-Flash environment. 12. We will need a new Flash button that has a small group icon on it. Maybe use a photo size button with a small group image already in the button. Make it have a transparent background. That will allow for colors. 13. When showing groups and subs… make sure that the categories show up correctly. 14. Add the group first… then go back and make sure that the display mode is correct. 15. Make sure and search for all occurrences of: - my_cart_favorites.cfm - bulk_sort_cart_favorites.cfm - view_other_cart_favorites.cfm 16. Basic settings: when coding page - cart_button_type_id = 3 - 1=simple, 2=photo, 3=group - use_math_part = 4 - 1=exact, 2=general, 3=recipe, 4=group 17. Add options to view all (without sub filters) from pages. Pass in a group value of “0” (zero). 18. Check the code and comments inside the dynamic Flash movies and re-upload the new buttons. |
|
|
AU 426 |
|
Daily Tasks | 3/25/2011 |
• Working on the flash buttons. Changed the size and added the payee id and time code to the group buttons. • Working on bulk sort page. • Working on copying and switching to other people’s cart favorites on a more permanent assignment through the session scope. • On the phone with a customer going over the update PO’s and the global find and replace parts section. |
|
|
AU 427 |
|
Daily Tasks | 3/26/2011 | • Logo for four companies. | |
|
AU 428 |
|
Daily Tasks | 3/28/2011 |
• Working on the csv file and automated upload via FTP for a company. Ran into a new FTP problem. Moved files over to the adilasuniversity.biz server. • On the phone with a customer going over different things that they want as far as reports. • Signed up for a webinar for a company to see what they have going on. Working on the my cart favorites and started on the advanced add to cart grid. • Also spent some time writing an email to the guy at Sorenson Media about our future video and training needs and options. |
|
|
AU 429 |
|
Daily Tasks | 3/29/2011 |
• Working on the my cart favorites advanced add to cart grid. • On the phone with a customer going over find and replace and inventory clean-up. • Wrote an email to a customer. It was kind of sad; it was a turn-off of shut-off email. I thanked them for their suggestions and offered to help where needed. We’ll see what happens. • Spent some time on the phone setting things up to handle Amex. • On the phone with the contact about the webinar, I will be watching that on Thursday. • On the phone with Steve going over things from schedulers, to video upload and training, to merchant processing, to my cart favorites, to reps and new accounts. • Finished up the advanced grid and my cart favorites. • Posted files online and updated a number of help files. Long day! (finished at 2am) |
|
|
AU 430 |
|
Daily Tasks | 3/30/2011 |
• Work on a company’s site: Took off a couple of bullets (line items) and added a bullet for patent pending. Did both the main site and the shopping cart. • Working on a new logo for a company. Posted logo and colors. • Small fix for a customer on a small thumbnail image. • Did some clean-up on the new my cart favorites code (advanced grid). • On the phone with Sorenson Media about different things. • Did some research on cfspreadsheet and other new spreadsheet functions. |
|
|
AU 431 |
|
Daily Tasks | 3/31/2011 |
• Small tweak for a customer. Changed out a small stock thumbnail photo. • Playing with Excel spreadsheets and Google maps. • Watched an hour webinar and took notes. • On the phone with a customer going over their floor plan. • Did some research on Ajax and ColdFusion. • Spent some time on the phone with another customer. • Ended up getting a virus right about 6pm(ish). I was searching websites for info on blank form actions. |
|
|
AU 2193 |
|
Note - Dispatch Direct Webinar Notes | 3/31/2011 |
Dispatch Direct Webinar: Service Companies Dispatch board - time across the top and resources down the side Canceled = strike through text One customer can have multiple sub locations On service calls: - Status - Call type - Department - Call type - Salesperson - Priority - Mark as billable - Estimated hours Documents and links: be able to link and save different docs and content tied to customer, locations, or service calls, not just images but .pdf, .doc, .xls, etc. Customer online bill pay – this would be nice Be able to copy or duplicate calls First log the call, and then schedule the call. You could also do a thing called a quick call which is logging and assigning at the same time. Schedule codes, date, times, ranges, or general like AM/PM, 1st call of the day, etc. Dealing with calls: - Arrived/departed - Estimated hours - Actual hours - Use hours or standard charge - Dt hours (double) - Ot hours (overtime) - Travel hours - Use hours or standard charge - These were fields that went with each call Each location (sub of customers) can have notes and items that are on that location – a 1-many on locations to equipment with serial #’s – these need a photo gallery They allow series contracts with billing options (kind of like reoccurring invoices) Basically… all calls (time) need to be created and then assigned. Technician can have specs or options. Techs can have an assigned skill set - able to filter techs by their skillset. Create a call type for whatever. Maps – show calls, scheduled, tech houses, etc. Maps – we can send lat & long (be able to set by location) or a physical address. Able to set-up custom reports and save them. On customer fields… they have a couple date options, a couple of number options, 10 text fields, and all were editable. You can go to a date for a tech and just add a quick call. This skipped the log call first and then assign later. Able to change techs and assign multi (checkboxes of who’s up). |
|