Win a copy of Soft Skills: The software developer's life manual this week in the Jobs Discussion forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

B&S: Is it okay to hide customerId in the GUI View?

 
Rudolph Jen
Ranch Hand
Posts: 37
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi everybody.

At the moment I am implementing the GUI and I am a little bit confused about the customerId ( the id of the customer who has already booked that record):

I would say, that a Customer Service Representative (CSR) gets only records display, that are actually bookable. All the other already booked records would only distract the CSR.

1. Is anyone agreeing with me, that the Search Criteria in DB.find(String[] criteria) should not include the customerId-Field? That means, that this array only have the length of 5 (name, location, specialties, size, rate)??
OR
2. That the serachCriteria for customerId is always "", so that only not booked records are shown.

You see, I am confused. Would be nice if someone could let me know his/her opinion. Thanks.

Best regards,
R
 
chris bajada
Ranch Hand
Posts: 41
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What if a CSR phones sick and another CSR has to take over his work...
it would be a good idea if he can search the records which the sick CSR has booked so that he can follow up on his work
 
Rudolph Jen
Ranch Hand
Posts: 37
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You are right! I should not do this more complicated than expected. KISS is a very fine pattern

CSR is going to see everything. There are no specification for this area, so I am not going to interpret to much details in that by my own.

Best Regards,
R
 
Don't get me started about those stupid light bulbs.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic