View Required Doc Data lists the document requirements that were added to the Record itself and lets you change them. It is on the Record screen under the Admin Actions menu in the footer, on systems licensed for Enterprise features, and appears only when the Record already holds at least one requirement of its own.


A Record's requirements come from two places. Categories, sub categories and documents marked Required on the Record Type apply to every Record of that type and are managed on the Record Type. Requirements can also be added to an individual Record as @RequiredDocument data values, usually by a workflow action or an add-in, and those are the ones this dialog shows. Both kinds appear together on the Record's Required panel, described in the Required Documents topic, with the Record Type's requirements always listed first.


The dialog shows one row per requirement with these columns:

  • ID is the internal number of the stored value. A new row shows 0 until it is saved, and a row marked for removal shows its ID in red.
  • Category, Sub Category and Name say where a document must be and what it must be called to count. Leave Name blank to require any document in the category rather than one with a particular name.
  • Number is how many matching documents are needed. Blank means one.
  • E-form ID and E-form Name make the requirement a form rather than an uploaded file: only a document created from that E-form satisfies it. Pick the form from the E-form ID list and E-form Name fills in by itself. A name on its own, with no ID selected, also works and is looked up by name.
  • Complete Field and Complete Value let a field on the Record decide when the requirement is finished instead of the form's own completion flag. Name the field, then either leave Complete Value blank so that any yes value counts, which suits a checkbox, or enter the exact value it must hold, which suits a status field.
  • Order sets where the requirement appears among the Record's own requirements. Blank keeps the order they were entered in. Record Type requirements always come first regardless.


Each part is described in full under @REQUIREDDOCUMENT in the Special Data Variables topic.


To add a requirement click Add New Required Document and fill in the new row. To remove one click the delete button at the end of its row: the row turns read-only and the button changes to a restore button in case you change your mind. Nothing is written until you click Save Changes, which saves the rows to the Record as an ordinary edit, so each change is logged in the field's history and Revert Record Data can undo it. Close discards everything you did in the dialog.


Since the option only appears once the Record has a requirement of its own, the first one has to come from elsewhere, for example a workflow action that sets a @RequiredDocument value; after that the dialog can add as many more as you need.