In this video, we'll be going through the steps to configure the convert task for converting models into steps like PDFs. This can be done automatically on a transition action or within a right click menu. This is a great option to save time and help speed up the design process. To configure the task in PDM, you'll need to import the added. If you haven't done so, then take a look at our guidance on importing convert editing and setting up a task host. Open up the PDM administration tool and log onto your vault. Once you've connected to your vault, you'll need to go to the task node about three quarters of the way down and expand this within the node. You should see an entry for the convert task. To make things a little easier, we suggest making a copy of this to make sure you always have a default task to go back to. Very simply, right click on task and select Copy. Once that's done, double click to open up the task configuration. It's always best practice to rename this to something relevant in this instance. SolidWorks part Assembly to step. This first page is the in page and this is going to be the convert add in as well as who will execute the task. This can be an individual user such as admin or the logged in user. This is important if the user has triggered the conversion task. Does not have permission to add files to the book. When executing the task as a specific user can overcome this. The number of retries and how long you want to wait before failing is how many times you want the task to run again. If it fails, and how long you want to wait before the task fails. The next page is the execution method page. Essentially, which computers do you want this task to run on and how it should run? So either let the computer choose prompt the user to choose, or run on the computer where the task was initiated. It's really important to select the appropriate option here, as wherever this task will run, it will need an installation of SolidWorks, for example, if an approval is triggered this task but does not have SolidWorks installed, the task will fail. Remember that your computer will only appear here if you set it up as a task host. First. The next page is the menu command page and this is optional. You can turn it on and off through this checkbox. This is showing you how you'd like to see the task appearing on a right click shortcut menu. Each backslash here is a new submenu. Again, it's best practice to rename this to something appropriate, such as soda rocks or some way to step. Moving on to the conversion settings for this, we're going to select the step option for an output file format. And you do have the option to adjust some of the settings of the output file, such as the version of the step. So 2 or 3 214242 depending on how many features you'd like. The first tab here is the configurations tab. And this is this. All the box configurations. You might want to export all configurations or the last active configuration. Or if you have a specific configuration in mind you can select this third option. Within source file references you have two options. You can use the as built if you want the drawing and its references to be exactly one. That first one was created, or the latest version. If you want the drawing to automatically reflect any changes made to any of the reference parts since that time. The latter is usually not the best option for step files being created as a part of an approval process, as you want it to be an exact match for the approved model. You also have a couple of checkboxes which are on by default, which allow the user to change the setting. The second tab is the sheets tab, and we can just leave those settings as default. The following page is the output for all cards. Page. This allows you to populate the output stats file card with values from the source files. Data card. For example, you could take the revision from the source file and apply it to the revision of the output file. You also have the option of adding in some free text if you wanted to define those values yourself, or perhaps put a comment in a box somewhere. In this example, I'll pop a comment into the common area of the data card. Moving on to the Output Files detail page, this is defining what the output step file is going to go. In Pro you can define two locations. So you might want to include one output file in PDM vault and one externally in another business who does not have access to PDM. You can construct the file names differently for both, so the external version might include some additional details such as the description or the revision from the source file. By default, the primary output path is a source files folder path. If you wanted to build this up yourself, you can click this box and use an arrow on the right hand side. Add in the location that you want. There are a couple of other useful things to note here. First is the error log file and this is where the error log could go. If your task fails. So that's usually within a log folder at the root of your fault. But you might want to define a different location here. The second is this advanced scripting options. So this allows you to view the script or the code of the task. And this is in Visual Basic. script can be reset. And this is useful for troubleshooting. And you can also just find the default program opened here. Just to note that if the script is modified to make sure the editor document it as they will need to be re-applied after any script presets reset process is recommended after each major version upgrade, as the macro might have been modified by SolidWorks to fix previous bugs or offer new capabilities. The following page is permissions, and this is who has the ability to initiate this task. So usually this is admin and perhaps the engineering group as well. We recommend giving permissions at the group level rather than the individual level. Apart from the admin user. The last couple of pages are for our success and error notifications, so here you'll be notified if the task completes or fails. Usually you want to be cautious about applying the success notifications, as you don't want to be overloading someone's PDM account with notifications. Notifying the user here is usually enough. The contents of the notification can be defined here. The last page is the same thing again, but if the task fails, recommend that you notify the user here and perhaps another user such as admin. You'd be able to investigate what felt. Now that you're done, you can apply what's relevant in your workflow and give it a test, either through a right click menu or by pushing us all through a state change. If you would like some additional assistance on tasks, please get in touch with our support line which is included as part of your subscription. You can do this either on our website or on the details shown on screen.