in this video we'll be running through how to set up the convert PDF task for PDM standard. prior to confirming the task, you will need to import the add-in and set up a machine as a task host. So if you haven't already done so, please view our video on importing the convert add-in and setting up a task host. to start off with, open up the administration tool and you will log into your vault. So either double clicking or right click connect. And then once you do that you want to expand out the task node. So about three quarters of the way down. And within there you'll see two further tasks. You click task list and then you convert. Always helpful here to just create a duplicate. I means that you've got something to go back to as a backup. You can do that through a right click and copy. Double click to open up that task. Properties. And then when it's open, it's always best practice to rename your task to something relevant, such as, convert drawings to PDFs. here. So the first page is the add-in page. So this is going to be the sort of work convert add-in. And then the second bit is going to be who is going to execute this task. So this can be an individual user such as admin or as the logged in user. But it's very important here to define, the correct user as if the user who's triggered this conversion task does not have permission to add files to the vault. Then executing the task as a specific user can overcome this. Last bit then is number of retries and how long to wait before failing. So how many times you want the test to run again, it fails. And how long to wait before the task fails? so moving on to the execution method. So essentially which computers will run this task? Again important. So you select the appropriate option, as wherever this task is run, it will need an installation of solid So for example, if in a previous during this task it does not have slots installed. That task isn't going to run. So remember that your computer is only going to appear here if you've set it up as a task host first. Next page then, is our conversion settings. PDM standard. The conversion is limited to the PDF only option. And then you do have some further conversion options on the, on the right. And then, some source file references. So the source file references down the bottom. So the as built can be used if you want the drawing. And its reference is to be exactly when that version was created or the latest version, if the drawing needs to reflect any changes made to any of the reference passed since that time. So what that means is any changes to the child within an assembly, for example? Regardless of that, if that assembly has it has remain checked in, it's going to reflect any, any changes to those child's. The latter is not usually the best options for PDFs being created as part of an approval. As you want this to be an exact match for the approved drawing. There are some additional PDM options found here in the conversion options. if you need a high quality or perhaps a header or footer is needed. so the following page is for the output files date card. So this allows you to populate the output PDF straight to carb with values from the source files data card. So for example here I'm going to take the origin value from its source file. And I'm going to apply that to the revision of the output file. There is also an option for writing in some free text. So I'm going to use this to create, a something in the comments section of my output PDF data card. So this page, this is for the output file details. So this is defining where you want that output PDF to go. So by default that brings in, the source files for the location. This can just be cleared if needed. And we can edit that to a different location. So I'm going to change this to default root folder path. In a folder called PDF. Used source file name. To name that PDF. Couple of things to note on this page. First is the error log file. So this is where the error log will go if the task fails. Usually a log files in the root vault. But a different location can be defined if needed. Just be aware here that it has to be located within the vault. It can't be external to the vault. second is this advanced scripting option. this shows you the code of the task. So it's written in visual Basic. And the script can be reset here. Useful for troubleshooting. And you can define the default program it opens to run this task here. Just a quick caveat on that. if the script is modified at all, the edits need to be documented as they need to be reapplied after any resets. So the reset will pull through a brand new script from the archive. Reversing or overwriting any of those edits. Reset process is actually something that's recommended after each major version upgrade. As the macro might have been modified by the works to fix, you know, previous bugs and offer new capabilities. Last couple of pages, then, for our success and error notifications. So who will be notified if the task completes? Or fails? So Usually there needs to be some caution when applying the success notifications. As you not don't want to be overloading one single account with a load of PDM notifications. admin user doesn't need to know whether 100 tasks have been successful. the option for notifying the user here is usually the most appropriate. On the content of that notification can be defined here. And the last page then is the same thing. But what if the task fails. Again. Recommend that you notify the user who launched the task. And then potentially someone like admin or another, administrator who'd be able to help you investigate why it failed. Once you're done, you can hit. Okay. You can now apply what's relevant in your workflow, and give it a test by right clicking and pushing a file through a state. Change.