- 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.
