Skip to end of metadata
Go to start of metadata

This glossary will help you understand terms or acronyms with which you may not be familiar, or which may require explanation.

Icon

License

This documentation is copyrighted by Nuxeo and published under the Creative Common BY-SA license. More details on the Nuxeo documentation license page.

Space Index

0-9 ... 0 A ... 3 B ... 1 C ... 5 D ... 3 E ... 2
F ... 1 G ... 1 H ... 0 I ... 0 J ... 0 K ... 0
L ... 3 M ... 1 N ... 6 O ... 0 P ... 2 Q ... 0
R ... 1 S ... 1 T ... 3 U ... 0 V ... 2 W ... 5
X ... 0 Y ... 0 Z ... 0 !@#$ ... 0    

0-9

A

Page: ACL
ACL stands for Access Control List. An ACL is a set of security rules defined on a document. It says for instance: For the Document D,  the group G has the permission to Write and the User U has the permission to read. In the Nuxeo Platform ACLs are inher
Page: Action
Historically, actions (and user actions in Nuxeo Studio) were a mean to add a link, a tab or a button in the user interface in a declarative way. It’s a great way of making the platform modular, since you can add a new button in the user interface afterwa
Page: Artifact
(Maven) Artifact In general software terms, an artifact is one of many kinds of tangible by-product produced during the development of software. In Maven terminology, artifacts are specific results from build process. In Java, artifacts are mostly JAR fil

B

Page: Blob
Blob Blob is a frequent term used in the Nuxeo Platform documentation. In a more end-user language, it is equivalent to a file, a binary content.    

C

Page: CAP
Content Application Platform (CAP) It is the basic set of features of the Nuxeo Platform, so as to offer a minimal set of document management features that can be used to develop content management applications while keeping it lean and thin. CAP features
Page: CMF
Nuxeo Case Management Framework (Nuxeo CMF), replaced by the technical module Content Routing in the Nuxeo Platform 5.6, extends the proven power of Nuxeo Enterprise Platform (Nuxeo EP) to the deliver content-centric applications needed by business users.
Page: CMIS
Content Management Interoperability Services (CMIS) CMIS is a specification for improving interoperability between Enterprise Content Management systems. OASIS approved CMIS as an OASIS Specification on May 1, 2010. It proposes a data model plus a set of
Page: Component
A component is a set of code and all kind of software instructions deployed on your Nuxeo Platform application. This Nuxeo Runtime term is inspired by the OSGi specification.    
Page: Content View
A content view is a list of data that comes from the repository. Most of the time, it is a list of documents, but it can also be a list of vocabularies or a list of audit entries. A content view is composed of a query, an optional filter, a result layout

D

Page: DAM
Digital Asset Management (DAM) DAM consists of management tasks and decisions surrounding the ingestion, annotation, cataloging, storage, retrieval and distribution of digital assets. Digital photographs, animations, videos and music are samples of media
Page: Document
Document The Document is the main structure managed by the Nuxeo Platform. A document in the Nuxeo Platform is an object that holds system properties and custom properties. It goes far beyond the “file” concept. Inside the Nuxeo Platform, documents are fi
Page: Document Type
Document Type A document type is the set of properties that define a document. A document type is defined by the list of its schemas, its life cycle, the forms to present to the user or its versioning policy.    

E

Page: EAR
EAR (Enterprise application ARchive) From Wikipedia: EAR (Enterprise application ARchive) is a file format used by Java EE for packaging one or more modules into a single archive so that the deployment of the various modules onto an application server hap
Page: ECM
Enterprise Content Management (ECM) ECM is a formalized means of organizing and storing an organization's documents, and other content, that relate to the organization's processes. The term encompasses strategies, methods, and tools used throughout the li

F

Page: Flavor
A flavor is a set of variables which defines the branding of an application: the logo, the backgrounds and borders colors, and the font family and color. The Nuxeo Platform uses these variables in its default style set. The flavors are used for the global

G

Page: Graph
Graph (Workflow) A graph is the definition of a workflow process. It tells the server what should happen first, how execution is orchestrated, which nodes are orchestrate, etc. The graph has a start node, and one or multiple end nodes and between them a s

H

I

J

K

L

Page: Layout
A layout is a definition of how data or UI components should be organized on the screen, in terms of “position”. A layout is organized either as a table or as a “grid”.  Layouts are used for specifying how the content of a tab in the UI should be displaye
Page: Lifecycle
The life cycle of a document defines the states the document can be in. It also defines the possible paths, called transitions, to go from one state to another. The life cycle is useful to say a case is “created”, “being_processed”, “processed”, “archived
Page: Log4J
From Log4J page on Wikipedia: Apache log4j is a Java-based logging utility. It was originally written by Ceki Gülcü and is now a project of the Apache Software Foundation. log4j is one of several Java Logging Frameworks. See the Apache Log4J documentation

