Thank you for joining me for this video, Schedule or Plug-In. For Servoy University, I'm Bob Cusick. The Schedule or Plug-In allows you to create timed or cron jobs. This allows you to execute global methods set on any schedule that you want, according to almost any condition you can think of. I've created a very simple sample here that will just simply get the number of records in the database, and it will run for 10 times. So right now there are no records in this database, and I'm going to click Start Schedule. And you'll see down here there are zero records and it's run once, twice, I'm going to create a record, I'm going to create another record, and as you can see, it's running every two seconds and giving me the count of records. Now this is a very simple example, obviously, but when it gets to the tenth iteration, it will just stop running. Let's take a look at the code behind it. There's two ways that you can go ahead and start these timed jobs. Number one is to add a cron job, and adding a cron job, you tell it what the job name is that you want it to be, the cron timings, and we'll get into that in a second, which global method you want to trigger, what the start date, end date, and any other arguments that you want to pass into that method. You can also use add job, and again, you give it a name, a start date, the global method, how often you want it to repeat in either milliseconds or the number of times you want it to repeat and or an end date and or arguments. You can also get a list of all the current job names, so you can schedule many jobs to run at the same time, all at different intervals, all at triggering different global methods. You can get the job that ran last, and finally you can remove any named job that you have. So to add a cron job, it takes a very specific timing string, and that's explained more at the courtschedule or dot org website. So here are some examples of what that string means. It starts with seconds, minutes, hours, days of the month, month, day of the week, and year, so you can go ahead and get very, very exotic in the timings. So fire every day at the same time, fire every five minutes starting at 2 p.m., and ending at a certain time, the last Friday of every month, anything that you want to do, you can do using this specialized cron timing. So if you have something that's very exotic or very specific that you need to run at very, very specific times, then you want to use add cron job. You can also use it for normally scheduled stuff as well. You can use add job to do the same thing, but it's really meant for timings that are less exotic than ones that you would use for add a cron job. They both do exactly the same thing. So a job scheduled with add cron job or add job, you can still remove it, you can still get the current job, and still get the last run job. There are a number of different ways you can use this in your solution. For example, if you have a dashboard and you want to update that dashboard in real time, you would set up a job that ran the global method to update every so often, maybe every five minutes or 20 seconds. You can also build specialized solutions that are meant just to run cron jobs, and in fact, they will run inside the headless client in the application server. That's done here in the application server under batch processors. You can choose a solution name, pass it any starting arguments, give it a username or password if you need to log into authenticate. And this will run inside of the headless client on the server. That means that you can have as many of these specialized solutions that run these time jobs as you want. Keep in mind though, that each batch process does use a concurrent user license. With the batch processor, you can automate tasks like sending out invoices, group emailing, functions, past due notices. There's all kinds of things that you can do on a time basis. With the scheduled plugin, your imagination is the only limit. Thanks for watching.