Hello
We got same requirement in the ONAP/External API component and we add an orderMessage structure.
But then we reported this 'extension' to TMF but not get an approval to add this because it could bring confusion with note that already exist.
Probably - and like mentioned by
@Jonathan Goldberg- you can leverage the polymorphic extension.
If we have to do it it again in ONAP/extAPI we will probably create an orderMessage structure as a note specialization and use note.@type as discriminator to rout to standard note or to orderMessage structure.
Hope it helps
Ludovic
------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------
Original Message:
Sent: Nov 06, 2019 06:49
From: Kailash Mali
Subject: TMF641 reason/message for a failed order
Hi Alexandre, For GET operation, we will indeed need an additional attribute to share the reason (code/description) to the consumer. We did not implement a GET operation with reason so far.
BR,
Kailash
------------------------------
Kailash Mali
Ericsson Inc.
Original Message:
Sent: Nov 06, 2019 05:53
From: Alexandre Meynaud
Subject: TMF641 reason/message for a failed order
Thanks for the hint Kailash. We can indeed reuse/recycle other attributes for another purpose, as long as both the client and server apps agree on the new semantic (which is btw the role of a standard). Your example is for notification events (ServiceOrderStateChangeNotification), but I was more thinking about the ServiceOrder GET result. Did you also reuse one of the TMF Order attribute (e.g. "description") to put the order rejection reason: "Order rejected - No free lines available"?
Cheers
Alexandre
------------------------------
Alexandre Meynaud
Hewlett Packard Enterprise
Original Message:
Sent: Nov 06, 2019 04:04
From: Kailash Mali
Subject: TMF641 reason/message for a failed order
We faced the same requirement to convey the reason code/desc and we re-used eventId and eventDescription for this purpose to remain compliant to API specs.
------------------------------
Kailash Mali
Ericsson Inc.
Original Message:
Sent: Nov 05, 2019 11:12
From: Alexandre Meynaud
Subject: TMF641 reason/message for a failed order
Hello,
The TMF641 orders or order items state can be "Failed" or "Partial", but there is apparently no attribute to convey the reason of the service ordering failure (e.g. "reason", "error message", else ...). Is it implementation specific or can it be standardized and added in a next TMF641 specification version?
Thanks
Alexandre
------------------------------
Alexandre Meynaud
Hewlett Packard Enterprise
------------------------------