Your DayBack is about to get a lot smarter. Two new capabilities will make scheduling and workflows more intuitive and reliable.
DayBack isnโt just a calendar; itโs the workflow engine for your schedule. It should work how you thinkโ helping to guide you through decisions, catching mistakes before they happen, and making data entry feel natural.
Thatโs why weโre introducing two powerful features, available now through custom implementations:
- Live Event Validation
- Dynamic Calendar Forms
Together, they bring your business rules directly into DayBackโs event forms, enabling live validation for any field, enforcing data integrity, and triggering smart workflows without leaving the calendar.

Why This Matters
Until now, ensuring your business rules were followed often meant extensive custom scripting, or falling back to record pages, triggers, or workflows elsewhere in Salesforce. DayBack can now guide your team as they work with an event:
- Live Event Validation
- Prevent mistakes during data entry โ Required fields, validation checks, and data entry rules appear right in the calendar.
- Enforce data integrity in real time โ Cross-check other Salesforce objects in real time to catch mistakes at the source.
- Adaptive Calendar Forms
- Streamline the user experience โ Hide or reveal fields based on the type of appointment, status, or resource selected. As you make selections, your forms change to guide you to the next steps.
- Automate smart defaults โ Set appointment durations or auto-fill details when a field changes.
And because your validation criteria defined in Salesforce, your team can refine or expand the rules as your business changesโensuring the calendar always reflects the way you work.
Whatโs New Under the Hood
Here are a few examples of what the Responsive Event Validation and Responsive Popover Forms enable:
- Conditional required fields โ Example: require โConsent on Fileโ only for certain treatment types.
- Responsive field visibility โ Dynamically hide or show fields as users interact with the event form.
- Single, unified rule set โ Define validation once, and run them selectively on multiple triggers:
- on render โ Perform simple validation when events are first displayed, allowing your user to spot and react to problems at a glance.
- on event click โ Check the integrity of an event right when the popover opens, catching errors immediately when interacting with an event
- on field change โ Ensure that your data entry matches expected values, changing the whole data entry interface based on changing user choices.
- before save โ Finally, before committing your changes, perform a final data integrity check, ensuring all rules are expected.
- Inline feedback โ Errors and warnings appear as tooltips next to the exact field causing the issue.
- Safe rollbacks โ Optionally revert changes if a validation fails.
- Asynchronous support โ Run SOQL queries during validation (e.g., confirm a practitionerโs license matches a procedure) without blocking user interaction.
- Address fields directly โ Simply your CSS, but using field labels or API names directly in your CSS rules or scripts, making your custom code legible and easy to follow.
Instead of catching scheduling issues days later in reportsโor worse, in front of a clientโtheyโre flagged right where your staff is working.
How to Get Started
Every org has its own nuancesโwhether thatโs resource allocation in manufacturing, credential checks in healthcare, or approval workflows in consulting. Our system is designed to adapt to those differences.
If youโd like to see how these rules could streamline scheduling in your own org, our team can help with a custom implementation.
Leave a Reply