Configure trouble ticket notifications using the Producer Event Notification Framework

concept australia Updated Sep 10, 2026 1 min read prd_evt_not-dev_gd-cfg_trbl_tkt_not.md

The base implementation of trouble ticket notification includes a set of trouble ticket events to demonstrate the capabilities of the system.

These trouble ticket events include:

Trouble ticket created (incident): TROUBLE_TICKET_CREATE: "TroubleTicketCreateEvent"
Trouble ticket created (case): TROUBLE_TICKET_CREATE_FOR_CASE: "TroubleTicketCreateEventForCase"
Trouble ticket status change (incident): TROUBLE_TICKET_STATUS_CHANGE: "TroubleTicketStatusChangeEvent"
Trouble ticket attribute value change (incident): TROUBLE_TICKET_ATTRIBUTE_CHANGE: "TroubleTicketAttributeChangeEvent"

If needed, you can add trouble ticket events to your implementation by performing the following steps:

Add a new business rule. This business rule must be associated with the table in which the record, incident or case, is stored. For additional information, see Add a business rule for a new trouble ticket event.
Configure the payload generation for the new trouble ticket event. For additional information see, Generate the payload for a new trouble ticket event

You can also modify the payload of existing trouble ticket events. For details, see Modify a trouble ticket event payload.

33 lines · 2.5 KB Wrap lines

---
title: Configure trouble ticket notifications using the Producer Event Notification Framework
description: The base implementation of trouble ticket notification includes a set of trouble ticket events to demonstrate the capabilities of the system.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/api-reference/developer-guides/prd\_evt\_not-dev\_gd-cfg\_trbl\_tkt\_not.html
release: australia
product: Developer Guides
classification: developer-guides
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Producer Event Notification Framework developer guide, Developer guides, API implementation and reference]
---

# Configure trouble ticket notifications using the Producer Event Notification Framework

The base implementation of trouble ticket notification includes a set of trouble ticket events to demonstrate the capabilities of the system.

These trouble ticket events include:

-   Trouble ticket created \(incident\): `TROUBLE_TICKET_CREATE: "TroubleTicketCreateEvent"`
-   Trouble ticket created \(case\): `TROUBLE_TICKET_CREATE_FOR_CASE: "TroubleTicketCreateEventForCase"`
-   Trouble ticket status change \(incident\): `TROUBLE_TICKET_STATUS_CHANGE: "TroubleTicketStatusChangeEvent"`
-   Trouble ticket attribute value change \(incident\): `TROUBLE_TICKET_ATTRIBUTE_CHANGE: "TroubleTicketAttributeChangeEvent"`

If needed, you can add trouble ticket events to your implementation by performing the following steps:

1.  Add a new [business rule](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/business-rules-classic/c_BusinessRules.md). This business rule must be associated with the table in which the record, incident or case, is stored. For additional information, see [Add a business rule for a new trouble ticket event](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/developer-guides/prd_evt_not-dev_gd-add_bus_rule.md).
2.  Configure the payload generation for the new trouble ticket event. For additional information see, [Generate the payload for a new trouble ticket event](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/developer-guides/prd_evt_not-dev_gd-gen_evt_pay.md)

You can also modify the payload of existing trouble ticket events. For details, see [Modify a trouble ticket event payload](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/developer-guides/prd_evt_not-dev_gd-mod-evt-pay.md).