Great catch Vance!
Sushil - you'll need to get support from your specific vendor (ServiceNow) to understand their API alignment.
You can of course verify formal conformance on the dedicated TMF page https://www.tmforum.org/certifications-awarded/ - from my check it looks like they have indeed certified TMF642 at version 4 of the API.
But be aware that formal certification is not a complete guarantee of 100% interoperability.
Good luck
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: May 31, 2024 02:06
From: Vance Shipley
Subject: TMF642 payload validation
You are confusing the create alarm operation with the payload of an event notification.
------------------------------
Vance Shipley
SigScale
Original Message:
Sent: May 30, 2024 13:39
From: sushil musale
Subject: TMF642 payload validation
one of the vendor is mandating the TMF 642 payload in a specific format
Following is the link Alarm Management Open API (servicenow.com)
however I dont see the payload is complying with the api user guide to conform to the following format
{
"eventId":"00001",
"eventTime":"2015-11-16T16:42:25-04:00",
"eventType":"AlarmCreateEvent",
"event": {
"alarm" : {-- SEE Alarm RESOURCE SAMPLE --}
}
}
The vendors payload is missing the following attributes and the payload structure
{
"eventId":"00001",
"eventTime":"2015-11-16T16:42:25-04:00",
"eventType":"AlarmCreateEvent",
}
I need help to verify the payload the vendor organization asks and if it is TMF 642 compliant
------------------------------
sushil musale
BT Group plc
------------------------------