Visualforce Pages, LWC, and Aura Components

DayBack operates as a Canvas App in Salesforce, meaning its application code is hosted externally on DayBack's servers at dayback.com, rather than within your Salesforce pages. This architecture allows for regular updates without requiring users to install new packages. When new features or bug fixes are implemented, customers benefit from them immediately.

Because of this setup, some of your calendar settings are also stored on DayBack's servers. Please refer to our Architecture and Security page for an outline of what data is stored and how responsibilities are divided between DayBack and Salesforce.

DayBack is wrapped inside a Visualforce page to facilitate authentication and communication between Salesforce and the DayBack Canvas App. The Visualforce page acts as a bridge, enabling the Canvas App to function within Salesforce. Most interactions between DayBack and Salesforce, such as loading data or opening new tabs, are handled via the REST API directly between the browser running the Canvas App and Salesforce. Only when initializing the calendar or opening a new window does the Visualforce or Canvas app get directly involved.

In some scenarios, DayBack can be embedded inside an Aura component, particularly when using DayBack inside a Salesforce flow. However, using a Visualforce page remains the preferred method because it handles the Canvas SDK more effectively, especially when sending data into DayBack. (Canvas Apps in Aura components are constrained by Lightning Locker, meaning once the app is loaded, it's not possible to send messages from the Aura component to the Canvas App.)

Currently, DayBack is not supported in the LWC framework, as it doesn't yet support Canvas or Aura components. But we're looking forward to when it does.