Consider an hospital's UrgentAlert MBO that has these attributes: Username, AlertTime, Message.
To support this deployment, an administrator might:
A hospital executive demands that alerts be delivered to a specific doctor (or medical team) according to each person's unique user name, within one minute of the message being created in the EIS server.
The Unwired Server administrator responds in such a way that when a new alert is entered into the back-end server, the alert is delivered to the corresponding doctor by setting the cache interval to 0 or "real time". Data is always live and immediate with no caching involved. However, the administrator also sets the schedule repeat for 1 minute and is required 24 hours a day, seven days a week. This refresh schedule is paired with a subscription template for the UrgentAlert MBO with push synchronization enabled.
When any mobile client with an application that includes the UrgentAlert MBO initially synchronizes, Unwired Server creates a push subscription. Because the administrator configured a schedule repeat for every minute, changes are delivered as they occur: when a change is detected, Unwired Server scans through the subscriptions to find all clients that are subscribed to this MBO and determines where the Username matches. When a match occurs, Unwired Server sends the client a push notification, telling doctor to run another synchronization to retrieve the new message using the UrgentAlert MBO.