The Support Group Blog

Let’s Play Cards!

The Card Window was introduced in FileMaker 16. We learned some pretty cool development techniques and use cases for Card Windows during a FileMaker Developer Conference 2018 session.

TRANSACTIONS

Card Windows can be a great tool for transactional programming. You can easily arrange for transactional events to either pass or fail, meaning all edits/adds/deletes that happen during the transaction are either committed or not. Cards can be leveraged to guide the user through a process, storing the data via global fields, variables or JSON arrays along the way. Ultimately, the data will only be committed if the user completes all of the steps. Incidentally, you can also use slide panels to create this user experience. 

We've created a cheat sheet to help you directly access the files in FileMaker Cloud. There are a few tutorials on the web, but none of them quite work anymore so we thought it would be useful for us to share one that does.

There are times when you may need to get to something in your FileMaker Cloud instance’s folder structure. Perhaps you need to access an old log file or even a file within the Documents folder - whatever the reason, you’ll know it when you need it. Please be aware that it's not a good idea to mess around with any of the files in the instance unless you have a backup and know what you’re doing. Having said that, here are three things you'll need to get started.  

It amazes me how easily we adapt and respond to visuals. Not only is functionality important to software development, but design is also pretty important. Because time is a limited commodity, usability and intuition are important factors when encouraging users to adopt a new system. And generally, the visual elements of the system determine how quickly users are able to learn a new application. Design includes many different aspects – color, layout, fonts, sizes, etc. You have to be strategic with your design elements, including those micro-images we call icons. Those seemingly small symbols ultimately make a big impact on user navigability and comprehension.

Who else but Google has created a style guide for all of their applications and shared it on the interwebs for everyone to use. Material Design is basically a design language that Google created to unify digital interfaces and experiences. They offer lots of good UI/UX design ideas in this document and a bunch of free resources. Who doesn’t like free stuff? One of those free things is a whole set of icons, nice ones. You can browse through them here: https://material.io/icons/.

One of the things our clients often request is for us to set up their custom application so that it is mandatory for users to fill in certain fields. You all know what this looks like, right? You go to a website to sign up for a service and next to the places you have to put your email and password, you see a little red asterisk. And then at the bottom or top, or somewhere on the page, it will be explained that these fields are required. Now you can specify required fields in FileMaker Pro quickly and easily.

Data is powerful! It's generally the backbone of most strategic business decisions to improve products and operations. But the data that businesses collect can be mutually beneficial to consumers as well. Our trackable behaviors and habits make innovation and efficiency possible by allowing computers to process and interpret data in such a way that it can actually help to fulfill a task or goal . This is known as artificial intelligence (AI) and we'll continue to hear a lot about it going into 2018 in terms of research, development and controversy, so we'll save a serious discussion about that and custom applications for another time. For now, we just want to have a little fun with AI.

Design is an important factor in the development process and it warrants extra special attention. Yes, an application needs to work, but it also has to appeal to its users. What good will the application do if no one will use it?

We rely on indicators to let us know that a process is running. We can hear our engines running or see the timer ticking down on the microwave – all positive indications that something is working. Have you ever been on hold with no hold music or regular automated updates? It can be frustrating because you don't know if you're still in the queue or wasting your time. So it's good, virtually expected, to include a progress bar or an alert within a process in order to maintain engagement.

We’ve been writing FileMaker scripts for over 25 years now (ever since FileMaker Pro 2.0, when the ScriptMaker first appeared) and we’ve developed our own set of best practices in terms of managing them here at The Support Group. Every FileMaker developer has his or her own set of methods, preferences, styles, etc., but we all agree that writing and maintaining scripts properly can save you a lot of time and frustration in the long run. Whether you're an experienced FileMaker developer or new to development, you should find these seven scripting tips useful.

Sometimes, when writing a FileMaker script to do a find, sort, or export, doing it manually first can save you LOTS of time.

I was just tasked with creating a script to export all the fields on a layout.  The layout, however, is non-trivial and contains fields from multiple different tables, and the relationship graph I inherited is very complicated and nearly impossible to decipher.  It would have taken me HOURS to identify the table occurrence and field name of every field on this layout and then set up the export in a script.

Over the years I have noticed that some beginner and intermediate level developers are not aware of the possible uses of extended privileges, other than as a means of controlling methods of sharing (such as through standard FileMaker Pro to Server networking, Instant Web Publishing, PHP, etc…).  Extended privileges are probably one of the most underused features in FileMaker and at the same time incredibly simple and powerful with regards to enforcing security and access control.  I have seen people write very complex scripts that attempt to manage or limit access to specific areas of a system, creating elaborate, complex security access levels or hard coding some of this security functionality within the data structure when they could have used custom extended privileges to do the same in a cleaner and most efficient manner.