How an Admin can create and configure a Lifecycle

00:07

The purpose of this video is to demonstrate how an admin can create a new lifecycle

00:12

and configure it for use in Autodesk Vault.

00:19

To access lifecycle definitions,

00:22

log in as an administrator to Autodesk Vault client.

00:26

Navigate to tools,

00:28

click on administration,

00:30

Vault settings.

00:32

In the Vault settings dialog,

00:34

click on behaviors,

00:37

and click on lifecycles.

00:42

The lifecycle definitions dialogue,

00:44

you can see the existing life cycles here.

00:47

To create a new lifecycle,

00:49

there are 2 different methods.

00:52

One is to copy an existing lifecycle

00:59

And start

01:01

building a new lifecycle.

01:05

By copying an existing lifecycle,

01:07

you can use it as a base to quickly get started.

01:12

With a new lifecycle,

01:14

you can edit

01:15

the category assignments here as necessary.

01:18

You can assign the new lifecycle either with file categories,

01:22

folder categories,

01:23

or with item categories.

01:27

In this case,

01:28

we will go with.

01:30

File categories.

01:32

Let me associate it with the Inventor category.

01:40

In the definition security,

01:42

we have two different options.

01:44

One is to

01:46

Use combined with object-based security,

01:49

Which means

01:51

any state-based security defined for individual state

01:55

within this life cycle definition

01:57

combine with the object-based security

01:60

set on the Vault object.

02:02

In other words,

02:03

the combined security becomes the effective security for the entity.

02:08

The other option is

02:09

override object-based security.

02:12

Which means the state-based security

02:15

becomes the effective security

02:17

for the entity.

02:19

The state-based security is defined here.

02:23

You can go with the existing

02:26

states here.

02:28

Or you can choose to edit these states.

02:41

Likewise,

02:42

you can change the state names

02:45

or add any new states,

02:49

as applicable.

02:54

Let's add a new state here called Approved.

03:13

Provided a small description for what the state is.

03:18

Specify any color as desired.

03:26

Click OK.

03:28

Now we can see that

03:30

we have added a new state into this

03:33

lifecycle.

03:34

You can sort the states by using the up or down arrow here.

03:40

I would like to place this approved state in between review and released.

03:45

Let me move this up.

03:48

Now,

03:48

we have added a new state here,

03:50

called Approved.

03:54

Since we are using an existing lifecycle and we have copied it,

03:58

to create a new lifecycle here.

04:04

Permissions are also copied from the existing lifecycle.

04:07

Security permissions here define who can access the files

04:11

or objects that are in the state specified here.

04:14

For example,

04:15

for the WIP state or the work in progress state,

04:17

the current configuration for security is that everyone can read,

04:22

everyone can modify,

04:24

everyone can delete,

04:25

or everyone can download.

04:26

You can add

04:27

individual users here or groups

04:31

by selecting

04:32

what you want to see.

04:35

Let's add

04:38

my name here,

04:45

and specify the permissions.

04:47

The security here is different from the transition security

04:51

that is specified here.

04:53

The transition security

04:54

defines who can change the state of file from one state to another.

04:59

For example,

05:00

you can define

05:01

who can send the file from working from the state to review state by editing.

05:08

Edit the transition.

05:14

So under the transition,

05:15

you can define

05:17

criterias,

05:19

actions

05:21

custom job types, security,

05:24

and peer review.

05:26

The criteria we can build condition and define

05:28

what condition based on a property should be

05:31

met to allow the change state to happen from work in progress state to review state.

05:36

We will leave it blank for now.

05:38

In the actions

05:40

you can specify whether you want to bump

05:44

revisions,

05:46

synchronized properties,

05:48

check that dependent child files are released,

05:51

check that dependent child folders are released,

05:54

so on and so forth,

05:56

which are self-explanatory.

05:57

You can choose

05:59

whatever the action is necessary and configure the desired end results here.

06:10

In the security tab,

06:14

remove the no restrictions on this transition to

06:16

set restrictions or security permissions as desired.

06:22

Let's add a couple of users here.

06:28

And you can define whether this person can change the state

06:33

from work in progress to review or not. Allow will let the user to

06:37

change the state. Deny will explicitly deny the user from changing the state

06:42

from one state to another.

06:47

Likewise,

06:48

you can define the permissions for any state's transitions here by

06:53

