Hi Jonathan,
Thank you for your support. I need some information to develop relationships.
I've two ProductSpecification like below:
"specification product 13" which has Characteristic1, Characteristic2 & "specification product 15" which has Characteristic3, Characteristic4.
"productSpecification":
{
"id": "13",
"@type": "ProductSpecification",
"href": "http://serverlocation:port/catalogManagement/productSpecification/13",
"name": "specification product 13"
},
"productSpecCharacteristic":
[
{
"name": "Characteristic1",
"valueType": "string",
"productSpecCharacteristicValue":
[
{
"valueType": "string",
"isDefault": true,
"value": "value11"
},
{
"valueType": "string",
"isDefault": false,
"value": "value12"
}
]
},
{
"name": "Characteristic2",
"valueType": "string",
"productSpecCharacteristicValue":
[
{
"valueType": "string",
"isDefault": true,
"value": "value21"
},
{
"valueType": "string",
"isDefault": false,
"value": "value22"
}
]
}
]
"productSpecification":
{
"id": "15",
"href": "http://serverlocation:port/catalogManagement/productSpecification/15",
"name": "specification product 15"
},
"productSpecCharacteristic":
[
{
"name": "Characteristic3",
"valueType": "string",
"productSpecCharacteristicValue":
[
{
"valueType": "string",
"isDefault": true,
"value": "value31"
},
{
"valueType": "string",
"isDefault": false,
"value": "value32"
}
]
},
{
"name": "Characteristic4",
"valueType": "string",
"productSpecCharacteristicValue":
[
{
"valueType": "string",
"isDefault": true,
"value": "value41"
},
{
"valueType": "string",
"isDefault": false,
"value": "value42"
}
]
}
]
We are trying to determine validations according to the relationships.
1- Does "specification product 13" and "specification product 15" have to be in the same bundle, if I want to define a ProductSpecificationRelationship.
2- Or if I added a dependency relationship in to the ProductSpecificationRelationship, should I add that specification into the bundle?
3- Is the relationship between specifications necessary to define characteristic relationships?
5- Although there is no relationship between specifications, can the relationship between the characteristics of the specifications in the same bundle be established?
6- How relationships (Dependency, Migration, Substitution, Exclusivity) between specifications affect characteristics?
7- What does productSpecificationRelationship mean? Does it effect characteristic resultset? If it is, how productSpecificationRelationship type works? Is there any attribute like that?
Also if there is a document that tells about relationship, could you give us a link? We would like to research deeply.
If it possible, Can you give examples for each type of relationships (Dependency, Migration, Substitution, Exclusivity).
"productSpecificationRelationship":
[
{
"id": "15",
"href": "http://serverlocation:port/catalogManagement/productSpecification/15",
"type": "Dependency",
"validFor":{"startDateTime": "2017-04-19T16:42:23.0Z"}
}
]
OR
"productSpecificationRelationship":
[
{
"id": "15",
"href": "http://serverlocation:port/catalogManagement/productSpecification/15",
"type": "Migration",
"validFor":{"startDateTime": "2017-04-19T16:42:23.0Z"}
}
]
OR
"productSpecificationRelationship":
[
{
"id": "15",
"href": "http://serverlocation:port/catalogManagement/productSpecification/15",
"type": "Substitution",
"validFor":{"startDateTime": "2017-04-19T16:42:23.0Z"}
}
]
OR
"productSpecificationRelationship":
[
{
"id": "15",
"href": "http://serverlocation:port/catalogManagement/productSpecification/15",
"type": "Exclusivity",
"validFor":{"startDateTime": "2017-04-19T16:42:23.0Z"}
}
]
------------------------------
memet harun ozer
PiA Bilisim Hizmetleri Ltd.
------------------------------
Original Message:
Sent: May 23, 2019 07:10
From: Jonathan Goldberg
Subject: TMF620-Product Catalog-Product Specificaiton Resource-productSpecificationRelationship
This is the purpose of the relationshipType attribute in ProductSpecificationRelationship . To give a concrete example, consider the following JSON fragment from a ProductSpecification:
{
"id": "7655",
"href": "https://mycsp.com:8080/tmf-api/productCatalogManagement/v4/productSpecification/7655",
"name": "Cisco Firepower NGFW",
"productSpecificationRelationship": [
{
"id": "23",
"href": "https://mycsp.com:8080/tmf-api/productCatalogManagement/v4/productSpecification/23",
"relationshipType": "Dependency"
}
]
}
In this example, we are saying that a Firewall product spec (ID 7655) is dependent on another product spec (ID 23) , might be business broadband for instance.
Note that ideally ProductSpecificationRelationship is a technical, not commercial relationship. Commercial relationships should be expressed at ProductOffering level. Currently there is no ProductOfferingRelationship in the API model but we hope to add this in release 19.5, and we can expect that it will be very similar to ProductSpecificationRelationship.
Hope it helps.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Original Message:
Sent: May 22, 2019 12:06
From: memet harun ozer
Subject: TMF620-Product Catalog-Product Specificaiton Resource-productSpecificationRelationship
Hi,
How can I define:
- migration,
- substitution,
- dependency,
- exclusivity relationship between/among product specifications.
------------------------------
memet harun ozer
PiA Bilisim Hizmetleri Ltd.
------------------------------