Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Can update every fields?

 
Song Jing Lim
Ranch Hand
Posts: 56
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
DBMain.java mention in Sun's instruction need implement update as below signature:
// Modifies the fields of a record. The new value for field n
// appears in data[n].
public void update(int recNo, String [] data)

My questions:
- Is all fields (e.g. subcontractor name) can be update or only customer id (for booking function)?
- Once record had booked (customer id field contain value), can CSR cancel the booking or/and change the customer id for new booking?

p/s: My assignmnet is implement a CSR system for LLC. is a broker of home improvement contractors
 
Jan Heideken
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have interpreted the requirement:
It must allow the user to book a selected record, updating the database file accordingly

to mean that user can update record only for booking purposes. I have not implemented any relase functionality - alltough now when I start to think about it, it would make sense. In my 'backend'-code I do allow updating of any column but in UI update is limited.
 
Song Jing Lim
Ranch Hand
Posts: 56
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks

Can understand.

So backend code actually allow update all fields, but UI only allow update booking info.

well, left one question:
Once the record had been booked, can other CSR go in to make the change (e.g. update the customer id or cancel the booking)?
 
Jan Heideken
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
After quickly skimming the specs, I can't find any requirements about that. On the other hand, you would not excpect others to reserve the room you have already reserved. Canceling room reservation is another issue that I'm thinking myself also. That is not strictly required, but it would seem to be logical operation to avoid user typos etc.
 
Song Jing Lim
Ranch Hand
Posts: 56
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ya, that is quite logical thinking in real world.

So I should have a cancel button or release button, else the record will always book.

Thanks
 
Jeroen T Wenting
Ranch Hand
Posts: 1847
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jan Heideken:
After quickly skimming the specs, I can't find any requirements about that. On the other hand, you would not excpect others to reserve the room you have already reserved. Canceling room reservation is another issue that I'm thinking myself also. That is not strictly required, but it would seem to be logical operation to avoid user typos etc.


That would be just an update of a record where the reservation details are blanked out, thus is an implicit requirement.
 
Jan Heideken
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yep, agree. So the rules are something like this:

- Room can be reserved if date if following the 48 hour rule
- 'Owner' is empty (room can be reserved) or the value is the same as your own 'user id' (room can be unreserved).
 
Mark Smyth
Ranch Hand
Posts: 288
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jan Heideken:
Yep, agree. So the rules are something like this:

- Room can be reserved if date if following the 48 hour rule
- 'Owner' is empty (room can be reserved) or the value is the same as your own 'user id' (room can be unreserved).


But bear in mind the application is a Customer Service Representative (CSR)
booking system so it is booked on behalf of customers by the CSRs not by the customers. As we do not track which CSR booked what room then we cannot restrict the unbook function to the CSR that booked the room. In that case we either allow all CSRs to unbook rooms or we leave it out (and since it is not required I think this is the best option).

Mark.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic