Cannot Change state of assembly to released, part from CC restriction

Cannot Change state of assembly to released, part from CC restriction

cadadmin
Advocate Advocate
2,099 Views
7 Replies
Message 1 of 8

Cannot Change state of assembly to released, part from CC restriction

cadadmin
Advocate
Advocate

Hello,

I was under the impression that Vault would "ignore" content center parts within assemblies. I am currently having difficulties changing the life-cycle state of assemblies with content center parts in them to "Released". During check in at the review process state, I do not see the CC item(s) listed. I enter the comment in the comments area and click OK.

 

I click Change State, and select Released and click OK.

 

Error; "One or more files cannot change to the specified state due to errors or restrictions."

 

2018-12-19.png

 

It's a content center part, why doesn't Inventor/Vault ignore it during lifecycle state change to Released?

 

Regards,

Tom

 

0 Likes
Accepted solutions (3)
2,100 Views
7 Replies
Replies (7)
Message 2 of 8

ChSchmidt
Enthusiast
Enthusiast
Accepted solution

Hi Tom,

the message doesn't look like poining to a CC part. But thats not the problem here.

I f you release a component, the components child have to be released too, no matter if CC part or not, which makes sense.

I you implement your categories and lifecycles in the right way you can create a category for standard parts and an appropriate lifecycle and appropriate rules to automatically assign CC parts to the category. This can be done by using a hidden property in the CC parts (boolean, IsContent = true), the CC parts will then be automatically assigned to the standard parts category, the appropriate lifecycle should have the released state as the initial state.

Once you then checkin an assembly with CC parts in it, they will be released automatically, and don't disrupt the release process of your components

 

Best Regards

Chris

Message 3 of 8

cbenner
Mentor
Mentor

@cadadmin

 

You could also edit your lifecycle definition, and on the Released transition, remove the action to check that dependent child files are released.... but this also does not distinguish CC parts, so it would mean that NONE of your children are being checked for a released status.  

Message 4 of 8

cadadmin
Advocate
Advocate
Accepted solution

Chris,

 

 Thank you for your response you got me looking in the right direction. The Vault was setup by our VAR, and it appears that the CC parts were never setup to be auto-assigned to category upon check in and were being assigned to "Base". Of the Lifecycles that were created, CC parts and our "purchased parts" were using Lifecycles called Library components and Library Components Rev-Controlled, both with a simple Lifecycle process and both were set to "work in progress" as a default.

 

I decided to do the following:

  • Create a new Property "Is CC Part" Type Boolean, all files. Map to files in vault select a CC part, Property = Is Content
  • Created a new lifecycle definition by copying Simple Release Process to a LifeCycle Definition named Content Center Simple Release Process and Changed the default Lifecycle state to "Released".
  • Copied the existing Category named Library Components as Library Components Content Center and assigned the lifecycle definition Content Center Simple Release Process
  • Assigned a Category rule for Library Components Content Center and rule conditions. *Moved to top of list.

Source: Introduction to Categorizing Inventor Content Center Files

 

In initial testing it looks as though everything is working as we would like. Time to learn, implement and test was roughly 1.5 hours which is less time than we spent spinning our wheels yesterday. I overlooked one item and at first nothing worked. Finally I tried reorganizing the rule Content Center Simple Release Process to the top and had success! I appreciate the help!

 

Regards,

Tom

0 Likes
Message 5 of 8

ChSchmidt
Enthusiast
Enthusiast

Hi again,

sounds all good to me!

In addition to the rules for Content Center I forgot a detail about that.

If you use pre products e.g. for frame generator or routed systems, then you will need 2 additional rules, because the pre products carry also the IsContent property as true, and would then be assigned to the standard parts category and would be released as sonn as you check in.

To assign these components to your standard lifecycle like all other self made parts you have to catch them before they get assigned as standard parts, so these rules have to be the top rules in the list:

 

- for frame parts: property G_L is not empty & file extension is IPT & & direction file to Vault

- for routed system parts: property PL is not empty & file extension is IPT & direction file to Vault

 

You have to create 2 Vault Properties (text format) and map them to G_L and PL, and take these for the rules.

 

Best regards

Chris

 

 

0 Likes
Message 6 of 8

cadadmin
Advocate
Advocate

Chris,

 

 Currently we do not use Routing, but in the future may use the Frame Generator. I am trying to follow your instructions for adding the items in Vault for that but I'm stuck here:

 


@ChSchmidt wrote:

 

 

- for frame parts: property G_L is not empty & file extension is IPT & & direction file to Vault

 

  


as I'm not sure how to get the "& Direction file to vault" within the rules 

 

Rule G_LCapture.JPG

 

Could you please clarify? Thank you again!

Regards,

Tom 

 

0 Likes
Message 7 of 8

ChSchmidt
Enthusiast
Enthusiast
Accepted solution

Hi Tom,

sorry for the confusion, you need the write direction file to Vault not in the rule but in the setup of the Vault property mapping.

 

Best Regards

Chris

Message 8 of 8

cadadmin
Advocate
Advocate

Chris,

 

 Thank you again, that did the trick and I appreciate it greatly!

 

Tom

0 Likes