Mark As Read Notification

• Log in to the Kuika platform and open the project you will be working on.
• Go to the UI Design module.
• Select the element (e.g. a button or list item) that will mark the notification as read.
• Click on + ADD ACTION in the Properties panel on the right side.

• + ADD ACTION menu, add the Notification > Mark As Read Notification action according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).

Action Parameters

• User Name (String): The username of the user who read the notification. Example: ‘john.doe’ This field is required so that the system can track which user read the notification.
• Notification ID (String): The unique ID of the notification that will be marked as read in the system. Example: ‘notif_123456’
• All parameters can be dynamically linked via the Symbol Picker using Action Result, Method Input, Current, Screen Input, Fixed or Component sources.

When a user views the details of a notification, the notification is automatically marked as ‘read’ in the system. This allows the system to track which notifications the user has reviewed.

Add Action to Mark as Read in Notification Details Screen

• When the user opens the notification details screen, the action is added to the Initial Actions section of this screen.
• Enter the UI Design module.
• Select the notification details screen.
• In the right panel, select Initial Actions → + ADD ACTION and add the Mark As Read Notification action.

Configuring the Mark As Read Notification Action

• User Name
• Notification ID

With this configuration, only the status of the opened notification is updated to read. When the user lists the notifications again, this notification will no longer appear as ‘unread.’

• Bulk Marking: Multiple notifications can be marked as read in bulk by sending them to the Notification ID field in array format (with customised processing logic).
• Dynamic User Binding: The name of the logged-in user can be automatically retrieved from a source such as CurrentUser.userName and bound to the parameter.
• List Integration: Users can manually mark notifications as read by clicking an icon on each row in the notification list.

Technical Risks and Precautions

• Empty or Incorrect Notification ID: If an invalid or empty notification ID is sent, the process will fail. Make sure that the ID comes from a reliable source.
• Missing User Name Link: If the user name is missing or incorrect, the system cannot track who read the notification. It is recommended to automatically retrieve it from the logged-in user.
• Repeated Process: There is no need to mark the same notification repeatedly. Therefore, the read status can be checked before the process.

The Mark As Read Notification action ensures that your application's notification system works in a sustainable, controlled, and user-focused manner. It is an indispensable tool for tracking read statuses and optimising system feedback.