Skip to main content
Jul 9, 2025 9:35 PM UTC
Acknowledged

Better handling of Document vs Drawing Handling from Windchill (including COMPARE)

Please include detailed documentation such as screenshots, images or video.

1. What product and version are you running?
Creo View 11.1


2. What is the problem?
Reference:

Cases: 17800652 & 17808140

Article: CS447345

 

     There are some key functionality differences between the way Creo View manages a PDF imported as a Drawing vs a Document. As an example, a PDF opened as a drawing can leverage the COMPARE functionality, but a PDF opened as a document can not.

     When opening a PDF from Windchill, the default preference is that it is a "document", NOT a "drawing"! Which means we can't use the COMPARE functionality in Creo View. 

     When opening a standalone PDF, Creo View at least prompts the user whether it should be opened as a document or drawing. 


3. Are you using a workaround? If yes, please describe it.
Kind-of. We used the workaround listed in the article. However, that only works on NEW data in Windchill - not the YEARS and YEARS of data we have in Windchill. Therefore, we really don't have a solution for all of that data.

4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
We design products with artwork, which are stored in Windchill, The visualization should opens the PDF and allow users to compare one version to another without being limited to whether it is a document or drawing. 

5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
It affects hundreds of users, with the inability to create a process with the compare functionality - leading to production issues due to improper checking of data before it is released.

1 reply

Community Manager
Jul 10, 2025 11:19 AM UTC
Status changed to: Acknowledged

Thank you @jwagh for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.