![]() That’s what hosting the file accomplishes. #Filemaker web direct url updateAnd while our in-app update scripts (alongside tools like Otto) work to minimize the amount of work it takes to get a file back up to date, all these users wished DayBack had just been updated for them. This meant that we’d occasionally hear from folks using a version of DayBack that was over a year old, having missed out on a ton of new features and bug fixes. 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 web direct url proWe’re also big fans on the SMTPit Pro plugin which has a nifty function for converting rich text into HTML on the fly which makes this so much easier.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. #Filemaker web direct url for macThis made things a lot easier for us as we don’t have to deal with complex substitutions in the html source (we’ve only tested this on Windows XP and have since heard this doesn’t work for Mac users but we haven’t had a chance to test on a Mac yet). If you export the contents of the container fields to the user’s temp folder using the Get(TemporaryPath) function the Web Viewer will somehow “discover” the images and show them when displaying the preview of the html email. ![]() This works well for plain text type emails with no inline images as you can simply reference the fields using something like: ![]() ![]() We investigated using a Data URL with a Web Viewer as this would provide a “live” view of the content. We also didn’t want to have to keep exporting files and then opening the exported file as that creates unnecessary clutter for the developer and the customer (though with FM Pro 9 you can use the new Get(TemporaryPath) function to dump files into the user’s temp folder. We wanted to have a way to preview an html email that was being composed in Data Manager so the user could see how it will look to the recipient, just as it does in Outlook etc when composing a new email. Whilst working on our new CRM (Customer Relationship Management) solution – Data Manager – this week we made an interesting discovery with the way the Web Viewer works. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |