Release a drawing without a released assembly

[johan.degreef]

Sometime I can put a drawing in released state without the model is being released, sometimes it won't let me.

Why the difference? They have all the same lifecycles. Is there a setting to allow for released drawing without a released model?

[johan.degreef]

Sometime I can put a drawing in released state without the model is being released, sometimes it won't let me.

Why the difference? They have all the same lifecycles. Is there a setting to allow for released drawing without a released model?

[dmorse · Accepted solution]

There is a rule set inside of the Lifecycle definition on transition that checks to see if Children are Released.  If they are not, you cannot Release the drawing.  If this rule is unchecked, then you would be able to Release the drawing without the the Children being Released.  I can't imagine that this would sometimes work, and sometimes not.  There could be several reasons for this behavior:

1. The file you are trying to Release must be using a Lifecycle definition that is different from the model files and does not have this checked.
2. There may be multiple Releases within that Lifecycle definition and one of them is not set to check that Children are Released.
3. Some of the Checks are selected, but not others.  An example would be dependent child vs linked files.

You need to go into your Lifecycle Definitions to find out what needs to be modified, as this discrepancy can wreak some havoc on your processes and your vaulted files.  

[dmorse · Accepted solution]

There is a rule set inside of the Lifecycle definition on transition that checks to see if Children are Released.  If they are not, you cannot Release the drawing.  If this rule is unchecked, then you would be able to Release the drawing without the the Children being Released.  I can't imagine that this would sometimes work, and sometimes not.  There could be several reasons for this behavior:

1. The file you are trying to Release must be using a Lifecycle definition that is different from the model files and does not have this checked.
2. There may be multiple Releases within that Lifecycle definition and one of them is not set to check that Children are Released.
3. Some of the Checks are selected, but not others.  An example would be dependent child vs linked files.

You need to go into your Lifecycle Definitions to find out what needs to be modified, as this discrepancy can wreak some havoc on your processes and your vaulted files.  

[arkad_s]

Hi,

Check also Released Bias view to see what revision of your model is expected by your drawing. When it allows you to move drawing to released state without having latest model revision released then probably expected revision is not the latest revision. See example below:

Non-Released Biased view (showing latest):

Released Biased view:

If drawing expects previous revision then it might let you change a state (as that revision might be released).

Regards,
Arek

[arkad_s]

Hi,

Check also Released Bias view to see what revision of your model is expected by your drawing. When it allows you to move drawing to released state without having latest model revision released then probably expected revision is not the latest revision. See example below:

Non-Released Biased view (showing latest):

Released Biased view:

If drawing expects previous revision then it might let you change a state (as that revision might be released).

Regards,
Arek

[johan.degreef]

@dmorse 

Ok.

"Check that dependent child files are released" was not set on WIP->release, but it was set on Quick Change -> release 

[johan.degreef]

@dmorse 

Ok.

"Check that dependent child files are released" was not set on WIP->release, but it was set on Quick Change -> release