 As usual, we had a high participation rate with a wide range of entries. What we did is we created a pool of submissions from this session, and we combined them with previous requests, grouped them into high-level categories and tasks, and then we chose an idea from the most popular one to demo. But keep in mind, FileMaker will continue holding idea to iPad events in the future. If your idea wasn't selected at this time, just keep submitting them for use as a potential demo in the future. While your use case may differ from the one that we're going to demonstrate today, we'll still be covering some common techniques and features that you can apply to your solution. I also wanted to point out that for today's session, we'll be using some advanced beginner techniques and methodology, but don't worry, you'll receive a recording of this webinar later on to follow at your own pace. Now, your requests are really similar to the ones that you're seeing on your screen right now, but based on the popularity of your submissions, the winning entry is a job ticketing solution. Now, we've been getting a lot of requests for this idea, and there's a lot of avenues we could take for building out a workflow. There's most likely going to be a contact management piece, job tracking, notification functionality, maybe a scheduling feature, and given our timeframe, we'll cover some of that today, but before we start building this out, let's go ahead and assume that we all work for the same company. We're IT technician to spend the day out in the field providing maintenance repairs and services. Now, let's say that our boss, let's go ahead and choose someone from our attendees list, and okay, we'll say that Perry is our boss. Now, Perry knows that every day we're spending too many wasted cycles on inefficient processes, managing our work orders, or ad hoc processes like double entering information we collect in the field and bringing it back into the office. Now, compounding things are these brand new iPad devices we purchased, but just haven't found a good way to incorporate them into our field work. Overall, we're getting results, but Perry knows that we're costing our company time and money, and that's when I get called into his office. Perry knows there has to be a more efficient, more effective way for us to work and communicate in the field, and he's tasked me with the following. Perry wants a solution that we can easily customize to line with our unique workflow out in the field. It's got to be a solution that we can access whenever we want the data from wherever we are, and the solution should also make it easier on our customers too. Now, it's late on the day on Friday, and it's really just not a good time for me to start this project. I have to pick up my kid from school in about an hour, but that's when I remember FileMaker. And the first thing I want to do is make sure I can create a solution that matches how we want to conduct our business. So I'm going to create a brand new database, create a layout designed for the iOS, and then I'm going to use features like fields, relationships, popovers, and portals to optimize our workflow. So let's talk about how we do that. Now, there's a lot of different ways to get started creating a database in FileMaker, but what I'm going to do is I'm just going to launch my FileMaker Pro Advance and go up to the File menu and select New Database. So let's go ahead and give this database a name. I'll just call this Job Ticket, and we'll save it to the desktop. Now, right off the bat, we're taken to what FileMaker calls layout mode, and this is where we can add objects and fields and change the formatting, however we want the interface to look. But I'm going to actually start with a brand new layout. So I'm going to go up to the Layouts menu and select New Layout Report, and we get this fantastic new layout report wizard in FileMaker 13. Okay, so let's give this layout a name. I'm going to call this Job Tickets, because that's what we're going to be tracking here. And this is going to be built out for a touch device. I'm going to select iPad or iPad Mini. Certainly, we could choose a computer dimensions or envelopes or reporting or labels. But we're going to stick with the iPad Mini, and we're going to select Form. Again, we're going to get this out into the field. And then finally, I get to choose, do you want to build this out in a Portrait mode or a Landscape mode? So I'm going to choose Landscape for this layout and click Finish. So what happened? Well, FileMaker gave us a layout automatically designed to the dimensions of the iOS device in Landscape mode, and it also gave us a touch theme. Now, there's 61 themes in FileMaker 13, fully customizable. You can change them however you want. And you'll notice that some of these are marked as touch. So you'll look at the difference, Enlightened to Enlightened touch, Sophisticated to Sophisticated touch. Those touch themes, they have the larger fonts, larger objects like you'd expect on an iOS device. I'm going to go ahead and just stick with the Enlightened touch theme and click OK. So we have our layout, a really great blank slate to build our custom solution. Let's start personalizing it. I'm going to add some literal text to my layout. And we'll give this the title Job Ticket. And let's go ahead and make that font a little bit larger. Right now it's an 18, 36 font. That sounds good. Let's put that over here. And we also have a company logo. So what I'm going to do is I want this to appear on every single record, every single ticket. So I'm just going to take that image and drag and drop it right onto the layout. That easy, okay? And this is going to ensure that this picture is now an object associated with the layout. So it's going to appear on every single record. Now we need to get information onto our layouts. And how do we show information? Well, in FileMaker, information is stored in what we call Fields. And new to FileMaker 13 is this fantastic tool called the Field Picker. I can access it right here in the formatting toolbar. Okay, and give us one second here. It's like FileMaker's thinking. Let's go ahead and close that and bring up the ticket database again. All right, let's go back to layout mode. And we have this Field Picker object again, brand new to FileMaker 13. And oh, it looks like our text didn't save, or our job ticket title didn't save. That's okay. That's because we didn't save our changes to this layout yet. No problem. So I'm just going to go ahead and again, make this font just a little bit larger. Or actually, you know, we need to create our new layout. Put this on touch device, say job ticket iOS, touch device, iPad mini form, and again, put it in a landscape mode. There we go. Dimensions, nice. Set to the iOS device and landscape. And again, I'll add the job ticket title here. Okay, we'll make this a bit larger, 36 font. And again, if I want to image directly onto my layout, just a drag and drop. Okay, this image is never going to change from record to record. So we're just going to make it part of the layout that simple. Okay, so back to the Field Picker. This is a great tool that allows me to add database schema directly from layout mode. It's now more efficient than ever. It's quicker than ever to start designing and building your layouts in FileMaker 13. So what kind of objects and what kind of things do I want to track in this ticket solution? First thing I want to do is make sure that each ticket is unique, right? So I'm going to go ahead and give this a unique ID field. I want to call this ticket ID. I just have the two underscores before the primary key just to make sure that when I sort the fields, they'll always sort to the top. You don't have to have the double underscores. It's just like a best practice for formatting or just one way that you can format your fields. Okay, so I'm going to change this type from text to number. Okay, and I'm going to go ahead and control click or right click if you're on Windows and select field options. Alright, because I want to make sure that every time a record is created, okay, I want to insert a serial number. Okay, and that makes, that's going to ensure that every ticket is unique. And this can be an alphanumeric number if you want to change that as well, if that's how you want to set up your ticketing. But I'm just going to go ahead and stick with this default numeric style. So I'm going to go ahead and click OK. Okay, so what else do we want to track? Well, we probably want to track the issue. Let's go ahead and change that back to text. We want to track the request date. We'll change that file format to date. And I'm going to go back to the field options, again, control click or right click. And I want to make sure that when a record is created, we're automatically going to put the creation date in that field again cutting down on the amount of typing my users have to do. Okay, we probably want to track who the ticket is assigned to, which one of our employees is assigned to. So I'm going to change that back to text. And then the status, is it going to be open? Is it completed? Are we still waiting for a customer? And then speaking of the customer, we want to track a lot of the customer information as well. So we'll probably have customer name, customer address, customer city, customer state, customer zip, getting really easy to add fields in FileMaker 13. And then we probably want to add a site address, and a site city, a site, state, and a site zip as well. Because the person who's going to be our contact, you know, they may not always have the same address as the site that we'll be visiting for maintenance. Okay, so how do we get our information onto the layouts? Well, it's kind of like what we've already been doing, just drag and drop. So if I want to, I can just select a field and I can use the shift key or I can use like the command key, for example, and grab a bunch of fields and just drag them directly onto the layout just like that, that easy. I don't notice that this kind of takes up a lot of space. Again, we have that larger font, larger objects for the iOS. And we have a lot of information to track here with the customer information, the site information. And really the main point of this layout is to really focus on the tasks that are going to be associated with each ticket or the status updates associated with each ticket. That's a lot of information, a lot of workflow to place onto this layout. We have some real estate here that we can work with, but it may be a tight fit. So there's a few different approaches you can take that you can really optimize the space on your layout. One way is by using this tab control feature. And tab controls, it's exactly what it sounds like where you're putting tabs onto a layout or it's kind of like you're stacking folders on a layout as well. So we had to have ticket info, customer info, site info. I do a full justification here and click OK. So we can place objects and fields on each tab and they're only viewable when you click on the appropriate tab. Again, a really nice way to work with the space in your layout. So that's one way to approach it. I'm actually going to use a new feature in FondMaker 13 called popover buttons. And if you're on the web and if you have an iOS device, you know what popover buttons are, you just click on a button and you get a brand new window that appears. This is another really new, another great modern way to maximize your space on an iOS device especially. So what I can do is just start placing some fields in this area, this popover area, but the color scheme is pretty close to the popover button and the background. So the first thing I want to do is let's go ahead and make that just a little bit darker. So in the inspector appearance tab, there's a gradient on this. So let's just make this a little bit darker again just so it stands out a little bit more. And we'll stick with the gradient. Certainly you can make it a solid color if you want. Now I'm going to go ahead and double click this window and let's give this a title. This is going to be ticket info. All right. Now with ticket info, we're going to break our fields up into different categories. So I'm probably going to grab the ID, the request date, who assigned to and the status. So let's go ahead and bring these fields over onto the layout. All right. And then I'm going to go ahead and realign these fields. And you'll notice these blue lines that appear. That's what we call dynamic guides. They just help you quickly align your objects and fields. So a lot of different approaches that we could take for formatting this particular window. What I'm going to do is I'm just going to go ahead and give these labels a fill. Okay. And we'll just do some quick formatting on these. So appearance fill will do a solid color. So it's white. And I'm going to go ahead and start making these the same size. Okay, I'm going to bring this out a bit. Make these the same size as the fields that are associated with. All right. Again, using the dynamic guides to quickly align and help out. All right. And our last label, the status. Okay. All right. Now I'm going to go ahead and do some formatting with the actual fields themselves. They have a corner radius or they're a little bit rounded. I'm going to make them square and turn that corner radius off. And then I'm also going to remove some of the lines around the fields. I'm just going to keep the left line up to kind of give these fields a bar. So let's go ahead and connect these a bit. And, you know, I'm going to add some right padding on these a little bit there as well to give them some space. Okay. So we have a lot of real estate here in this window. We can probably make this a little bit smaller. I don't want to block everything in my iOS device. The layouts are already going to be a little bit smaller that we're working with. All right. So let's move this up a little bit more and then we should be good on that. Okay. Now what can we do with these fields themselves? These are going to auto enter the ticket and the request date for the assigned. Well, let's go ahead and let's change this to a pop-up menu. Okay. And I'm going to go ahead and specify a value list for the pop-up menu and we'll call this employees. All right. Again, just cutting it down on the amounts of typing that my users have to do. Now a best practice would involve having a table strictly for my employees and then using a value list comprised of fields from that table. So I could grab, you know, the IDs of the employees and the names of those employees without having to hard code the values because if people leave, I have to go back to that hard coded list and update that every time. So that's the best practice. But for this demo, we're just going to go ahead and hard code some of these names. Just this will suffice just again for giving the time constraint. So we'll just add a few names here. Okay. All right. So that's our employees list of field technicians. All right. And click okay. And let's do the same thing with the status. Again, we don't want to have to type in every time what the status is of the ticket. So we're going to change that to a pop-up menu as well. All right. And we'll call this status. And for this value list, it's okay if we hard code these values. I'm going to say open, completed, and we'll say waiting for customer. And click okay. All right. Really good start with our pop-over button here. All right. Let's make this a little bit larger. Now, what should we do with the button itself? Certainly, we could just have a text label that just says click here, but we want to make a little bit more associated with what is in the window. I'm going to give a little bit more information on the layout. Now, I could certainly duplicate some of these fields and place it on the button. But what's going to happen is every time I click in that area of the field, it's going to allow a user to enter that field and not trigger that button. And I don't want that to happen. I really just want the values to appear on the button. And there's a great way to do that by using merge fields. So I'm going to go to the insert menu and select merge field. And merge fields, again, this allow you to strictly grab the values in these fields. And they're non-edible editable objects. So this is great for, again, placing text over a button. Maybe you have a letter layout or a receipt layout, for example. And you don't want people to edit that data. You just want that information to be pulled and shown and, again, non-editable. So this is a great way to show that information on your layout. So we'll have the ticket ID here. And let's add some literal text just to help point out what that value is. And then we're going to add one more merge field. And we'll say status. So we can get a quick view of this ticket. Okay. What's the ID? Is it completed? Is it open? A great way for our text to kind of manage their tickets under their name. So this literal text here, status. Okay. So we have a nice button object. But I want to make it even more, I don't really want it to stand out even more that this button is editable, that you can click on this area and edit some text, refine further information. Now, before I do that, I'm actually going to step out of this solution. Okay. And I'm going to talk about the FileMaker starter solutions. At the very beginning of our presentation, we talked about different ways you can get started working with FileMaker. And we created a brand new database from scratch. But there are also 16 free starter solution templates. They're fully customizable. They're generic enough to match really any company. So this is a great way to kind of get a head start on your ideas, get some of that development out of the way. And again, you can fully customize them to match your workflow. I also like to use these as repositories and learning tools as well. I'm going to go ahead and open up a invoice solution that I'm currently hosting. That's a starter solution. This is not modified. It just has some dummy data in there. Okay. And what I'm going to do is I'm just going to go ahead and grab this little pencil icon, kind of universal icon for editing. I'm just going to close that out. And I'm going to bring that back into my layout. So I'm going to just go ahead and paste that. All right. Just another great way to use the starter solutions. I'm going to do one thing with this icon. It is anchored to stretch to the right. I'm just going to go ahead and change that so it doesn't move across the layout when I resize this. Okay. So a lot of good changes with this button. Let's go ahead and take a look at what we've done. So I'm going to go ahead and exit this layout. Okay. And that brings us into browse mode. And browse mode in FileMaker is where you can edit and interact your data. So I'm going to go ahead and click on New Record and right off the bat, the merge field grabs the value in the ticket ID. Remember we set the ticket ID to be an auto enter number. So I'm going to click on that button. You see that we have the auto generated ticket ID, auto generated request date. We have a popover. We can say this is assigned to Eric Frazier and then status. This is an open ticket. This is a really great workflow for someone in the office who needs to create a ticket and so we can have a nice view for the text to see. Okay. And there we go. That's simple. So what I'm going to do is I'm going to go ahead and step out of this file for now. Okay. And I'm going to go ahead and open up I'm going to go ahead and open up this job ticket to file that I have. Okay. And actually, that's all right. Let me go to this file here on ticket to all right. So a lot of the same workflow just again in interest of time, I just went ahead and created the initial buttons and these buttons have information for the customer fields and the button on the bottom has information for the site location. Okay. And then what I did as well is I just create I just dragged the issue field over onto the layout and I just made that a 24 font. Okay. So again, just a lot of the techniques that we've already been discussing just a lot of the dragging and dropping. All right. So we have some space left open here and again, we talked about wanting to show the different types of statuses and different type of tasks associated with each ticket. Again, different approaches that you can go with for your database. One thing I could do is create a text field and you know, just start having that it's entering a lot of information into that one text field. It could be a good approach, but let's say that this ticket lasts weeks and months and a lot of information going to be stored in that one field. It's not really going to be the best way to organize and manage the different things that we're doing for each ticket, having all the information stored in one field. A better approach and the approach that we're going to take is kind of have a repository for all of those tasks. And we're going to create a table where, you know, each record and table is going to be a task or status update associated with each ticket. So let's talk about how we would do that. I'm going to go to file, manage, database, and there's a lot of different ways you can get to this window, but this window is where you can add additional parts of your database schema. So you can add more tables, you can add fields to those tables, and then really the power of FileMaker, you can create relationships between those tables, and we'll see that in a second. But first thing I'm going to do is I'm going to create a brand new table, and we're going to call this services performed, okay, and click create, all right. So again, this is going to be kind of like a repository. And certainly you could create a table for billable objects and a table for, you know, like status updates, but we're going to kind of combine them all in one table for this demo. So let's start adding some fields for that services performed table. Again, we want to make sure that each record is uniquely represented, right? So I'm going to go ahead and change that type from text to number and click create, and then we'll have the options button. And again, every time a record is created, give us a unique number. So we'll do serial number and click okay, all right. And then I'm going to go ahead and create a brand new field. We need a key that will allow us to create a relationship to the, to the tickets table. So we'll call this ticket ID and create, all right. Now, what are the type of things we want to track in the services table? Well, I'm going to go ahead and add another date field. And we're going to change that type to timestamp. Anytime we perform a task or, you know, if we create an order, if we send a receipt, we want to make sure that not only we have the date, we have the timestamp as well. So I'm going to go ahead and create that. And we probably want to make sure that this has an auto enter value as well. So every time a record is created, we'll auto enter for that. Then we'll have a description of the service performed, we'll change that back to text. Okay. And as we're doing a lot of billing, we probably want to capture the rate, the subtotals, and maybe, you know, the quantity, like the hours performed or the quantity of peripherals purchased and things like that. So we'll add a quantity field, and we'll change that to a number and create that. We'll add a rate field, and that will be a number as well. And then we'll add a subtotal field. Okay. And subtotal, this is going to be a calculation. All right. We'll click create. And what you're looking at right now is FondMaker's calculation dialog window. It's everywhere in the software. And all you're really looking at are just the fields associated with the tables, operators, and FondMaker's preset calculation functions, which help cut down on the amount of coding that you have to do. And all you really do in this window is combine these elements with some literal text to form different expressions that produce different results. In this scenario, if we want a subtotal of the service, all we really need is just the quantity times the rate. Okay. So we'll click okay. And then we'll click okay again. All right. So we'll just go back into the file-managed database. All right. So we created our fields. And now let's go to the relationships tab. Let's create a relationship between these two tables. And how do you do that? Well, first thing, before you create a relationship, you always want to look for fields that are going to have common values. And in this scenario, it's going to be the values in the ticket IDs. So all the services performed that have the ticket ID one, for example, are going to be associated with the first ticket. All the services that have a ticket ID of two, they're going to be associated with the second ticket and so on and so forth. So if I want to create a relationship, again, we're just dragging and dropping. I'm going to take that ticket ID field and drag and drop over to the ticket ID field in the services table. And just like that, we have a relationship in FileMaker. So when the value in the ticket ID field equals the value in the ticket ID field, allow us to share those records. So let's go ahead and click okay. Now, how do I get those records to show up in this open space here? Well, we have this tool specifically for that called a portal. And a portal is just a view into another related table's records, okay, a portal into another table. So FileMaker is asking us, where do you want to show related records from? Well, we just created a relationship with the services performed, okay. And I'm going to show a vertical scroll bar and a number of rows we'll say five, and I'll click okay. Now, we probably want to add the date, description, quantity, and rate, and subtotal. But I'm going to cancel this because I'm going to show you that in this field picker tool, you can also grab fields that are not in the current table. Again, really quick and easy way to build and design your layouts in FileMaker 13. All right, so let's just go ahead and make these a little bit higher. There we go. All right, the time stamp, we can make it a little bit smaller. And I'll bring the description over. Okay. And then we'll add the quantity, rate, and subtotal. All right, just a little formatting on our layout. Okay, we'll add those there. All right. And we'll make this just a little bit larger. Okay, and we have some real estate at the top. So let's just bring this up a bit. Okay, there's the dynamic guides. Okay, there we go. Again, using the dynamic guides to help me out. Let's format these a little bit more. Okay, so I'm going to highlight all of these fields. And just to make it a little bit look a little bit more cleaner in my portal, let's bring up the inspector and go to the appearance tab. Let's make sure that the alignment is in the middle and the text is in the middle of the field as well. And then finally, these fields have a solid fill and a line. What I'm going to do is, that's the default style of these fields. I'm just going to choose a minimal edit box. That way, the fill and the lines are removed, and any formatting is removed, and it kind of adopts the background of the portal. Okay. Changing that style also changed my alignment, so we'll just quickly change that back. And then the last piece of that is just quickly aligning the labels. Okay, again, dynamic guides help us out tremendously here. All right. Now for this rate and subtotal, right now, they're just kind of formatted as a standard number, but we can actually change those to a currency. All right. So from the data tab, we change currency and then use the thousand separator. All right. Now let's go ahead and take a look at our changes. Right now, we have the portal listed here. The final piece is back in the file managed database window. Okay. Now that we have the portal set up, let's go back into the relationship. All right. And we want to specify to FileMaker, hey, allow us to create records in that services table based off of that relationship. Okay. And this is going to allow us to add records to the services table directly in the portal. Okay. So we'll say label hours. Okay. And we have the time stamp automatically created. We'll say the quantity. We worked five hours on this home network. The rate for that is 40 bucks. And FileMaker's calculation automatically pulls that in for us. Okay. Let's say we have ordered a new router. All right. And there's no rate for that. Okay. We're not, there's no cost associated that for now. And then we have installed a new software that was needed and that he had to purchase. And this is just one. And it was a fairly cheap purchase. It was just 20 bucks. Okay. And again, this, we're adding a task that will perform billable things. We're adding status updates. Again, you could break this up into different tables and different portals if you want. But we're just combining that into one workflow on this layout. Okay. Now, wouldn't it be great if we could have FileMaker, not just total, the subtotal, but total the ticket overall? Well, in order to do that, let's go back to FileManageDataBased. And we're going to jump to that services table. Okay. I'm going to create a brand new field called Total. I'm just putting a s underscore to label that this is actually going to be a summary field. Okay. It just helps me format when I, when I sort fields, you know, it's going to group like type fields together. Okay. So we're going to create this summary field and we have a few different options, but I'm just going to choose the first option. I'm going to say FileMaker, give me the total of the values in the subtotal fields. I'm going to click okay, and then click okay. Let's go back to layout modes. We're going to make a change that layout. All right. And I'm going to go ahead and use the field picker. Services performed. All right. We'll bring the subtotal onto our layout. Just like that. And we'll change the label to total. And we'll change this field to have some currency formatting as well. All right. Let's take a look at our changes. I'm going to exit the layout back into browse mode. And just like that, FileMaker has given us a complete total of the ticket up to this point. Okay. So what did we do? Well, we created a brand new database, a new layout, and then we used relationships, portals and popovers to create a custom interface designed to meet our needs. Now we're already starting to solve some of the problems our ad hoc processes have created for us, allowing us to focus on more effective activities. So I'm feeling pretty confident that I can prove to Perry that its first criterion is met. And it looks like we should be out of the office well under the hour, but we still have a few more features and functionality to add. I need to make sure that we can access the solution out in the field. So I'm going to go ahead and host the solution, then access it with FileMaker Go. And let's talk about how we do that. So I'm going to go ahead and close that out. All right. And you've already kind of seen me working with FileMaker Server. And what FileMaker Server is, it's strictly a hosting application, runs the services in the background of your machine. And it essentially acts as a way for you to manage your own cloud. Okay. So let's open up this solution. How do you get a solution up into FileMaker Server? Well, there's this great icon called the share icon. And you're just going to select upload to FileMaker Server. Okay. And click OK. And I'm going to select my computer. Okay, again, FileMaker Server is running in the background of my computer. I'm just entering the credentials of FileMaker Server right now and click Next. Okay. And we're going to go ahead and upload that and upload that database with FileMaker Pro. Okay. Now, this is the solution that we are originally working with. We're just working with JobTicket2. You can see if we go to File, Open Remote. If I ping that Server Machine, we'll see the JobTicket2 database we were also working with. So it's just a really quick way to access your files remotely. Okay. Now, how do we get this over onto an iOS device? Well, in order to show you, I'm going to go ahead and launch my reflector app. Okay. And this is going to allow me to, it's going to allow me to display the iPad I have in my hands right now over onto the screen. So just give me one second to do that. Okay. And there's the iPad. You'll see at the bottom you have FileMaker Go icon. Again, that's a free download off the App Store. But I'm going to go ahead and tap on FileMaker Go. All right. And this is FileMaker Go 13. You have a few different icons in the upper left corner. Recent shows the recent server machines and databases that I've been working with. If I tap on the device icon, this shows the recent, or this shows the files and documents I have stored locally on this device. So this is a really great way to work with your solution offline in an area with a bad network connection or no network connection at all. And then when you have a network connection, you can push those changes up to the hosted server. And then if I tap on the host icon, this allows me to access external servers or it allows me to access servers that are on my local area network. And you can see we have quite a few applications hosting FileMaker databases right now. I'm just going to go ahead and scroll through that list. And you'll see right about the top Ryan Minooks FileMaker server. So I'm going to go ahead and tap on that. Let's give one second for that to populate. And we scroll through that list. There's that JobTicket2 database we were working with. I'm going to go ahead and tap on that. Okay. And there you go. The FileMaker solution. As close as possible as you can get. And if we tap on some of the functionality like that ticket, all right. The popovers work just like expected. And we can interact with the portal object as well. Now let's take that a step further. Let's say that we're working with Doug. Okay. And he wants to update his email address. Okay. So the i2i.com domain email is just not the best way to reach him. So what I'm going to do is I'm going to change that to just email.com. Okay. Now I'm going to go ahead and tap those and commit those changes. All right. Now let's take a look at the FileMaker Pro side. Okay. You look at the email. It automatically shows the change. Again everywhere, anyone who's accessing this, Mac, Windows, iOS, even a web browser, everybody's going to see that change from Doug's email. Now let's take that a step further. Let's say that I'm working with Doug. Okay. And I'm in the middle of changing his email. Okay. We're in the middle of changing it to email.com. Now at the same time, we have an admin in the office. Okay. And the admin is the one who takes the tickets and creates the tickets. Right. And the admin notices that Doug's contact number is also not up to date. Now watch what happens when the admin tries to make a change at the same time. We're trying to make a change to this record out in the field. Okay. So I'm going to click on the phone field from the desktop and I'm going to click on Delete. We get this message pretty much saying, hey, you cannot modify this record because someone else is already modifying this record. We call that automatic record locking. It's right out the box, nothing to configure. So what does that mean? Well, that means that you can have hundreds, thousands of people looking at your records, but only one person can modify a record at a time. So it guarantees that when you're working with FileMaker, you're always going to be working with one version of the truth. So what did we do? And really just two things. It was just hosting the solution and connecting to it with FileMaker Go. And really, that's just a minute without me talking. Right. So we're making great progress, but I just need to make sure I can figure out a way to make sure our customers directly benefit from this tool as well. I mean, wouldn't it be great if we could just send an email or a receipt while we're standing right next to them? So I'm going to create a script that saves our records as PDFs and then emails a copy of that to the customer. So let's talk about how we do that. I'm going to go ahead and hide this reflector. Okay. Anytime we're making database schema changes, it always happens in the FileMaker Pro side. I'm actually going to close this JobTicket2 as well. I'm going to bring up a third version of that file. Okay. So let's go ahead and open up the JobTicket3. You might have seen that as I've been going through this window. Okay. Now, what I've done in JobTicket3, all I've done is created a brand new layout using the skills that we've already been doing. Okay. And this again, just in the interest of time. So if I go into layout mode, I'm just using a portal, just like we created the totals there. And then I'm using merge fields to populate some information. These fields right here are merge fields as well. I just haven't tightly bunched because estate, for example, are going to take up two characters. So I have some of these bunched together. Okay. And again, this is a great use case for merge fields. This is a layout that I don't want anyone really touching or have the ability to kind of edit the information. I just want the values to appear on this layout meant for printing, right? Or being saved as a PDF. Okay. So a lot of the same skills that we use, this is still pulling from the tickets table. I'm still using the relationship to the services table. This is just another layout, just another view into those tables into that relationship. Okay. I also designed this layout with page margins in mind. So I use view page margins. That way when we save it as a PDF, all of this information is going to be stuck within that page or visible within that page. Okay. So how do we send this out to customers? All right. Well, let me go ahead and go to the scripts menu because we're going to need to create a script. Actually, let's go to the tickets layout just for some context because this is where we're going to fire off that script. Now, if you're not familiar with scripts or the idea of scripts, they're just an instruction list that produces results. Okay. And typically you want to create scripts to handle repetitive tasks, repetitive and tedious tasks, things that you just want automated. Like for example, if you want to create a receipt, certainly I could find the appropriate receipt. Then I could save it as a PDF manually. Then I could write an email manually and attach that PDF to the email manually. But do I want to do that every time I'm with a customer? That's something I probably want to automate. Okay. So just think of it as an instruction list set. Like if you're getting ready in the morning, if you get ready in the morning, like you would follow a script, you wake up, you stretch, you get out of bed, you walk to the bathroom, you brush your teeth. Those are all steps involved with getting ready in the morning. And that's what you do when you create a script. You tell FileMaker, these are the steps I want you to follow to produce a result. So getting started with the script. First thing, I'm going to give it a title. I'm just going to call email receipt. Okay. Now on this job tickets right now, we only have five records. Pretty easy to navigate, but this is going to expand. We could have hundreds and hundreds of ticket requests. So I want to make sure FileMaker knows that when I fire off the script, it needs to know the exact ticket that I want it to print out for. So first thing I'm going to do is I'm going to use the set variable script step. The set variable script step allows me to capture a dynamic value. We don't want a hard code that we're always going to be on ticket one because that's not always going to be the case. We may want to print out the receipt for ticket 10 or ticket 18 or ticket 97. Setting a variable is going to allow us to capture that dynamic value. So I'm going to go ahead and give this variable a name. I'm just going to call it a receipt number. And then for the value, I'm just going to tell FileMaker, hey, grab the value that's in the ticket ID. So grab this value right here. So click OK. Once I grab the appropriate ticket value, then I'm going to tell FileMaker, now that you know the ticket value, go ahead and jump to the receipt layout. Jump to the receipt layout, and then I need to tell FileMaker, hey, now that you're on the receipt layout, make sure you jump to the appropriate ticket that I was just on. And in order to make sure that happens, I'm just going to do a find. I'm going to tell FileMaker, hey, perform a find for that ticket. So we're already on the receipt layout, then we're going to do a perform find. Okay, and we're going to tell FileMaker, hey, when the ticket ID equals the value in the receipt number variable, okay, click Add and click OK. Those are the results I want you to produce, okay. So find me the record that matches this ticket value, okay. And then once we're on the appropriate record, we need to create a file name for what we're going to produce for the PDF or a receipt that we're going to produce. So again, the file name could, it could be very dynamic, so I'm going to go ahead and choose the set variable script step again, okay. So I'm going to choose set variable, we're just going to give this file name, okay. And then the value, I'm going to add some literal text, I'm going to say this is a receipt, the underscore, and then I'm going to add, you know, I want to add the date. So it just kind of distinguishes which receipt it is, okay. So I'm going to use a get function, get current date. Now what's going to happen if I use this in my script or in my calculation? FileMaker is going to grab the current dates like so, 12, 9, 2014, okay. That is today's current date, so that is appropriate, but since this is going to be a file name, this is pretty much going to be like a file path. And FileMaker is going to be looking for, you know, a folder or a directory called 12 followed by a folder directly called 9 followed by a folder directly called 2014. So we actually need to remove those, okay. And I'm actually going to substitute those with underscores kind of like what we're doing with the receipt here. So we still want that get current date function, but we're going to combine it with the substitute function. So let's go ahead and scroll down and bring up the substitute function, okay. And I'm going to say substitute in the current date, find the slashes and replace those with underscores, okay. Now we're no longer confusing FileMaker. And then finally, we'll add some literal text again, add .pdf, all right, to make sure that we have the proper file extension, okay. So it's going to be receipt underscore 12 underscore 9, 12 underscore 2014 .pdf. That's going to be the end result. So we'll click okay. All right. So now that we have a file name, I'm going to tell FileMaker to go ahead and save those records as a PDF. Okay, I'm going to put the outputs file as the file name. Now we're doing this for the iOS, we're out in the field. Just a heads up, if you're doing this out, if you're wanting to create this workflow for users on the desktop, you know, you would specify the actual output location. So you would say, okay, put this in the desktop, put this in a particular folder in a directory. On the iOS device, we have no control over where it goes, it just goes into FileMaker goes documents folder. So we don't need to specify that. Okay. So it's just going to save it where it saves it. And you know, we're okay with that. Okay, so we're giving it a name, we're telling FileMaker, go ahead and save that PDF. All right. Now we need to tell FileMaker, okay, this is exactly where that PDF that was saved is located. All right. So we're going to do another variable. Okay. Because it's always going to change in terms of the name, that's what's going to make it change. So we're going to go ahead and we're going to call this PDF path. Okay. And then the PDF path is just the get documents path, just get documents path function. And then the file name variable. Okay. So create a file, then save that PDF under the file name, where you store it by default. And then hey, FileMaker, that's actually stored at the documents path. And I want you to grab this particular file. Okay. All right. So FileMaker knows which file to grab, we just need to attach it to a mail. Okay. So I'm going to go ahead and use the send mail script. Okay. Script step. And we have a few options. And I'm going to choose to have FileMaker automatically enter the customer email. I don't want to have to type this in every single time. Okay. So FileMaker automatically grab the value in that customer email. For the subject, I'm just going to add some literal text. Okay. And messages, we'll just skip that for now. And then for attached file, okay, I'm going to put in the PDF path. Okay. And click okay. All right. Let's do a performer.dialog right here. Okay. Let's go ahead and save the script. And now I need to put this onto my ticket layout. So I'm going to go ahead and edit the layout. And I'm going to go ahead and add a button. We use popover buttons. I'm going to use a regular button here. Okay. Okay. And we'll say perform the email receipt script. Okay. And it's going to say send, or let's say email receipt. That's better. All right. Just align that a little bit better with the total. Okay. And then just for some added color, let's go ahead and use FileMaker 13 styles to change the color of that button. Yeah, the blue button is fine. Just again, adds a little bit of color to our layout. Okay. So let's go ahead and save that layout back in browse mode. And then let's go ahead and bring up our iOS device. Okay. Again, I'm going to launch reflector and then bring that over onto my screen to give me one second to do that. All right. There it is. Okay. Okay. We're currently in job tickets too. So let's close that. All right. Let's go back to Ryan Minook's FileMaker server and open up job tickets three. Okay. There's a layout that we're just working with. I'm going to go ahead and tap that email receipt button. Okay. And email appears we have Doug's email automatically associated to the two field. The subject automatically has our literal text. And then you see that receipt PDF that we created and attached to the email. Again, just like we expected on an iOS device. One important note about this particular feature, if you want to build that functionality out, if you create multiple receipts in one day using FileMaker, the iOS device will create an appended number. So like one, two. So this would be receipt 12924-1 and then dash two, dash three, dash four. So that's something that you want to, you want to parse, you want to capture. You could have a field, like a global field dedicated to the amount of receipts generated in a day and then append that to your script and your variables so you know which one to actually pull for. Okay. Okay. So what do we do? Well, we created a script that saved our records as PDFs and then we emailed a copy to the customer. So there's still a lot that we could build on if we wanted to using a similar approach with portals. We could create a view for each one of the text so they can see which open tickets are associated with them. We could create a table to manage our clients or maybe we could start fleshing out the point of sale system that we just started hinting at. But really in just about 40 minutes, we've created a fantastic little tool that has already started to impact the business. So for the field reps, our day to day has become much more efficient, but what does Perry have to gain? Well, think about how just one rep can affect the top line by fitting in one more customer visit a one more customer contact a day and then roll that into the week and roll that over a month or the year and then look at the impact across the entire team. Okay. So I'd like to open this up to Q&A. Looks like we have some really good Q set up for the questions already. Again, go to the control panel, click on the questions section, enter your question and click on send. We'll try to get as many as we can. And if you haven't already, let's give you some time to do so. I'm going to talk about some great resources as a follow-up to these webinars. The first resource, the FileMaker training series, this is recently released. We have two options, the basics and the advanced. And the basics books, it's free to download. Get it off our website, get it off iBooks, okay? Free download advanced, $19.99 for the download, $39.99 for the hard copy. This is FileMaker's official training curriculum. And it's also a great resource for the path to serve to certification. You can be interested in becoming a FileMaker developer, or just sharpening your developer skills. Again, FileMaker Go for $13, free to download, get it off the App Store. If you do so, remember to download FileMaker Pro 13 Trial like you saw today. The building your solution, the database schema and the layouts can only happen on the desktop client side. You have additional FileMaker web seminars, a really great free resource content in there. If you have any interest in taking your ideas over to the web, there's a great best tips and practices webinar. And then for all your ideas, all your solutions, we just came out with a webinar presented by one of our business partners. He talks about how you can get the maximum performance out of your solutions. I think that's a fantastic resource for you to check out. And then if you're ready to purchase, give us a call at 1-800-725-2747 or go to the URL that you see at the top of your screen. We have a fantastic annual volume licensing agreement program. FileMaker is starting as low as $9. FileMaker server as low as $29. Again, give us a call. We'd love to chat with you to see if FileMaker is a good fit for you or just to discuss how FileMaker can be deployed for your solution. All right, so let's go ahead and jump into the Q&A. Looks like we have a little bit of time left, but I don't want to shut you guys out of your questions, so we'll answer as many as possible. Okay, the first question. How much work would it be to add Google Maps to the ticket layout? This is a fantastic question, especially for, especially because it makes sense in terms of what we were talking about, in terms of, or what we were designing with the customer addresses and the site addresses. Wouldn't it be fantastic for our field team to just look at the solution, see a ticket, and then get some quick directions to where they need to go next? Actually, in FileMaker, let's go ahead and do the solution open up here. We have this tool called a WebViewer. Okay, and a WebViewer allows you to show a web browser directly on your layout. Okay, and here's a WebViewer setup window. You can choose some preset URLs or you can create your custom URL as well. And you'll notice the first one, Google Maps, I can actually specify fields from my FileMaker records, right, or my FileMaker table. So I can say, hey FileMaker, go ahead and grab the value in the customer address field. Grab the value in the customer city field and so on and so forth. And you see that the URL is dynamically adding these to the URL. So what that means is that as I go through the records, the web browser is going to dynamically change your location for each site. Okay, so that's a really good question and it really ties well into where we could start taking this little tool next. Okay, the next question. Is it better hosting using FileMaker server or use locally on the iPad and sync back later? This is a fantastic question. You always want to host with FileMaker server, you know, that's always going to be the hub of your solution. But if you're going to be out in the field, it's always good to just have a backup copy on the device. Okay, so it doesn't have to be either or. All right, you don't just have to work locally and sync back later or just work on FileMaker server. If you have a network connection, then by all means, I would say just continue working with FileMaker server because you're getting updates in real time. Okay, if anyone else needs to see that data, you know, they're getting updates in real time. So if I have a network connection, I'm connected to FileMaker server, but I wouldn't approach a job out in the field with an either or mentality. I would be prepared for both. Good question. Okay, and we actually have another question kind of tied to that. What do you recommend using FileMaker go in the field but with limited Wi-Fi? Again, put it on the device and, you know, sync back later. Let's talk about syncing back. Okay, FileMaker, just to make sure we're on the same page, doesn't have a native sync feature. So there's not like a feature that you can just turn on and off as I sync these to my records. What you're working with is pretty much an imported or a scripted import. Okay, so you're writing a script that imports your records into the hosted file and importing your changes into the hosted file. If you're working with records or creating records that no one else is going to update, that's a straightforward import. If you're going to be working on records that other people are going to be working with at the same time while you're offline or they're offline, then you're going to have to incorporate some business logic. Whose updates are you going to keep? Is it based off of time? Is it based off of who they are in the company and things like that? Okay, so if you want to tackle that yourself, we have a great FileMaker Go sync guide. It's available for free on FileMaker's TechNet website. TechNet is a free to join program. Everyone here who's attending, if you're not already, you absolutely should. Again, it's free. You get access to a bunch of great white papers, a bunch of great videos and tutorials, and also another forum site which kind of goes into a little bit more heavier development and things like that. So it's a fantastic resource that you should definitely take advantage of. But you can get that sync guide off of TechNet. Now, there are software out there that kind of take that responsibility of creating that script out of your hands. So off the top of my head, if you're ready to write it down, but 360 works, MirrorSync, C codes, Go sync. There's another software that just came out, Easy Sync. I forget the developer of that, but again, those kind of take the responsibility of writing that script to import out of your hands and you can just deploy with their solution. So again, you're either writing the script yourself or using third party software to sync that information back to your hosted solution. Again, there's going to be a level of complexity there. So you just want to approach that one carefully. Okay. The next question, how do we get the, how do we get this solution onto the iOS device for areas with bad network connections? Good question. We didn't really touch on this too much. We just talked about how you can have it on there. But to get it over onto the layout or over onto the iOS device, you have a few ways. Use iTunes. You can email it to yourself. You can use a third party software like Dropbox, for example, or you can put it up on a website and then download it. All right. A lot of great questions. A recording of this will be sent to you and you can also be able to find it on that filemaker.com, forward slash support, forward slash webinars page. Thanks for sticking around. I know we ran a few minutes late and on behalf of FileMaker, it was my absolute pleasure chatting with you guys today and I hope to see you on another webinar soon. Thanks.