Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Windchill Status and Windchill Actions for Creo DrawingsAcknowledged

1. Describe the Problem When Creo Parametric is connected to a Windchill session, the 3D model tree automatically gets the super helpful Windchill status column. This helps users understand statuses like Checked Out, Out of Date, etc without having to constantly check the Workspace. Unfortunately, there's no similar functionality for 2D drawings. Please add the same ability for 2D drawings so users can quickly know if the drawing is Checked Out, Out of Date, etc. without having to track it down in the workspace. It would also be helpful to have the Windchill actions (Check out, Update, Lock File, etc.) available via right click in the drawing model tree.   2. Are you using a workaround?User has to manually check their workspace for this information which can take 30 seconds or more if there's a lot of objects in the workspace. User's often forget to check. We've added a custom Windchill tab to help with the lack of Windchill quick actions. We added the following buttons: Check Out, Save and Upload, Update Current, Undo Check Out, and View Server Properties. 3. What is the use case for your organization?Helping users know if the the local version of a drawing is out of date and needs to be updated. Quickly perform Windchill actions on the drawing. Same reasons PTC added the Windchill status and right click actions into the 3D model.4. What impact does this problem currently have on your organization?Users looking at out of date drawings without realizing it. Extra time to update, undo check out, etc. Having to customize the Creo UI to display Windchill actions.

Creo View NavigationAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo View 10.12. What is the problem?Navigating through the model means moving the model itself3. Are you using a workaround? If yes, please describe it.I'm using a spacemouse with all the controls inverted to simulate flying around the model, however, its still wonky due to center of rotation being around an object instead of center of the camera.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.Unified navigational controls between BCA and BDS. BCA uses IVT which works in this fashion where the model is stationary and what moves is the camera. This can be set up with/without a spacemouse. Without the spacemouse, the controls would look like this, and most importantly, they would be movements to the camera, not the model:W - forwardA - leftS - backwardD - rightX - downSpace - upQ - rotate anti-clockwise about y axis (z axis is up, x is left/right, y axis is forward/backward)E - rotate clockwiseZ - rotate anti-clockwise about z axisC - rotate clockwise about z axisF - gyroscope toggle (z axis remains up)Right mouse-button click - single click toggle to enable/disable looking around (camera angle changes based on where mouse is pointing, but camera position does not change)Mouse scroll-wheel - change flying speed With a spacemouse, all the keyboard controls and mouse look-around would be replaced with the spacemouse movements, with the shared controls being flying sensitivity via scrollwheel, and a toggle for gyroscope (z axis will remain up).5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Anyone transferring from BCA to BDS or working a BDS SOW where they'd be using Creo View would have to go through a navigational learning curve. This translates to several users spending several hours due to several moments of trying to navigate in one way, and receiving a different response from the program.

Pro/TOOLKIT: Enable Adding Varied Items to an Already Flexible Assembly ComponentAcknowledged

1. Describe the ProblemThe current Pro/TOOLKIT API lacks an essential capability related to flexible assembly components — it is not possible to add new varied items to a component that is already flexible.At the moment, this can only be achieved through complex workarounds, and even then, only partially.To add a varied item using Toolkit, the existing flexibility must first be removed and then re-applied via ProAsmcompFlexibleUnset() and ProAsmcompFlexibleSet(), passing all previously defined varied items (ProParameter, ProFeature, ProDimension, ProGtol, ProSurfFinish, and ProMaterialItem) along with the new one.This approach introduces multiple issues:Existing varied items are lost when flexibility is unset, so they and their corresponding new values must first be collected using visitor functions before unsetting flexibility.After resetting flexibility, the new values are not automatically restored, requiring another iteration to manually reassign them.Varied materials (ProMaterialItem) cannot be retrieved through Toolkit — ProVariantfeatItemsVisit() does not visit model items of type ProMaterialItem. As a result, flexible materials and their values are permanently lost, and there is no way to determine whether they existed in the first place.This significantly limits automation and increases the risk of data inconsistency or loss during Toolkit-driven operations.2. Are you using a workaround?A partial workaround exists but does not cover all use cases and carries the risk of losing flexible material information, making it unreliable. The workaround is based on the approach from PTC article CS316199, which involves:1. Visiting and storing all varied items using ProVariantfeatParamsVisit() and ProVariantfeatItemsVisit().2. Unsetting flexibility with ProAsmcompFlexibleUnset().3. Reapplying flexibility using ProAsmcompFlexibleSet(), passing the previously stored varied items. However:- The varied items are preserved, but their new values are lost.- To restore values, the additional steps from article CS454875 must be implemented — visiting and storing all varied items and their new values before unsetting flexibility, and then manually reapplying those values after resetting it.- Even after following all of the above, varied materials remain unrecoverable, as ProVariantfeatItemsVisit() does not recognize model items of type ProMaterialItem (see article CS453209). Thus, even the most comprehensive workaround fails to fully replicate the native Creo Parametric behavior.3. What is the use case for your organization?In Creo Parametric, flexible components can only be defined individually through the user interface, requiring significant manual effort when multiple components must be configured similarly. Our organization is developing a Toolkit-driven automation that allows users to select multiple assembly components (flexible or non-flexible) and apply flexibility in a single operation. The tool automatically:- Adds a predefined flexible parameter to each selected component, and- Sets its desired flexible (new) value. This automation saves significant time for developers, particularly in assemblies containing numerous components. However, due to the current Toolkit limitation, we cannot reliably modify or extend flexibility for already flexible components — especially when varied materials are involved.4. What impact does this problem currently have on your organization?Approximately 200 users in our organization are affected by this limitation. In Creo Parametric’s UI, adding a varied parameter and assigning its value to an already flexible component typically takes around 10 seconds per component. In many real-world use cases, developers need to apply this operation to 30–40 components at once, which translates to 5–7 minutes of repetitive manual work. Our planned Toolkit automation would perform the same operation for all selected components in about 10 seconds total. This means a time saving of roughly 5–7 minutes per operation, per user. Given that this task is performed daily across multiple projects and users, the cumulative time saving would reach dozens of developer-hours per week, significantly improving productivity and reducing manual errors.

