1 Reply Latest reply on Aug 12, 2015 4:00 PM by richard mcleod

    How to use the Processes CO in Compliance?

    richard mcleod

      Anyone have any best practices or pointers for using the Processes CO inside of Compliance or more specifically for Discovery?


      I've only been able to get it working using Processes.Process:/<PID> (this is sort of useless since systems will start a process up with different PIDs)


      I am trying to use Processes.Process:/*.Command = /some/process but I can't get this to work (inside of a discovery condition)


      My end game is to only create components where /some/process is running. Am I better off creating an extended object?