Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Add “Recent Directories” to the Select Working Directory FunctionArchived

1. Describe the Problem Hi Creo provides a helpful list of recently opened files, which allows quick access without repeatedly navigating through the file system. However, when selecting a Working Directory, the user must manually browse to the desired folder every time. There is no option to choose from a list of recently used directories, even though switching Working Directories is a frequent and repetitive action.   In my estimation, adding such an option is not complex, yet it would provide significant value to all users.   2. Are you using a workaround?The only available workaround is to create Windows shortcuts or use the Windows Favorites section to store commonly used project folders. Another option is to start Creo directly from a specific folder. These workarounds are external to Creo, not integrated into the user interface, and they are not practical when switching between multiple project folders.3. What is the use case for your organization?Our team works on several projects in parallel, and each project has its own dedicated Working Directory. Users frequently switch between these projects depending on their tasks. Each switch requires setting a new Working Directory, and currently this involves manual navigation to the correct folder every time.4. What impact does this problem currently have on your organization?Our team works on several projects in parallel, and each project has its own dedicated Working Directory. Users frequently switch between these projects depending on their tasks. Each switch requires setting a new Working Directory, and currently this involves manual navigation to the correct folder every time.Status changed to: ArchivedHello,We are archiving your 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.

Increase search limit beyond 14000 itemsArchived

1. Describe the ProblemWhen working with large assemblies, it is easy to perform a search operation that exceeds 14000 items.  Creo currently just gives you that subset and there is no way to find the additional items above this.  User has to resort to starting from lower level subassemblies to reduce each individual search action.  This limit applies to searching for anything.I am running into this repeatedly for large assemblies transferred into Windchill from Elements Direct when I search for coordinate systems.  I need to hide all the crazy coordinate systems that come over unhidden, but if I cannot find them all in one shot, this process becomes tedious.2. Are you using a workaround?Work around is to select all the first level subassemblies, one at a time and search those separately. For particularly large subassemblies, even those might run into the 14000 object limit and going a level deeper is needed.3. What is the use case for your organization?After checking a large Elements Direct assembly into Windchill through Workgroup Manager, when the assembly is opened in Creo, it is needed to hide most of the spurious default coordinate systems and only show those that were created by name in Elements. Current procedure is to search for all coordinate systems and Hide, then go back and search for the named systems and Show. Increasing the object limit would allow processing large assemblies more efficiently.4. What impact does this problem currently have on your organization?Reduces efficiency of processing large assemblies when search is needed returning object counts exceeding 14000 items.Status changed to: ArchivedHello,We are archiving your 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.

Repeat region support for multi-detail drawings (Column Models with BOM Balloons and bulk items)Archived

1. Describe the ProblemIn a drawing that details more than one model, such as an assembly with two configurations, the repeat region cannot handle it, with two major disabilities and one minor.No BOM balloons. According to CS102227 you cannot create BOM Balloons for a repeat region using column models. You have to create them by hand, and then they are not parametric.No bulk items. The quantity for bulk items is shown as 1. You cannot alter it with relations and show it as "AR" (As Required), you have to place a note over the 1 to hide it in the R. This is the kind of fakery that we are trying to avoid and should not rely on as a best practice.Adding columns on the edge of a repeat region puts them outside the repeat region. You have to add them inside the edge column, which makes expanding an existing table unnecessarily complicated.Here's an example. But in this example, the workaround chosen was to add a dumb text column to the left of the repeat region, and several more rows of dumb text above the repeat region, which then makes the BOM table not sorted correctly, BUT it supports BOM balloons and bulk items.So what Creo offers is a choice. You can have a functioning parametric BOM, or you can have balloons and bulk items. But not both. 2. Are you using a workaround?Add a column inside the first column, change the quantity columns to rpt.qty, set the column models appropriately, then put manual balloons everywhere and cover the bulk items with fake notes. OR create secondary tables with repeat regions outside the drawing borders, one for each configuration, fix the index on every item to match the index in the combined BOM, and create balloons off of them. THIS IS THE RECOMMENDATION FROM PTC! It's fakery and not parametric, either way, and it's cumbersome extra work, easily done incorrectly even with templates set up for it. The most common workaround I've seen by far is giving up, removing the repeat region and entering it all as text.3. What is the use case for your organization?We would use it to create our multi-detail drawings, which can have any number of configurations on the same drawing number.4. What impact does this problem currently have on your organization?We use multi-detail drawings a lot, but it seems like everyone has to relearn how to do it every time. Like it has to be custom built for each drawing, even with a template. And essentially it does. This is a fundamental shortcoming in Creo's drawing mode, it always has been, but that's no reason to let it always be.Status changed to: ArchivedHello,We are archiving your 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.

