Document Type: Difference between revisions
No edit summary |
No edit summary |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 7: | Line 7: | ||
* [[Document:Folder|'''Folder''']] in which the document is placed | * [[Document:Folder|'''Folder''']] in which the document is placed | ||
* [[Document:Role|'''Parties''']] to the document | * [[Document:Role|'''Parties''']] to the document | ||
* Custom [[ | * Custom '''[[Custom Field|fields]]''' | ||
A type can be assigned during [[Upload Document|upload]] or at any time afterwards (until the document is [[ | A type can be assigned during [[Upload Document|upload]] or at any time afterwards (until the document is [[Document:Destruction|destroyed]]). If a type is assigned during upload, ContactsLaw will attempt to [[Catalogue Document|catalogue]] the document automatically (using metadata to populate any required parties); however, if this is not possible then cataloguing must be performed interactively instead. This behaviour can also be overridden for individual document types. | ||
== Purposes == | == Purposes == | ||
Line 25: | Line 25: | ||
== Description Definitions == | == Description Definitions == | ||
If desired, document types can define how document '''descriptions''' are generated. Description definitions use the same syntax and semantics as [[Document | If desired, document types can define how document '''descriptions''' are generated. Description definitions use the same syntax and semantics as [[Document Template|templates]] (although they cannot contain any formatting, such as bold typeface). An important difference is that, while templates draw upon the '''assets''' created by their author, description definitions can only draw upon assets which directly correspond to the parties and fields on the document. When editing the definition, the available assets are listed for ease of access. | ||
Note: Since the assets are derived from the properties of the document type, the system may modify their names slightly to fit within the required syntax. | Note: Since the assets are derived from the properties of the document type, the system may modify their names slightly to fit within the required syntax. |
Latest revision as of 10:05, 3 December 2024
Document types serve as a method of categorising documents in ContactsLaw.
Types also influence the behaviour of the document, determining:
- The description of the document (dynamically generated)
- Folder in which the document is placed
- Parties to the document
- Custom fields
A type can be assigned during upload or at any time afterwards (until the document is destroyed). If a type is assigned during upload, ContactsLaw will attempt to catalogue the document automatically (using metadata to populate any required parties); however, if this is not possible then cataloguing must be performed interactively instead. This behaviour can also be overridden for individual document types.
Purposes
Document types can be assigned a purpose, which causes the system to automatically select that type in certain situations:
Purpose | When Used |
---|---|
Correspondence |
|
Multiple document types can be used for the same purpose. ContactsLaw will select the most-specific type that applies to a given document; for example, a document type in the same workgroup will be chosen over one in a parent workgroup or at the subscription level.
Description Definitions
If desired, document types can define how document descriptions are generated. Description definitions use the same syntax and semantics as templates (although they cannot contain any formatting, such as bold typeface). An important difference is that, while templates draw upon the assets created by their author, description definitions can only draw upon assets which directly correspond to the parties and fields on the document. When editing the definition, the available assets are listed for ease of access.
Note: Since the assets are derived from the properties of the document type, the system may modify their names slightly to fit within the required syntax.