Show Available Slots that Match Multiple Criteria Schedulers often look for gaps in their schedules to find the open resources for each opportunity. But sometimes, gaps don’t tell the whole story. You may have invisible criteria like skill-matching, cleaning requirements, or multiple resources to schedule at once. Or you may be on the phone with an opportunity and must suggest available times as quickly as possible. In these cases, DayBack can suggest the best slots that match all of your requirements. Scheduling Criteria Are Often Invisible In the movie above, schedulers can see openings for the two technicians, but they can’t easily see if the required rooms and equipment are free at the same time. While DayBack can show different types of resources simultaneously, as the number of criteria increases, it can be hard for schedulers to see everything at once and still make good decisions. Our customers often have rules that constrain when an otherwise open slot can be scheduled. Here are some of the invisible criteria we’ve built out for customers: Because DayBack is highly scriptable, it can scrub open slots against a variety of criteria to render just the slots that fit all your requirements. When multiple slots match, DayBack can even rank them so you can present the most ideal slots to your clients first. You Have to *See* Slots in Context to Make the Best Decisions Many scheduling apps present possible appointments as a list of dates and times. Without showing more information about each slot, schedulers can book days too tightly, always suggest the same providers first, or create huge gaps in some provider’s schedules. Ranking slots can help, but we’ve found that highlighting ideal slots alongside existing appointments gives schedulers the information they need to make the best decisions. We’ve seen schedulers quickly offer to split appointments or to slightly change services when they see available slots in the context of other appointments, trainings, vacations, and breaks. Getting Started We customize the recommendation of slots for each deployment as part of DayBack’s implementation packages. Please get in touch if you think DayBack could make a big impact on your team.
3 Comments
John suggested that I include some more details about our FileMaker Pro/Go Signature Capture Method. I’ll post this on our blog too.
It runs completely within FileMaker. There are no plugins needed and it doesn’t communicate with server. It works like this:
– You load the signature capture layout. It has a webviewer that displays the interface so the user can use their finger to sign the screen.
– When the record loads, an OnTimer starts to watch the URL of the webviewer for a code indicating that the URL has changed.
– The user signs the page, enters their name, and enters any other fields that you might add. The Name field is optional.
– The user submits the web form that’s in the webviewer. It uses javascript to change the webviewer URL to a Thank You message with an html comment containing a text flag and the fields including the text representation of the signature as parameters.
– The OnTimer script sees that the URL now contains the text flag. It collects the parameters and sets the fields in the database.
– At this point the signature is captured.
– Viewing the signature is simple. You just need a webviewer to display the text representation of the signature.
It’s really amazing that all this can be done with out any add ons. I think the biggest thing that I’ve learned is that you can have an html form submit its values to the webviewer URL. That makes it easy to communicate back to FileMaker, if an OnTimer script is running to capture the values.
Yesterday, FileMaker Go was updated to include FMP7Script URLs that can contain parameters. We’ll update the signature capture soon to use the new URL scheme. If it works like I think it should, the OnTimer Script might not be needed anymore. We might update the interface a bit too.
Feel free to download the demo. It’s unlocked so you can examine how it works.
http://bit.ly/FileMakerSignatureCapture
Also check out Andy Frazier’s demo. His example file takes ours one step further so you can convert the text representation of the signature into an image file that can be stored in a container.
http://www.reliablesoftworks.info/GO_SignMe.zip
Take Hal’s recipe, add a scoop of Server, a splash of ScriptMaster, and you can store the captured signatures in container fields.
http://www.reliablesoftworks.info/GO_SignMe.zip
Here’s something similar, with open source.
http://campsoftware.com/blog/signature-capture-filemaker-implementation/