Version: Windchill 13.0
Use Case: Windchill is automatically re-linking a previously removed "Describe-by" document (NMBP-ICT) to a part (NMBP-G1) after the document is revised and released, even though a new document (NMBP-SVD) was already assigned. This auto-update, triggered by the system user wcadmin, also increments the part's revision unexpectedly and without notification, causing unintended changes in released data.
Description:
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.
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.
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.
The history of the Part shows "Describe-by link auto update" .
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
