Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Creo View - Microsoft Edge and Adobe PDF PartnershipAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What version of the software are you running?Creo View 9.02. What is the problem? Currently Creo View can be configured to use 'use native viewer for pdf viewer' or the supported versions of Adobe Reader, Adobe Acrobat installed on the local machine for opening pdf files. If you are not using  'use native viewer for pdf viewer'  this means Adobe Reader, Adobe Acrobat has to be pre installed on the device before Creo View is installed, and then for enhancements, performance security and performance to Adobe Reader updated on a regular basis. With the newest partnership between Microsoft and Adobe Adobe Reader, Microsoft Edge and Adobe partner to improve the PDF experience Would it be beneficial to have Creo View support opening pdfs, if Microsoft Edge and Adobe Enhancement Viewer is enabled on the device?  This means, Adobe Reader standalone would not have to be installed and managed on the device , and updates would be bundled into Microsoft Edge releases for not only Edge, but Adobe PDF Enhanced Viewer3. Are you using a workaround? If yes, please describe it.Installing Adobe Reader as pre-requisite for Creo View on every machine4. 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. Managed updates of Adobe Reader via Microsoft Edge Updates, and no longer having to install or manage Adobe Reader on organization estate.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Many

Renaming in Windchill - Add preference for "Change" to New Number and New NameAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What version of the software are you running?Windchill 12.0.2.9 2. What is the problem?There is no preference to make the radio buttons default to "change" when using the Set New Name UI while Renaming.  The optional radio buttons for New Number are Unchanged, Autogenerate, Generate document number based on related Part and Change.  The optional radio buttons for New Name are Unchanged, Same as number and Change.  However, the only options in the preferences menu for New Name and New Number are "Unchanged" and "Autogenerate".  We want the option of  "Change" so the user doesn't have to select these two radio buttons everytime they enter this UI.  3. Are you using a workaround? If yes, please describe it.The workaround is to train the users(and maybe they will listen) and have the user's manually select the radio button for change on New Number and New Name when they enter into this UI.  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.What we want is to eliminate two steps of having the user manually select the two radio buttons of Change on the New Name and New Number.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Extra steps that the user will need to do....and WC10.2 already has the defaults set correctly so we are going backwards when upgrading to WC12 because the user now has to do extra steps that they did not do before.