In this tutorial, you learn about each stage of developing
and managing lifecycles, and then practice creating and maintaining
them in an example environment.
At the asset level, requirements for master and community
lifecycles are inherited by the asset lifecycle. Lifecycle managers
can add requirements for the asset to supplement those requirements
specified by repository and community administrators.

For example, a lifecycle manager
might decide to invite additional reviewers for a specific asset.
They might also adjust how a policy is configured, in order to better
match the requirements of a particular asset.
Any changes that
you make to the lifecycle configuration of an asset apply to only
that asset. Your changes do not apply to other assets in the community
that are using the same master or community lifecycle. If you often
make the same adjustments to assets, you might ask a community administrator
to adjust the lifecycle at the community level.
At the individual
asset level, you cannot change the following aspects of the lifecycle:
- The workflow for the lifecycle
- The conditions for the asset to enter the lifecycle
Learning objectives
After completing
this tutorial, you will understand:
- Which capabilities you have based on your role within the lifecycle
processes
- How asset lifecycle properties are inherited from master and community
lifecycles
- How to customize lifecycles with policies appropriate for a particular
type of lifecycle
- How to complete a successful asset review based on a particular
workflow
Time required
This tutorial takes approximately
45 minutes to complete. If you explore other concepts that are related
to this tutorial, it might take longer to complete.
Skill level
Intermediate
Audience
Repository administrators, community
administrators, and lifecycle managers using the web client