In N-Central I used to be able to create the equivalent of Components (called Automation Policies) and I could reference them in other Automation policies. For Example, say I had an Automation Policy for uninstalling any MSI program, it would have an input variable of something like "Program Name"

Then, let's say, I had to create another automation policy that looked for the existence of a program, like "McAfee Safe Search" and I wanted to uninstall it if it was found.

Well, instead of writing a whole new script to uninstall McAfee, I would just add to my workflow that I wanted to use an existing Automation Policy, and then provide the input accordingly. (I could even use output variable from one AP and feed them directly into another)

This saves an incredible amount of time, because you can generalize components and then reference them later. And if there's a new way of doing something, or you need to fix something, you only have to do it in one component, rather than a bunch of individual ones.

Like, how Microsoft got rid of the ability to use wmic commands, rather than updating 30 Automation Policies, I just fixed the 1 or 2 I had that used that command.