In general, a document can be thought of as a file that you expect to be able to create, save, and subsequently retrieve and update, replacing the old version with the updated version. This topic provides a high level description of the primary features of document objects, and provides links to further information.
Documents are objects that
Documents are instances of document classes
Document classes contain essential properties and methods that comprise documents. Individual documents are called "instances" of their class or subclass. See Classes for more information.
All document classes are assigned system-created properties, such as Document Title and Creation date. Custom properties are created and assigned to specific subclasses by system designers or advanced users, and are used to further identify the documents for later retrieval. See About document classes for more information.
A user , or a process like a Process Engine workflow, can check out a document to edit it. When you check in the updated document, Content Engine preserves both the new version and the previous version. Each time you check in the document, another version is created for that document. See About versioning for more information.
The content of a document is composed of pieces of information such as word processing files, spreadsheets, graphics, images, etc. These pieces of information are called a URL while the file itself resides elsewhere on the available network or internet. See Document content for more information.
Network-wide search and retrieval
You can assign titles to your documents using simple, easy-to-read phrases instead of with file names or ID numbers. Users and automated processes can search for documents based both on their descriptive properties and their content. Regardless of the user or the document location, complex path commands with coded document names are not required. Client applications are designed to make it easy for users to find and use important documents and other objects.
Documents can be filed in folders
You can file documents in folders for easy display and organization, just like you are using Microsoft's Windows Explorer. However, while Microsoft Windows enables only one instance of a document, FileNet P8 enables documents to be filed in many different folders. An action taken on any of these document instances is made on all the others. For example, DocumentA could appear in FolderA and FolderB. If DocumentA is checked out from FolderA, it will also be marked as checked out in FolderB. See Folders for more information.
Documents can be associated with lifecycle policies
You can pass a document through a predetermined series of states and transitions called a lifecycle. See Lifecycle and events for more information.
Documents can be attachments in a workflow step
You can attach documents and folders to a step in a workflow. Depending on your access rights, you can
Documents can subscribe to server-side events
You can trigger actions such as delete or check out using the Content Engine's event subsystem. See Event actions and subscriptions for more information.
All documents are designed for easy application of security templates, as the document version goes through predefined states. See the Security Guide for full security information. Also, see About versioning for more information.
Documents can be grouped together into compound documents
A compound document consists of a single parent document, containing zero or more child documents. Any child document can be the parent of a separate compound document structure.
Compound documents are referenced by component relationship objects or "links" that
For more information, see About compound documents.