Modelcheck condition if the part contains an imported feature.Acknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders. We work for Schneider Electric multinational company that specializes in digital automation and energy management.  My role in the organization is Mechanical Platform Solutions Architect and our stakeholders are all  of our Business representatives who spoke for all company designers.2. What version of Creo Parametric are you currently running?Creo Parametric 8.0.23. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.we have a model check configured to review and mark an error if a flexible modeling feautre is present.however there are use cases where we have imported model coming from neutral files or other CAD systems and we want to apply a condition if an imported feature exists it does not mark an error if flexible modeling are founded.there is a similar functionality with Pipe featureshttps://www.ptc.com/en/support/article/CS1025124. What is the use case for your organization?We want to identify flexible modeling features and mark an error if they exist but also allow the usage of this features if they come from imported feautre (neutral files or other CAD Systems, Creo unite, etc).5. What business value would your suggestion represent for your organization?It will ease the adoption from people coming from other CAD Systems.

ModelCHECK "Required Relations" block capabilityAcknowledged

1. Describe the ProblemIn Creo Parametric it can be helpful to have a common required block of relations to drive company standard attributes or calculations.    For normal relations and comments ModelCHECK will only check for the existence of a relation or comment.  There is no position check.     (For solve blocks ModelCHECK does understand order dependance).   2. Are you using a workaround?Manual Checking3. What is the use case for your organization?Checking of models prior to release for compliance to company standards. I want the relations to look like /*Begin Required Common RelationsCDA_CAGE_CODE=CAGE_CODE/*Comment About Contract Number Should Be BelowCONTRACT_NUMBER=CONTRACT_IDENTIFIER/*End Required Common Relations But this will pass /*Begin Required Common Relations/*Comment About Contract Number Should Be Below/*End Required Common RelationsCDA_CAGE_CODE=CAGE_CODE/*Comment About Contract Number Should Be BelowCONTRACT_NUMBER=CONTRACT_IDENTIFIER Using this configurationPRT_COMMENT Begin Required Common RelationsPRT_RELATION CDA_CAGE_CODE=CAGE_CODEPRT_COMMENT Comment About Contract Number Should Be BelowPRT_RELATION CONTRACT_NUMBER=CONTRACT_IDENTIFIERPRT_COMMENT End Required Common Relations Notes1) I was also going to test the "RELATION_UPDATE_FILE", but I don't see a way to specify part vs assembly.2) It would be good if the check would also report if there are additional copies of the lines in other parts of the relations.    For instance has "/*End Required Common Relations" been repeated multiple times.4. What impact does this problem currently have on your organization?Currently manual checking steps are needed to ensure the correctness of the relations.

Piping Module - Allow Users to Specify Minimum Inside Bend RadiusArchived

1. Describe the ProblemIn the Piping module, the designer specifies a minimum centerline bend radius in the line stock. However, many hose suppliers specify the minimum inside bend radius of their hose stock. There is no way to directly input inside bend radius as a requirement in the line stock.2. Are you using a workaround?The designer can add the hose's cross-section radius to the centerline radius that is specified in the line stock.3. What is the use case for your organization?The ideal solution would enable the designer to select, in the line stock menu, whether they want to specify inside bend radius or centerline bend radius.4. What impact does this problem currently have on your organization?Our organization uses the piping module for flexible hoses for several components on every engine project. Therefore, all projects in the organization are impacted. The primary impact now is that most designers specify the supplier's inside bend radius as the CL bend radius and therefore have not properly accounted for the bend requirements. This drives packaging issues on the real product, where the hose does not bend as expected in real life compared to the 3D layout. This can, if the nominal clearance was small enough, lead to interferences and design recycle.Status changed to: ArchivedHello,We are archiving your 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.

Start with CreoView Lite and if needed toggle to get MCAD without exiting the tool:Acknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?Creo View 9.1.0 and CreoView 10-1-02. What is the problem?End-users wants to start with CreoView Lite and when needed toggle to MCAD without the need to restart CreoView. Consider a company with around 11500 end usersConsider 2 packages in this company: one for CreoView LITE and one for CreoView MCAD 2/3 of users applied for CreoView MCAD1/3 of users applied for CreoView LITESometimes, MCAD users just need to visualize small parts, in which case LITE would suffice.Sometimes, LITE users need to change the color of a component, in which case they need MCAD.Given the large number of CreoView users, CreoView MCAD is dedicated to some activities. (licenses) Scenario 1: CreoView LITE user.- user needs to visualize a small 3D model to verify something.-  when geometry is loaded, he needs to highlight some items and create an annotation that is kept in Windchill               ==> to highlight the geometry, he/she would like to change the color to gray out the entire assembly except 2 components.               ==> But this action can be performed with CreoView MCAD only and he/she start MCAD.               ==>The user exit CreoView and complain. Scenario 2: CreoView MCAD userUser needs to visualize a small 3d modelsAs it’s a small assembly, he/she chooses CreoView Lite in the CreoView Startup box  He/she visualizes the 3d models, perform some measurements and close CreoView.One or two days later, the same user needs to open a large assembly.He/she forgets to switch to CreoView MCAD in the startup box as he often starts MCAD and starts LITE instead.After some time, he/she receives this error message “the memory needed for the last operation requires the Massive Assembly License Option Click [Exit] to close the application”.Sometimes he/she realized he/she forgot to choose MCAD at the startup, sometimes he/she creates an incident. And now the user will never toggle to LITE and always starts MCAD grabbing a MCAD license even if not necessary. Advantage to start with CreoView Lite and if needed toggle to get MCAD without exiting the tool:Advantage to start with CreoView Lite and if needed get MCAD features without exiting the tool.No risk for the end users to start LITE instead of MCAD.A single package for all CreoView usersMassive assembly license could be loaded when required.3. Are you using a workaround? If yes, please describe it.no workaround4. 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.please look chapter 25. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.) More than 11500 users in the company.  

Ability to copy component name from the assembly model treeAcknowledged

1. Describe the Problem Hi,   In Creo, it is not possible to easily copy the name of a component (part or assembly) directly from the Model Tree.Copying a component name is possible only through workarounds. For example, one method: opening the component, selecting Save As, and then copying the name from the File name field. This approach is cumbersome and inefficient.   In many workflows, component names need to be copied, for example to paste into documentation, search dialogs, or to re-insert the same component into the assembly using the Assemble command.   Adding the ability to copy a component name (only text) directly to the Mini Toolbar in the Model Tree would significantly improve productivity and usability.     I believe that this enhancement will increase the usability and efficiency of Creo users.It is a quick win that likely requires only a few hours of development time but has a big impact on usability and efficiency.   Thnaks. 2. Are you using a workaround?Opening the component, selecting Save As, and then copying the name from the File name field.3. What is the use case for your organization?It is often necessary to re-insert the same component into the same or another assembly using the Assemble command. Component names are also copied for searches within Creo or in the PLM system. Currently, this can only be done through cumbersome workarounds, which reduces efficiency and increases the chance of errors.4. What impact does this problem currently have on your organization?The current lack of an easy way to copy component names forces users to rely on cumbersome workarounds, which slows down workflows, increases the risk of errors, and reduces overall efficiency when managing assemblies or performing searches within Creo and the PLM system.

Creo Elements Direct License Server 20.8 not supportable if you cannot access the web interface fromImplementation In Progress

1. Describe the ProblemCED License Server 20.8 not supportable if you cannot access the web interface from the client computerHello all.The new CED License Server 20.8 is not supportable if you cannot access the web interface from the client computer.For example, if a user reports that he does not receive a license, it was previously possible to access the web interface via a web browser with:http://SERVER-Name:17171to access the MELs and check whether licenses are still available or whether the license server service is running at all.This is no longer possible with CED License Server 20.8 and is therefore no longer supportable.Then at least the possibility MUST be created that you can check from every client computer whether the license server is accessible and whether licenses are still available, as in FlexNET with the ptcstatus.bat.So the CED License Server 20.8 is not really applicable and usable.Best regards,Christiane2. Are you using a workaround?No there is no workaround.3. What is the use case for your organization?There must be a way to query the licenses from the client computers. One option would be similar to Creo Parametric, where the availability of FlexNET or the existing licenses can be queried from each client computer using ptcstatus.bat.4. What impact does this problem currently have on your organization?The MELs cannot be supported in this way.