Tc Requirement Structure Synchronize: Fullsynchonization of Requirement structure
This example shows how a full synchronization removes a child from an existing requirement structure.
The JSON document provides an example to synchronize a requirement structure in Teamcenter OOTB data model. The example is based on structure created in Example for Tc Requirement Structure Create Snap. There a structure was created like:
SnapTestSpec |--P1 |--Req1 Desc |--P2 |--Req2 Desc
Now the content of the JSON defines that SnapTestSpec shall only have one child P1. The Tc Requirement Structure Synchronize Snap now has to keep P1 and remove P2.
In the snap configuration following values has to fed into fields
- $ to Structure Data Path
- $.expandAttributes to Expand Attributes Path
[
{
"revisionRule": "Latest Working",
"config": {
"mode": "FullSynchronization",
"match": [
"bl_sequence_no"
]
},
"lineObject": "AqEAAtTW7hAnmD",
"children": [
{
"lineObject": "A_IAAtTW7hAnmD",
"lineData": {
"bl_sequence_no": "10"
}
}
],
"expandAttributes": [
"object_name",
"object_desc",
"object_type",
"object_string"
]
}
]UIDs in Teamcenter are as the name says UNIQUE. The UIDs in the example only exist in our Teamcenter system as expected for our example. Same is valid for Adapter ID "_id" since its base is the UID.
Snap configuration | Snap output |
|---|---|
![]() | |
