FileWave End-User Notifications (15.5+)

What

Now,With adminsthe usingrelease of FileWave version 15.5.0 and onward, administrators can now send custom messages to enrolled devices directly from FileWave Anywhere, FileWave Central, or through API callscalls. can send customThese messages to enrolled devices, displaying themappear as system notifications foron users.users’ Thisdevices, feature empowersallowing administrators to communicate important information directlyefficiently toand users'effectively, devices,thereby enhancing user engagement and user experience.

Key Functionality:

Functionality

• User-Friendly Interface:Interface: Administrators can easily send notifications by selecting one or multiple devices or groups and accessing the "“Send Notification"Notification” action.

• Customizable Content:Content: Administrators can personalizePersonalize notifications with titles,a authors,title, textauthor, message content, and optional links.

  links to provide context and additional resources.

• Expiration Date:Date: Notifications can be set withSet an expiration date and time for notifications to ensure they are timely delivery and relevance.

  relevant.

• Platform Compatibility:Compatibility: Notifications are supported across multiple platforms, including macOS, Windows, iOS, iPadOS, ChromeOS, and Android devices.

• Client Compatibility:Compatibility: NotificationsThis arefeature supportedrequires fordevices clientsto thathave arethe onFileWave Client version 15.5+

  5.0 or newer installed.
• Audit History: Sent Notificationsnotifications are availablerecorded and can be reviewed in the Audit History.History for compliance and tracking purposes.

• Validation and Error Handling:Handling: The system ensures that all mandatory fields are filled out and provides clear error messages forif issues arise, such as invalid input or unsupported devices.

User

When/Why

Experience:

When to Use

• Urgent Announcements: Quickly inform users about critical updates, security alerts, or system maintenance.

Company Communications: Share company news, policy changes, or reminders directly to users’ devices. Event Notifications: Notify users about upcoming events, meetings, or deadlines. Support and Guidance: Provide users with immediate assistance or instructions when issues are detected.

Why Use This Feature

Direct Communication: Bypass email clutter and ensure important messages are seen by delivering them straight to the user’s device. Improved Engagement: Enhance user experience by keeping users informed and engaged with timely notifications. Cross-Platform Support: Reach users regardless of the device or platform they are using. Efficient Administration: Streamline the process of sending notifications to multiple devices or groups simultaneously.

How

Sending a Notification

 

User Experience

System Notification: Users will receive the notification as a system alert on their devices. Notification Details: Clicking on the notification will display the full message and any included links. Confirmation Dialog:Dialog: UsersAfter sending, administrators receive a confirmation dialog after sending notifications, providing assurance and transparency about the sent notification.

When device will not receive a notification?

iOS/iPadOS

Client is < 15.5.0 version.

FCM didn’t register the device (the user hadn’t opened the App portal ever since enrollment).

macOS

CliClient is < 15.5.0 version.

Kiosk running any issue.

Windows

Client is < 15.5.0 version.

Kiosk running any issue.

Chrome

FCM running issues.

Chrome extension is pinned to earlier version(s).

If one user has read a message, other users can’t seeconfirming the notification duewas tosuccessfully technical limitations.

Android

FCM didn’t register the device.

FW Client running any issue.

sent.

BehavioralRelated specificsContent

General (all platforms)

• Force

  WhenNotifications sendingon notificationsmacOS withfor aFileWave specificKiosk

expiration time,

Digging theDeeper

expiration

Important willConsiderations

occur

General (All Platforms)

Time Zones and Expiration: Notifications expire exactly at the exactspecified expiration time specified,in UTC, regardless of the recipient'recipient’s local time zone. For example, if a notification is set to expire at 2:20 PM UTC, it will expire at 2:20that PMtime UTCglobally. for all recipients, no matter their local time. Therefore, aA user in the United States (Eastern Daylight Time,Time (EDT), where the current local time is 7:20 AM, will see the notification expire at 7:20 AM EDT. This ensures consistent behavior across all time zones.

