Windchill REST Services Domain Capabilities > Examples for Basic REST Operations > Examples for the PTC Change Management Domain > Creating a Change Object Link
Creating a Change Object Link
You can create a Change Object link between a Change object (Problem Report, Change Request, or Change Task) and a Changeables object by providing the required attributes and the Changeables OID in the request body. You can add any of the Changeables such as a part, document, subtype of a part, or subtype of a document as a Changeable object. To create a Change Object link, both the Change and Changeables objects must exist.
To create a Change Object link such as CIAffectLinks, CRAffectLinks, CNAffectLinks, or ResultingLinks, you must have Read, Modify, and Create permissions.
* 
You cannot add a Change Management Revision (BOM Redline) object as a Changeables object while creating a CIAffectLinks, CRAffectLinks, CNAffectLinks, or ResultingLinks object. If you specify any such object to be added as a Changeables object, the request fails and returns an error.
Example: Creating a CIAffectLinks Object for a Problem Report
This example shows you how to create a CIAffectLinks object for a Problem Report specified in the request URI. This example shows you how to associate a part with the specified Problem Report. You must first reserve the Change object before you run this request. Use the following POST URI with the request body.
URI
POST //Windchill/servlet/odata/ChangeMgmt/ProblemReports('OR:wt.change2.WTChangeIssue:266684')/CIAffectLinks
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"Description": "Link Description",
"ApprovedQuantity": 345.9,
"Changeable@odata.bind": "Changeables('OR:wt.part.WTPart:265193')"
}
Example: Creating a CRAffectLinks Object for a Change Request
This example shows you how to create a CRAffectLinks object for a Change Request specified in the request URI. This example shows you how to associate a part with the specified Change Request. You must first reserve the Change object before you run this request. Use the following POST URI with the request body.
URI
POST //Windchill/servlet/odata/ChangeMgmt/ChangeRequests('OR:wt.change2.WTChangeRequest2:266601')/CRAffectLinks
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"Description": "Link Description",
"@odata.type": "#PTC.ChangeMgmt.RelevantRequestDataLinkItem",
"Changeable@odata.bind": "Changeables('OR:wt.part.WTPart:122556')"
}
Example: Creating a CNAffectLinks Object for a Change Task
This example shows you how to create a CNAffectLinks object for a Change Task specified in the request URI. You must first reserve the Change object before you run this request. Use the following POST URI with the request body.
URI
POST //Windchill/servlet/odata/ChangeMgmt/ChangeTasks('OR:wt.change2.WTChangeActivity2:265086')/CNAffectLinks
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"Description": "Link Description",
"Changeable@odata.bind": "Changeables('OR:wt.part.WTPart:265193')"
}
Example: Creating a ResultingLinks Object for a Change Task
This example shows you how to create a ResultingLinks object for a Change Task specified in the request URI. You must first reserve the Change object before you run this request. Use the following POST URI with the request body.
URI
POST //Windchill/servlet/odata/ChangeMgmt/ChangeTasks('OR:wt.change2.WTChangeActivity2:265086')/ResultingLinks
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"Description": "Link Description",
"Changeable@odata.bind": "Changeables('OR:wt.part.WTPart:265193')"
}