Problem
Custom Detection Methods are related to a application and not to a version and can't be or-linked.
Description
If custom detection Method are used to detect an installed application, the information to be checked might change if a new Version is added. As sometimes not only one Version is used within an environment, today you need to have 2 different applications added to your unified catalogue, which blows up the size of the catalogue.
At the moment the custom detection Method can only be set for a whole application and not for a version and if you add more than one rule, they are and-linked.
Vision 1:
Custom Detection Methods are bound to a version and not to an application
Vision 2:
You can decide if you want to link the custom Detection Methods with an “and” or an “or”
Comments (2 comments)