Tuesday, April 15, 2014

Ticketing / HelpDesk System

* Common: Remedy, Clarify, Quantum, RT.

RT
  • perl-based main engine
  • connect with MySQL / PostgreSQL
  • Apache Web Server (with mod-perl and mod-fastcgi)
  • customer-facing UI: Email VS admin-facing UI: web
RT main concepts:
1) Ticket
  • central object in RT
  • each ticket defines a task to do or a problem to solve.
  • 1 ticket is opened  for each issue, regardless of how many notes or interactions happen with users about said issue
  • include: owner, watchers, status and queue.
  • STATUS: 
    • NEW - just created, not acted on
    • OPEN - being worked on
    • STALLED - not getting worked on right now
    • RESOLVED - ~ completed
    • REJECTED - unreasonable requests
    • DELETED - removed from system
2) Queue
  • central admin domain of RT
  • as a group of services, groups of machines or organizational units.
  • for splitting work flow
  •  
3) Users / Groups
  • ticket Requestor: ppl opened ticket
  • ticket Owner: ppl responsible for working on it.
  • watcher: ppl interest in beeping track of it
    • owner and requestor auto as watchers.
  • queue admin
4) Date / Time
  • Ticket created DateTime
  • Response / Ack. Time
  • Fixed DateTime
  • Completed Date Time
5) Templates
  • generalized action notifications created and applied on global or queue basis.
  • BLANK
  • AUTOREPLY
  • ADMIN COMMENT
  • STATUS CHANGE
  • RESOLVED
6) Relationships
  • ticket-to-ticket's relationship
  • DEPENDS ON: tickets can't be resolved unless another ticket is also resolved.
  • REFERS TO: tickets don't need other tickets, but it would sure be useful for you to look at it.
  • PARENT: a big, general ticket
  • CHILD: a sub-project of a parent

Java Notes

Defensive (防禦) Design = Contingency Design (意外事故)

A) CRISIS POINTS

- the screens people see when things go wrong.

e.g. This isn't what I searched for.
Did my order go through?
How do I get out of here?
Where is the page I clicked on?

> Typical crisis points:
  • Form Error
  • Page Not Found Error
  • Server Error
  • Help Screen
  • Inaccurate search results
  • Out-of-stock item
> Causes for crisis points:
  • A server malfunction
  • Browser incompatibility
  • Unclear Language
  • Sloppy forms
  • A code bug
  • Failed Internet connection
  • Confusing Design
  • Page that have been moved, deleted or renamed
> Consequences / Results when crisis points exist:
  • The customer gives up & bails out.
  • The customer deals, but becomes frustrated & jaded.
  • The customer is helped back on tracked & had a satisfying customer experience.

> Feedback from customers:
  • Abandoned shopping carts
  • Failed registrations
  • Irrelevant search results
  • Increased support inquires
  • Customer frustration
  • Customer bailouts
> Examples of successful design
  • Customized "Pages Not Found" screen that explains the problem & helps people get to the desired page.
  • Contextual help (definitions & inline FAQs that answer questions on spot)
  • Login help (for instance, "Forgot your password? Click here")
  • FAQs that solve the most common problems that plague customers
  • A smart search engine that understands misspellings and other common errors. Like Google: Did you mean to search for: xxx xxx
  • Email notification for the return of an out-of-stock item.
  • Show an alternative items/methods when the selected item is unavailable.
> WHO should consider Defensive Design?
  •  Designers & Information Architects
    • e.g. screenshots, case studies, layout techniques
  • Developers
    • form validation, 404s & common errors
  • Copywriters
    • see how clear copy keeps customers informed & on track
  • Project Managers & Executives
    • learn how a top-down commitment & interdepartemental cooperation can be deliver bottom-line results

GUIDELINE #1
"Give an error message that's noticeable at a glance."

Case#1 - Wrong Login

Problem: No explanation. Just ask try again.

Solution:
You entered an invalid username and/or password. Please check your spelling and try again or click here to get help.

Case#2 - Wrong URL

Problem: Auto. redirect to Homepage. This isn't what I wanted.

Solution:
A customized "Page not found" screen.


GUIDELINE #2
"Use color, icons & text to clearly highlight & explain the problem area."

1. Clearly state the error at the top of the page and at the problem area that needs to be corrected.

2. Indicate the problem area with Bold Red Text.

3. Draw attention to the problem area with an Alert Icon or other graphical cue.

4. Offer possible solutions to the problem or give example / xxxx -xx-xx formats.

5. Don't force visitors to retype data entered correctly.

Thursday, April 3, 2014

iOS7 > TextField and TextView data checking

iOS7 > ASAssetsLibrary Usage

iOS7 > UIRefreshControl

Background Fetch API

iOS7 drastically changed thanks to the Background Fetch API, which is part of the new multitasking features that the latest version of iOS supports. When the Background Fetch feature is enabled to an app, the system wakes the app up in the background from time to time and lets it go online to fetch new data with goal to refresh its content. 


Enabling and using the Background Fetch API in an application, is a really easy, three-step process that contains the following:
  1. To enable it in the Multitasking Capabilities of the app.
  2. To set the time interval in which the system should fetch new data in theapplication:didFinishLaunchingWithOptions: delegate method.
  3. To implement a new delegate method in the AppDelegate class that will handle the result of the fetching process.


Source:
http://www.yourdeveloper.net/item/program-a-uitableview-with-pulldown-to-refresh/
http://www.gowhich.com/blog/528
http://www.appcoda.com/ios7-background-fetch-programming/

iOS > Difference between iOS6 and iOS7

http://bundlr.com/clips/51ee56c84802e10015000030