Windchill Ideas

When using the "Save as" funtionallity, the newly created objects inherit the values for all custom made attrubutes. Often these values has to be modified anyway, so the object has to be check out/modified/checked in after the "Save as" Having the ability to modify the values in the "Save as" wizard would reduce the work of copying an object. ... View more

The OOTB "lock" transition can only be used in Promotion Requests. Please implement it also for other Change Objects.   Goal: Lock the edit of the resulting objects (WTParts, EPMDocuments, WTDocuments) as long as the Change Notice is in state "Under Review". That would force the user to do a "rework" so that the resulting objects are unlocked again and the process runs through all needed steps (validations, reviews, update attributes...) again. ... View more

The subject was meant to catch your attention as this is a very important function.  But today it seems like a fairly useless function.  Aside from not being able to navigate within in it (no links) which was already submitted separately, the only obvious awareness to the supersede is if you are on the part and see the icon or by chance are in the correct tab.   With supersede, a user should be able to do replace like substitutes or alternatives.  Especially as when something is superseded, that means it is being replaced by something else.  There should be a function to make it clear when viewing a BOM structure that the superseded part is no longer to be used (maybe highlight in red).  Along with this, there should be a preference to prevent checkin of a BOM if a part has been superseded.  We don't want people doing a save as of an old BOM and carrying over parts that can't be used. There needs be a function that can output the "superseded by" in the XML of the distribution target like substitutes so our ERP can be flagged accordingly.  (We'd obsolete the part in the process)  Back to the subject, what is the point if we can't convey it in our ERP system where parts are ordered from. ... View more

Not always it is supported or intended to start right away with a AutoNumber for CAD Docs. There are cases for import or special features in CAD especially when autonumbering is configured with manual overwrite. It would be great to have a renumber feature for INWORK objects which might be already checked in but did not get released yet - initial revision. After a revise this feature should not be available for that object anymore. Best practice s to use for wtparts same sequence as for CAD Models, CAD Drawings should get there own sequence ... View more

Basically allow a user to do anything to multiple objects that they can do to a single object. This includes but is NOT LIMITED to: RENAME of Multiple unrelated objects from Search page (or folders) [Windchill 11.0 F000] DELETE Multiple unrelated objects from Search page (or folders) [In Roadmap for future release] Change STATE of Multiple unrelated objects from Search page (or folders) (It looks like this one may be implemented in 10.1) (I crossed off Item 3 because I heard it was available in in WC10.1, but since switching we found it is not available under the search results page...so I am re-including it) [Windchill 10.1 M040 Folders, 10.2 M030 Search) Any other action that you can do for one object should be able to be done for many objects from a search page (or folder) There are product ideas submitted for each one of these but I think they all need changing. Some references to other Product Ideas for more details: Rename: http://communities.ptc.com/ideas/1982 /communities.ptc.com/ideas/1982   Renaming multiple objects in Windchill 10.0 Rename: http://communities.ptc.com/message/186891#186891 Set State: http://communities.ptc.com/ideas/1597           Set State for multiple objects Set State: http ://communities .ptc.com/ideas/1597#comment-6727 (to be implemented in 10.1 M040)        https://www.ptcusercommunity.com/ideas/1597#comment-6727 PS. Another example that falls into this category but was not listed above:   5. Purge Non-latest Iterations (Added per comment below on 6/18/2014) PPS: Crossed out broken links and provided new ones. [JZ 12 Jan-16 I am going to close out this idea.  If other actions are needed please open ideas specific to those actions.  It is difficult to try to track these broad "bucket" idea categories] ... View more

A WTPart can have different view versions (e.g. Design View, Manufacturing View, Reduced View, etc.).   To be able to differentiate the view versions better and to avoid selecting the wrong ones (e.g. in the Resulting Objects of a Change Notice...), these should have different icons.   It becomes even more complex / confusing if you work also with different WTPart subtypes and you have for each subtype the possibility to have the different view versions. Therefore a different icon / marker in the icon for different view versions would be helpful. ... View more

Provide the ability for administrator or user to create and save a configuration filter that can be used during Checkout/Add To Workspace. This saved configuration filter could then optionally be set via the existing Preferences: Preferences:                                                               Current Values:                       Additional Value: Set Configuration for Add To Workspace                   Default/Latest/As_Stored              <User Defined> Set Configuration for Check Out                              Default/Latest/As_Stored              <User Defined> Background: We have a need for Latest Released data (or In Work if no version has been Released).  By giving the option of saving the configuration filter, it would allow our needs to be met and also allow for other customers to meet their own needs. There are also some default configuration filters (Latest/Baseline/Promotion Request/Baseline), but these too do not provide Latest Released.  Configuration filters can currently be created each time (8 clicks?), but not stored for use again in the Checkout/Add To Workspace dialog.  From the structure page on a checked in object, there IS the option to Save a configuration filter, but these do not show up during Add to Workspace or Checkout, also these cannot be set via the Preferences shown above. ... View more

Subject: Modification of the Option Pool and Option Set behaviour.   Today the option pool management is linked to a product or library context level. The option set is at the same level and is created by selection in this pool. I can have multiple option set and I can assign them to a product or to a wtpart.     It could be interesting to change the behaviour of the option pool My ideas are the following : I wanted to manage several option pool, at different level for example common option in an option pool at the organisation level and specific option in an another option pool at the product level. It will be necessary to manage option pool independently from the product context level. And the option set could be created by select option in the both (org option pool and product option pool) with inheritance capabilities.    See examples below:         ... View more

Whatever the icons set on WTPart soft types, the uwgm always display the grey one in the WS view. ... View more

From CS146447 Since Windchill 10.2 the value of PTC_WM_CREATED_BY and PTC_WM_MODIFIED_BY contains a bracket with the information “(<username>:<organization name>)" PTC_WM_CREATED_BY and PTC_WM_MODIFIED_BY are system generated parameters in Creo Parametric The values of PTC_WM_CREATED_BY and PTC_WM_MODIFIED_BY will be filled by Windchill during upload The preference User unique identifier display format controls the format string with the following options: 1. User name and organisation 2. Email Please add a third option to this preference to be "User name" only to restore pre-10.2 behavior. ... View more

Allow upload of modified but not check-out object to server-side workspace. The user might have changed the object without check-out for many reasons, eg: by accident, for trying out alternative design, etc. Currently, only new or check-out object can be uploaded to the server-side workspace and it is quite puzzling why modified non-checkout object is not able to upload. The server-side workspace serves a few purposes: 1) As a "backup" of users work in case if the client machines has crashes 2) Allow user to goes to another machine and able to download his work to another machines without exporting to a external drive and carry It seems like the "blocking" of uploading the modified and not-checkout object goes against the use of server-side workspace ... View more

