DayBack BETA: Improvements to Custom Actions

We are excited to announce a planned update currently in beta that includes some major improvements to how app actions and event actions work.

Previously, if any action was set to “Prevent Default,” all code for each trigger type had to be grouped together. So, if you had one “Before Event Save” action with “Prevent Default” set to yes and wanted to add a second one, you’d have to merge the JS for those into a single action. This was sometimes a lot of work and resulted in more complicated actions.

Now, DayBack is smart enough to handle the execution of custom code even when stored in different actions, so merging is no longer required. This will make it much easier to maintain and edit custom code as you can now keep code stored in a more logical, atomic structure.

Important: There is one known behavior change. Syntax errors may surface more reliably now. For example, there may have been scenarios where a variable was not declared but set. Like this, for example:

resource = "Person";

Before this would not have produced an error in DayBack, although the code may not have executed properly. Now, that same code would show an error dialog when the action attempts to run. This should be corrected to:

let resource = "Person";

There are no other known behavior changes. If you would like to test your current DayBack install to make sure there are no changes necessary for this update, please access Beta Mode in administrator settings. Then use DayBack as you normally would.

The expected release date for this update is August 6th.

Current Status
All Systems Operational
Updates by Category
Subscribe to Feature Updates

Subscribe to receive updates on new features, bug fixes, and examples. (Please subscribe to status updates on the status page.)

Discover more from DayBack Updates

Subscribe now to keep reading and get access to the full archive.

Continue reading