How to send incident id details to external system in response of TMF642?

AnilPathi
Tera Contributor

Hello Everyone,

 

We have a requirement for sending incident details to external system in TMF642.

Upon receiving a trigger from an external system via the TMF642 POST endpoint, ServiceNow initiates creation of an "event" record, which then escalates to an "alert" and ultimately to an "incident" record within the ServiceNow platform. Concurrently, ServiceNow transmits a response message back to the external system, adhering to the established OOB TMF642 standards. Below is the response.

{
    "externalAlarmId": "Testing 89484",
    "alarmType": "QualityOfServiceAlarm",
    "type": "Test",
    "ackState": "acknowledged",
    "perceivedSeverity": "CRITICAL",
    "probableCause": "Software_failure",
    "specificProblem": "Software_failure",
    "alarmedObjectType": "ROUTER",
    "alarmedObject": {
        "id": "Port CI Test",
        "href": " http://api/alarmedobject/000000"
    },
    "sourceSystemId": "SOURCE_SYSTEM_Router_R1_Test",
    "alarmDetails": "Software Failure on SD-WAN Controller Router_R1_Test",
    "state": "RAISED",
    "alarmChangedTime": "2017-08-15T07:04:15.666Z",
    "proposedRepairActions": "Switch in standby equipment",
    "alarmReportingTime": "2024-09-25T09:05:15.666Z",
    "alarmRaisedTime": "2024-12-06T011:04:16.666Z",
    "plannedOutageIndication": "IN_SERVICE",
    "id": "Port CI Test_Testing 89484",
    "href": "/api/sn_ind_tmf642/alarm_mgmt/alarm/Port CI Test_Testing 89484"
}
We need to include incident details in the response to the TMF642 POST endpoint. Our initial attempt involved customizing the response and using gs.sleep(30000) to delay the response for 30 seconds, allowing incident creation. While this approach works, it's not considered best practice within ServiceNow due to potential performance issues, unpredictable delays, and reduced code maintainability.

 
Please share your ideas on this if you have implemented this in your projects.


Thanks & Regards,
Pathi Anil
 
0 REPLIES 0