Hi TM Forum Team,
I am implementing TMF641 Service Ordering API (v4.1) for a telecom provisioning use case.
In our implementation, a single Service Order can contain multiple ServiceOrderItems. However, all ServiceOrderItems within the same request always represent the same business operation. Mixed operation types are not allowed in a single request.
For example:
- PRE_PROVISION
- ASSIGN
- PEERING_NUMBER
A request may contain multiple numbers, but they all belong to the same operation type.
Example:
{
"operationType": "PRE_PROVISION",
"serviceOrderItem": [
{
...
},
{
...
}
]
}
Instead of repeating the same value in every ServiceOrderItem, we would like to represent this operation only once at the ServiceOrder level.
My questions are:
1. Is there a standard TMF641 attribute that should be used for this purpose (for example, category or another existing attribute)?
2. Is it recommended to use a custom top-level attribute such as "operationType" or "type"?
3. If a custom attribute is added to the ServiceOrder resource, will it still be considered TMF641 compliant and pass CTK validation, or should custom business information be modelled using service/serviceCharacteristic instead?
Our goal is to remain as close as possible to the TMF641 standard while avoiding redundant data in every ServiceOrderItem.
Thank you for your guidance.
#AIandData#BusinessAssurance#CustomerExperience#OpenDigitalArchitecture#General------------------------------
Gopal Bera
TO BE VERIFIED
------------------------------