Beta Mode

"Beta Mode" allows DayBack admins to preview soon-to-be-released features by running a pre-release version of the DayBack Calendar codebase. Your data and calendar configuration will be live, so you can see exactly how upcoming versions of DayBack will work with your setup.

Turning Beta Mode On and Off

Similar to Draft Settings Mode, the switch to enable or disable Beta Mode is located in the Tools tab of DayBack's admin settings. You can find Tools at the very bottom of the admin settings left-hand sidebar

Turning Beta Mode "on" applies only to your current session. Other users in your organization will still be running the production version of DayBack, as will any other sessions logged in with your account.

This means you can experiment in Beta Mode without affecting any other users. However, remember that you're working with your real data (or your sandbox data if you've logged into a sandbox org in Salesforce), so changes to your events and appointments are real changes.

When to Use Beta Mode

We frequently update DayBack, often as twice a week, making continuous small improvements to the app. Many of these changes are not the kind of thing you need to preview—or would even notice. They are speed improvements or bug fixes: you can see a history of recent updates here.

These changes go through a thorough QA process and are pushed to our Beta servers before being released to production, usually on the same day. While it's not practical to preview every minor update, you’ll encounter them if you consistently use Beta Mode, just as we do internally.

Occasionally, we implement significant updates that may alter the way the calendar functions or appears. These changes undergo extensive internal testing to ensure they’re ready for general use.

For users with elaborate customizations, we may need help anticipating how the changes will react with their customizations. While we strive to add new features rather than modify existing ones, the breadth of potential DayBack customizations is nearly infinite. This means some unintentional side effects may occur.

For these bigger releases, once they’re internally tested, we'll announce them and push them to Beta, allowing users to experiment with them for a period before they go live in production. This testing period could last a few days or even weeks.

If you manage a mission-critical instance of DayBack, such as a call center, online booking site, or medical scheduling system, consider subscribing to DayBack's New-Features alerts (see below). This will notify you via email about significant upcoming changes pushed to Beta, ensuring you’re informed and prepared.

Stay informed about all updates to DayBack by subscribing to email alerts at updates.dayback.com. These alerts will notify you whenever a new feature is announced, including major upcoming changes pushed to Beta. Announcements for Beta updates will begin with "DayBack BETA," allowing you to easily filter or set alarms for them in your email client.

FAQ

What Should I Do If I Notice a Problem?

We'd like to hear about any changes you notice between your regular app and Beta. So please send us a note at [email protected] describing what you're seeing. If you can include a screenshot or a video of the issue, that's ideal.

Can You Postpone a Release?

If you find a conflict between one of your actions and Beta, we'll work to customize your action so it works with the soon-to-be-released version. If it's a serious conflict, we can delay our release until we have a way to resolve the issue. However, we can't postpone a release because you haven't had time to look at it.

Can You Test My DayBack For Me?

Yes! For customers on our Enterprise plan, we can log into your org and test your actions against big changes in Beta, provided you keep a sandbox up to date for us, and we're able to log into that when new versions arrive in Beta. Please get in touch if this is something you're interested in.