Status file configuration

The status files have a similar structure and are configured in a similar manner.

Table 1. Status attribute definitions for each object cycle
Attribute	Possible values	Description
Name	Authoring Localization Published Deleted	Workflow cycle
Level	Always 0	N/A
Type	Work Localization Published Deleted	No longer required and may be used for backwards compatibility
Collection	Filepath and folder name	Collection folder in Content Store
Initial	True False Not given	Content is created in the cycle set as`initial="true"`
Lastworkcycle	True False Not given	The cycle defined as the last one in which the objects are initially created

Table 2. Status attribute definitions for each status in the cycle
Element or attribute	Possible values	Description
Name	Any value	Status name as it will appear to the user
Level	Any number 0 or higher	Usage for dependencies between status types. Note: An object cannot move to a higher status until all its dependencies are at a status with the same or a higher level value.
Type	Contribute Work Review Approval End External Cancelled	No longer required, but may be used for backwards compatibility
Drop	True False	When a child object's status is moved back to a status with a lower level number than its parent object, the parent object changes status automatically to the status in the same cycle with the drop attribute set to true Note: This should only be applied to one status.
Color	RGB values separated by semicolons	Configures the colors of the pie charts in the Project Management view
Lockable object types	All None	The permission to lock, open, or release an object is overwritten by the access rights file Note: If set to none, the Edit button is dimmed, since it is unavailable to users.
Milestones	N/A	Not used
Next status	Any other existing status for the same object in the same cycle	The object can be moved from the current status to any next status, even if the next status is at a lower level