Skip to main content

Document Types

Document Type (CM_Document_Type__mdt) is the highest level of classification for a document and dictates the lifecycle, states, metadata, and workflows that are available to the document once it is created. Document subtypes are also managed using this custom metadata type. To view the Document Type schema, visit Document Type.

Note

Document classification is not managed in CM_Document_Type__mdt. Classification is dependent on Subtype. When creating a document, the value you select for CM_Document_Subtype__c determines the available CM_Classification__c values that you can choose from for that document.

Configure Document Types

To configure Document Types, follow the steps in these sections:

Step 1 - Create Document Type metadata records

To create a Document Type (CM_Document_Type__mdt) metadata record:

  1. In the Quick Find box in Setup, search for and select Custom Metadata Types.

  2. Navigate to the Document Type (CM_Document_Type__mdt) row.

  3. Click Manage Records.

  4. Click New.

  5. Complete the Information section.

  6. Click Save.

Step 2 - Create picklist values

To create picklist values for the CM_Document_Type__c field on CM_Document_Version__c:

  1. In the Object Manager, search for and select the Document Version (CM_Document_Version__c) custom object.

  2. Click the Fields & Relationships tab.

  3. Based on the selected Category value in the Document Type (CM_Document_Type__mdt) metadata record created in Step 1 - Create Document Type metadata records above, click either the Document Type (CM_Document_Type__c) or the Document Subtype (CM_Document_Subtype__c) field.

  4. In the Values section, click New.

  5. Based on the existing Document Type metadata records, enter picklist values.

    Note

    CM_Document_Version__c.CM_Document_Type__c picklist values must match 1:1 to the DeveloperName values for all CM_Document_Type__mdt records. For example, if your instance has the Document Type records in Table 109, “Example Document Type Records”, enter Brochure__c and Magazine__c. The saved picklist value API Names in Table 110, “Example Picklist Values” are an exact match for the Document Type DeveloperNames in Table 109, “Example Document Type Records”.

    Table 109. Example Document Type Records

    DeveloperName

    Label

    Category

    Default Expiration in Days

    Brochure__c

    Brochure

    Type

    365

    Magazine__c

    Magazine

    Type

    90



    Table 110. Example Picklist Values

    API Name

    Label

    Brochure__c

    Brochure

    Magazine__c

    Magazine



  6. Click Save.

Step 3 - Add the picklist values of the Concept or Rate Card objects

Note

This step only applies if you are using the Concept or Rate Card objects.

To add the document type, subtype, and classification picklists of the Concept (mvn__PP_Concept__c) and Rate Card (mvn__PP_Rate_Card__c) objects:

  1. Navigate to the Concept mvn__PP_Concept__c or Rate Card (mvn__PP_Rate_Card__c) object.

  2. Click the Fields & Relationships tab.

  3. Click the Document Type field.

  4. In the Values section, click New.

  5. Enter picklist values. These picklist values must match the ones created in the Step 2 section above. In this example, the values in the Table 111, “Example Picklist Values” table would be used.

    Table 111. Example Picklist Values

    API Name

    Label

    Brochure__c

    Brochure

    Magazine__c

    Magazine



  6. Click Save.

  7. Navigate to the Document Subtype field on the object.

  8. Repeat steps 1-6.

  9. Navigate to the Classification field on the object.

  10. Repeat steps 1-6.

  11. If you use both the Concept and Rate Card objects, complete this process for both objects.