DayBackForFileMaker

In App Updates

How Do In-App Updates Work?

DayBack can deliver code changes--both bug fixes and new features--without asking you to reintegrate the calendar into your files.

Weuse this to deliver all sorts of enhancements to the calendar, including some big features like FileMaker Go support (delivered Jan 15, 2014) and the gantt chart (delivered Dec 7, 2015). (Here is a list of the updates delivered so far.)

And here's what it looks like in action:

http://youtu.be/1Ll_qIGMBwM

What if FileMaker file changes are required?

A lot of the codebase for DayBack is written in Javascript and executed in the web viewer: that code is modified though these in-app updates without developers needing to do anything. However we are still running this in FileMaker, and there are many interactions with the FileMaker file itself. Sometimes this means there will be necessary changes in FileMaker scripts and possibly layouts. Generally it will be a matter of copying and pasting scripts from a newly downloaded version of DayBack. You can find a link to specific instructions on the version history page. If FileMaker file changes are required the update will have two components. Update the core calendar codebase as shown in the video above, then follow the instructions for updating FileMaker scripts.

What if I don't like an update or it breaks something?

Should we ever release a breaking change, you'll have the ability to revert to the last version you were running before the update. At the start of the update routine, DayBack saves a copy of your current code base just in case you need to revert. (Only one copy is stored, so you can only revert one version back.)

To revert, visit the "Under The Hood" layout and click "Revert to Previous Version". If any FileMaker script changes were made those will not revert and you may need to undo those changes manually. You could do this by pasting script contents from a backup into the scripts that changed.

=)

(855) SEEDCODE
support@seedcode.com
Follow us: