Creating a Driver Link for an Existing Non-revisable Regulatory Submission
A driver link exists between an existing regulatory submission and the driver object associated with it.
 |
To add a driver object to an existing regulatory submission, the driver object type must adhere to the association type that is defined in the association rules for the regulatory submission.
|
This example shows you how to create a driver link for an existing non-revisable regulatory submission. This example shows you how to create a driver link by specifying the regulatory submission object in the request URI and the driver object in the request body.
In this example, the association type, that is, Role B Type for the non-revisable regulatory submission is set as Part in the association rules.
Use the following POST URI with the request body.
URI
POST Windchill/servlet/odata/RegMstr/RegulatorySubmissions('OR:com.ptc.qualitymanagement.regmstr.RegulatorySubmission:256705')/DriverLinks
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"@odata.type": "#PTC.RegMstr.DriverLink",
"Driver@odata.bind": "Drivers('OR:wt.part.WTPart:125644')"
}
"@odata.type": "#PTC.RegMstr.DriverLink",
"Driver@odata.bind": "Drivers('OR:wt.part.WTPart:125644')"
}
The request adds the specified part as a driver object to the non-revisable regulatory submission.
The request creates a driver link between the specified non-revisable regulatory submission and the driver object that is associated with it.