When a triggered automation API call includes a category data field, the system currently bypasses match condition evaluation and applies the provided category directly, rather than checking it against configured match conditions. This behavior prevents customers from restricting automated diagnosis triggers to only those issues that meet defined criteria when the integrated third-party system always supplies a category value. This enhancement proposes adding an option to enforce match condition evaluation even when an API-provided category is present, so the system can determine trigger eligibility based on configured conditions rather than defaulting to the supplied value. Supporting this option would give customers finer control over which incoming events trigger diagnoses, reducing unnecessary automation runs from integrations that always populate the category field.
Available
Enforce Match Condition Evaluation for API-Supplied Category in Triggered Automation
Login to the community
No account yet? Create an account
Sign in with SSO
Login via NetBrain Universityor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
