Status file configuration

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

The following is defined for each object cycle:

Attribute	Possible value(s)	Description
name	Authoring, Localization, Published, Deleted	Workflow cycle
level	Always 0	-
type	work, localization, published, deleted	No longer required; may be used for backwards compatibility.
collection	Filepath and folder name	Collection (folder) in Content Store
initial	true, false, or not given	Content is created in the cycle set as initial="true"
lastworkcycle	true, false, or not given	Defines the cycle as being the last in which the objects are being initially created.

The following is defined for each status in the cycle:

Element/Attribute	Possible value(s)	Description
name	Any value	Status name as it will appear to the user
level	Any number 0 or higher	Used for the dependencies between statuses. An object cannot move to a higher status until all its dependencies are at a status with the same or a higher level number.
type	contribute, work, review, approval, end, external, cancelled	No longer required; 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. 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/release an object is overwritten by the access rights file; however if this is set to none, the Edit button will be greyed out for the user.
milestones	-	Not used
next statuses	Any other existing statuses for the same object in the same cycle	The object can be moved from the current status to any of these "next" statuses (even if the "next" status is on a lower level).