The community will undergo maintenance on October 16th at 10:00 PM PDT and will be unavailable for up to one hour.
Hello everyone,
Our current 3.4 system the users are allowed to save modified objects to the workspace that are at the “Released” release level and thus are read only.
With 9.1 ProE is forced to “Revise and Checkout” before any files can be saved.
Has anyone figured out a work around to being forced to “Revise” a model in order to save it to the workspace?
Thank you in advance for your help.
Kevin
When you open a Released object in Pro/E and try to modify it, 9.1 prompts you to Check Out, Make Read Only, or Continue.
If you select Continue, you will be able to make changes without checking-out the object, and you will be able to save them to your Workspace, but you won't be able to check those changes in to Commonspace (without some wrangling).
The modified objects will have a symbol next to them in your Workspace that says "Modifications not eligible for Upload".
To "Update" the objects (in 3.4 speak), just re-add them and un-check "Reuse content in target workspace".
Does that answer your question, or are you wondering how to actually set up permissions and release states?