Thank you for your post. Based on the complexity of what you're trying to do, you can either push the installation of Fortinet via a custom action or custom patch. A custom action has less parts to configure to make most operations work and additionally doesn't require you to create your own detection logic. Whereas a Custom patch, this does require you to create your own detection logic in order to find the patch as missing prior to deployment. The one benefit of Custom Patches versus Actions is that you can verify installation of the product on a Custom patch.
Here is some documentation that goes over both items to help you decide which option may be the best.
Thanks for the help. I was able to get a new custom action created and used successfully when I apply it directly, but it does not seem to be working when it is part of a Deployment Template that is used by an agent. Do I have to do something different when an agent is involved?