See attachment. Screens that follow a list & "detail" model, should conform to the suggestions as specified in the attachment.

"Detail" screen changes:

1) Remove the cancel buttons.

2) In the toolbar, where we have "<<<Back to ...", add all other form actions that are relevant to that object & that user has access to.

a) AquaScript Detail screen: remove cancel button, add a "Delete" option in toolbar

b) Servers: add "edit", "clone", "delete" buttons in toolbar, remove cancel button

c) Scheduled Jobs: add "edit", "delete" buttons in toolbar, remove cancel button

d) User: add "edit", "remove" buttons in toolbar, remove "OK" button

e) Role: add "edit", "remove" buttons in toolbar, remove "Cancel" button

f) User (Admin side): add "edit", "Delete", "reset password" buttons in toolbar

g) Role (Admin side): add "edit", "delete" buttons in toolbar, remove "Cancel" button

h) View "Scheduler": add "execute now" button in toolbar

3) When viewing a "detail" screen, always ensure that the "back to..." is the first action 

4) Rules to implement:

  a) On an edit/reset/... (any "post" type action) operation, both the "Save" & Cancel" buttons should go back to the calling page

  b) When on an "edit" screen, clear the action bar -- meaning, no actions (incl back) should be shown in the action bar.

    bi) One known exception is AquaScript | Execute -- keep this action even while editing an aquascript

    bii) If in AquaScript | Edit & then click OK or cancel, warning dialog should not appear.

c) New operation.

  ci) If I click on New | Save -- go to list screen of the object type that was created. (Note: in future, there could be a story to change this to the detail screen of the object created.)

  cii) If I click on New | Cancel -- go back to calling screen

d) Delete operation: If the user clicks "Ok" to confirm the delete operation, then user should be taken back to the corresponding object's list screen. If, however, the user clicks cancel, the user should be returned back to the calling screen.

e) Back to ... - go back to calling screen

f) Implementation guidelines:

  -- Enforce a maximum stack depth: make it 5 for now.

  -- Clicking on the pagination controls (next, previous, etc) should not add any items to the stack

  -- When adding an item to the stack, the entire querystring should be saved