• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

interaction with customer id?

 
Alenkhe David
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The id value (an 8 digit number) of the customer who has booked this. Note that for this application, you should assume that customers and CSRs know their customer ids. The system you are writing does not interact with these numbers, rather it simply records them. If this field is all blanks, the record is available for sale.

Am placing emphasis on the bolded text therein: can I restrict CSR not to book records that allready have a valid custormer id, or do I leave this since it says "The system you are writing does not interact with these numbers, rather it simply records them".

Thanks.
[ August 18, 2008: Message edited by: Alenkhe David ]
 
Roberto Perillo
Bartender
Posts: 2271
3
Eclipse IDE Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
can I restrict CSR not to book records that allready have a valid custormer id


You can, and you should!
I mean, at least that's what I did... unless you want to assume something else (like, a CSR can somehow override a reservation made by another CSR), this is pretty much what you have to do.
[ August 18, 2008: Message edited by: Roberto Perillo ]
 
Alenkhe David
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think, making a CSR override a reservation would make better sense; since CSR should know more about customer id's than the application.
 
Roberto Perillo
Bartender
Posts: 2271
3
Eclipse IDE Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, as long as you justify your decision, that's ok. For instance, this is how my application works: after the CSR books a room, the reservation cannot be overriden. In other words, the room cannot be "unbooked". I took this approach for 2 reasons: first, security (since the CSRs do not have user name/password), and second, simply because this was not required. But I know other people did implement an "unbook" function. As long as you justify why you're taking a particular approach, you're ok.
 
Jeffry Kristianto Yanuar
Ranch Hand
Posts: 759
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My Solution is like this, when a CSR books a record that already been booked, the application ask the CSR for confirmation. I don't think it is a good solution but my requirement doesn't say about that kind of situation so I just use simple solution.

Hope this help

Jeffry Kristianto Yanuar
SCJP 5.0
SCJA
SCJD (Working on UrlyBird 1.3.2) --> testing and documenting the assignment
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic