Vault General

Reply
Valued Contributor
Posts: 60
Registered: ‎12-06-2012
Message 1 of 9 (281 Views)

rule based category and lifecycle change

281 Views, 8 Replies
02-05-2013 10:33 PM

 

 

I want to be able to set my vault to change categories from internal documentation to external documentation ,

so as I reached revision G ( released for production) , can I set up a rule in vault then to change the Category from internal docs to external docs automaticly, and then use revison scheme numerical  from there on tinstead off alphabeticlly , and ad differant  lifecycle?

*Expert Elite*
cbenner
Posts: 2,827
Registered: ‎04-06-2010
Message 2 of 9 (270 Views)

Re: rule based category and lifecycle change

02-06-2013 04:52 AM in reply to: jacoj

I believe this should be possible.  Create a Category rule using the Rev Number property, set to "is" whatever rev you want to be the trigger, "G" perhaps.  This SHOULD trigger a change from one category to the next when the rev hits that trigger.  Then in the new category assign the lifecycle that has the numerical revision scheme in it. 

 

I haven't tried this yet, but theoretically it should work.  If I have some time later this morning I will set up some test for it and report back.

 

EDIT:

 

So far have not been able to get the rule to trigger a category change.... this is going to take some trial and error.

ChrisB

ADSK_Expert_Elite_Icon_S_Color_Blk.png

Please use Mark Solutions!.Accept as Solution &Give Kudos!Kudos to further enhance the value of these forums. Thank you! :smileyhappy:

http://cbennertipstricks.blogspot.com/


   

Valued Contributor
Posts: 60
Registered: ‎12-06-2012
Message 3 of 9 (264 Views)

Re: rule based category and lifecycle change

02-06-2013 05:10 AM in reply to: jacoj

Did try this,

maybe my rule was not correct.''

do I assign this rule to the current category or the new category?

 

Employee
Posts: 760
Registered: ‎12-12-2006
Message 4 of 9 (260 Views)

Re: rule based category and lifecycle change

02-06-2013 05:52 AM in reply to: jacoj

I assume we are talking about files, right?

 

I belive that the only time category rules can get automatically triggered is when a file is created.  In all other cases, you need to explicitly set the category.

 

Even through the API, there is no good way to perform custom actions when moving to a new revision.

 

If I'm reading this right, you want to do something specific when you get to revision G.  It sounds like lifecycle states may be a better fit.  For example, you can create a lifecycle state called "Released to Production".  When users want to release something, they do a state change instead of a revision bump.


In terms of custom programming, there are ways to trigger custom actions when a state change is performed.



Doug Redmond
Software Engineer
Autodesk, Inc.
http://justonesandzeros.typepad.com/

*Expert Elite*
cbenner
Posts: 2,827
Registered: ‎04-06-2010
Message 5 of 9 (258 Views)

Re: rule based category and lifecycle change

02-06-2013 06:01 AM in reply to: Redmond.D

Doug, I think you might be right, I've been messing with this for a while now.  What I don't understand though, is if it only triggers a category change (or set) on object creation,... why is there even a check box for that as an option on the Rules dialog box.  That "option" to check or no check that box, would lead you to believe these rules should work anytime the conditions of the rule are met.  I thought perhaps a "Sync Properties" would do it.

 

rules.JPG

ChrisB

ADSK_Expert_Elite_Icon_S_Color_Blk.png

Please use Mark Solutions!.Accept as Solution &Give Kudos!Kudos to further enhance the value of these forums. Thank you! :smileyhappy:

http://cbennertipstricks.blogspot.com/


   

Employee
Posts: 760
Registered: ‎12-12-2006
Message 6 of 9 (244 Views)

Re: rule based category and lifecycle change

02-06-2013 07:02 AM in reply to: cbenner

Categories are a lot more than just properties.  A lot of behavior depends on the category.  So it's not something that can be switched around every time an object gets edited.

 

But you make a good point.  What is the purpose of rules?  If you don't check the "Apply rules on object creation" then what is the point of the rule?

 

As far as I can tell, rules are used for two things:

  • Assigning new objects to a category
  • When running the "Change Category" command there is an option to set the category based on the rules.

 



Doug Redmond
Software Engineer
Autodesk, Inc.
http://justonesandzeros.typepad.com/

*Expert Elite*
cbenner
Posts: 2,827
Registered: ‎04-06-2010
Message 7 of 9 (241 Views)

Re: rule based category and lifecycle change

02-06-2013 07:20 AM in reply to: Redmond.D

Thanks Doug.  I never really used rules before, but as I was playing with them to try to help the OP, I saw where I might be able to use them in the future.  This helps.

ChrisB

ADSK_Expert_Elite_Icon_S_Color_Blk.png

Please use Mark Solutions!.Accept as Solution &Give Kudos!Kudos to further enhance the value of these forums. Thank you! :smileyhappy:

http://cbennertipstricks.blogspot.com/


   

Valued Contributor
Posts: 60
Registered: ‎12-06-2012
Message 8 of 9 (230 Views)

Re: rule based category and lifecycle change

02-06-2013 08:35 PM in reply to: jacoj

Hi Guys,

 

so this is what I want to achieve. we are a fairly big company and needs strict rules one behaviours and lifecycles.

 

1. Working in a category called Internal docs, bumping up the revision A-G as managed by the Lifecycle as it runs through our companies doc flow before it goes to the client.

as soon as it reaches rev G , I want vault to automaticlly change the category from Internal docs to External docs, taking on a new lifecycle, bumping it to rev 0 ( zero )( issue for construction ) . locking it to the users

so I want to be able to create this rule,

but doesn manage, Do i create a rule in the internal docs category, wher the file is currently in?

What I dont understand from the rule is this, you set up the rule to say " if Rev Nuber is G "

but you dont state " than this needs to happen to the file", and I think rhis is why the category doesnt change when it reaches rev G.

 

your thoughts?

 

Employee
Posts: 760
Registered: ‎12-12-2006
Message 9 of 9 (221 Views)

Re: rule based category and lifecycle change

02-07-2013 04:40 AM in reply to: jacoj

Let me expain things with a picture.  Let's say you have three states Work in Progress, In Review and Released.  A document starts out in WIP.  Next it goes back and forth between WIP and In Review until it reaches revision F.  At that point the reviewer can transition it to the Released state.  There is a constraint on the In Review -> Released transition that prevents anyone from Releasing it before revision F.

 

States.png

 

Everything I have described so far can be done with just the Vault administrator settings.

If you want to change the category and lifecycle state after a document transitions to Released, you will need to use custom programming.  But it is possible. 

 



Doug Redmond
Software Engineer
Autodesk, Inc.
http://justonesandzeros.typepad.com/

You are not logged in.

Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register

Announcements
New button for Platinum & Gold Subscription customers
Gold & Platinum Subscription customers can alert Autodesk if they require assistance with their forum post

Manufacturing Community
The Manufacturing Community provides additional access to tips, tutorials, blogs and networking with peers.

Need installation help?

Start with some of our most frequented solutions to get help installing your software.

Ask the Community