iOS/iPadOS

Platform-Specific Behaviors

• iOS/iPadOS:

  The expiration date is checked on the Apple side - the notification may be still valid when checked on Apple servers - but not valid for the device → In this case - the notification will be visible, but when clicking on the notification only App Portal without full notification will be displayed.

  • Delivery to Active Users: Notifications are only delivered to the user who is currently logged in on the iPad. device.
  • Session-Specific:

    Logged-outNotifications usersreceived doby not receive any notifications sent while they were logged out, regardless of how many were sent.

If aone user is logged in and receives notifications, those notifications are not deliveredvisible to other users who log in afterward.

later. Expiration Handling: If a notification is valid on Apple’s servers but expired on the device, it will display, but clicking it will only open the App Portal without showing the full message.

macOS

:

• Logged-Out Users: Users who are logged out will not receive notifications sent during their absence.

IfMultiple multipleUsers: All users useon thea same device, each userdevice will receive athe notification.notification individually.

IfUnread theNotifications: notificationUnread, isvalid notnotifications read,will butreappear still valid, andin the Notification Center getsif it is cleared (or the device gets restarted) -restarts, after a new notification arrives, all old unread notifications that are valid are going to be listed in the Notification Center again.arrives.

Expiration Cleanup: After the expiration date/timetime, ismacOS reached,may atake cleanup period needsup to happen in macOS (1an hour byto default) beforeremove the notification disappears from the Notification Center.

Kiosk Visibility: If the Kiosk is not visiblenormally by default,visible, it will temporarily appear when Notificationdisplaying notification details are displayed and will be removed from the UI once the Notification is closed.

ThereEnabling isNotifications: aAdministrators possibilitycan of automatically enablingenforce notifications using Notificationsan Apple Profile, (thispreventing willusers disablefrom userdisabling of turning of Notifications for the Kiosk app): LINKthem.

Windows:

• IfMultiple multipleUsers: Similar to macOS, all users useon thea same device, each userdevice will receive athe notification.

• IfNotification thePersistence: notificationUnread isnotifications notwill read,reappear but still valid, andafter the Notification Center getsis cleared (or the device getsrestarts, restarted)as -long afteras a new notification arrives, all old unread notifications thatthey are validstill are going to be listed in the Notification Center again.valid.

• IfKiosk Visibility: The Kiosk app behaves the Kiosksame isas noton visiblemacOS byregarding default,temporary it will temporarily appear when Notification details are displayed and will be removed from the UI once the Notification is closed.visibility.

ChromeChromeOS:

• User Limitations: If one user has readreads a message,notification, it becomes unavailable to other users can’t seeon the notificationsame device due to technical limitations.

• Delivery Issues: Notifications may not be received if there are issues with Firebase Cloud Messaging (FCM) or if the Chrome extension is not updated to the latest version.

Android:

• Expired notificationsNotifications: Notifications that have expired are not automatically removed from the preview and can still be opened.

• Device Offline: If an Androida device is turned off and a notification expires during that time, the deviceit will not receive the notification whenupon poweredpowering on.

Troubleshooting: When Devices Will Not Receive Notifications

General Requirements:

Devices must have FileWave Client version 15.5.0 or newer. Ensure the device is properly enrolled and connected to the FileWave server. iOS/iPadOS:

FCM Registration: The device must be registered with Firebase Cloud Messaging (FCM). Users need to have opened the App Portal at least once since enrollment. macOS and Windows:

Kiosk Issues: Notifications rely on the Kiosk app. If the Kiosk is not functioning properly, notifications may not be received. ChromeOS:

FCM Issues: Ensure FCM is functioning correctly. Extension Version: Confirm that the Chrome extension is updated and not pinned to an earlier version. Android:

FCM Registration: Devices must be registered with FCM. Client Functionality: The FileWave Client must be running without issues.