How to handle TMF Service Characteristics with valueType = "object" for task generation and fulfillm
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi Team,
I'm working on a TM Forum / ServiceNow implementation where some service characteristics are received as complex objects instead of primitive values.
Example:
{
"name": "advancedInternetAccessConfig",
"valueType": "object",
"value": {
"accessType": "Primary",
"bandwidth": "100Mbps",
"location": {
"siteName": "Sample Site USA",
"postcode": "AB12CD"
}
}
}
Currently, we are discussing whether these nested objects should:
- Be stored as a single characteristic record with the entire JSON payload.
- Be flattened into multiple characteristics.
- Be stored as object structures and parsed later during fulfillment/task creation.
Our challenge is that task generation requires specific attributes from these objects. For example:
- Create Site Survey Task using location details.
- Create Network Configuration Task using bandwidth/access type.
- Create Validation Tasks based on nested object attributes.
How are others handling TMF service characteristics with valueType = "object" in ServiceNow?
Specifically:
- What is the recommended data model?
- Do you store the full object JSON or normalize it into related records?
- How do you parse object attributes during task creation and orchestration?
- Are there any best practices when mapping TMF641/TMF638 object characteristics into Order Management for Telecom workflows?
Any implementation examples or lessons learned would be greatly appreciated.
Thanks in advance!
0 REPLIES 0