Skip to main content

Filter by idea status

Filter by product

6851 Ideas

GD&T Advisor: Recognize holes in pattern of groups as patternAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We are working for automotive company. I'm the CAD expert and support for more than 3000 users worldwide. 2. What version of Creo Parametric are you currently running?Currently we are working with Creo 7.0.8.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.Following situation appears when I work with GD&T Advisor.Preset:I have a hole in a group with analysis feature and some planes. This group is patterned. Process:I try to create a tolerance pattern (automatically) from this holes. Problem: The GD&T Advisor does not recognize the holes as pattern, as they are within a group that is patterend. Wanted solution:The GD&T Advisor should also recognize the patterned holes that are within a grouppattern.4. What is the use case for your organization?We have a huge amount of holes that are created by UDF as we have a lot of additional information attached to the holes. Patterns with more than 20 instances in bore plates.The UDF (group) patterns are not recognized by GD&T Advisor and thus we have no benefit from the GD&T Advisor and thus are not using the GD&T Advisor currently.5. What business value would your suggestion represent for your organization?If this would work within the GD&T Advisor we would have a lot of more users for GD&T Advisor (the whole Tool department)

Creo View - View State Compare to report changes in Family Table instancesAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders. I am a CAD checker for a large aerospace and defense company. 2. What product and version are you currently running? Creo View 9.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.When using the View State Compare tool with an assembly file, the structure of the assembly is compared and any changes cause Vies State Compare to report that there are changes. However only when a model has been replaced with a non-associated CAD model does it get reported in the results window as models being deleted/added. Changes between instances of a family table are recognized by the tool, but not reported in the results window. Results when comparing with non-associated model changes:Results when comparing with Family Table instance change: While the geometry compare tool can be used to compare structure, getting incomplete results from View State Compare is less than desirable. It can lead to confusion, missed changes, errors and ultimately additional cost to the program. View State Compare should be updated to report Family Table instances the same way as unrelated models.4. What is the use case for your organization? Verification of changes to MBD based assemblies.5. What business value would your suggestion represent for your organization? As stated above, having incomplete data can and will lead to misses when comparing more complex assemblies/changes which will lead to additional revisions and cost to the programs.

Allow the "Use Parent View Style"-checkbox to also be used in Projection Drawing ViewsAcknowledged

(A similar product idea was created in 2014 by somebody else, but has been archived)1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.All our clients using Creo Parametric2. What version of Creo Parametric are you currently running?Creo Parametric 7.0.x.0 to 10.0.x.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.In the current Creo releases, the checkbox "Use Parent View Style" can only be used in Detail views.This option is greyed out for Projection views. Ideally, it would be useful to also be able to use this checkbox in Projection-type drawing views.Additionally, a new drawing option can then also be created: for example "use_parent_view_style" that can be set to "yes" or "no". (The only way to control the View Style of (projected) drawing views at the moment is through the model_display_for_new_views drawing option - but this also controls the View Style of new Drawing Views, so the addition of use_parent_view_style could help give the user more control over his drawing configuration)  4. What is the use case for your organization?Allow more control over how the view dispay style of projected drawing views are handled.5. What business value would your suggestion represent for your organization?Improve efficiency while working in Creo

Add TOOLKIT APIs for getting/setting column widths of tabulated ProUIList widgetsAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.I am a software developer working in the aerospace industry. We have 47 TOOLKIT applications most of which I wrote. The applications are written using a C++ framework I started creating in the early 2000s that encapsulates all calls to the TOOLKIT APIs.2. What version of Creo Parametric are you currently running? Version 7.0.9.0 is our current production version. Looking to go to 9.X.X.X this year.3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Our applications use 48 resource/GUI files. In these there are 34 ProUIList widgets that define tabulated lists. Tabulated lists allow one to display a table. The width of the columns is set using the TabStops attribute which does not appear to be documented in the User Guide. A user can change the width of the columns interactively. However there are no current APIs for doing this. My request is for the following APIs to be added: ProError ProUIListColumnwidthsGet(char* dialog, char* list, int* count, int** values);ProError ProUIListColumnwidthsSet(char* dialog, char* list, int count, int* values); They are modeled on the existing ProUITableColumnwidthsGet() and ProUITableColumnwidthsSet() APIs. Below is a snippet from our caeselectmodeldialog.res resource file and a sample display of the dialog.4. What is the use case for your organization?See above.5. What business value would your suggestion represent for your organization?Allow proper display of tabulated lists when the content/order of the columns is modified programmatically.

