Skip to main content
6-Contributor
October 1, 2025
Solved

wcadmin adding old describing document back into part on update

  • October 1, 2025
  • 2 replies
  • 846 views

Hi PTC community.

We’ve recently discovered a behavior of the wcadmin user related to Describe by document update.

1. We created a Doc Part NMBP-G1 with Releasable Describe by document NMBP-ICT for its first version.

2. Upon release, it has the “NMBP-ICT” releasable document and a Releasable Report (parts list) linked to it. This is normal behaviour and what we expect to see.

KS_13883962_0-1759278044036.png

 

3. Then I revised the Doc Part NMBP-G1 to version 2.2 via a CN and replaced the “NMBP-ICT” document with a “NMBP-SVD” document as the describe by document.

KS_13883962_1-1759278111184.png

 

4. Then This Rev 2.2 of the Doc Part NMBP-G1 and “NMBP-SVD” document were then released.

5. For some reason, We updated the previous describe by document NMBP-ICT and released on a separate CN. Upon release of Rev 2 of the “NMBP-ICT” document, wcadmin user adds the Rev 2 “ICT” document back in as a describe by document automatically to the original Doc part NMBP-G1 without notification. and also rev up the Doc part to version 2.3.

 

KS_13883962_2-1759278208985.png

 

The history of the Part shows "Describe-by link auto update" .

 

KS_13883962_3-1759278297214.png

 

This is issue for us. We want windchill to stop doing this. or at-least send notification to the subscriber of the part. I hope I have explained the issue. I cant provide the full snap shots because of security reason. 

 

Regards,

Khalid Shamim

 

Best answer by HelesicPetr

Hi @KS_13883962 

No it is not OOTB behavior.

I test it. If I release the revised doc2 that is not part of the last wtpart iteration, the describe by link is not autocreated to the newest one. 

 

DOC1 linked to the old revision

HelesicPetr_1-1759911959712.png

In the WTPart version B.1 I removed DOC1 and added DOC2 

everything has been released. 

latest WTPart with only manually added document

HelesicPetr_2-1759912093425.png

first document was also revised to new revision and released by an ECN

HelesicPetr_3-1759912112226.png

Then I revise the DOC 1 and release new revision. The latest iteration of the WTPart is without any system admin change. 

WTP history table

HelesicPetr_4-1759912270912.png\

Conclusion your system could contains some customization to do what you described.  

 

PetrH

2 replies

Fadel
23-Emerald I
October 3, 2025

so the need to add a described by to a part without iterating ?

Buiꓘa
6-Contributor
October 6, 2025

Thanks Fedel. 

Adding old "describe by document" to Parent part is the issue. as I explained above. Windchill admin added it without notification. so the owner of the Parent part doesn't know a describe by doc has been added. 

HelesicPetr
22-Sapphire II
22-Sapphire II
October 7, 2025

Hi @KS_13883962 

I can see that the iteration comment is Describe By link auto update.

I haven't seen this behavior OOTB yet that system ootb writes any comment to the iteration.

 

So my question is: do you have any customization that do this for you or is it OOTB behavior that I do not know?

 

PetrH

6-Contributor
October 7, 2025

Hi HelesicPetr,

This appears to be out-of-the-box (OOTB) behavior, which I’m generally fine with, unless WCadmin is triggering notifications or email subscriptions to inform the Part owner.

I would like to know where I can adjust this setting or disable it entirely.

HelesicPetr
22-Sapphire II
22-Sapphire II
October 8, 2025

Hi @KS_13883962 

No it is not OOTB behavior.

I test it. If I release the revised doc2 that is not part of the last wtpart iteration, the describe by link is not autocreated to the newest one. 

 

DOC1 linked to the old revision

HelesicPetr_1-1759911959712.png

In the WTPart version B.1 I removed DOC1 and added DOC2 

everything has been released. 

latest WTPart with only manually added document

HelesicPetr_2-1759912093425.png

first document was also revised to new revision and released by an ECN

HelesicPetr_3-1759912112226.png

Then I revise the DOC 1 and release new revision. The latest iteration of the WTPart is without any system admin change. 

WTP history table

HelesicPetr_4-1759912270912.png\

Conclusion your system could contains some customization to do what you described.  

 

PetrH