Spec depot

The spec depot is used to track changes to user-edited forms, such as client workspace specifications, jobs, and branch mappings. A server is not required to have a spec depot, but a server is allowed to have one spec depot. If you already have a spec depot, attempting to create another one results in an error message.

To retrieve change histories of user-edited forms, you must enable versioned specifications. After you have enabled versioned specs by creating the spec depot, all such forms are automatically archived as text files in the spec depot. Filenames within the spec depot are automatically generated by the server, and are represented in Helix Server syntax as follows:


Some formtypes (for example, theprotect, triggers, and typemapforms) are unique to the server, and do not have corresponding objectnames. See Control which specs are versioned.