Glossary
This topic provides you with terminology and concepts about d.3one.
Terminology | Concept |
---|---|
Dossier | An entity consisting of items and properties describing the items. Items of a dossier can be documents and/or dossiers. |
Dossier type | Describes the type of a dossier (e.g. customer dossier, supplier dossier) and thus defines the properties that are available. |
Common properties | Properties owned by a document or dossier despite of the document type or dossier type. |
App | d.3one integration in a leading application that provides dedicated functions and user interface, if applicable. |
Tasks and Messages | Refers to the location at which messages and tasks initially arrive and remain until the user works on them. |
Base address | The definable part of an URL under which any services of a system can be accessed and which serves as a reference point. |
d.3 link | Reference to repository items. |
d.3one application server | Collection of all apps, which can be expanded by third-party apps, if applicable. Abbreviated: d.3one server. |
d.ecs domino | A service that is installed on the IBM Domino server. This service provides the access to the IBM resources and communicates with the d.3one server. |
Document | An entity consisting of a file and the properties describing the file. Files can be, for example, images, digital writings, Excel files, etc. |
Document type | Describes the type of a document (e.g. invoice, delivery note) and thus defines the available properties (e.g. invoice number, delivery note number). |
Drop zone | A user interface section used to drop an item in order to store it. |
Property | A trait that describes a document or dossier in condensed manner. |
Results | Set of documents and dossiers found by a search. |
Advanced properties | Customized additional property (optional) that describe a document or dossier. |
Facet | Results can be viewed with regard to a specific property by using a facet. |
Feature | A set of related functions in an integration. A feature has got a dedicated name. |
Business process | A Business process consists of a collection of logically related actions (tasks, activities) that are performed in order to achieve a business or operational target. (see Wikipedia in German) |
Main dossier | Dossier on top-level of a dossier structure. The main dossier is a logical parenthesis and is used to digitally combine additional items, such as dossiers and documents. Thus, a document can be part of several different top-level dossiers. |
Integration: | A set of front-end functionality (features) that may be integrated in a leading application. |
Category | Covers the items "dossier type" and "document type". |
Context action | An action that provides a context-specific function related to a selected item. |
Multi-value property | Special property to describe a document or a dossier. The multi-value property can consist of several values. |
Source | Refers to an item in a source system with specific properties and categories, such as e-mail, e-mail attachments, contacts, and appointments. |
Source property | Defines the item's property of any source system, for example, the source "e-mail" has the properties "Subject", "Sender", "Recipient" and "Body". |
Source category | Defines the item's category of any source system, for example, the source "e-mail" has the categories "supplier invoice" and "customer invoice". |
Source system | Refers to any systems providing source data (such as an e-mail application or ERP system) which can be used, for example, to map data in various systems. |
Repository | Refers to a logical storage location, that is, a collection of documents and dossiers. These collections may also be used to separate information for security reasons, for example. A d.3 system can provide several repositories. |
Workflow | Business process implemented by a rule-based, defined sequence of handling steps. |