ModelCHECK check for view-related layer status in drawingsAcknowledged

1. Describe the Problem There is currently no ModelCHECK check for determining view-related layer status in drawings.   drawing dependent layer statusview-related layer status 2. Are you using a workaround?Some users activate the layer object selection in drawings so that the colored view frames are displayed. The color of these frames can at least visually indicate whether any view has a view-related layer status set.3. What is the use case for your organization?In principle, it's only very rarely necessary to set a view-related layer status, but sometimes there is no way around it. If you aren't the creator of a drawing that you are currently editing, you often don't notice whether view-related layer status are available. And in my company there are several hundred Creo users, which means that it's very common to have to change drawings from other people or to use them as templates for new drawings. It would be very helpful if ModelCHECK could report view-related layer status.4. What impact does this problem currently have on your organization?It often happens that Creo users want to control the display of drawing elements by changing the drawing layer status. At first glance, this doesn't seem to work for individual views and they then contact the CAD administrator in IT. And even the CAD administrator sometimes doesn't realize that the cause of the display problem is simply a view-related layer status and creates a support case at PTC. So it sometimes takes a long time and costs time (and money) to find the cause of the problem, which is actually easy to fix.

Enhancement Request: Add Orthogonality Validation for Coordinate System Creation in CreoArchived

1. Describe the ProblemDescription:When creating a coordinate system in Creo, the software currently allows users to select three planes that are not perfectly perpendicular to one another. This behavior can cause significant issues during the manufacturing process. In our workflow, we frequently use product surfaces directly as references for coordinate systems. However, some of these surfaces are only approximately perpendicular rather than exactly 90 degrees. As a result, this leads to errors during NC programming and machining.Proposed Improvement:We would like to propose that Creo include an additional validation or option when defining a coordinate system:Automatically verify that the three selected planes are mutually orthogonal.If they are not, the system should either prevent the creation of the coordinate system or display a clear warning to alert the user.Benefit:This enhancement would help users avoid potential machining errors, improve manufacturing accuracy, and ensure consistent coordinate definition standards across teams and projects.2. Are you using a workaround?No, currently there is no effective workaround. Users must manually ensure that the selected planes are perpendicular, which is time-consuming and error-prone.3. What is the use case for your organization?Our organization uses Creo for product design and manufacturing preparation. During NC programming and machining, we often define coordinate systems based on product surfaces. However, when these surfaces are not perfectly perpendicular, it can cause errors in toolpath calculation and machining accuracy. Therefore, we need a function to ensure or validate that the coordinate system planes are orthogonal.4. What impact does this problem currently have on your organization?This issue causes errors during NC programming and machining because non-perpendicular planes lead to inaccurate coordinate systems. It increases rework time, reduces machining accuracy, and sometimes requires manual correction of toolpaths. Overall, it impacts production efficiency and increases the risk of manufacturing defects.Status changed to: Archived 2026-07-06We are archiving this idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.You can always post a new idea with all the details required in the form.Thank you for your participation.

When an annotation flips the associated symbol should followArchived

1. Describe the ProblemIn some cases Creo will automatically "flip" an annotation to the other side of it's leader, if a symbol is associated to the annotation the symbol will no longer appear to be located correctly in relation to the annotation.  PTC says this works as designed currently.  So the request is to have the associated symbol "flip" when the parent annotation flips so that the symbol maintains it's relative location to the annotation.  The attached video illustrates the issue very well.  It's worth noting that fixing this manually is fairly easy in the example shown where it is a discreet model, but there really is no fix for family table models.2. Are you using a workaround?Reposition the symbol when there is a discreet model. However if it is a family table instance there is really no way to fix this other then having unique annotation sets for each family table instance.3. What is the use case for your organization?This occurs with many annotated family table models which vary in size from instance to instance.4. What impact does this problem currently have on your organization?Annotations appear very messy in some family table instances and if that is not acceptable then each instance needs to have it's own set of annotations.Status changed to: Archived 2026-07-06We are archiving this idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.You can always post a new idea with all the details required in the form.Thank you for your participation.

When editing a dmt file the first color in the file should be sorted alphabetically like all others!Archived

1. Describe the Problem Reference: Case: 17891712 Article:  CS451598   We had created a few custom appearance .dmt files many years back and only recently noticed that all colors are sorted alphabetically (good) except for the first color in the .dmt file (bad)! In our mind, it should have been alphabetical! The response from PTC, in the article, says "The reason to sort the default color first is so that it is easily accessible for users to restore to its default setting." I'm not sure that is intuitive to the user. We weren't aware of this 'exception' for many years. If someone wanted to sort it first, they could always rename it such that is is earlier in the alphabetical sort!   2. Are you using a workaround?Editing the .dmt file, such that the first color is the first one of the list alphabetically. That means, that if we ever add a color which should be sorted even earlier, we need to remember to put it in the beginning of the file.3. What is the use case for your organization?Managing custom appearance files.4. What impact does this problem currently have on your organization?Ease of use for the users, without it seeming that it it another Creo 'bug'.Status changed to: Archived 2026-07-06We are archiving this idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.You can always post a new idea with all the details required in the form.Thank you for your participation.