Changing property "State" in a version?!

Hakro

Why is it possible to change the  property "State" (and other properties) in a version? I thought "versions are view only".

"The first important thing to remember is that you can only edit the State property while creating a version."
<code><a href="https://www.onshape.com/cad-blog/tech-tip-assigning-a-state-to-your-design-in-onshape" title="Link: https://www.onshape.com/cad-blog/tech-tip-assigning-a-state-to-your-design-in-onshape">https://www.onshape.com/cad-blog/tech-tip-assigning-a-state-to-your-design-in-onshape</a>

Works as designed, bug or missunderstanding?

Jake_Rosenfeld

Hi Harko,

The intention here is that creating a version is locking in all of the geometry of the part you are building.  Imagine I create a part, I'm happy with it, and want to send it to be produced.  I will create a version of my part called 'For Production'. Because that model is being sent off to the manufacturer, I change the state to 'Pending'.  The manufacturer finishes their first bach and I begin to sell my product, I change the state to 'Released'.  Then I have to make changes for the next release, branch off to make my changes, and stop producing that version of the product, I change the state to 'Obsolete'.  The state tag is the state of this version of my product.  I would not want to make a new version to change the state tag because that tag refers to the state of this specific revision of my product. A new version would imply that I have made some change to the product itself.

Hope this helps explain our reasoning behind mutable tags.  Best of luck!

Edit: I understand your confusion Harko, that blog post does imply that 'state' can only be assigned while creating a version (@cody_armstrong)

cody_armstrong

@hakro @Jake_Rosenfeld  That sentence is worded poorly.  In my haste to explain that you cannot assign a state to an active workspace, I left out that it can be edited later on.

cody_armstrong

@hakro This is intended. Properties can be edited (assuming you have permission) after a version has been created. They are independent of the model data which is view only. The state property cannot be changed in a workspace. 

Hakro

@cody_armstrong: Changing the “State“ property in  a “view only version“ seems very strange to me. I always thought a version is a “snapshot“ and hence an unchangeable document of all model data, geometry AND properties. Why should I change the properties (especially the state) after creating a “snapshot“. Then it is not a snapshot any more.

What do others think?

Jake_Rosenfeld

Hi Harko,

The intention here is that creating a version is locking in all of the geometry of the part you are building.  Imagine I create a part, I'm happy with it, and want to send it to be produced.  I will create a version of my part called 'For Production'. Because that model is being sent off to the manufacturer, I change the state to 'Pending'.  The manufacturer finishes their first bach and I begin to sell my product, I change the state to 'Released'.  Then I have to make changes for the next release, branch off to make my changes, and stop producing that version of the product, I change the state to 'Obsolete'.  The state tag is the state of this version of my product.  I would not want to make a new version to change the state tag because that tag refers to the state of this specific revision of my product. A new version would imply that I have made some change to the product itself.

Hope this helps explain our reasoning behind mutable tags.  Best of luck!

Edit: I understand your confusion Harko, that blog post does imply that 'state' can only be assigned while creating a version (@cody_armstrong)

cody_armstrong

@hakro @Jake_Rosenfeld  That sentence is worded poorly.  In my haste to explain that you cannot assign a state to an active workspace, I left out that it can be edited later on.

Hakro

@Jake_Rosenfeld @cody_armstrong : Thanks for your detailed explanation. In your point of view it makes sense. Your state prozess starts from design leaving design department with creating a version (start of production) until end of production.  
I interpreted the state as a process only inside the design department. From start of design until end of design. But that is not intended in Onshape and of course will not work because its not possible to change the state in the workspace.
Thanks for clearing up, sorry for confusion.