When a document is checked in or changed to the selected status |
- Change the document owner to: <do not change>, <none>, or a user name in the list.
- Change other document revisions at the selected status to status: <do not change> or a status in the list
|
When a document at the selected status before check in is next checked in, change the document status to:
|
- <do not change>
- Previous status item
- Next status item
- First in list
- Last in list
- A status in the list
|
When a document at the selected status before check in is next checked in, allow its revision to change at these levels |
Depending on the document's current revision, you can restrict document check-in. Selecting Primary, Secondary, or Tertiary controls which elements of the revision level are allowed to change during check in. The initial check-in is considered a change from null to a value. For example, if the revision scheme uses both Primary and Secondary levels, then you must select both Primary and Secondary levels for check in at the selected lifecycle status for documents to be checked in at that status. However, if you select Primary and not Secondary, then Secondary is allowed to change to first in the list when Primary changes; for example, PRE-11 to DEV-01.
If Working copy is the only revision level selected, then Working copy is required when checking in documents at the selected lifecycle status, including the first check for documents not in the vault when the status is first in the list.
|
Do not allow status to return to the selected or a prior status |
Following the sequence of status levels under Lifecycle statuses, documents that move beyond the selected status cannot return to this status.
|
Control access to document revision at the selected status as follows (select in columns 1 and 2) |
Select RO (Read-only ) or RW (Read/Write ) for specific users and groups. You can restrict access more with lifecycle status than for projects.
|