Delete Source

1. Log in to the Kuika platform.
2. Open the project you are working on from the Apps screen.
3. Add a Button element from the left side of the UI Design module.

4. Open the +ADD ACTION menu from the Properties panel on the right.
5. From the + ADD ACTION menu, add the Searching > Delete Source action according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).

Configure Action Parameters

• Correlation Id (String - Required): This is the unique transaction ID associated with the deletion process. It can be obtained with the Get All Source List action or defined as fixed.

1. Create a New Screen

First, you need to create a screen specifically for these operations.

• Go to the Screens section in the application.
• Click the ‘+ Add Screen’ button to open a new screen.
• Name the screen System Maintenance or Temporary Resource Cleanup.

This screen will be used to list and clean temporary data.

2. List Temporary Resources

• Add the Get All Source List action to the screen.
• Enter COLL-ARCHIVE-202507 as the Correlation Id in the action parameter.
• Display the results in a table or list format.

3. Add a Clean Data Button

• Add a button named ‘Clean Data’ to the screen.
• Link the ‘Delete Source’ action to this button.
• Use COLL-ARCHIVE-202507 again in the action parameter.

4. Confirmation and Result Message

To add a confirmation window to the ‘Delete Source’ action linked to the ‘Clean Data’ button, follow these steps:

• Find the Delete Source action linked to the button.
• Click the three dots (...) menu in the upper right corner of the action.
• From the menu that opens, click + Add Confirmation.
• In the confirmation window that opens, write the message to be displayed to the user. For example: ‘This action will permanently delete temporary data. Do you want to continue?’
• Save.

• Dynamic Correlation Id: The deletion process can be made dynamic by selecting the form data or API result.
• Bulk Deletion Operations: Multiple sources can be configured to be deleted sequentially (e.g. with a for-each loop).
• Pre-Deletion Warning: A modal warning such as ‘Are you sure you want to delete?’ can be added before the action is triggered.
• Post-Deletion Notification: The user can be notified with a toast/alert when the deletion is complete.

Technical Risks

• Incorrect Correlation Id: If an incorrect or incomplete ID is entered, unwanted data may be deleted. Make sure that the ID matches the correct source.
• Unauthorised Access The deletion process should only be triggered by authorised users.
• Irreversible Process: Deleted data cannot be recovered. Where necessary, verification should be performed before the action is taken.
• Data Inconsistency: If the deleted source is linked to other processes, it may cause system errors. Linked records should be checked.

The Delete Source action is a powerful solution for eliminating data clutter in the system and maintaining the order of the application. With dynamic parameter support and advanced usage scenarios, it provides great flexibility to application administrators.