Use Preset Explode if source data is definied in the subassemlies and not only in the top-levelAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We have over 100 designers in the Creo Elements / Direct Modeling environment. We use Windchill in the company. In the company, we use Creo View for visualization. Since we are paperless in assembly and and the other departments, the information needs to be at the Digital Object.2. What product and version are you currently running?Windchill 12.0.2.0 Creo Elements /Direct Modeling 20.4Creo View 7.1.0.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Expect to obtain the Creo Elements / Direct Modeling configurations of the subassemblies in the Preset Explode  of Creo View  Description:In the help you can read that "You can use the Preset Explode function only if the source data has top-level explode states defined".  This is the structure on Creo Elements / Direct Modeling.   The objects are stored in Windchill.The visualization of Sub-Assy1 is a monlith visualization  and the visualization of the Top-Level-Assembly /Tops-Assy is a strutcure visualization. Only the Modeling configruation  off the Top-Level-Assembly is available in Creo View in the Preset Explode    We also expect to obtain the modeling configurations of the subassemblies in the Preset Explode  of Creo View  4. What is the use case for your organization?We have very large assemblies and the assembly is defined in the subassemblies. In the assembly, this means that you cannot see how the components are assembled.  5. What business value would your suggestion represent for your organization?This leads to ambiguities, time-consuming errors and ultimately to costs.

Utility function ProUtilErrPrint() should support all error codes defined in ProToolkitErrors.hAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders. The organization where I work is in the manufacturing industry.In the organization I am responsible for the CAD and PDM system administration as well as for the Toolkit development.I support about 300 Creo Parametric users. 2. What version of Creo Parametric are you currently running? We are currently working with Creo Parametric 7.0.10.0.3. Description of the idea:The error codes are ultimately only integer values, since ProError is of the enumeration type.For debugging purposes, such as output in the Creo message area or log files, it is often very helpful to have meaningful names (strings) instead of just numbers.Here, the ProUtilErrPrint() utility function provided by the Toolkit installation (found in the file \protk_appls\pt_examples\pt_utils\UtilError.c) could be very useful.Unfortunately, this function supports only 18 of the more than 80 existing error codes defined in the header file ProToolkitErrors.h.Of course, a simple workaround would be to create a corresponding function yourself.But our corporate strategy is to always use as much of the standard as possible before customizing.Therefore we would prefer the existing function ProUtilErrPrint() to be extended accordingly and kept up to date!"   Cross reference: This idea is a result of PTC article CS387353.

Restore drawing Show/Erase functionality in order to search all non-displayed dimensions (erased or deleted)Acknowledged

Please vote to restore the ability to show any annotation (dims, notes, axis, etc) on a drawing that is not currently being shown (whether erased or deleted) using a single interface such as the show dialog (or show/erase dialog in WF4).Currently Creo2 only allows the user to show all "deleted" annotations or those that have not yet been shown.  It does not allow the user to show all erased annotations, as was the functionality in ProE wf4.  --------------------------------------------------More details if want to keep reading:There is no acceptable workaround to this loss of functionality.  The Dwg tree has its uses, but the user should not have to rummage through dozens or even hundreds of annotations to find the hidden one(s) that they need simply because the show dialog does not show erased dimensions as it used to.  This comes up in 2 frequently occurring cases:User erased a dimension and now needs to restore it (which is now buried somewhere in the drawing tree, requiring the user to manually click on every erased dimension to see if it is the one they are looking for).User wants to verify that a part is fully dimensioned according to the model(in ProE this was done simply by showing all hidden dims, which show up in a different color, and then the user can easily and quickly make sure that the ones that need to be represented are).In short, this change from WF4 to Creo is a destruction of the efficient show/erase tool, and the 'workaround' is incredibly inefficient and is an abuse of the drawing tree.  Update: Even though we have been on Creo for almost a year, I still get questions like, why can't I find this dimension or axis?  Answer? Perhaps I should tell them that PTC doesn't want you to find it so they hid it in the dwg tree so well that users, the find tool, and the show tool can't find it. Most perplexing is that PTC introduced (broke) this "feature" in WF5, and we are now on Creo3, years later, and it is still not fixed?!?  Maybe in Creo4?

