Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Auto Submit Filters Overview

    Service Now receives JMBs from devices when an event occurs on the devices and creates incidents. If auto submit policies are configured, the incidents can be submitted to Juniper Support Systems (JSS) for creating a case automatically. Starting from Junos Space Service Now Release 17.1R1, auto submit filters assigned to an auto submit policy provide options to select incidents for submitting to JSS or Service Now partner (in case of End Customer mode) at a granular level.

    You can use the auto submit filters for the following purposes:

    • Define incidents that should be submitted to JSS for creating cases
    • Define incidents that should not be submitted to JSS for creating cases

    Service Now provides options to define a basic filter, advanced filter, and import auto submit filters directly to Service Now.

    Basic filters filter incidents based on attributes such as event synopsis, platform, event type and so on by using the and and or predefined computational logic whereas in advanced filters, the filter terms are defined by using Perl scripts and therefore you have the flexibility to define your own filtering logic.


    • Auto submit filters cannot be applied on incidents created for on-demand JMBs, BIOS JMBs, and Product Health Data JMBs.
    • In a Service Now partner, auto submit filters cannot be applied to incidents received from a Service Now end customer.
    • There is no limit on the number of auto submit filters that can be created. However, a large number of incident filters impacts the performance of Service Now when submitting incidents to JSS or Service Now partner.

    You can view the configured auto submit filters on the Auto Submit Filters page. You can perform the following tasks from the Auto Submit Filters page:

    Modified: 2017-06-06