Specifications & Requirements
Browser Support
- DayBack requires an internet connection to function.
- DayBack runs in all contemporary browsers and in the mobile browsers on current smartphones. However, we no longer support Internet Explorer and old Edge/Safari browser versions.
In this article
Requirements in Salesforce
No limits: DayBack is an Aloha app
DayBack for Salesforce is an "unlimited" Aloha app; tabs, objects, and apps in this package don't count against the limits in your organization.
Salesforce editions
DayBack is compatible with Professional, Enterprise, Unlimited, Force.com, Developer, Essentials, Platform licenses, and Performance editions. DayBack also works in Experience Cloud (Salesforce Communities) and in the new "Lightning Platform Starter." DayBack runs great as a console app as well.
Mobile and iPad
DayBack also runs in Salesforce 1 Mobile. We're fully committed to mobile and you'll find all of DayBack's admin settings available on mobile as well.
On iPads, DayBack runs the desktop version with the addition of support for touch events. The mobile interface (with whole-screen event editing) is only for screens smaller than iPad.
Offline Mode
DayBack does not work in the Salesforce 1 mobile app's offline mode, as DayBack requires an internet connection.
Requirements in FileMaker (FM 19 and higher)
Requirements
DayBack requires FileMaker 19 or higher on Mac and WebDirect, FileMaker 19.3 or higher on Windows, and the latest version of FileMaker Go. DayBack does not work offline and requires an internet connection.
Mac Requirements:
DayBack requires Safari 14 or higher. If you're using Mojave, be aware that it comes with an older version of Safari that doesn't support modern JavaScript functions. To run DayBack on Mojave, you'll need to upgrade Safari to version 14.1.
Windows Requirements:
DayBack is compatible with FileMaker 19.3 or higher on Windows.
WebDirect and FileMaker Cloud:
DayBack also works with WebDirect in FileMaker Server 19 or higher, as well as FileMaker Cloud 2x.
Internet Connection:
DayBack requires an internet connection to function and does not operate offline like DayBack Classic. The connection doesn't need to be as fast as what's required for accessing FileMaker files remotely, but it does need to be reliable. A typical internet connection speed, similar to what’s needed for using web viewers with Google Maps, will be sufficient for DayBack to run smoothly.
Requirements in FileMaker CWP (DayBack Classic)
Requirements
DayBack Online requires your data to be hosted on FileMaker Server 12 or higher with XML web publishing enabled and PHP running (the PHP that comes with FileMaker Server works great). You'll also need to have access to place a simple php file on your FileMaker server.
FileMaker Go
You can run DayBack Online inside your FileMaker Go solution (or inside your Pro solution) by placing it in a web viewer: this is the same thing you'd do for WebDirect and you'll find details here.
You can also just open DayBack Online in Safari on your iPad, even configuring custom actions to then open records in your FileMaker Go file as needed. DayBack Online does require an internet connection, however, as it does not have an offline mode.
WebDirect
DayBack Online works great in WebDirect from FileMaker Server 14 and feel very fast. (We haven't tested earlier versions of WebDirect and can't support them). More here: WebDirect.
Runtime
The fmp:// URL protocol used by DayBack calendar's custom actions is not supported in runtimes but DayBack Online can run within a webviewer in a runtime as it does in WebDirect.
Whitelisting URLs
If you're having trouble accessing to DayBack
Access problems may be due to your corporate firewall blocking necessary URLs. In highly regulated environments, you might need to whitelist certain servers. To do this, try opening the following URLs from within your network. If you can't reach any of them, ask your IT department to whitelist them.
Cloudflare URLs:
DayBack uses Cloudflare as its CDN. If you can load dayback.com, it means the necessary Cloudflare domains are already working. However, if you experience issues, refer to this list of potential Cloudflare domains:
Firebase:
DayBack uses Firebase for real-time updates. Ensure the following URL is whitelisted:
Firebase also uses web sockets, which may have region-specific domains. These URLs typically look like this:
wss://s-usc1c-nss-375.firebaseio.com/.ws?v=5&ns=dayback
DayBack URLs:
Make sure the following DayBack-specific URLs are whitelisted: