Skip to main content

Filter by idea status

Filter by product

6851 Ideas

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

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.

"Delete broken"Acknowledged

1. Describe the ProblemI often find myself plucking through lists of references that have been lost, one by one, to delete the broken ones. There should be some "remove all red". Example: you put a large set of fillets on various edges on a 3D solid. Then you edit the base model such that some of those edges disappear. The Round feature needs fixing, so you Edit it and find yourself with a table where some of the selected edges are marked red, because the do not exist anymore. There you have to select a row and right-click to get a Delete operation - for each, one at a time since you cannot select more than one - and there can be a dozen. In other dialogues, you have to select the row and click a separate button instead, which is marginally better. Sometimes you can select more than one row and delete several in one operation, which is an improvement. Sometimes though, you can select multiple rows but when you attempt to delete them all you find that you only deleted the first (or last) of the selection. It varies depending on where you are. Fillets work one way, Simplified Representations another. There is sometimes a "Delete all" which is not what you want to do. And you can open a Details dialogue to manipulate things further - but what is sorely lacking is a "Delete all red" option to just remove all failing references in one go.2. Are you using a workaround?No, this is manual labor.3. What is the use case for your organization?Use case? I don't know what to write here.4. What impact does this problem currently have on your organization?Annoyances and time consuming.

Color Manager added to View ManagementAcknowledged

1. Describe the ProblemI would like to have a color management system in Creo Parametric.   This would be similar to simp-reps and styles.   I'm not aware of a tool to save different surface/component colors and quick switch back and forth.    2. Are you using a workaround?Just living with having to choose one set of colors or another.3. What is the use case for your organization?The main function would be to be able to save different color configurations for a part and assembly.   One use case is that when engineering its nice to have contracting colors from component to component, but when presenting a product to customers its nice to have the design have surface colors which represent the final product.    This would also have applications in communicating design functions such as identifying machined surfaces, or components with different material properties.  A simple Color Manager would be a nice addition, and then advanced features like rule based coloring could be nice as well, such as •In Color Set 1 "if surface is in a specific Data Reference Group (Reference 1), then make it orange" •In Color Set 2 "if surface is in a specific Data reference Group (Reference 1), then make it Deep Candy Blue"4. What impact does this problem currently have on your organization?There is a additional work to communicate design intent and different design stages. Or, special assemblies are needed to capture color states.

Embed CREO View Settings During WVS PublishingArchived

Problem summary:3D PDFs contain consistent engineering content but can only render small models, making it impossible to send even medium-sized MBD engineering to outside suppliers. This is a sharp limitation on the extent and effectiveness of MBD implementation within existing PTC tools. Enhancement summary: During WVS publishing through Windchill / PLM, embed the source company’s local settings in the resulting CREO View file, so that any other outside company or organization that receives that file and opens it in CREO View (including CREO View Lite) can view its content identical to how the source company sees it. This eliminates the need for 3D PDF to send MBD engineering to suppliers and enables significantly larger models to be sent, since CREO View is a lightweight tool that can handle significantly larger models than 3D PDF. Details:To send MBD data to suppliers (who do not have access to our company’s internal instance of Windchill / PLM for security reasons), the current method is to publish that model to a 3D PDF using a third-party tool, such as ANARK. The use of 3D PDF for sending this data is driven by consistency: a 3D PDF viewed in Adobe always looks the same. Sending CREO View files is not viable at this time: the content will display differently at a supplier than internally, because their local CREO View settings are different from ours. That variation in engineering content is unacceptable, since all parties viewing the content must see the same engineering requirements. Thus, use of 3D PDF is the only viable option to send MBD engineering to outside suppliers for the current state. However, 3D PDFs have a low limit on the size of the model that can be rendered. Models that are medium size or even medium-small (from a CREO Parametric perspective) run very slowly in 3D PDFs, taking a long time to load and render. This slowness even occurs on engineering machines that have large RAM and graphics capabilities (machines that can run CREO Parametric for large assemblies). When such a 3D PDF is viewed on a standard machine – such as those used by suppliers who do not run CREO Parametric or any other CAD tool – they are nearly unworkable and often crash. It is therefore impossible to send our suppliers MBD content of any significant size using 3D PDF. CREO View is a powerful tool, since it uses lightweight models. Its weakness is consistency across companies: the engineering won’t look the same to different companies because the CREO View files do not bring over the source company’s local settings. This inconsistency in CREO View is the reason 3D PDFs are used instead. But if WVS can pull the source company’s CREO View settings and embed them in the CREO View file at the time of publishing, those settings can “ride along” with the CREO View file and therefore cause the model to be viewed consistently at any supplier and internally. To make this approach realistic, CREO View software must be easily and widely available without costly licenses, meaning CREO View Lite must have the capability to read and utilize the settings included in the WVS files for every model that is below the Massive Assembly threshold (since Massive Assembly is a special license for CREO View). This would enable all our many suppliers to install the viewer quickly and easily to process our engineer data, just as they can with Adobe.