Logo Practice with Ankit | Form and DB Operations

Client Survey

Id Name (Link) Surname Gender Marital Status Have Kids Mobile Age Last Updated On Remove
Requirement: Form and DB Operation 7 - Delete Feature (Soft Delete)

This exercise finalizes the CRUD operations by implementing **Soft Deletion** and adding necessary UI feedback for destructive actions.

List Screen Updates:

  • Add a new column, Remove, at the end of the table.
  • Each row in the Remove column must contain a **Trash icon** (🗑️) that triggers the delete process.

Delete Functionality:

  1. Clicking the **Trash icon** must open a **Confirmation Popup** (Modal).
  2. The popup should display the message: "This action will remove the record from the database, would you like to proceed?".
  3. The popup must have two buttons: Yes and Cancel.
  4. If the user clicks Cancel, the popup closes, and no action is taken.
  5. If the user clicks Yes:
    • The delete operation must perform a **Soft Delete** (set the record's **IsActive** attribute to False). Do not physically delete the record.
    • A **Spinner** must be shown on the screen, simulating the execution of the database operation.
    • After the simulated operation (e.g., 1 second delay), the list data is refreshed (which hides the now inactive record).

Hint (OutSystems): For soft delete, use an **Update Server Action** to set the `IsActive` field to `False`. Filtering the table data is then done by adding a condition: `Filter = RecordList.IsActive = True`.

Ankit G Avatar
About the Author: Ankit Gangrade

Ankit Gangrade is a passionate Low-Code Architect, Developer, & Educator dedicated to helping students and professionals build modern applications faster using OutSystems and Cloud-Native technologies. His goal is to bridge the gap between traditional coding and modern low-code platforms — empowering the next generation of developers to build smart, scalable, and cloud-ready apps.