---
sourceDocument: Xanadu API Reference
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/api-reference

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Configure trouble ticket notifications using the Producer Event Notification Framework

# Configure trouble ticket notifications using the Producer Event Notification Framework {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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"`
{#prd_evt_not-dev_gd-cfg_trbl_tkt_not__ul_fhv_qvl_b1c}  
If needed, you can add trouble ticket events to your implementation by performing the following steps:

1. Add a new [business rule](https://www.servicenow.com/docs/access?context=c_BusinessRules&version=xanadu&pubname=xanadu-application-development&ft:locale=en-US). 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://servicenow-prod.fluidtopics.net/xiQk9WfyUiAL9_fkReAzLQ "When adding a new trouble ticket event to your implementation, you must add a business rule to your ServiceNow instance.").
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://servicenow-prod.fluidtopics.net/HKUiA0h~XtZC89cCOGr_RQ "When adding a trouble ticket event to your implementation, you must create a function that generates the required TMF-compliant payload for that event type. In addition, you must add that function to the case statement that directs the logic to this function when processing this type of event record.")

You can also modify the payload of existing trouble ticket events. For details, see [Modify a trouble ticket event payload](https://servicenow-prod.fluidtopics.net/uqVOfn_nuRqRb396sD11JA "The base trouble ticket event notification implementation provides multiple default trouble ticket event type examples. You may need to alter the payloads for these events within your implementation to meet your actual needs. You may also need to configure the payload for any new trouble ticket events that you add to your implementation.").