> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/patch/advanced-settings/bots/bots-deployment.md). # Deployment Bots OneSite Patch Deployment bots are used for filtering, for instance, if you want to create special rules for zero-day patches or patches flagged as critical. By using a deployment bot, you can define different user interaction settings, or set deployment or reboot windows based on urgency. You can either use the bot templates provided or create your own. Deployment bot templates include various filtering scenarios to cover most filtering requirements in an enterprise. When deciding which bot template to choose, consider the following examples to understand the different filter types. **Risk-Based Filters** These templates filter several aspects of patches based on risk. They include different rollout schedules and approval levels, and all require mandatory installation. **Mandatory Installation for Specific Categories** These templates filter specific categories of patches, including bug fixes, expired by vendor, known exploit, and so on. These bots filter based on category and then approve installation for all patches included in that category. ### Open and Save a Patch Deployment Bot Template OneSite Patch includes prepopulated templates that address most filtering scenarios. You can save these templates using a descriptive local naming convention, and then customize them to your environment. Or, you can create your own templates by clicking **+ New**. The following steps show you how to modify an existing template. 1. Select **Advanced Settings > Intent Schema > Bots > Patch Deployment Bots**. The top folder lists the templates provided by OneSite Patch and any partner integrations you have installed. 2. Select **Show All** to see the available templates or select **Filtered by:** in the bots list to see only the templates associated with that filter. 3. Select the **Name** of a template to open it. For example, in **Filtered by: Known Exploit**, select **Mandatory Install (Known Exploit Exists)**. ![Import Selector](/files/Hu6saqEyBWqtCtgIDPND) 4. Save the template with a new title: a. In the upper-left of the dialog, select **More**, and then select **Save As**. b. Enter a new name for the template, and then select **Save as**. This returns you to a copy of the template with the new name. c. Enter a detailed **Description** of the process covered in this template, or leave the prepopulated description. Add a character to enable the **Save** button, and then select **Save**. ### Patch Filter Settings The purpose of patch filter settings is to filter patches based on associated properties, either including or excluding them from the processing by this bot. Patches that meet the filter criteria will be processed, while those that do not will be disregarded. It's important to note that patch filter settings are not mandatory. If not specified, the bot will process all patches. You have the option of specifying a single filter condition or grouping multiple filter conditions using AND, OR, and NOT logic, allowing for a high level of configurability. To add a patch filter condition, simply click the ellipse button located on the right-hand side. ### Preview Filtered Patches Preview a list of software filtered by this bot based on the patch filter condition, using the steps below: 1. Select **Preview Filtered Software** on the lower-right of the **Patch Filter Settings**. 2. Select the **Software Patches** tab to see the Software Patches included in this bot with your filter. 3. Select the **Software Releases** tab to see the Software Releases included in this bot with your filter. 4. Select **OK** to return to the **Patch Filter Settings**. ### Configure Bot Settings Pre-requisites: these options will mostly be grayed out unless you have set up a Strategy that includes Business Units and Products. #### Select Deployment Settings In **Bot Settings**, use the **Deployment Settings** toggle to set a **Desired State** and an **Urgency level**. You can also designate **Business Units** as an additional filter for the bot. To create a bot workflow, enter a support ticket and request help from [Adaptiva Customer Support](https://adaptiva.com/support). ![Bot Settings](/files/9xdkBYUlVcqBwYkMusHj) With **Deployment Settings** selected, complete the following steps: 1. Select the **Desired State** from the list (**Mandatory Install**, **Do Not Install**, **Rollback**, **Uninstall**). 2. Select the **Urgency** from the list (**Low**, **Normal**, **High**, **Critical**). #### Business Units for Bot Deployment Settings 1. For **Business Units**, select **+ Browse**: * With no Business Units added to the bot, the patching cycle patches the devices in all Business Units identified in the Patching Strategy. * With one or more Business Units added to the bot, the patching cycle patches the devices in the Business Units. The Patching Strategy must include the same Business Units as part of its assigned Deployment Wave, for more information see [Deployment Settings](/patch/patching-fundamentals/patch-strategies.md#deployment-settings). 2. Select the right arrow next to a Business Unit type to expand one or more **Business Unit** structures. ![Select Business Units](/files/pzJZ41eCTcLJrEYZBhz5) 3. Select one or more **Business Units** to include in this Deployment bot, and then click **OK**. 4. Select **Save** at the upper-left to save your progress. * Now, when you need to add this Deployment bot to a Patching Strategy or other object, you will see it in the list of available Deployment bots. ### Use a Custom Deployment Bot Workflow If you have created a custom Deployment bot workflow, you will see it listed in OneSite Patch. If not, contact [Adaptiva Customer Support](https://adaptiva.com/support) to create a Deployment bot workflow for use with these settings. ### Related Links [Notification bots](/patch/advanced-settings/bots/bots-notification.md)