Improving usability with colors

Shenpen
Member Posts: 386
Do you want to really impress customers and collect much praises? Use coloring.
For example in Customer List make a customer name bright red if they are over their Credit Limit:
Name - OnFormat trigger:
calcfields(balance);
if balance>"credit limit" then begin
currform.name.updateforecolor(255); //red
currform.updatefontbold(true); //much more visible
end else begin
currform.name.updateforecolor(0); //standard black
currform.updatefontbold(false); // standard
end;
Sounds like a fancy and unimportant things, but REALLY helps implementation. I mean the system of the company consists of the software + the users, every management information relies on the seamless cooperation of the two, and the weak link in the chain is definitely the users. If yo do such things, the trainings you hold are easyer in an order of magnitude, because you can say simple orders like:
"Don't sell nothing if the customer name is red!"
"Don't sell this item if it is red! If it is lilac, check inventory and reservations before selling!"
"If this item is red or lilac, consider purchasing it!"
Really a big help.
Everything that helps users actually helps the consultant as 1) they will be less unhappy, maybe they will even be happy in the long run 2) they will make less errors that you have to hand-hack out of the database.
For example in Customer List make a customer name bright red if they are over their Credit Limit:
Name - OnFormat trigger:
calcfields(balance);
if balance>"credit limit" then begin
currform.name.updateforecolor(255); //red
currform.updatefontbold(true); //much more visible
end else begin
currform.name.updateforecolor(0); //standard black
currform.updatefontbold(false); // standard
end;
Sounds like a fancy and unimportant things, but REALLY helps implementation. I mean the system of the company consists of the software + the users, every management information relies on the seamless cooperation of the two, and the weak link in the chain is definitely the users. If yo do such things, the trainings you hold are easyer in an order of magnitude, because you can say simple orders like:
"Don't sell nothing if the customer name is red!"
"Don't sell this item if it is red! If it is lilac, check inventory and reservations before selling!"
"If this item is red or lilac, consider purchasing it!"
Really a big help.
Everything that helps users actually helps the consultant as 1) they will be less unhappy, maybe they will even be happy in the long run 2) they will make less errors that you have to hand-hack out of the database.
Do It Yourself is they key. Standard code might work - your code surely works.
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions