FILEMAKER SERVER WEBDIRECT URL PRO
FILEMAKER SERVER WEBDIRECT URL CODE

And even though most updates were installed with a single click, users still didn’t always know to update. We worked very hard to develop scripted, in-app updates for the previous version of DayBack, which was not hosted.

New features and bug fixes get deployed simultaneously and while not all features can be used on every platform, the default becomes that all users get the new features. Even though there are some scripts and schema to maintain on the FileMaker side, by moving most of the logic into the single JavaScript build we can cut down chasing if an issue a customer is facing is based on a versioning issue or not. Having multiple versions of the same product out in production can make things extra difficult for your support team. However, there are other benefits beyond working with multiple platforms that FileMaker developers should consider. If we had to maintain different repositories and servers for the different platforms, that would exponentially more complex with each new calendar source we added–both in terms of architecture and in terms of making decisions on which version gets which features deployed.

FILEMAKER SERVER WEBDIRECT URL CODE

DayBack as a hosted app in Salesforce Lightning Why Host your FileMaker Web Viewer Add-On?įor DayBack Calendar, which works with different platforms both embedded, like the FileMaker web viewer, and in the browser, hosting offers us a single code base and a single host for us to maintain. This is a pattern that we’ve become very familiar with: it’s how DayBack works in Salesforce using Salesforce’s Canvas toolkit.

FILEMAKER SERVER WEBDIRECT URL PRO

DayBack as a hosted app in FileMaker Pro client In addition to being able to maintain a single codebase, we can host that codebase on a single server and have the FileMaker web viewer simply reference the server’s URL. In this article, we’re going to look at taking this idea a step further. One of the important takeaways of writing JavaScript this way is that we can now maintain a single code base for our DayBack Calendar app across all platforms.

In a previous article, we looked at writing JavaScript for FileMaker 19 that matches a typical JS pattern of making asynchronous calls to a data source and handling the results. What are the benefits of building a hosted app for the web viewer in FileMaker? And how can we make this approach work in WebDirect where it looks like FileMaker only supports data URLs?

Filemaker server webdirect url