Documents Custom Fields: Types and Configuration

This article will help you understand the main functions of Documents Custom Fields.

Documents Custom Fields (DCF) are assigned to Users and Documents. Usually, this is the list of Departments/Projects or other custom fields. You can use them in documents, budgets, approvals, and access limitations. 

You can use Documents Custom Fields for the following purposes: 

• For tracking department or project spending.
• To limit access to documents.
• To set up approval workflows based on Documents Custom Fields.
• As an additional custom field with text or date format.
• To create budgets per Department/Project.

Read how to set up your Departments/Projects here.

Types of Documents Custom Fields

1. Drop-down list

Use this type to create a field with a fixed list of options that your users can select. For example, it will allow you to restrict user access, trigger relevant approval workflows, or assign budgets according to the DCF. You can add codes and up to 5 sub-levels to your options and edit or delete them.

This DCF type is the best way to add your Departments/Projects to Precoro. This is how it may look like:

Creating, for example, a Purchase Order with the Drop-down list type will look like this:

2. Text

It is an open text field available to fill out when creating documents. With this type, you cannot create a preset list with options, select limit access to documents, use it in approval workflow, or create a budget for this DCF. 

Creating a Purchase Order with the Text type will look like this:

For example, you can use this type of Documents Custom Fields to specify the purpose of the Purchase Order, Machine #, Project Stage / Phase, Quotations References, etc.

3. Date

If you set this type, you will insert a specific date each time when creating a document.

Creating a Purchase Order with the Date type will look like this:

For example, you can use the Date type to specify the Quote Date in documents and set the Validity Date of an Order or Requisition or Expected Payment Date.

Configurations of Documents Custom Fields

1. ON means the company currently uses it. You can disable this Custom Field if you do not need it. 

2. Required to select in documents means it will be a mandatory row in your documents. Such Documents Custom Fields will be marked with an asterisk (*) on the document creation page:





3. Show Option Code — if this switch is on, you will see codes in your documents:





4. Display in the lists of documents — if this switch is on, the DCF will be displayed on pages with document lists:





5. Print in Excel & PDF documents means that the field will be printed in Excel and PDF versions of Purchase Requisitions/Purchase Orders:





6. Limit access to documents — if this switch is on, users will have access only to the documents with options assigned to them in User Management.    

For example, you have Departments with two options: Marketing and Development. The user has access only to the Marketing department. Thus, if you check the Limit access to documents, the user will only see documents assigned to Marketing. If the switch is off, the user will see documents for all departments but can create/approve documents only for Marketing.

Previously created documents will be available to users even if you deactivate access to their departments/projects. Thus, for example, if your user switches from Marketing to the Development department, all their old documents will remain available.

You can also set up where your Documents Custom Fields will be available for selection:

1. Available in the Warehouse Requests / Purchase Requisitions / Requests for Proposal Receipts / Invoices / Expenses / Purchase Orders — the field will be available to fill out in the selected documents.
2. Available in Approval Workflow means that the field can be included as a trigger for your approval workflow.
3. Available in Budgets means that you can tie your budget to the Custom Fields.