topic Re: REST API - Include "Resulting Objects" When Creating Change Notice in Windchill Customization

REST API - Include "Resulting Objects" When Creating Change Notice

Turko — Fri, 20 Feb 2026 04:16:12 GMT

Version: Windchill 13.0

Use Case: The link below explains that it is possible to create add "Affected Objects" to a change task within a change notice when creating the change notice using a REST API call. https://support.ptc.com/help/windchill_rest_services/r2.5/en/?_gl=1*ylfb42*_ga*MjAzNzQyOTYzMC4xNjc4MTcyNTE4*_ga_1QBT6P6HR1*MTY3ODE3OTA5Ni4yLjEuMTY3ODE3OTA5OS4wLjAuMA..#page/windchill_rest_services/example_changemgmt_create_changenotice_mul_tasks.html#

Description:

I have been able to use this script to successfully create a change notice which features a change task with an affected object included on it. I have developed this script further in an attempt to also add "Resulting Objects" (see below). When I add this script into the request body, the interface reports no issues and it seems as though the call runs successfully. When I navigate to the "Changes" section of Windchill, I can see that the change notice was created along with the change task and affected object. However, the "Resulting Objects" table of the change task contains nothing.

Can anybody explain why this might be and if it is possible to add "Resulting Objects" during the creation of a change notice in the same way that "Affected Objects" are?

{
"Name": "Test",
"Context@odata.bind": "Containers('OR:wt.pdmlink.PDMLinkProduct:xxxxx')",
"ChangeNoticeComplexity": {
"Value": "SIMPLE"
},
"ImplementationPlan": [
{
"Name": "WRS_ChangeTask_Deepinset1",

"Assignee@odata.bind": [
"Users('OR:wt.org.WTUser:xxxxx')"
],
"Reviewer@odata.bind": [
"Users('OR:wt.org.WTUser:xxxxx')"
],
"AffectedObjects@odata.bind": [
"Changeables('VR:wt.part.WTPart:xxxxx')"
],
"ResultingObjects@odata.bind": [
"Changeables('VR:wt.part.WTPart:xxxxx')"
]
},
{
"Name": "WRS_ChangeTask_Deepinset2",

"Assignee@odata.bind": [
"Users('OR:wt.org.WTUser:xxxxx')"
],
"Reviewer@odata.bind": [
"Users('OR:wt.org.WTUser:xxxxx')"
]
}
]
}

Re: REST API - Include "Resulting Objects" When Creating Change Notice

Fadel — Fri, 20 Feb 2026 15:01:37 GMT

this needs batch processing see my article https://www.ptc.com/en/support/article/CS447981

Re: REST API - Include "Resulting Objects" When Creating Change Notice

Turko — Mon, 23 Feb 2026 19:04:37 GMT

Hi. Thank you for this. Why is it that the result I am trying to achieve needs to be batch processed and cannot be achieved in the same way that affected objects are added to a change task with a REST API call?

Re: REST API - Include "Resulting Objects" When Creating Change Notice

Fadel — Tue, 24 Feb 2026 08:40:33 GMT

generally its a two step process. the batch is to get everything in one script

Re: REST API - Include "Resulting Objects" When Creating Change Notice

Turko — Tue, 24 Feb 2026 11:02:30 GMT

Do you know why is this the case? Why can you add affected objects in during the change notice creation but not resulting objects?

Re: REST API - Include "Resulting Objects" When Creating Change Notice

Fadel — Tue, 24 Feb 2026 11:08:25 GMT

This is how its designed in 13.0 , it is enhanced in 13.1 https://www.ptc.com/en/support/article/CS435634

Re: REST API - Include "Resulting Objects" When Creating Change Notice

Turko — Wed, 25 Feb 2026 15:25:07 GMT

Thanks Fede.