Archive for the ‘Web Application’ Category

Online Artwork Approval

Wednesday, October 27th, 2010

We are a promotional product company which sells pens, mugs, bags, rulers etc printed with our customer’s message / logo on. Currently our designer designs the product makes amendments and then sends the customer a PDF proof for them to check spellings position content etc and then sign and fax it back to us before we send the item into production. We basically want to streamline this process and let the customer digitally sign the proof off.

The Features we would be looking for are as follows:

When a job is booked in we would enter the customer’s details if not already in the online database, and open up a new job under a job number. We then can send an email template to the customer asking for artwork for the order, the status of the order would initially be set as awaiting artwork. If we the status has not been changed to awaiting mock-up then an automatic artwork reminder email is sent after a specified number of days. Under the customer information they will have a unique customer number and then each order will have a unique job number.

Once we have received the artwork the designer would set this status to awaiting mock-up
Once the mock-up is uploaded the customer is automatically emailed and the status changes to waiting for amendments or approval.

Once the approval is uploaded there will be a box with a deadline of approval this will have a default number of days in it (e.g. 5days), but if the designer requires the approval more urgently he can overtype it to a specified number of days. If the approval is needed the same day he can type in 0 which stops any chase emails but puts it to the top of priority list.

Once the artwork is uploaded and an email is automatically sent to the customer if they do not approve or make amendments within a set number of days they will get an automatic reminder email after 2 days (template 1) and again after 4 days (template 2) an email is also sent to the designer to let him know the customer is close to the deadline. If they go over the number of days specified then an overdue email is sent (template 3).

The customer will receive an email with a link, where they will be taken to the artwork page of that specific order. If the customer is happy with the design then they can click a few tick boxes saying they have checked spelling, layout, colors etc and put their name and then click a button to approve. A confirmation box will be displayed to make sure they do want to approve the artwork – this feature needs to be date and time stamped in the database as well as taking a note of their IP address. An email will be sent both to the customer and to the designer saying that the artwork has been approved; also the status of the job will be changed to approved.

If the customer is not happy with the design then they can click amendment which will bring up a text box, in which the customer can type what they want changing and click send. This will then send an email to our designer with the amendment information. If the customer asks for an amendment this will automatically open a new page amendment 1 (job number-1) where the designer needs to upload the changed artwork and the status would change to awaiting amendment. The whole process of approval will then start again until the customer is happy with the design.

An overview page will be available to the designer with all the jobs on the go that are awaiting artwork, approval or amendments (probably colour coded whether we are waiting on the customer or the designer) and in order of priority (days left to approve).

A customer online portal will be available where they can login under their email address and password (customer number); there would be a list of jobs with the ones that have not been approved at the top in date order. The customer will have the ability to go through the history of their artwork approvals and amendments.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Product Comparision Tool

Friday, October 8th, 2010
I was going through the site, Carwale.com, And i was impresed with thier design on comparing cars. Every reseller has this option used by their customer who visits thier site. Let it be an popular algorithm/logic/interface, i just wanted to try myself to create that kind of interface and let’s see how can we improve further on this.
There are few points i have considered in my mind, one among them is the data should be picked dynamically, so that it doesn’t need any code change to add something new. After spending 80mins to finalize the DB design, i came to the following design.
ER-Diagram
Based on this, now i’ll proceed to code, lets see…How can i improve further, i know i’ll get many changes ;)
Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Issue Tracking System With SAAS Model

Thursday, June 17th, 2010
I was not able to write on my blog, since my concentration was little diverted to my old pending task of completing the SaaS based issue tracking system, Actually the idea started in 2007, when my boss asked manojbabu to look for an issue tracking system. And started coding for two or three pages, then stopped after that, due to some other important work. Now thought of starting it again and since i lost the previous code I’ve started again from scratch. i.e Writing a Class for DB Connection and for Grid View as well, including JavaScript and luckily i have got the images from Manojbabu.Thanks to him for the designs.I’m still brain storming for many ideas. But the basic skeleton is ready.
Since i said this follows SaaS model, we need a to establish the master data, we need many interfaces for this it self.Even though the requirements are pretty similar it took little more time than the expected, this is since i lost the touch in Coding and in LAMP stack tooo. It was a great fun to go back to LAMP and code again. Following screen shot shows how does an admin establishes the master for a company from scratch including from creating a new company.
Login Page
Login
Admin Page with All the Master Data Creation Page
Admin Home
Grid View with Pagination
Grid View
Form Validation With AJAX
Forms
Creating an Issue
Issue Creation
Search For an Issue
Search an Issue
Search For an Issue Result with a Special Image for Edit
Issue Result Grid
Features that are really in need and to be implemented are

  1. File Upload is still pending, since i need to learn that clearly and write a generic component :(
  2. Grid View Can get a Search Bar.
  3. Exporting to Other Microsoft Office Formats.
  4. Revision History is Not Complete Yet.
  5. UI improvements for Changing the Status of a Issue.
  6. and goes on.
During my brain storming, i have got lot of ideas, to be implemented are

  1. JQuery can be used to improve the UI
  2. LAMP can use MemChache module to improve the performance
  3. Can be integrated with Twitter,RSS and SMS
  4. LDAP authentication
  5. Multi language and DB support.
There are many options like this, but i don’t know how far go ahead and do it. After completing the necessary features, i’ll be attempting to integrate with Twitter and RSS.
Very seriously i’m laughing @ me because we have 100’s of open source web application available for Issue tracking, i don’t understand whats the fun in developing one more on the same, End of the day i’ve brushed by LAMP knowledge to the level, but the not upto the mark what i’ve learned from my Guru in Baba9.
Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)
Get Adobe Flash player