DayBack allows you to manage a specific list of visible calendars for a given user but not visible for others. Using the Filter Calendar List Custom App Action, you can specify which individuals have access to view a calendar or a group of calendars, which calendars everyone should have access to, and whether there are certain users […]
Dev
Default Durations for each Resource
KC Embrey has just published a new custom action for assigning default values to new appointments: this is great for giving each resource in your org a default duration or status. This action works in any calendar source, including FileMaker and Salesforce. Here’s what it looks like in action: While you can usually set defaults […]
Managing Undos in Custom Actions
DayBack’s custom Event Actions are powerful tools for adding additional logic to your calendar workflow. They let you add your own scripts to everyday behaviors in the calendar, like dragging or editing an event. Each action is tied to a specific “trigger” like “On Event Create” or “On Event Save. ” The On Event Save […]
Make Your Own Calendar Selector
DayBack lets you set up multiple calendars from different data sources. When creating a new event in DayBack, a few different rules govern to which calendar the event will belong. First, you can specify a single default calendar for new events in DayBack’s settings: this can be for the whole group or an individual user. […]
Add Decision Points to Your Calendar Workflow – Using Forms
In our previous article, we looked at creating custom dialogs for DayBack with multiple button options. This article will expand on this pattern and add different input types to these dialogs to create simple forms. With forms, DayBack’s Event Actions can present users with a rich set of controls for gathering data and support more varied workflows. […]