Start a topic
With the exception of Windchill, The PTC Community is on read-only status until April 6 in preparation for moving our community to a new platform. Learn more here
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

The PTC Community is on temporary read only status in preparation for moving our community to a new platform. Learn more here

Translate the entire conversation x

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

Turko
14-Alexandrite

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

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')"
]
}
]
}

ACCEPTED SOLUTION

Accepted Solutions
Fadel
23-Emerald I
(To:Turko)

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

Fede

View solution in original post

6 REPLIES 6
Fadel
23-Emerald I
(To:Turko)

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

Fede
Turko
14-Alexandrite
(To:Fadel)

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?

Fadel
23-Emerald I
(To:Turko)

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

Fede
Turko
14-Alexandrite
(To:Fadel)

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

Fadel
23-Emerald I
(To:Turko)

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

Fede
Turko
14-Alexandrite
(To:Fadel)

Thanks Fede.

Announcements


Top Tags