1. Bluetooth Datasource Definition

• Log in to the Kuika platform.
• Open your mobile project from the Apps screen.
• Go to the Datasources module.
• Open the new data source screen using the + icon on the left. Then select Bluetooth as the Datasource Type.
• Click the CREATE button.

• Enter the following information in the field that opens:
  
  • Device Name: Required (device name)
  • Device ID: Optional
  • Device Address: Optional (e.g., 00:1A:2B:3C:4D:5E)
• Complete the registration with CREATE.

2. Creating a New Bluetooth Method

1. Click the ADD NEW METHOD button in the data source you created.
2. Enter the following fields in the pop-up form:
   
   • Name
   • Characteristic ID
   • Service ID
   • Characteristic Type: Read, Write, Notify, Indicate
3. Click the SAVE button.

3. Add the Forgot Device Action

1. Click the method you created.
2. From the Properties panel on the right:
   
   • +ADD ACTION → Custom → userguide123 → ForgotDevice_bluetooth.
3. Click the SAVE button to complete the process.

Parameter Definitions

This action does not require any special parameters. The action is performed through the Bluetooth data source to which it is linked.

In a manufacturing facility, a field worker is no longer using the Bluetooth-enabled barcode reader they previously paired with and wants to connect to a new device. For this process, the application must forget the current device and then scan for new devices.

1. Go to the UI Design module.

• Add a Button element.
• In the Properties panel, set the button name to “Forget Device.”

2. When this button is clicked, add the following action from the + ADD ACTION menu to forget the current device:

• OnClick → Custom → Kuika → ForgotDevice_bluetooth.

3. As the next action, add the following to scan for new devices:

• ADD ACTION → Custom → Kuika → ScanForDevices_bluetooth.

With this flow, when the user clicks the “Forget Device” button, the current pairing is removed first, then new devices are scanned and listed. This allows the user to easily pair with another barcode reader.

• Automatic Device Forgetting: In case of a specific error code (e.g., connection_failed), the device is forgotten with notify and confirmation steps added to the scenario.
• Deletion with User Confirmation: A modal screen asking “Do you want to forget this device?” is displayed to obtain user confirmation; after confirmation, the device is forgotten. This process is controlled with notify and confirmation steps created according to the scenario.
• Conditional Forgetting: Can be controlled with an If-Then-Else structure, such as “Forget if the connected device is X, otherwise skip.”
• Notification Display: After the device is forgotten, the user can be notified with Notify.

Technical Risks and Precautions

• Deletion While Active Connection: If the device is still connected, the Disconnect action must be applied first.
• Data Loss Risk: If data has not been transferred from the device before it is forgotten, this information may be lost.
• Wrong Device Deletion: Device name verification is recommended to prevent the user from deleting the wrong device.
• Reconnection Problem: Some devices may experience problems reconnecting after being forgotten; therefore, the Scan → Pair → Connect sequence should be applied.

The Forgot Device action is ideal for clearing the history of Bluetooth devices in your mobile apps and simplifying connection management. It provides a powerful and secure way to reset the user's device usage history and re-establish connections.