M

Page: Module
Module A module can be seen as a set of plugins that altogether add a useful functionality to the platform. The Nuxeo Platform has three modules available that enable you to easily add sets of features to the default content management functionalities, to

N

Page: Node
Node (Workflow)  A workflow node is a “step” of the workflow model. The node holds a set of configurable properties that define what the workflow engine should do at this step. For instance, it can create a task for someone,  send some notifications, upda
Page: Nuxeo EP
Nuxeo Enterprise Platform (Nuxeo EP) Nuxeo Platform (aka Nuxeo EP in versions up to 5.4.x) is a platform for building ECM applications. It provides the technical infrastructure and the high-level services needed to build customized ECM applications. In or
Home page: Nuxeo Glossary
This glossary will help you understand terms or acronyms with which you may not be familiar, or which may require explanation.   Navigate space
Page: Nuxeo Platform
Page: NXQL
NXQL stands for Nuxeo Query Language. It is a SQL-like language used to query documents in a Nuxeo repository. NXQL allows for querying documents with their metadata as well as their full-text content. Related pages:  NXQL in developer documentation How t
Page: NXR
NXR (NuXeo application aRchive) Definition The Nuxeo application archive is a structure built by a Nuxeo packaging process. That archive (a ZIP or an exploded directory) contains all the required Nuxeo bundles and third-party libraries assembled as an app

O

P

Page: Plug-in
A plug-in is a JAR (Java packaging) that contains none to several components and resources that are deployed on the Nuxeo Application. Related pages: Plug-in in developer documentation Plug-in in Studio documentation
Page: Property
Property Also sometimes referred to as metadata, properties are the granular elements of data stored on a document. There are different types of properties: text properties are strings; dates are stored as such; yes/no properties are booleans; numbered pr

Q

R

Page: Repository
Repository The repository is the part of the Nuxeo Platform in charge of storing and serving the documents. It embeds a lot of logic to ensure the security and availability of the documents. We could make a parallel between a database and a repository. Th

S

Page: Schema
Schema A schema is a set of property definitions. For instance, the Nuxeo Platform uses the Dublin Core schema for most of its documents. A document that holds the Dublin Core schema has the following properties: a title, a description, a creation date, a

T

Page: Tab
A tab in the Nuxeo Platform is a view displayed on a document, controlled by a filter. It is a UI pattern used for presenting information and user actions related to one concept on the document. On the same document users with different profiles will have
Page: Task
Task (Workflow) A task is a persisted object that represents what a workflow instance expects from a user or a group of users. Usually they are expected to give some information through a form and click on a button (like Accept, Reject, Confirm, Notify, T
Page: Transition
Transition (Life cycle)  A transition is what enables a document to go from one state to another in a life cycle. Studio documentation about transitions in life cycle: Life cycle Developer documentation about transitions in life cycle: Repository Concepts

U

V

Page: VCS
Visible Content Store (VCS) VCS is a storage model for Nuxeo documents that uses a SQL database as a backend and stores data in a clear and understandable manner (hence the name). VCS is available since Nuxeo 5.2 and is the default backend storage since N
Page: Vocabulary
A vocabulary is a list of values stored in the Nuxeo Platform. Vocabularies are used to let the user choose the value of a document property among a controlled list of values. Power users and administrators can edit vocabularies from the Admin Center. The

W

Page: WAR
WAR (Web application ARchive) From Wikipedia: A WAR file (or Web application ARchive1) is a JAR file used to distribute a collection of JavaServer Pages, Java Servlets, Java classes, XML files, tag libraries, static Web pages (HTML and related files) and
Page: Widget
A widget is an element of UI that can be displayed via the layout system. A widget can have a varying complexity. They can be used to display a static text, to pickup values in a list or, for the most complex ones, to display a full  form or list of data.
Page: Workflow Engine
The Nuxeo Platform embeds a workflow engine. This workflow engine knows how to read a workflow model. It starts a specific instance from the model, from the beginning to the end of the process execution. You should read the Workflow Model entry for a bett
Page: Workflow Instance
A workflow instance is the instance of the execution of one given workflow model by the workflow engine. A workflow instance hold the data bound to a specific execution as well as the current state of execution.  A workflow instance is composed of node in
Page: Workflow Model
A workflow model is an enterprise process digitized in the platform. Typical candidates to this digitization are documents validation, purchase orders, case processing, invoice management. From a technical point of view, a workflow is an automated process

X

Y

Z

!@#$

Recently Updated

 
Navigate space
  • No labels