If your WDK-based application supports manual assignment, you can manually assign a lifecycle if you have administrator or developer permission levels. You might want to manually assign a lifecycle to support new or different states. For example, let us say you have a lifecycle with four states: Start, WIP, Staging, and Approved. And let us say a user checks in a press release using that lifecycle. However, this particular press release must be reviewed by upper management before it is sent to staging, so a different lifecycle must be applied to the press release. An administrator could apply a different lifecycle.
To assign a lifecycle to an object, you must have at least Write permission on the object. If you are attaching the item to a lifecycle or replacing a lifecycle, you must have at least Relate permission on the lifecycle.
When you assign a lifecycle to a file, you can also select an alias set to associate with the file and the lifecycle. The alias set can identify the particular individuals who review, promote, or, depending on your WDK-based application, demote the file. Alias sets can also specify permission sets and repository locations.
Consult your repository administrator for specific information on the alias sets available in your installation.
When setting a lifecycle for a template, keep in mind that the lifecycle is assigned to all future files created from the template. The new lifecycle does not affect files that have already been created.
To assign a lifecycle:
Navigate to the file.
Do one of the following, depending on the options available:
Click More>Document>Apply Lifecycle.
Select the file’s checkbox. (To assign a lifecycle to several files at once, select each file’s checkbox). Select Tools>Lifecycle>Apply.
Select a lifecycle.
Click OK.