Object Handling – Delete

Intro

You can delete objects either from a list report or from the corresponding object page. If the object contains subitems, the delete flow for the items depends on the structure of the object (simple or complex).

To avoid accidental deletion, display a message dialog asking the user to confirm deletion. In some non-critical use cases, you can omit this message (see Top Tips).

The examples below show all delete flows in a full screen layout.

Delete from List Report

To keep it simple, the example below shows the flow for deleting just one object. The flow is the same for deleting multiple objects.

Deleting an object from within the list report

Deleting an object from within the list report

  1. From a list report, the user selects an object and clicks Delete.
  2. A message dialog prompts the user to confirm deletion.
    1. Delete closes the dialog. The user sees the updated list report and a confirmation message toast.
    2. Cancel closes the dialog. The object is still selected.

Delete from Object Page

Usually, Delete is only shown in display mode for the object page, since the user does not edit and delete an object at the same time. Nevertheless, you might need to offer a Delete button in edit mode (for example, if there is no display mode).

If an object contains items, the delete flows for the items depend on the page structure (simple vs. complex). The object itself can be in display or edit mode.

For both simple and complex objects, you can offer Delete in the toolbar of the table that contains the items. For complex objects, you can also show Delete in the header toolbar of the item subpage.

For the flows see:

Delete Complete Object

Delete Item from Table

Delete Item from Subpage

Delete Complete Object

The flow is as follows:

Deleting an object from the object page

Deleting an object from the object page

  1. From a list report, the user navigates to the object details.
  2. The user selects Delete in the header toolbar of the object page.
  3. A message dialog prompts the user to confirm deletion.
    1. Delete closes the dialog. The user sees the updated list report and a confirmation message toast.
    2. Cancel closes the dialog and shows the object in display mode.

If your app uses a flexible column layout and the user confirms deletion, the object page column is closed.

Delete Item from Table (Simple and Complex Objects)

To keep it simple, the example below shows the flow for deleting just one item. The flow is the same for deleting multiple items.

Deleting an item from a table on the object page

Deleting an item from a table on the object page

  1. On the object page, the user selects an item and clicks Delete in the table toolbar.
  2. If necessary, a message dialog prompts the user to confirm deletion.
    1. Delete closes the dialog. The user sees the updated object page and a confirmation message toast.
    2. Cancel closes the dialog. The object is still selected.

Delete Item from Subpage (Complex Objects)

The flow is as follows:

Deleting an item from the subpage

Deleting an item from the subpage

  1. On the object page, the user navigates to the item subpage.
  2. The user selects Delete in the header toolbar of the subpage.
  3. If necessary, a message dialog prompts the user to confirm deletion
    1. Delete closes the dialog. The user sees the updated object page and a confirmation message toast.
    2. Cancel closes the dialog and shows the item subpage in display mode.

Top Tips

Delete in Display Mode

In display mode, always show the delete confirmation dialog.
Reason: The objects or items are deleted in the back end and the user has no option to undo the action.

Delete in Edit Mode

Only omit the dialog non-critical use cases (for example, if the user can add the item easily again or just needs to simulate different data constellations).

Message Handling (guidelines)

Message Box (guidelines)

Message Toast (guidelines)

UI Text Guidelines for Messages (guidelines)