Using the producer framework for outbound notifications

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Using the producer framework for outbound notifications

    The producer framework in ServiceNow enables outbound notifications by picking events from the instance and sending them to external systems. External systems consume these notifications via an installed messaging service, facilitating integration and communication between ServiceNow and external applications.

    Show full answer Show less

    System Properties

    To use the producer framework effectively, you must configure several key system properties that control scheduling, logging, message bus selection, batch processing, and concurrency control. These properties determine how notifications are processed and delivered:

    • snapinotifmgmt.event.log: Sets the logging level for debug logs (e.g., error, warning, info).
    • snapinotifmgmt.publishermessagebusconfiguration: Defines whether to publish messages via Hermes Messaging Service, Open Message Bus, or both.
    • snapinotifmgmt.inboundqueue.maxrecords: Maximum number of records the scheduler pulls from the inbound queue per run, working with batch limits to control processing volume.
    • snapinotifmgmt.inboundqueue.batch.limit: Number of records processed per batch, optimizing throughput and scheduler runtime.
    • snapinotifmgmt.glide.mutex.script.maxspins and spinwait: Control concurrency by setting the attempts and wait times to acquire mutex locks when processing inbound queue records.
    • snapinotifmgmt.schedule.max.runtime: Maximum allowed runtime in milliseconds for the scheduled job before reporting failure, ensuring timely processing.

    Configuring these properties allows you to tailor the notification processing to your environment’s performance and reliability needs.

    Producer Framework Workflow

    When an event is pushed to the staging table, the following occurs:

    • The scheduler retrieves records at configured intervals and sends Glide snapshots to the event processor.
    • The snapshots are transformed into TMF 688-compliant event payloads based on the event type, ensuring standardized notification formats.
    • The system determines whether to send notifications via Hermes Kafka or Open Message Bus based on your configuration.

    This workflow ensures standardized, reliable outbound notifications that integrate with external messaging systems.

    Practical Benefits for ServiceNow Customers

    • Enables seamless integration with external systems by delivering standardized event notifications.
    • Offers configurable performance and reliability settings through system properties to handle varying workloads efficiently.
    • Supports multiple messaging platforms (Hermes and Open Message Bus) to fit diverse architectural needs.
    • Ensures notifications adhere to TMF 688 standards, supporting interoperability in telecommunications and other industries.

    By properly configuring and understanding the producer framework and its system properties, ServiceNow customers can automate outbound notifications with precision and scalability.

    The producer framework picks the event from the ServiceNow instance and sends the outbound notification to the external system. You can consume the details of the notification from the messaging service that is installed in your external system.

    System properties

    You must configure the system properties to use the producer framework for outbound notification. The following table explains the list of system properties that are set for the scheduled jobs.

    Table 1. Producer framework system properties
    Property Description Type
    sn_api_notif_mgmt.event.log
    Level of logging to be written to the debug logs. You can select the following logging levels:
    • emerg: Total failure.
    • alert: System corruption of a database, for example.
    • crit: Typically used for hardware errors, for example.
    • err: Any errors.
    • warning: Any warnings
    • notice: Possible action required but not essential.
    • Info: No action required.
    • debug: Generally not used except for capturing everything for fault-finding.

    Default value: err

    		 String
    sn_api_notif_mgmt.publisher_message_bus_configuration Defines whether messages are published using the Hermes Messaging Service, the Open Message Bus, or both message buses. You can use the following values:
    • openMessageBus
    • hermes
    • both

    Default value: openMessageBus

    		 String
    sn_api_notif_mgmt.inboundqueue.maxrecords Maximum number of records that the scheduler will pull from the inbound queue for one scheduler run. This value is used in conjunction with the sn_api_notif_mgmt.inboundqueue.batch.limit parameter.
    • Default value: 200
    • Other possible values: As needed

    For example, if the batch limit is set to 50 and the maxrecords is set to 200, and if the number of records that are in the inbound queue is 130, then the scheduler would pull three different batches of records in a single run; two with 50 records and one with 30 records. If the number of records in the inbound queue is 220, the scheduler would pull four batches of 50 records and the remaining 20 records would not be processed until the next time the scheduler runs.

    When setting this value, you must also consider the time that it will take for the scheduler to process multiple batches and set the sn_api_notif_mgmt.schedule.max.runtime value accordingly.

    		 Integer
    sn_api_notif_mgmt.inboundqueue.batch.limit Number of records that the scheduler pulls and processes from the inbound queue at one batch.
    • Default value: 200
    • Other possible values: As needed
    		 Integer
    sn_api_notif_mgmt.glide.mutex.script.maxspins Maximum number of attempts to acquire a mutex lock in the inbound queue records.
    • Type: Integer
    • Default value: 100
    • Other possible values: As needed
    		 Integer
    sn_api_notif_mgmt.schedule.max.runtime The maximum time, in milliseconds, that the scheduled job can run before it fails and reports an error.
    • Type: Integer
    • Default value: 90000
    • Other possible values: As needed
    		 Integer
    sn_api_notif_mgmt.glide.mutex.script.spinwait Maximum Time, in milliseconds, to wait between attempts to acquire a mutex lock on the records in the inbound queue.
    • Type: Integer
    • Default value: 100
    • Other possible values: As needed
    		 Integer

    Producer framework workflow

    When the system pushes an event to the staging table, the following steps take place as part of the producer framework mechanism:
    1. The scheduler picks a number of records at a preconfigured interval and then sends Glide snapshots to the event processor.
    2. The system converts the Glide snapshot to a TMF 688 complaint event payload based on the event type.

      To learn more about the methods used to define and generate the TMF-compliant payloads for trouble ticket events, see TopicAPIUtilsOOB - Scoped.

    3. The system checks whether the notification configuration is intended for Hermes Kafka or the open message bus.

      To learn more about configuring the producer event notification framework, see Producer Event Notification Framework developer guide.