Windchill REST Services > Windchill REST Services Domain Capabilities > Examples for Basic REST Operations > Examples for the PTC Change Management Domain > Creating a Change Task with Affected Objects and Resulting Objects for an Existing Change Notice
Creating a Change Task with Affected Objects and Resulting Objects for an Existing Change Notice
With this request, you can create a change task or its subtype on an existing change notice:
• With only affected objects associated to the change task created.
• With only resulting objects associated to the change task created.
• With both affected objects and resulting objects associated to the change task created.
* 
Also, with this request, you can create a change task on an existing change notice and associate affected objects and resulting objects to the change task created using CNAffectLinks and ResultingLinks, respectively.
You can create a change task with one or more affected objects and/or resulting objects for an existing change notice by providing the change notice OID, the changeables OIDs that you want to associate as affected objects and/or resulting objects along with the required attributes in the request body.
To create such a change task, you must have Create permission and you must first reserve the change notice for Edit.
* 
In Utilities > Object Initialization Rules Administration in Windchill, when the object initialization rule (OIR) for the type "Change Task" is enabled for the Site context but is disabled on an OIR for the same type for the Product context, the Number attribute cannot be specified while creating a change task as the Site-level OIR takes a precedence in this scenario.
When the OIR for the type "Change Task" is enabled for the Site and Product context each, the Number attribute can be specified while creating a change task as the Product-level OIR takes a precedence here.
A change task can be created according to the defined association rules where the Role A type is a change notice and Role B type is a change task. When Role B is a required role, Cardinality of 1:many denotes that either multiple or at least one change task can be created on an existing change notice. The Cardinality value of 1:1 denotes that only one change task can be created on an existing change notice.
To associate one or more affected objects and/or resulting objects to the change task, the affected objects and/or resulting objects must exist, and you must have Read permission to those. The affected object types and/or resulting object types can be associated to the change task or its subtype according to the defined relationship constraints.
You can add any of the Changeables such as parts, documents, subtypes of parts, or subtypes of documents as affected objects and/or resulting objects.
* 
You cannot associate Change Management Revision (BOM Redline) objects as affected objects and/or resulting objects.
When you do not specify the Changeables OIDs, the request creates a change task for the specified change notice but with no affected objects and/or resulting objects associated to it.
Example: Creating a Change Task with Affected Objects
This example shows you how to create a change task with affected objects for an existing change notice specified in the request body.
In this example, the request creates a change task with four Changeables (here, parts) associated as affected objects.
Use the following POST URI with the request body.
URI
POST /Windchill/servlet/odata/ChangeMgmt/ChangeTasks
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"ActualFinishDate": "2027-04-30T17:12:59.847Z",
"ActualStartDate": "2071-08-01T14:30:00.000Z",
"Name": "CT12",
"[email protected]": "ChangeNotices('OR:wt.change2.WTChangeOrder2:265068')",
"[email protected]": "Containers('OR:wt.inf.library.WTLibrary:265314')",
"[email protected]": [
"Changeables('OR:wt.part.WTPart:122556')",
"Changeables('OR:wt.part.WTPart:123864')",
"Changeables('OR:wt.part.WTPart:123833')",
"Changeables('OR:wt.part.WTPart:123771')"
],
"[email protected]": [
"Users('OR:wt.org.WTUser:12')"
],
"[email protected]": [
"Users('OR:wt.org.WTUser:12')"
]
}
Example: Creating a Change Task with Affected Objects and Resulting Objects
This example shows you how to create a change task with affected objects and resulting objects for an existing change notice specified in the request body.
Use the following POST URI with the request body.
URI
POST /Windchill/servlet/odata/ChangeMgmt/ChangeTasks
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"ActualFinishDate": "2027-04-30T17:12:59.847Z",
"ActualStartDate": "2071-08-01T14:30:00.000Z",
"Name": "CTNew",
"[email protected]": "ChangeNotices('OR:wt.change2.WTChangeOrder2:274265')",
"[email protected]": "Containers('OR:wt.inf.library.WTLibrary:265314')",
"[email protected]": [
"Users('OR:wt.org.WTUser:11')"
],
"[email protected]": [
"Users('OR:wt.org.WTUser:11')"
],
"ResultingLinks": [
{
"Description": "Changing document",
"[email protected]": "Changeables('OR:wt.doc.WTDocument:274359')"
}
],
"[email protected]": [
"Changeables('OR:wt.part.WTPart:274339')",
"Changeables('OR:wt.part.WTPart:274349')"
],
"[email protected]": [
"Changeables('OR:wt.part.WTPart:274339')",
"Changeables('OR:wt.part.WTPart:274349')"
]
}
URI with Expand
You can further expand the URI to create a change task and additionally retrieve information about the resulting objects and affected objects that have been associated to the change task created.
URI
POST /Windchill/servlet/odata/ChangeMgmt/ChangeTasks?$expand=ResultingLinks($expand=ResultingObjects),CNAffectLinks($expand=AffectedObjects)
Was this helpful?