Allow a removing WTDocument links from WTPart during save as operation separately

[HelesicPetr]

based on archived idea I rise hand to implement it

When duplicating a WTPart, user should be able to select whether linked WTDocuments shall be linked ... 

Currently, it is possible to set the behavior system-wide whether the copied WTParts should also have links to the previously linked WTDocuments or not.

This is currently possible to set for describing documents and reference documents separately If new copy should be crated.

It would be good if "copy with or without links to WTDocuments" could be set for each WTPart by the user individually in the "Save As" dialog list.

"Copy of WTPart with cutting the Link to the WTDocs individually" has not been implemented.

Please Vote for it.

[olivierlp]

Thank you for publishing your idea. We need more information as specified in the form you saw in the submission process. (Questions below). The more details and context you give, the better.
Please let us know within the next two weeks.

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
2. What product & version are you currently running?
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
4. What is the use case for your organization?
5. What business value would your suggestion represent for your organization?

[HelesicPetr]

Hello @olivierlp,

1. Why ? PTC does not know partners activity roles atc.?

- industry? Transportation, Automotive, Arms industry, Flexo presses, Agricultural machines and more...

2. All actual versions. 11.0 - 12.1.0.0

3. During WTPart save as operation it is possible to create copy of linked WTDocuments. But there are some types of documents which are not suitable to copy and that documents need to be removed from the described or referenced tables manualy. More work for user and also problem with integration if user forgets to remove the document. 

it is more clear?

4. described as point 3... 

5. Much more better relationship with customers, They know that creating a idea has a purpose.

[RME_DH]

---

@HelesicPetr wrote:

Currently, it is possible to set the behavior system-wide whether the copied WTParts should also have links to the previously linked WTDocuments or not.

---

This is certainly a problem at our company as well.  it is essentially a training element now.

I would like to know where this system wide setting is - if you know?

[HelesicPetr]

Hello, @RME_DH, 

In a help center there is point that the behavior is default, which means that can be changed.

I haven't tried to change it but the help center describes a opportunity to do so.

HelpLink

Hope this can help you.

Best Regards

PetrH

[RME_DH]

Thankyou very much @HelesicPetr 

I have sent this to our team to test out on dev environment.  

I still think the idea to select copy/do not copy is a better way forward, as we do have some wtparts that have consistent documents (standards).  however the percentage is very low compared to the ones that don't need to come across with a save as.

[olivierlp]

Hello HelesicPetr, 

Thank you for your idea and the information provided.

[fcoulmeau]

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
Swiss Industry, in charge for Windchill solution deployement.

2. What version of Windchill are you currently running?

We are currently running Windchill PDMLink 12.02.3

3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.

Users copy WTPart to save time by reuse of a existing WTPArt and its documentation (Part Centric). Save as a copy does't allow user to remove link between WPTart and documents (Described and Reference ink types), even if he removes the document in the Save as collector.

The user think that the document is not longer linked to the new WTPart but it is.

If the user need to remove the document link, it will do by modifying the WTPart copy, that creates a new unexpected iteration for the WTPart.

4. What is the use case for your organization?
It should be usefull to allow user removing a WTDocument from the collector for WTPart Save as action. Doing it it should copy the WTPart without a link to the removed WTDocument.

5. What business value would your suggestion represent for your organization?
Actually, users create new WTPart with unexpected documents linked  because they think the document link has been removed during Save As action. And remove later the document link spents time by enrolling WTParts in change management workflow to remove document. That cause huge bottlenecks in change management process.

(Edit from Community Management: we merged this idea into one slightly older and closely related) 

[fcoulmeau]

An ehancement should be usefull and conform to most of the business current use case for all cutommers. Please consider this idea as a good idea.