going on to individual states and define the permissions as required.

06:58

In the control tab

06:59

you can specify

07:01

which are the controlled versions for purge,

07:03

and in case of a

07:04

release date, you can define which state of a document

07:10

in a lifecycle

07:12

should be considered as release state or

07:15

which state should be considered as obsolete state

07:19

by checking the appropriate flags.

07:22

You can include any default comments for each

07:25

state so that whenever that state is applied,

07:28

a default comment is also applied

07:31

for the files.

07:33

Specify a meaningful name here,

07:43

and

07:45

click Apply,

07:46

and click OK.

07:47

So this is how you can create a new lifecycle

07:51

by copying an existing lifecycle and build on that.

07:55

If you want to

07:56

create a lifecycle from scratch,

07:60

click on the new button here,

08:04

and start by providing

08:07

a definition name.

08:15

Select the categories that you want

08:19

this lifecycle to be associated with,

08:29

and start building transitions or states,

08:32

as I said.

08:36

Create 3 different states here

08:39

Work in progress.

08:43

Review state,

08:52

and

08:54

Released state.

09:07

You can go on to specify the transition permissions here,

09:12

as we saw earlier.

09:14

Define the security permissions as to who is allowed

09:17

to access the documents in a specific state.

09:22

And set controls for release date and obsolete if you want to define one and also

09:29

the controlled purge settings.

09:32

Click apply,

09:35

and click OK.

09:37

Thus we have created two different lifecycles using 2 different methods in Vault.

Video transcript

00:07

The purpose of this video is to demonstrate how an admin can create a new lifecycle

00:12

and configure it for use in Autodesk Vault.

00:19

To access lifecycle definitions,

00:22

log in as an administrator to Autodesk Vault client.

00:26

Navigate to tools,

00:28

click on administration,

00:30

Vault settings.

00:32

In the Vault settings dialog,

00:34

click on behaviors,

00:37

and click on lifecycles.

00:42

The lifecycle definitions dialogue,

00:44

you can see the existing life cycles here.

00:47

To create a new lifecycle,

00:49

there are 2 different methods.

00:52

One is to copy an existing lifecycle

00:59

And start

01:01

building a new lifecycle.

01:05

By copying an existing lifecycle,

01:07

you can use it as a base to quickly get started.

01:12

With a new lifecycle,

01:14

you can edit

01:15

the category assignments here as necessary.

01:18

You can assign the new lifecycle either with file categories,

01:22

folder categories,

01:23

or with item categories.

01:27

In this case,

01:28

we will go with.

01:30

File categories.

01:32

Let me associate it with the Inventor category.

01:40

In the definition security,

01:42

we have two different options.

01:44

One is to

01:46

Use combined with object-based security,

01:49

Which means

01:51

any state-based security defined for individual state

01:55

within this life cycle definition

01:57

combine with the object-based security

01:60

set on the Vault object.

02:02

In other words,

02:03

the combined security becomes the effective security for the entity.

02:08

The other option is

02:09

override object-based security.

02:12

Which means the state-based security

02:15

becomes the effective security

02:17

for the entity.

02:19

The state-based security is defined here.

02:23

You can go with the existing

02:26

states here.

02:28

Or you can choose to edit these states.

02:41

Likewise,

02:42

you can change the state names

02:45

or add any new states,

02:49

as applicable.

02:54

Let's add a new state here called Approved.

03:13

Provided a small description for what the state is.

03:18

Specify any color as desired.

03:26

Click OK.

03:28

Now we can see that

03:30

we have added a new state into this

03:33

lifecycle.

03:34

You can sort the states by using the up or down arrow here.

03:40

I would like to place this approved state in between review and released.

03:45

Let me move this up.

03:48

Now,

03:48

we have added a new state here,

03:50

called Approved.

03:54

Since we are using an existing lifecycle and we have copied it,

03:58

to create a new lifecycle here.

04:04

Permissions are also copied from the existing lifecycle.

04:07

Security permissions here define who can access the files

04:11

or objects that are in the state specified here.

04:14

For example,

04:15

for the WIP state or the work in progress state,

04:17

the current configuration for security is that everyone can read,

04:22

everyone can modify,

04:24

everyone can delete,

04:25

or everyone can download.

04:26

You can add

04:27

individual users here or groups

04:31

by selecting

04:32

what you want to see.

04:35

Let's add

04:38

my name here,

04:45

and specify the permissions.

04:47

The security here is different from the transition security

04:51

that is specified here.

04:53

The transition security

04:54

defines who can change the state of file from one state to another.

04:59

For example,

05:00

you can define

05:01

who can send the file from working from the state to review state by editing.

05:08

Edit the transition.

05:14

So under the transition,

05:15

you can define

05:17

criterias,

05:19

actions

05:21

custom job types, security,

05:24

and peer review.

05:26

The criteria we can build condition and define

05:28

what condition based on a property should be

05:31

met to allow the change state to happen from work in progress state to review state.

05:36

We will leave it blank for now.

05:38

In the actions

05:40

you can specify whether you want to bump

05:44

revisions,

05:46

synchronized properties,

05:48

check that dependent child files are released,

05:51

check that dependent child folders are released,

05:54

so on and so forth,

05:56

which are self-explanatory.

05:57

You can choose

05:59

whatever the action is necessary and configure the desired end results here.

06:10

In the security tab,

06:14

remove the no restrictions on this transition to

06:16

set restrictions or security permissions as desired.

06:22

Let's add a couple of users here.

06:28

And you can define whether this person can change the state

06:33

from work in progress to review or not. Allow will let the user to

06:37

change the state. Deny will explicitly deny the user from changing the state

06:42

from one state to another.

06:47

Likewise,

06:48

you can define the permissions for any state's transitions here by

06:53

going on to individual states and define the permissions as required.

06:58

In the control tab

06:59

you can specify

07:01

which are the controlled versions for purge,

07:03

and in case of a

07:04

release date, you can define which state of a document

07:10

in a lifecycle

07:12

should be considered as release state or

07:15

which state should be considered as obsolete state

07:19

by checking the appropriate flags.

07:22

You can include any default comments for each

07:25

state so that whenever that state is applied,

07:28

a default comment is also applied

07:31

for the files.

07:33

Specify a meaningful name here,

07:43

and

07:45

click Apply,

07:46

and click OK.

07:47

So this is how you can create a new lifecycle

07:51

by copying an existing lifecycle and build on that.

07:55

If you want to

07:56

create a lifecycle from scratch,

07:60

click on the new button here,

08:04

and start by providing

08:07

a definition name.

08:15

Select the categories that you want

08:19

this lifecycle to be associated with,

08:29

and start building transitions or states,

08:32

as I said.

08:36

Create 3 different states here

08:39

Work in progress.

08:43

Review state,

08:52

and

08:54

Released state.

09:07

You can go on to specify the transition permissions here,

09:12

as we saw earlier.

09:14

Define the security permissions as to who is allowed

09:17

to access the documents in a specific state.

09:22

And set controls for release date and obsolete if you want to define one and also

09:29

the controlled purge settings.

09:32

Click apply,

09:35

and click OK.

09:37

Thus we have created two different lifecycles using 2 different methods in Vault.

Create a lifecycle definition - Exercise

Create and configure lifecycle definitions on the Lifecycle Definition dialog.

  1. Click Tools > Administration > Vault Settings.
  2. On the Vault Settings dialog box, select the Behaviors tab > Lifecycles.
  3. Click New to launch the Lifecycle Definition - New Definition dialog.
  4. Enter a lifecycle definition name in the Definition Name field.
  5. Select the categories to which you want the lifecycle definition assigned from the Category list.
  6. Enter a description for the new lifecycle definition in the Description field.
  7. Select your preferred Definition Security from the drop-down:
    • Combine with object-based security – any state-based security defined for individual states within this lifecycle definition combine with the object-based security set on the object. In other words, the combined security becomes the effective security for the entity.
    • Override object-based security – any state-based security defined for individual states within this lifecycle definition override the object-based security set on the object. In other words, state-based security becomes the effective security for the entity.
  8. Click the Plus (+) button to create a lifecycle state for the new definition.
  9. After you have created your lifecycle states, select a lifecycle state in the Lifecycle Details list and click the checkmark to set it as the default state for the lifecycle definition.
  10. Reorder lifecycle states by selecting a state in the Lifecycle Details view and clicking the up or down arrow. The order of the lifecycle states determines the order in which they are displayed in the Change State dialog.
  11. When finished, click OK to save the new definition.

You can customize individual state behavior for lifecycle definitions by performing any of these tasks:

Was this information helpful?