DayBack Status – Search Results

Official status page for DayBack Calendar. Follow for updates, new features, and infrastructure status.

Save Configuration Snapshots

Today’s update also adds the ability to create configuration snapshots in Administrator Settings -> Tools. Configuration snapshots create a restore point for DayBack’s settings, allowing you to revert your calendar settings to a moment in time. Learn more here: Configuration Snapshots.

Read More »

Preventing Duplicate Events

Today’s release also fixes a bug that could cause events to render more than once (or render when they shouldn’t) when toggling a calendar on and off quickly before the initial process of fetching the events has been completed. 

Read More »

Reducing Redraw

Today’s update resolves an issue where the calendar could render more than once when switching views and a “no events found” message could appear in error.

Read More »

New Admin Tools – Migration Assistant

This update adds a new settings migration tool for enterprise customers, allowing them to migrate their calendar settings between Salesforce sandboxes where DayBack is installed. Enabling this tool requires SeedCode approval, so please get in touch if this would be helpful for your deployment.

Read More »

Improved Invitations

Today’s update fixes a bug that wouldn’t allow users with existing Salesforce accounts to be added to a DayBack group outside of Salesforce.

Read More »

Undo Edits with a Keyboard Shortcut (Shift + z).

Now you have more time to undo event edits in DayBack! When you edit an event in DayBack, you’re presented with a small toast at the bottom of the screen confirming the edit and offering an “undo” button. With today’s release, you can undo your last edit using a keyboard shortcut (shift + z). This continues to be available after the original button disappears, giving you more time to consider reversing your changes.

Read More »

Shared Events Now Updated After Field Mapping Changes

Today’s update fixed a bug where events on shared views could contain stale data when field mapping was changed after an event was shared. This could present as an event not being visible on shared views created after an event was initially shared. A user would create a shared view, then change field mapping, then create another shared view, and the event would not be visible on that second view. Fortunately, this has now been fixed.

Read More »
Current Status
 
Updates by Category
Subscribe to Updates

Subscribe to receive updates of new features and infrastructure status changes: