Here is a beautiful mod of DayBack Calendar by Denisa Myrta of Koni Solutions. Koni builds a vertical market app for the construction industry, and the whole app is gorgeous. Here are a few screenshots from the customizations they made to DayBack:

Koni's custom theme for DayBack Calendar in FileMaker

Custom theme for DayBack Calendar

I love the black styling they’ve added to the sidebar and the unambiguous use of icons and highlight colors. (If you’d like to add colored icons to your copy of DayBack, you’ll find detailed instructions here’s an overview with links to detailed instructions: adding text styles, colors, and icons to DayBack.)

DayBack Calendar in the Construction Industry

Koni Solutions was founded a year and a half ago in Toronto,  with the goal of serving the construction industry. CEO and founder, Arthur Kola, owns a successful roofing company in the Greater Toronto area and decided to build a team of programmers trying to tackle every detail of running a construction business smoothly. Here’s how Arthur sees DayBack fitting into their product:

DayBack calendar has been an excellent tool for us giving our product an edge when it comes to scheduling quotation and inspection appointments, ongoing projects, scheduling different crews in house and subcontractors, ordering materials, employee attendance schedules, and to do lists.

We did work very hard on giving a new modern user interface and when it comes to relationships like changing the status of customers which is very important to a trade.

Here are some more screenshots of their work:

FileMaker Layout in DayBack Calendar

Using their own FileMaker layout for items in DayBack Calendar

Icons in DayBack Calendar for FileMaker

Event colors and icons

Resource scheduling in DayBack Calendar for FileMaker

Resource scheduling

DayBack Calendar on iPhone in FileMaker Go

Single-day resource scheduling on iPhone in FileMaker Go (multi-day views available)

Koni does goegeous work; big thanks to Denisa Myrta and Arthur Kola from Koni for including DayBack in their app and letting us show off their designs.

Here’s a great implementation of DayBack Online with a FileMaker WebDirect solution by Jason Trenary at the South Carolina School of Music.

Jason built an online portal for students to reserve recording equipment using the DayBack Online calendar interface. Students are able to see exactly when the equipment they’ve selected is already booked, and when there are openings they can select to reserve the equipment for themselves.

Here’s a video showing it in action: https://vimeo.com/314928217

The equipment selection process is all done in FileMaker WebDirect layouts. Then the calendar is loaded, passing the selected equipment and a unique session id as url parameters to DayBack Online. Using Custom Event Actions, the student is notified when they try to reserve equipment that is already reserved. And when they save a valid appointment, the calendar is automatically closed and the page returns to the related FileMaker reservation record with the updated schedule information.

Big thanks to Jason Trenary at the South Carolina School of Music for sharing his work with us!

If you’d like help utilizing DayBack Online to create a custom appointment booking solution like this, please get in touch.

At SeedCode, we schedule most of our screen-shares with Zoom, so as part of streamlining our workflow we wanted to schedule these Zoom meetings directly from our calendar. Button actions in DayBack Calendar let you add your own buttons to events in the calendar. These buttons extend the calendar’s capabilities they’re great for connecting your calendar with third-party applications like Zoom.

Overview

We created a middleware service that runs the majority of the logic and sends requests to the Zoom API. Using middleware keeps the custom actions in DayBack much more straightforward than they’d be if all the required JavaScript were in these button actions. While this service could be run on just about any server, we decided that this would be an excellent opportunity to take advantage of Zeit. Zeit lets you spin up small instances of server-side code, similar to containers, without having to deploy and configure an entire server to run it on. Working with Zeit has been a great experience and is looking like it could be a pattern for future FileMaker API integrations.

I write a bit more about the technical side of this middleware (called DayBack Meetings Service) and Zeit further down in this post. You’ll also find downloads and a FileMaker example file that contains all the code you’ll need to add this to your own copy of DayBack Calendar.

Schedule Zoom Meetings from FileMaker

We’ve created buttons to schedule, start, and delete meetings. These actions also listen to DayBack events and reschedule Zoom meetings when you drag a meeting to a new time; they’ll also warn you if your new meeting time conflicts with another Zoom meeting.

Here’s a video of it in action: https://vimeo.com/314570405

 

Read Full Article →

We’re about to launch a new in-app update to DayBack that will include a new look for the sidebar header. This new version is much easier to modify with CSS for folks who want to remove tabs, rename tabs, or switch between icons and text for the tab labels. We also think it makes it more obvious that users can close and open the sidebar.

If you’re already using DayBack and don’t like the new look, you’ll find notes and CSS below that will let you revert to the old style. This preview and the instructions below are for you.

Here’s what the new header will look like. The current version is on the left, and the new version is on the right:

Getting the New Sidebar Look

The new sidebar will be available as an in-app update in the next day or so.

Changing Back to the Old Version

If you’d like to revert to the old style, add the CSS below to DayBack and you should be all set. If you haven’t edited DayBack’s CSS before, you’ll find detailed instructions here: Editing Calendar Themes.

A few more notes for existing users who want to keep the old style:

• If you removed tabs using your own CSS, those tabs should stay gone in the new version as the class names are the same. You likely changed the widths of the remaining tabs to get things to look right, and that’s likely not necessary now: try removing those width changes once you’ve updated to the new sidebar.

• If you made your own styling changes, you can likely recreate those using a combination of the CSS above and the changes you already made. Please let us know if you get stuck.

• The new sidebar puts a blue circle around the filters icon (the magnifying glass) when you have filters applied. We found that users would sometimes forget that they’d applied a filter and then wondered why some events weren’t showing up. This should help.

• DayBack Online is getting a similar sidebar refresh, so if you’re using shares and don’t want to use the new sidebar in your shares, you can use the same CSS above to revert DayBack Online. Notes for changing the online CSS are here.

For most teams, there’s a fine line between not having enough work and having way too much. DayBack Calendar helps us see the difference. Here’s a behind the scenes look at how SeedCode balances developers’ schedules using DayBack’s calendar analytics.

What’s working here

A couple of key ingredients need to be in place before this kind of scheduling works.

Blocking off time to work. That orange dotted line representing our goal only works if our developer has actually blocked out 5 hours a day to work on this stuff. And that means she’s blocked off other time for correspondence and meetings, and that she’s defending the time she’s blocked off to code. Blocking off uninterrupted time to work is critical.

Getting realistic about capacity. Some shops really overestimate how much you can get done in a day: I think 5 productive hours of coding is almost the most someone can average week after week. You may be able to get in the zone for longer days now and then, and it’s certainly easier if you’re just working on one project week after week. But if you work involves any amount of gear switching, that takes a considerable toll on the kind of focus good coding requires.

Calendar Analytics for FileMaker


(Click for a larger version)

Timeboxing (estimating is too hard). A quick look at the calendar above and you’d be forgiven for thinking we’ve estimated all these jobs down to the hour and the spread those estimates across our calendar. Custom software is incredibly hard to estimate accurately. Instead, we’re timeboxing these deliveries: committing to deliver three, five, or ten hours of work, instead of committing to deliver a specific feature set.

Small chunks (estimate accuracy degrades with size). Planning a series of very small estimates and deliveries makes success much more likely. We spoke about this at DevCon in 2017, and it’s proved itself countless times since then: small chunks make a big difference.

These are calendar problems

The scheduling problems we’re grappling with above are not things you can solve on a spreadsheet or solely inside your project tracking system. Both your deliveries and the time you’ve blocked out to work are meaningless outside the context of your other commitments.

That’s why DayBack shows you multiple calendars at the same time, be that records from different tables and even different FileMaker files. Or you can use DayBack Online to show Google and Basecamp calendars alongside your FileMaker records. At SeedCode, the delivery dates you see in the movie above are FileMaker records, but we’re looking at them in a browser in DayBack Online so each developer can also see their personal Google calendars at the same time.

The key is to make delivery promises in the context of your other commitments; that’s the only way to make promises you can keep.

Here’s a beautiful calendar mod by Catherine Kirkland of Digital Fusion. She added new FileMaker layout elements to the right edge and bottom of the calendar. Looks great!

FileMaker Calendar Digital Fusion

DayBack Calendar is a web viewer on the FileMaker layout, so by moving the web viewer around, you can create layout space around it. Folks often put their own navigation elements above or to the left of the calendar, but this is the first one we’ve seen with such an elegant set of controls below the calendar.

I love the white space around the “previous contact” entries: even though the display is very dense, leaving that space around the email icons makes it easy to read.

Huge thanks to Catherine, her client, and the team at Digital Fusion for letting us share this with you. Digital Fusion is doing great work: check it out!

More DayBack Sidebar Mods

Here are few more examples of what other folks have done by adding FileMaker layout elements outside the calendar frame: sidebar examples.

 

Here’s a mod I can’t live without. This tooltip will translate your appointments into three other time zones. Also, it’s easy to customize so you can add more cities if you need to. This is also a great example of how fun it can be to use JavaScript within FileMaker because JS makes these kinds of timezone transformations much easier.

Timezone Tooltips for FileMaker

Transforming Times with Moment.js

DayBack includes the wonderful momentjs and moment-timezone libraries for working with dates and times. That makes a tooltip like this a lot easier. For example, if you want to translate the event’s start time into London’s time zone, you do this:

And if you want to turn that time into text like “in 34 minutes” you can just do this:

Having written tons of FileMaker functions for date and time parsing back in SeedCode Calendar’s early days, I’m in love with these momentjs functions.

Adding little JS tooltips to DayBack is also a great way to get your feet wet with JavaScript, and you’ll find some simple examples here to get you started.

Add this to Timezone Tooltip to Your File

Tooltips were added to DayBack as an in-app update in version 10.42 so make sure you’re up to date. There are two methods for adding a tooltip to DayBack: you can add the commands inline, right into DayBack’s configuration script, or you can export the tooltip’s JavaScript as a file and then point DayBack at that. The inline version is fine when you have just a tiny bit of JavaScript, like this example which shows the event’s title in the tooltip:

That’s great and documented here, along with several examples. However, for longer code chunks, like the one for this timezone tooltip, it’s easier to export a file. This way, you can make changes to the tooltip in your favorite text editor and the paste that right into a FileMaker field without worrying about escaping your quotes as you’d have to if you tried to reference the JS inline in a FileMaker calculation.

The file-export method is the same one DayBack uses for JavaScript custom actions, here’s how to use it:

1. Download the JavaScript for this tooltip: TimezoneTooltipJS.txt.zip

2. Follow steps 1 through 3 here under the heading “Adding JavaScript actions to your file.” Those steps show you how to create a text file for this JS along with a FileMaker script to export it. You’ll add the name of your exported file to the script, so call it “timezoneTooltip.txt.”

3. Enter browse mode, then open TimezoneTooltipJS.txt. Copy the contents and paste that text into your new text field, so it’s ready to export.

4. Now edit the script “Load Source Settings at Startup…” in DayBack and find the comment “Event actions for WebViewer events…” at around line 33. (There is one of these sections per source, but line 33 is where the one for source no. 1 is located.) Edit the next Set Variable to set the $$sc_EventActions variable like this, replacing the “NA”s with the strings shown here:

5. Download this CSS (TimezoneTooltipCSS.txt.zip) and add that to DayBack’s theme. If you haven’t modified DayBack’s CSS before, it’s easy. You’ll find detailed instructions in our docs along with lots of cool examples.

6. That’s it! Run DayBack’s “Upon Opening” script and you should see your new tooltip when you hover over events. To make changes to the tooltip’s JS, paste new text into the text field you created in step 3 and run the “Upon Opening” script again to see your changes take effect.

Customizing the Cities

The JavaScript and CSS you’ll add to your file were created by Ana Petrechenko, SeedCode’s new intern from 42U. She did a great job making this easy to understand and easy to customize. To change or add cities, you’ll modify the section of the tooltip shown below. To add a city, copy the last block (Tokyo), paste it in below Tokyo’s section, and then change the city name and time zone name. The tz() function in each line takes the city’s actual time zone name, and you can find the complete list here.

Big thanks to Ana for this wonderful mod, and to Jason, Tanner, and KC for the coaching!

This is the third and final post in a series on using the Gmail API from FileMaker. Please review the previous articles, if you haven’t already, particularly the first one which covers setting your app up with Google and authentication. There’s also a great article by Brendan McBride from dbservices that covers importing emails from an inbox into FileMaker. This article can be seen as the first in the series as it leads directly to the ones we’ve done here.

Integrating FileMaker and Gmail Part 1 – Sending HTML Emails

Integrating FileMaker and Gmail Part 2 – Sending Attachments

dbservices – FileMaker Gmail Integration

As with the first article, all of these examples use the native Insert From URL script step so there won’t be any plug-ins required, and since the Insert From URL is supported in all aspects of the FileMaker platform, these techniques can be adapted to work on the Server, Go, FileMaker Cloud, and WebDirect. These techniques require FileMaker 16 or higher as they use the advanced cURL options introduced in that version.

Working With Threads

This article will be looking at working with email threads. It will cover querying for responses to a specific thread of emails and maintaining the thread correctly when responding to an email from FileMaker. Here’s a video overview along with a new free example file below:

FileMaker Gmail Integration: Example File

Please download the example file FM2Gmail v1.3 for a working demo. This new version adds the ability to receive incoming messages for existing threads and reply to them. This file replaces v1.2 from the previous article.

FileMaker Gmail Integration Example File

Latest FM2Gmail Example File

Managing Replies

At the end of our last example, we had successfully sent an HTML email with multiple attachments, but what if the correspondent responds to the message? If we want our outgoing message to be associated with a specific FileMaker record, then it’s likely we’ll want all the responses to this email, and all subsequent responses, to be associated with this record as well. Let’s look at this in action. I’ve sent a message from our example file to myself, and now I’m going to respond and add a new inline attachment to my response. Read Full Article →

The latest in-app update to DayBack introduces custom tooltips. These tooltips are completely scriptable. You can customize the content and can style the tooltips (and their content) using your own CSS.

How It Works

Tooltips are triggered by a new calendar action: On Event Hover. This new action can call FileMaker scripts or execute JavaScript. It’s JavaScript you’ll use for the tooltips, and you can call a simple function to show any content you’d like. Here’s the Javascript for the example above:

dbk.tooltip(event.title);

That’s passing the event’s title into the tooltip function. You can also pass in more fields and use HTML to make it more readable. Here’s another field (resource), separated by a line break:

dbk.tooltip(event.title + ‘<br />’ + event.resource);

The tooltip documentation covers all this and provides a more thorough description of this JavaScript, lots of examples, and notes on styling this with CSS.

Going Further

There are a lot of possibilities here when you combine the On Event Hover actions running JavaScript inline with tooltips that will show any HTML you put in there. By adding some logic to your JavaScript you can have different tooltips for different kind of events, or show different tooltips on different views. Tooltips have access to any of the JS libraries in DayBack, including momentjs for formatting dates.

Writing tooltips like this is probably the easiest way to get started with JavaScript in FileMaker. You can show meaningful, user-facing results with just a single line of JS, and we can help. Let us know what you’re working on and we can point you in the right direction.

And if you have interesting use cases for running a FileMaker script on hover, we’d love to hear about that too. Don’t forget, you can also add buttons to DayBack to run your own scripts (FileMaker scripts or JavaScript) and buttons may make more sense for some actions. More here: custom button actions in DayBack.

Get It Now

If you’re already using DayBack, tooltips and the new On Event Hover action are free in-app updates. Just click “Check for Updates” from the upper right corner. If you’re new to in-app updates, you can see them in action here: how in-app updates add new features and preserve your customizations.

If you’re not yet using DayBack, download an unlocked trial, link it to your files, and see if it can make a difference for your team’s schedule…

 Download an Unlocked 30-Day Trial of DayBack  

DOWNLOAD
DayBack Calendar
DayBack's 30-day trial is unlocked so you can customize it and integrate it with your files.
Download DayBack and we'll send you a couple short emails with tips on how to modify it and use some of the coolest features.
Thank you! Please download: DayBack Calendar
Need More?
SeedCode tips & example files in your inbox
Need More?
SeedCode tips & example files in your inbox
Want More?
Be the first to see articles and tips like these
DOWNLOAD
TimeZync
Download TimeZync and we'll send you a couple short emails with tips syncing your FileMaker Go files.
Thank you! Please download: TimeZync
Want More?
Be the first to see articles and tips like these