If you are reviewing out of date data, the Windchill object details page shows the text 'Go To Latest". Please make the "Go To Latest" text stand out more - perhaps make the text/cell red and blink. The bottom line - make it more obvious to the user that they are looking at old data. ... View more

Why does the number of objects in a WindChill Workspace have such an impact on performance while working in Pro/E or Creo Parametric?  Our top level assemblies contain more than 60,000 objects, but we can only efficiently work with under 3000 of them in the workspace.  Users are trained to remove objects in the workspace to get performance back when the number exceeds the threshold.  As an example, the simple function of expanding the model tree can take up to 5 seconds waiting for the assembly to be downloaded from the server because it currenlty doesn't exist in the workspace.  I want the missing files in the workspace to be downloaded at the same rate whether there are 10 or 10000 objects existing in the workspace.   ... View more

...one of the last gaps stil open from the Pro/Intralink to Windchill migration. Many CAD users checkin files they have worked on for the sake of promoting them to a higher state. It would be so easy for the users if they would have a "Checkin&Promote" icon in the Workspace that combines Upload, Checkin and startup of the Promotion wizard with the initially selected objects (only in case the upload and checkin was successfull). Currently the users have to go to the Commonspace and locate the objects by search or browse or via the Info Page to start the promote - a time consuming stupid action. In Intalink 3.x this option was available and the users loved it. I have no glue why it was removed and why we do not ask PTC to put it back again. My users would love it - what about you? ... View more

Wouldn't it be nice to know (or filter out) objects where the component is no longer used in a Where Used Report or in the information page for CAD Documents?  It would be nice to at least have a column to identify if it's the latest or what the latest version is. ... View more

Automatic Baseline Creation for Windchill Part Structures on Release: Best Practice when using Windchill Parts is to Create a Baseline on Release of a Product Structure;  This is a manual step. Baseline of Released Structure captures how the BOM Structure looked at Release. This is a Best Practice since Windchill Parts do not have an :AsStored similar to EPMDocuments. The reason is to Capture what a BOM Structure (Ex 8,000 Componennt Assembly) appears when Released at Rev A (say in 2012); This is Useful in 2014 when for Form/Fit/Function Exceptions where 100's of COmponents could be at higher Revisions.  Used by Engineering/Technical Support/etc... to note differences from Initial Approved Released and Current Configuration of a BOM Structure, via Compare Report Functionality. Also used by Companies that Create Unique BOMs for Customers such as simulators.. Where they can use baseline to manage the "As Maintained" Configuration of a Customer's BOM. As this step is Manual, it can be built into Workflow Instructions or Activities.. PRODUCT IDEA: Workflow in Windchill that will Automatic Build a Baseline using Default Collection when a Part/Part Type reaches a certain State. (Similar to ERP Connector KickOff  OR can be built into the OOTB Change Notice Process as a Condition Java Expression)  [A preference determines if it is used of not] This will be useful to new customers who do not realize they need Baselines until 2 years of using Windchill;  Or customers who do not have resources to teach/check users to create Baselines.  Covers the Gap of not having an equavalent AsStored Baseline and not wanting the Overhead of having a Baseline getting created everytime a Part was Checked In. ... View more

Updating out of date objects or canceling changes or both at the same time, can be tedious and time consuming, where if a user could simply just remove the object in question from the workspace and when the parent objects calls for it simply automatically add the latest version back to the Workspace as needed. Windchill already does this in two use cases: 1. Component was suppressed and not added to the Workspace because of dependency setting set to Required. Once unsuppressed, Windchill automatically retrieves the needed component. 2. Object in the Workspace has references to other object (external reference) that were not initially added to the Workspace. Opening such object for editing may result in Windchill fetching the other needed objects. Manually removing objects with dependencies is a similar use case, that would simplify resolving unwanted object conflicts in the Workspace. Example: I have an outdated object that has been modified which is a required dependent in an assembly. I cannot simply Update because it is modified, and I cannot simply Add to Workspace because it is out of date. I also cannot just remove the component from the Workspace because it is required for my assembly. I propose to let the user remove the object no matter what with a warning message that it has required dependencies, and the next time I open the assembly, Windchill should just then retrieve the latest version of that component automatically. ... View more

Enhancement Request: Provide me a way to rename multiple parts in a Windchill Product context folder (IBM garrity for Bruce Baker) Nov 1, 2012 Duplicate with Enable the ability to Rename multiple unrelated objects that already exist in the Windchill PDMLink Commonspace ... View more