![]() |
![]() |
![]() |
|
![]() |
|||
![]() |
|||
![]() |
GoLive 6 Dynamic Content Samples | ||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
||||||
Main View | Administration View | How it Works | ||||||
![]() |
||||||||
![]() |
|
A. Name of the employee to delete. B. Cancel and delete buttons. Content SourcesThe Confirm Deletion page uses the same content source as the other pages, the People table from the Search Engine database. When the user arrives at this page by clicking on a delete link, the content source automatically selects the right employee. A.The first and last name bindings indicate which employee the user is about to delete. B.The delete button uses the Delete Record Form Action. Clicking it deletes the indicated employee from the database. The success and failure pages are both set to edit.jsp, so that regardless of whether the delete action is successful, the user returns to the Edit Phone Directory page. A better design would show a different page on failure to give a useful error message. The cancel button works differently. It uses client side javascript to implement the cancel behavior. The javascript looks like this:
When the user clicks this button, he returns to the Edit Phone Directory page without making any changes to the database. Note that the cancel button is a normal button, not a submit button. |