What are AODocs documents?

AODocs documents are digital records managed within the AODocs platform. 

AODocs documents are stored in libraries. Each library has one or more document classes, which define the "type" of documents it contains – for example, Invoices, Expense reports, or Purchase orders.

AODocs documents contain the following elements: 

  • A title (required)
  • Attached files
    These are files that are attached to the AODocs document. They're stored in Google Drive, Google Cloud Storage or Azure Blob Storage. They are owned by the AODocs storage accountNote: Depending on the type of library, an AODocs document can have no attached files, one attached file, or several attached files. Learn more: AODocs document structure for each type of library.
  • A description field
    This is a rich text field that can include images and formatted text.
  • Custom properties
    These are configured at the document class level to provide custom information about the document. They are also called metadata.
    Learn more: Create and configure custom properties
  • System properties (required)
    These properties are automatically generated by AODocs, for example, Creation date, Last update, Author, Last updater.

Note: You can't modify system properties.

  • Relations 
    These are links between AODocs documents in the same library.
    Learn more: Document relations
  • Workflow state
    This is a step of the workflow specific to the document class the AODocs document belongs to. If a workflow is defined, every document of the class has a workflow state. The workflow state changes depending on the workflow transitions.
    Learn more: Step 2: Configuration — Create workflow states

Each AODocs document has a unique URL and document ID.

Note: Some elements are required. Some elements aren't available in certain types of library. Learn more: AODocs document structure for each type of library.


AODocs document structure for each type of library

There are three types of library:

  • Team Folder
  • Secured Folder
  • Document Management library

Each has specificities which affect the structure of an AODocs document.

The following diagrams show the specificities of AODocs documents in different library types.

image04a.png image04b.png image04c.png

Team Folders

image01.png


Team Folders have only one document class, so all documents in a given Team Folder are of the same "type". All documents in Team Folders have the same custom properties and workflow (if defined).

Documents in Team Folders do not have relations.

Team Folders and Secured Folders

image01.png

image02.png


Documents in Team Folders and Secured Folders have one attached file, stored in Google Drive. The title of the AODocs document and the attached file are the same.

Secured Folders and Document Management libraries

 

image02.png

dms_xxhdpi.png

Secured Folders and Document Management libraries can have more than one document class. This means that you can have documents of different "types" in the same library. 

Each document class can have a specific workflow. All documents of a given document class use the same workflow, for example, contract validation.

You can create relations between documents in Secured Folders and Document Management libraries.

Document Management libraries 

dms_xxhdpi.png

Documents in Document Management libraries can have zero, one or more attached files.

The attached files of Document Management libraries can be stored in Google Drive, Google Cloud Storage (CGS) or Azure Blob Storage. Learn more: Where is my content stored?

For Document Management libraries using Google Drive, you can't browse atached files in the Google Drive interface, only in the AODocs interface.

However, you can access the attached files of AODocs documents in Google Drive through the search bar, and the Recent, Starred, and Shared with me sections, but they aren't located in a folder structure.

All library types

image01.pngimage02.pngdms_xxhdpi.png

All AODocs document have system properties.

The description, custom properties, relations and workflow states are optional elements. They can be defined by the library administrator but are not mandatory for the document to exist.

 

Was this article helpful? 16 out of 21 found this helpful
If you didn’t find what you were looking for, don’t hesitate to leave a comment!
Have more questions? Submit a request

Comments

2 comments
  • Can you share examples of why you would create AODocs documents without attachments?

    -1
    Comment actions Permalink
  • I'm a bit of an old grump, so take what I say with a pinch of salt. I thought the knowledge article was 'hard to swallow', unnecessarily long, and difficult to digest. The heading was "What is an Adocs document?" and the first paragraph veers-off on a tangent and starts by talking about Adocs classes - why? This is the kind of dry, dull, long-winded, desultory text that defeats the purpose of KAs. It's not until the 3rd list that you actually start to say, rather cryptically what an Adocs is "An AODocs document can be considered as an envelope".. duh?

    0
    Comment actions Permalink

Please sign in to leave a comment.