Due to COVID-19, we recently had to invent a way to sign forms on-site without sharing devices. Part of the conversation went like this:
He thought for a minute and replied, “Here’s what we’ll do. We’ll make a way for a user to sign a form without ever touching the iPad. How about we create a record just for signatures? We can send a link out to the client that will open a WebDirect interface. It would present them their signature record on their own device, and boom! Touch-free signatures.”
“Brilliant!” I said happily. “Let’s go! I’ll grab some pizza.”
Working together today during our weekly dev meeting, the Portage Bay team ran across a slightly obscure requirements issue that took little bit of time for us to resolve, though once resolved the issue was pretty simple. Maybe this blog post will help someone catch the same problem a little more quickly.
This is a quick tip about how PSOS can vastly improve performance of the ExecuteSQL script step. Recently we received feedback on one of our solutions that uses Execute SQL to build a virtual list used in a picker window. The feedback had to do with the slow performance of loading the picker window. The user complained of the window sometimes taking up to 30 minutes to load. Obviously this design was not ideal!
With the release of FileMaker 16, we have seen a great number of new and improved script steps. FileMaker 16 extended the capability of the Save as PDF script step, now allowing it to work partially with WebDirect, FileMaker Go, and Server, however there are a few things of note.
