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:
User-Friendly
Interface:Interface: Administrators can easily send notifications by selecting one or multiple devices or groups and accessing the"“SendNotification"Notification” action.Customizable
links to provide context and additional resources.Content:Content:Administrators can personalizePersonalize notifications withtitles,aauthors,title,textauthor, message content, and optionallinks.Expiration
Date:Date:Notifications can be set withSet an expiration date and time for notifications to ensure they are timelydeliveryandrelevance.Platform
Compatibility:Compatibility: Notifications are supported across multiple platforms, including macOS, Windows, iOS, iPadOS, ChromeOS, and Android devices.Client
5.0 or newer installed.Compatibility:Compatibility:NotificationsThisarefeaturesupportedrequiresfordevicesclientstothathavearetheonFileWave Client version 15.5+- Audit
History: Sent
History for compliance and tracking purposes.Notificationsnotifications areavailablerecorded and can be reviewed in the AuditHistory. Validation and Error
Handling:Handling: The system ensures that all mandatory fields are filled out and provides clear error messagesforif issues arise, such as invalid input or unsupported devices.
UserWhen/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 dialogafter 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 notificationduewastosuccessfullytechnical limitations.
Android
FCM didn’t register the device.FW Client running any issue.
BehavioralRelated specificsContent
General (all platforms)
Digging theDeeper
Important willConsiderations
General (All Platforms)
- Time Zones and Expiration: Notifications expire exactly at the
exactspecified expiration timespecified,in UTC, regardless of therecipient'recipient’s local time zone. For example, ifa notification isset to expire at 2:20 PM UTC, it will expire at2:20thatPMtimeUTCglobally.for all recipients, no matter their local time. Therefore, aA user inthe United States (Eastern DaylightTime,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 userwho iscurrently logged in on theiPad. - Session-Specific:
Logged-outNotificationsusersreceiveddobynot receive any notifications sent while they were logged out, regardless of how many were sent.
later.If aone useris logged in and receives notifications, those notificationsare notdeliveredvisible to other users who log inafterward.- 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.
-
IfMultiplemultipleUsers: All usersuseontheasame device, each userdevice will receiveathenotification.notification individually. -
IfUnreadtheNotifications:notificationUnread,isvalidnotnotificationsread,willbutreappearstill valid, andin the Notification Centergetsif it is cleared(or the devicegets restarted) -restarts, after a new notificationarrives, 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,ismacOSreached,mayatakecleanup period needsup tohappen in macOS (1an hourbytodefault) beforeremove the notificationdisappearsfrom the Notification Center. -
Kiosk Visibility: If the Kiosk is not
visiblenormallyby default,visible, it will temporarily appear whenNotificationdisplaying notification detailsare displayedand will be removedfrom the UIoncethe Notification isclosed. -
ThereEnablingisNotifications:aAdministratorspossibilitycanof automatically enablingenforce notifications usingNotificationsan Apple Profile,(thispreventingwillusersdisablefromuserdisablingof turning of Notifications for the Kiosk app): LINKthem. -
Windows:
-
IfMultiplemultipleUsers: Similar to macOS, all usersuseontheasame device, each userdevice will receiveathe notification. -
IfNotificationthePersistence:notificationUnreadisnotificationsnotwillread,reappearbut still valid, andafter the Notification Centergetsis cleared(or the devicegetsrestarts,restarted)as-longafterasa new notification arrives, all old unread notifications thatthey arevalidstillare going to be listed in the Notification Center again.valid. -
IfKiosk Visibility: The Kiosk app behaves theKiosksameisasnotonvisiblemacOSbyregardingdefault,temporaryit 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 amessage,notification, it becomes unavailable to other userscan’t seeon thenotificationsame 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 notificationwhenuponpoweredpowering 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.