Consistency with Mass Properties reporting from Analysis Ribbon and Model PropertiesAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We design and manufacture high-end electronics. I am the CAD Manager / PTC SME. Stakeholders for this idea include our Creo user community. 2. What version of Creo Parametric are you currently running?8.0.6.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Reference: Case - C15984139 SPR - 13206241 Article - CS352120   We noticed discrepancies in Mass Properties reporting when viewing the results from the Analysis Ribbon vs the Model Properties. If a submodel, within an assembly, has PRO_MP_SOURCE set to Parameters, then the Geometry report from the Model Properties will use those parameter values. However, from the Analysis Ribbon, the Computed  value will NOT use that value. It would seem that the Computed  from the Analysis Ribbon is the same as Geometry from the Model Properties and the Assigned from the Analysis Ribbon is the same as Geometry and Parameters in the Model Properties. The verbiage is not consistent and definitely confusing. Having assigned values get used in a report called Geometry is even more confusing. The idea would be to make the verbiage and behavior clearer, consistent and understandable between the 2 mechanisms.   4. What is the use case for your organization?We have been trying to work out the specifics with setting up mass properties for assemblies. However, it is taking us years to work through some tickets due to confusing behaviors, options that don't really do anything, etc. It is holding us back from getting a clear understanding of behavior. If the SMEs are struggling, then users are surely going to struggle. We use a lot of PCBs in our products, all of which will require alternate mass properties. Now, the Geometry in the Model Properties will report those alternate values, but the Computed will not. 5. What business value would your suggestion represent for your organization?It would enable us to computer mass properties for our products easily and store them in Windchill. It would save a lot of manual effort down stream.

Fix Step File data, when exporting with "Datums" (layers, exploded lines)Acknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We design and manufacture high-end electronics. I am the CAD Manager / PTC SME. Stakeholders for this idea include our Creo user community. 2. What version of Creo Parametric are you currently running?8.0.6.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Reference: Case - C15496755 SPR - 10313631 Article - CS328821   When we export a step file, and check to include "Datums" in includes: 1 - Exploded lines  2 - A new layer for every part that has the same layer. For instance, let's say there are 10 models using layer "3_ALL_AXES". On reimport of the step file, there would be 10 layers with names "3_ALL_AXES_1" through "3_ALL_AXES_10". This makes breaks the whole purpose of layer management. It is a mess. Please fix so we can continue to move forward in our digital transformation journey.      4. What is the use case for your organization?We have the "Datums" checked so we can see export product artwork within the step file. Meaning, we either keep the option and loose layer functionality and show unintended elements, like exploded lined, or we uncheck that option and loose the ability to transfer artwork data (stored as curves).5. What business value would your suggestion represent for your organization?It allows us to move forward with MBD and MBE. Without having the ability for customers to see the step data appropriately, we can't leverage its full potential and move forward.

Enable more parameters in manufacturing for use in relationsAcknowledged

I am a user of Creo 8.0.7.0 ManufacturingI have been using PTC Manufacturing software for 20 years and have hit this limitation of the software many times, recently the topic has come up via the PTC community proving I am not the only one having the same pain.Within manufacturing there are many parameters but not all can be used/referenced for relations, enabling access to more of the parameters (that we know exist) would allow for a higher level of automation and improved consistency. POCKET_NUMBER is an interesting example, it is very valuable to manufacturing, it represents the tool # for the CL data generated but it is a little mysterious in the way it exists and that is OK, we would like more of these. If it is not possible to enable all parameters (model tree, process manager, PPRINT, XML templates, Pro/Report) to be used in the relation editor perhaps as a group of users we can build a list, here are a few to start:•STEP_NUM – the NC sequence number, Step # in process manager•FEATURE_ID – this can be output for PPRINT but not accessible in any other way•NC_SEQUENCE_NAME – another that can be output via PPRINT but not accessible via relations editor•TYPE – this can be added a column in process manager and lists the NC Sequence type but cannot be referenced•OBJECT_ID – this is a column that can be added to the process manager•AXES – 2,3,4,5 this can be added to the process manager•NC_SEQUENCE_CSYS – the pro/report symbol is &mfg.oper.ncseq.csys and MFG_NC_REF_STEP_CSYS is the parameter in an exported XML template or ORIENTATION column from process manager•NC_SEQUENCE_RETRACT – this is also a column option in process manager•COMMENTS – this column can be added to the process manager but it would be nice if we could populate with a relation