Currently in Creo Parametric 2.0, when an assembly is saved, a conflict dialog box appears listing all of the components that were regenerated, but not checked out. If a user sets components to continue, check out, etc., the save operation completes successfully. However, if the user sets any of the components to Read Only, the save operation fails. If the user saves again, then the assembly saves successfully.
The only notification a user gets that the save has failed is a little note in the message line and the event manager symbol turns red. This has been the source of many lost sessions because the user doesn't notice the messages.
It seems like it would be an easy fix to add some intelligence to the save operation to re-save automatically when something is set to read only during a save operation.
At the very least PTC could make a pop up dialog box that warns the user that the data they worked on all day was not saved.
I submitted a support ticket on this issue, but PTC refuses to acknowledge that it is a bug and gave the standard response, "working to specification".
PTC please fix the save failure bug and allow assemblies to save successfully when sub-components are set to read only during the save operation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.