Adding the Delete Record Action to the Project

1. Log in to the Kuika platform and open the project you are working on.
2. Go to the UI Design module and open the Properties panel on the right panel.

3. From the + ADD ACTION menu, add the Managed DB > Delete Record action according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).

Configuring Delete Record Parameters

• Select Table: Select the database table where the deletion will be performed.
• Id: Specify the unique ID of the specific record to be deleted.

Complete the Record Operation

After configuring your parameters, click the SAVE button to save your changes. This will successfully add the Delete Record action.

Workflow:

1. A user triggers the Delete Record action to delete a record from the system.
2. The user specifies the unique ID of the record they want to delete.
3. The Delete Record action is executed and the specified record is deleted from the database.
4. When the deletion is complete, the data in the system is updated.

• The user record with the ID user_12345 is deleted from the Users table.
• The data of the deleted record is automatically removed from other processes in the system.

• Dynamic Data Selection: The Id parameter can be made dynamic. The ID value can be determined dynamically with the form data received from the user. For example, the deletion process can be performed with the ID of the record selected from a list.
• Post-Deletion Actions: After the deletion process, you can redirect the user to another page or display a confirmation message about the deleted data.
• Data Deletion Confirmation: Since deletion processes are prone to user errors, it is important to use confirmation mechanisms to prevent accidental data loss. Two different methods can be used for this purpose:
  
  • Confirmation action: When the deletion process is triggered, a special confirmation window is displayed to the user. The user confirms or cancels the process by selecting “Yes” or “No.” This method creates a separate confirmation step along with the action that initiated the process.
  • Confirmation feature: Thanks to this feature, which can be defined within UI elements (e.g., a button), confirmation can be obtained directly from the user through the element. The message content, title, and button labels can be customized.
  • Both methods make user interaction secure. Depending on your application's needs, you can choose the Confirmation action for more control or the Confirmation feature for simple validation.

Technical Risks

• Incorrect Record Deletion: Make sure that the user has confirmed before deleting.
• Invalid ID: Make sure that the Id parameter is received correctly and is valid. Invalid IDs may cause errors.

The Delete Record action helps keep the system organized and manageable by cleaning up unnecessary or invalid data in the database. Thanks to integration with MSSQL and Oracle databases, effective data management can be achieved without changing the existing infrastructure.