Web Service Manual: November 2017 Author Tecnoteca SRL
Web Service Manual: November 2017 Author Tecnoteca SRL
2.5
November 2017
Author Tecnoteca srl
www.tecnoteca.com
ENG
www.cmdbuild.org
Web Service Manual
No part of this document may be reproduced, in whole or in part, without the express written permission
of Tecnoteca s.r.l.
CMDBuild ® uses many great technologies from the open source community:
PostgreSQL, Apache, Tomcat, Eclipse, Ext JS, JasperReports, IReport, Enhydra Shark, TWE, OCS
Inventory, Liferay, Alfresco, GeoServer, OpenLayers, Prefuse, Quartz, BiMserver.
We are thankful for the great contributions that led to the creation of these products.
Contents
Introduction...................................................................................................................................... 4
CMDBuild modules...................................................................................................................................... 4
Available documentation.............................................................................................................................. 5
Interoperability standards................................................................................................................. 6
Service-Oriented Architecture (SOA)........................................................................................................... 6
Web service and SOAP protocol......................................................................................................7
Examples of usage...................................................................................................................................... 7
Provided services........................................................................................................................................ 7
Description of support data structures....................................................................................................... 10
Description of web service methods.......................................................................................................... 13
Definition of authentication policy file......................................................................................................... 16
REST web service.......................................................................................................................... 18
Services..................................................................................................................................................... 18
APPENDIX: Glossary..................................................................................................................... 85
Introduction
CMDBuild is an Open Source web application designed to model and manage assets and services
controlled by the ICT Department, therefore it handles the related workflow operations, if
necessary according to ITIL best practices.
The management of a Configuration Database (CMDB) means keeping up-to-date, and available
to other processes, the database related to the components in use, their relations and their
changes over time.
With CMDBuild, the system administrator can build and extend its own CMDB (hence the project
name), modeling the CMDB according to the company needs; the administration module allows you to
progressively add new classes of items, new attributes and new relations. You can also define filters,
"views" and access permissions limited to rows and columns of every class.
CMDBuild provides complete support for ITIL best practices, which have become a "standard de
facto" by now, a non-proprietary system for services management with process-oriented criteria.
Thanks to the integrated workflow engine, you can create new workflow processes with external
visual editors, and import / execute them inside the CMDBuild application according to the
configured automatisms.
A task manager integrated in the user interface of the Administration Module is also available. It
allows to manage different operations (process starts, e-mail receiving and sending, connector
executions) and data controls on the CMDB (synchronous and asynchronous events). Based on
their findings, it sends notifications, starts workflows and executes scripts.
CMDBuild includes also JasperReports, an open source report engine that allows you to create
reports; you can design (with an external editor), import and run custom reports inside CMDBuild.
Then it is possible to define some dashboards made up of charts which immediately show the situation
of some indicators in the current system (KPI).
CMDBuild integrates Alfresco, the popular open source document management system. You can
attach documents, pictures and other files.
Moreover, you can use GIS features to georeference and display assets on a geographical map
(external map services) and / or an office plan (local GeoServer) and BIM features to view 3D
models (IFC format).
The system includes also a SOAP and a REST webservice, to implement interoperability solutions
with SOA.
CMDBuild includes two frameworks called Basic Connector and Advanced Connector, which are
able - through the SOAP webservice - to sync the information recorded in the CMDB with external
data sources, for example through automatic inventory systems (such as the open source OCS
Inventory) or through virtualization or monitoring systems.
Through the REST webservice, CMDBuild GUI Framework allows to issue custom webpages on
external portals able to interact with the CMDB.
A user interface for mobile tools (smartphones and tablets) is also available. It is implemented as
multi-platform app (iOS, Android) and linked to the CMDB through the REST webservice.
CMDBuild modules
The CMDBuild application includes two main modules:
• the Administration Module, used to define the data model and set config options (classes
and relations, users and permissions, reports and workflows, main options and
preferences)
• the Management Module, used to manage cards and relations, add attachments, run
workflow processes, visualize dashboards and execute reports
The Administration Module is available only to the users with the "administrator" role; the
Management Module is used by all the users who view and edit data.
Available documentation
This manual is for computer technicians, who manage external applications and who are interested
in interoperating with CMDBuild. It supplies the detail information necessary to implement the
communication system for the read-write access of its data and functions.
You can find all the manuals on the official website (http://www.cmdbuild.org):
• system overview ("Overview Manual")
• system administration ("Administrator Manual")
• system usage (“User Manual”)
• installation and system management ("Technical Manual")
• webservice details and configuration (“Webservice Manual”)
• connectors to sync data through external systems (“ConnectorsManual”)
Interoperability standards
Service-Oriented Architecture (SOA)
In order to make different applications interoperable,
they must be created as components that cooperate
with the services implementation, and these services
must be set through high level interfaces defined under
standard protocols.
CMDBuild is designed with Service-Oriented
Architecture (SOA):
• decoupling the different logic levels (see the
schema)
• implementing and setting in every interface
external specifications as a single modality for
the access to relating data and methods
• using the interfaces both for the interactive
access of the web client and for the
programmatic access of external applications
From a technical point of view, we chose to use the
following technology of web services:
1. SOAP protocol
2. REST protocol
Through web services, and safety policy permitting, CMDBuild provides the data filed in the CMDB
and its management methods to allow the use within other applications involved with the
information itself, both for the technical management and for administration.
Examples of usage
The mechanism of application interoperability, provided by CMDBuild through the SOAP web
service, can be used to activate the dialogue with every other information system pre-existing in
the same organization and supporting that standard protocol.
Exhaustive examples of usage can include:
• activation in non-“JSR 168-compliant” intranet portals of simple interaction with CMDBuild
for non-technicians (report print, workflow start or development, etc)
• synchronization with other CMDB tools
• integration with management applications which require to recover from CMDBuild the
updated inventory of fixed assets or which must take to CMDBuild administration data of a
fixed asset
• integration with monitoring technical tools which need to know information on assets
subject to their control
Provided services
Method categories
The CMDBuild web service provides methods for the external execution of basic functions
managed in the system, dedicated in particular to manage and print cards and to perform
processes.
In particular the available methods categories are as follows:
• management of cards: creation, modify, delete, search, history
• management of lists used to bind information fields to groups of predefined values:
Code Meaning
NOTFOUND_ERROR Element not found
AUTH_MULTIPLE_GROUPS The user is connected with multiple groups
AUTH_UNKNOWN_GROUP Unknown group
AUTH_NOT_AUTHORIZED The authorizations are not enough to
perform the operation
ORM_GENERIC_ERROR An error has occurred while reading/saving
data
ORM_DUPLICATE_TABLE There is already a class with this name
ORM_CAST_ERROR Error in the type conversion
ORM_UNIQUE_VIOLATION Not null constraint violated
ORM_CONTAINS_DATA You can not delete classes or attributes of
tables or domains containing data
ORM_TYPE_ERROR Not corresponding type
ORM_ERROR_GETTING_PK The main key can not be determined
ORM_ERROR_LOOKUP_CREATION The lookup can not be created
ORM_ERROR_LOOKUP_MODIFY The lookup can not be modified
ORM_ERROR_LOOKUP_DELETE The lookup can not be deleted
ORM_ERROR_RELATION_CREATE The relation can not be created
ORM_ERROR_RELATION_MODIFY The relation can not be modified
ORM_CHANGE_LOOKUPTYPE_ERROR The lookup type can not be changed
ORM_READ_ONLY_TABLE Read-only table
ORM_READ_ONLY_RELATION Read-only relation
ORM_DUPLICATE_ATTRIBUTE There is already an attribute with this
name
ORM_DOMAIN_HAS_REFERENCE Domains with reference attributes can not
be deleted
ORM_FILTER_CONFLICT Conflict by defining the filter
ORM_AMBIGUOUS_DIRECTION The direction relation can not be
automatically determined
“Attribute” object
It represents a single "custom" attribute (which is additional if compared to the two default
attributes “Code” and “Description”) belonging to a card typology configured in the system.
Activity name Type Mandatory Default Description
name string Attribute name, as created with the CMDBuild
Administration Module.
It corresponds to the table name in the
database table.
value string It corresponds to the attribute value.
code string It is developed only for "Reference" attributes
with the id of the card.
“Lookup” object
It represents the value of a list with predefined values (Lookup list) used for the development of a
Lookup attribute.
“Query” object
It represents a filter on the values to search. The filter can be unique (Filter) or a set of conditions
with a common comparison operator (FilterOperator).
Activity name Type Mandatory Default Description
filter Filter Atomic filter condition
or
filterOperator FilterOperator Concatenation of filter conditions
“Filter” object
It represents an atomic filter condition to select a card list.
Activity name Type Mandatory Default Description
name string Attribute which the filter condition is applied to.
value string Value for the comparison with the attribute's
content.
operator string Comparison operator (values such as
EQUALS, LIKE are admitted).
“FilterOperator” object
It represents a concatenation of atomic filter conditions connected with an operator.
Activity name Type Mandatory Default Description
operator string Concatenation operator to join filter conditions
(values such as AND, OR are admitted)
Sample of operation to perform: creation of the filter “Supplier = Quasartek s.r.l. OR Supplier =
IBM Italia s.p.a.”
Filter1:
name: Supplier
value: Quasartek s.r.l.
operator: EQUALS
Filter2:
name: Supplier
value: IBM Italia s.p.a.
operator: EQUALS
FilterOperator:
subquery: [Filter1, Filter2]
operator: OR
Query:
filterOperator: FilterOperator
“Order” object
It represents the ordering standard among the cards drawn from the filter query.
Activity name Type Mandatory Default Description
columnName string Attribute which the ordering is performed on.
type string Ordering typology applied (only ASC and
DESC values are admitted).
“Relation” object
It represents a correlation between pairs of cards, filed in the system.
Activity name Type Mandatory Default Description
domainName string Domain used for the relation.
class1Name string ClassName of the first card taking part in the
relation.
card1Id integer Identifier of the first card which takes part in
the relation
class2Name string ClassName of the second card which takes
part in the relation.
card2Id integer Identifier of the second card which takes part in
the relation.
status string A Relation status ('A' = active, 'N' = removed)
beginDate date Date when the relation was created (format
YYYY-MM-DDThh:mm:ssZ)
endDate date Date when the relation was created (format
YYYY-MM-DDThh:mm:ssZ)
“Attachment” object
It represents a document enclosed in a card filed in the system.
Activity name Type Mandatory Default Description
category string Category which the attachment belongs to
(from proper Lookup list).
description string Description related to the attachment.
filename string Attachment name with extension
version string Document version in the DMS Alfresco
author string User that performs the file upload
created date Date when the document was inserted in the
DMS
modified date Date of the last change to the document in the
DMS
getCardList string className Card[] cardList It returns the card list resulting from the
Attribute[] attributeList specified query, completed with all
Query queryType attributes specified in “attributeList” (all
Order[] orderType card attributes if “attributeList” is null).
If the query is made on a superclass, the
"className" attribute of the returned Card
objects contains the name of the specific
subclass the card belongs to, while in the
attributeList it appears the ClassId of the
same subclass.
getCardHistory string className Card[] cardList It returns the list of the historicized
integer cardId versions of the specified card.
deleteRelation Relation relation boolean return It deletes the existing relation between the
pair of cards specified in the "Relation" object.
It returns “true” if the operation went through.
getRelationList string domain Relation[] It returns the complete list of relations of the
string className relationList card specified for the specified domain.
integer cardId
getRelationHi Relation relation Relation[] It returns the relation history of a card starting
story relationList from a "Relation" object in which only
"Class1Name" and "Card1Id" were defined.
updateAttach string className boolean return It updates the description of the file enclosed
ment integer cardId in the specified card, which has the specified
string fileName name.
string description It returns “true” if the operation went through.
securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:HashPassword/>
</wsp:Policy>
</sp:UsernameToken>
</wsp:Policy>
</sp:SignedSupportingTokens>
<ramp:RampartConfgxmlns:ramp="http://ws.apache.org/rampart/policy">
<ramp:passwordCallbackClass>
org.cmdbuild.services.soap.secure.MyPasswordHandler
</ramp:passwordCallbackClass>
</ramp:RampartConfg>
</wsp:ExactlyOne>
</wsp:Policy>
For a deeper treatement of WS-SecurityPolicy, please refer to the related official document2.
2 http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf
Version 1
Endpoint
http://hostname:port/cmdbuild/services/rest/v1
Dates format
All dates (time, timestamp and date attributes) uses the format "yyyy-MM-dd'T'HH:mm:ss".
Session management
Access to the various resources is subject to the opening of a session that have associated some
privileges. Each session is identified by an alphanumeric string or "token".
Access to those resources requiring a session
After a session has been created or updated, its identifier must be used for all those resources that
require it. The identifier should be sent within request's header.
GET .../classes/foo/cards/ HTTP/1.1
[various other headers]
CMDBuild-Authorization: 0123456789ABCDF...
If the resource requires a session and the token is not sent or is not correct then the answer will
be:
HTTP/1.1 401 Unauthorized
[various headers]
Creation of a session
This is the only one method that does not require a session.
POST .../sessions/ HTTP/1.1
[various other headers]
{
username : ...,
password : ...
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id : ${SESSION}
username : ...
password : null
role : ...
}
}
Reading a session
GET .../sessions/${SESSION}/ HTTP/1.1
[various other headers]
HTTP/1.1 200 OK
[various headers]
{
username : ...
password : null
role : ...
}
Paying attention to the attribute role, if valued with "null" or absent then you will have some partial
authorizations, otherwise you will have full authorizations. If the user has only one role, then
already after creating this will be present within the session. Alternatively you will need to update
the credentials.
Update of a session
PUT .../sessions/${SESSION}/ HTTP/1.1
[various other headers]
{
role : ...,
}
You can change the role associated with a session (thus passing from a session with partial
authorizations to complete and vice versa).
Deletion of a session
DELETE .../sessions/${SESSION}/ HTTP/1.1
[various other headers]
HTTP/1.1 204 OK
[various headers]
HTTP/1.1 200 OK
[various headers]
{
data : [foo, bar]
}
Lookup management
Reading of all types
GET .../lookup_types HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_id : ...,
name : ...,
parent : ...
},
...
{
...
},
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id : ...,
name : ...,
parent : ...
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_type" : AlfrescoCategory,
_id" : 703,
code" : null,
description" : Document,
parent_type" : null,
active" : true,
number" : 1,
default" : false,
parent_id" : null
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_type" : AlfrescoCategory,
_id" : 703,
code" : null,
description" : Document,
parent_type" : null,
active" : true,
number" : 1,
default" : false,
parent_id" : null
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [
{
_id : Asset,
name : Asset,
description : Asset,
parent : Class,
prototype : true
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id : Asset,
name : Asset,
description : Asset,
description_attribute_name : Description,
parent : Class,
prototype : true
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
lookupType : null,
index : 1,
group : General data,
unique : false,
scale : null,
editorType : null,
targetClass : null,
active : true,
description : Code,
type : string,
displayableInList : true,
values : [],
length : 100,
name : Code,
_id : Code,
flter : null,
mandatory : false,
precision : null,
defaultValue" : null,
inherited" : true
},
...
{
...
}
]
}
Creation of a card
POST .../classes/Building/cards HTTP/1.1
[various headers]
{
Code = test,
...
}
HTTP/1.1 200 OK
[various headers]
{
data : 3217
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
Room : null,
Description : Acer - AL1716,
Notes : null,
Workplace : null,
ScreenSize : null,
Brand : 138,
PurchaseDate : null,
SerialNumber : null,
AcceptanceNotes : null,
Code : MON0001,
TechnicalReference" : null,
FinalCost : null,
AcceptanceDate : null,
Model : AL1716,
_id : 550,
_type : Asset,
Assignee : 134,
Type" : null,
Supplier" : null
},
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
Room : null,
Description : Acer - AL1716,
Notes : null,
Workplace : null,
ScreenSize : null,
Brand : 138,
PurchaseDate : null,
SerialNumber : null,
AcceptanceNotes : null,
Code : MON0001,
TechnicalReference" : null,
FinalCost : null,
AcceptanceDate : null,
Model : AL1716,
_id : 550,
_type : Asset,
Assignee : 134,
Type" : null,
Supplier" : null
}
}
Update of a card
PUT .../classes/Building/cards/3217 HTTP/1.1
[various headers]
{
Code = test,
...
}
Deletion of a card
DELETE .../classes/Building/cards/3217 HTTP/1.1
[various headers]
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [
{
_id : WorkplaceComposition,
name : WorkplaceComposition,
description : Workplace composition
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
data" : {
_id : WorkplaceComposition,
descriptionMasterDetail : Asset,
sourceProcess : false,
descriptionInverse : belongs to workplace,
descriptionDirect : includes assets,
destinationProcess : false,
name : WorkplaceComposition,
source : Workplace,
destination : Asset,
cardinality : 1:N,
description : Workplace composition
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : 1
},
data : [
{
targetClass : null,
editorType : null,
unique : false,
description : Default Group,
index : 1,
defaultValue : null,
lookupType : null,
active : true,
precision : null,
inherited : false,
displayableInList : true,
name : DefaultGroup,
mandatory : false,
type : boolean,
group : null,
scale : null,
values : [],
_id : DefaultGroup,
flter" : null,
length" : null
}
]
}
Creation of a relation
POST .../domains/UserRole/relations/ HTTP/1.1
[various headers]
{
date : {
_sourceType : User,
_sourceId : 123,
_destinationType : Role,
_destinationId : 456,
DefaultGroup : false
}
}
HTTP/1.1 200 OK
[various headers]
{
data : 789
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_destinationDescription : Helpdesk,
_sourceDescription : Jones Patricia,
_sourceType : User,
_sourceId : 678,
_destinationType : Role,
_type : UserRole,
_destinationId : 677,
_id : 681
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id : 681,
_destinationId : 677,
_destinationType : Role,
_destinationDescription : Helpdesk,
_sourceId : 678,
_sourceDescription : Jones Patricia,
_type : UserRole,
DefaultGroup : null,
_sourceType : User
}
}
Update of a relation
POST .../domains/UserRole/relations/123 HTTP/1.1
[various headers]
{
date : {
DefaultGroup : true
}
}
Deletion of a relation
DELETE .../domains/UserRole/relations/123 HTTP/1.1
[various headers]
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [
{
_id : RequestForChange,
name : RequestForChange,
prototype : false,
parent : Activity,
description : Request for change
}
...
{
...
}
]
}
Read of the details of a process
GET .../processes/RequestForChange HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
date : {
name : RequestForChange,
statuses : [
6,
7,
8,
10
],
description : Request for change,
description_attribute_name : Description,
prototype : false,
_id : RequestForChange,
parent : Activity,
defaultStatus : 6
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
name : Dummy,
scale : null,
_id : Dummy,
inherited : false,
precision" : null,
description : Dummy,
editorType : null,
type : string,
unique : false,
targetClass : null,
defaultValue : null,
values : [],
flter : null,
group : null,
lookupType : null,
length : 100,
mandatory : false,
index : 0,
active : true,
displayableInList : false
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : 1
}
data : [
{
_id : RegisterRFC,
description : Register RFC,
writable : true
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
attributes : [
{
mandatory : true,
_id : Requester,
index : 0,
writable : true
},
{
writable : true,
index : 1,
_id : RFCDescription,
mandatory : true
}
],
instructions : ...,
description : Register RFC,
widgets : [],
_id : RegisterRFC
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
description : Formal evaluation,
_id : foo,
writable : true
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
widgets : [
{
type : .OpenAttachment,
active : true,
_id : widget-57a9a9d9,
required : false,
date : {
...
},
label : Attachments
},
...
{
...
}
],
_id : FormalEvaluation,
attributes : [
{
mandatory : false,
writable : false,
_id : RFCStartDate,
index : 0
},
...
{
...
}
],
instructions : ...,
description : Formal evaluation
}
}
HTTP/1.1 200 OK
[various headers]
{
data : 1460
According with the value of the "_advance" attribute, an instance can be advanced or just saved.
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [
{
Category : null,
FinalResult : null,
RFCEndDate : null,
ExecutionEndDate : null,
RFCDescription : test,
Requester : 123,
...
_type : RequestForChange,
_name : null,
_id : 1460,
_status : 6
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
FinalResult : null,
RFCEndDate : null,
ExecutionEndDate : null,
RFCDescription : test,
Requester : 123,
...
_type : RequestForChange,
_name : null,
_id : 1460,
_status : 6
}
}
Update of an instance
PUT .../processes/RequestForChange/instances/1460 HTTP/1.1
[various headers]
{
Requester : 123,
RFCDescription : test,
_advance = true
}
According with the value of the "_advance" attribute, an instance can be advanced or just saved.
Deletion of an instance
DELETE .../processes/RequestForChange/instances/1460 HTTP/1.1
[various headers]
Menu management
Reading of the menu
GET .../menu HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
date : {
menuType : root,
children : [
{
menuType : folder,
objectId : 0,
children" : [
...
],
...
},
...
{
objectDescription : Employee,
children : [],
objectType : Employee,
objectId : 0,
index : 34,
menuType : class
},
]
}
}
Configuration management
Reading of all attachments categories
GET .../confguration/attachments/categories HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_id : Document,
description : Document"
},
...
{
description : Image,
_id : Image
}
]
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
length : null,
index : 0,
editorType : null,
targetClass : null,
inherited : null,
...
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_id : 6,
description : Open,
value : open
},
...
{
...
}
]
}
Privileges management
Reading of all privileges for a role
GET .../roles/Foo/classes_privileges HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
name : UPS,
description : UPS,
mode : w,
_id : UPS
},
...
{
name : License,
_id : License,
description : License,
mode" : r
}
]
}
Attachments management
It is applied in the same way as reported for process instances. So, by replacing
.../classes/${CLASS_ID}/cards/${CARD_ID}
with
.../processes/${PROCESS_ID}/instances/${PROCESS_ID}
you will have the same capabilities.
Upload of an attachment
POST .../classes/Building/cards/64/attachments HTTP/1.1
[various headers]
Content-Type : multipart/form-data
HTTP/1.1 200 OK
[various headers]
{
data : abc123
}
Notes:
• the mehod uses “multipart/form-data” content-type
• uploads file and sets properies
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [
{
_name : test.jpg,
_id" : "abc123,
_version : 1.3,
_description : this is a test,
_modifed" : 2014-12-16T12:35:12,
_category" : Image,
_created" : 2014-11-20T14:20:04,
_author" : admin
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_category : Image,
_created : 2014-11-20T14:20:04,
_description : this is a test,
_author : admin,
_id : abc123,
_version : 1.3,
_modifed : 2014-12-16T12:35:12,
_name : test.jpg
}
}
Download of an attachment
GET .../classes/Building/cards/64/attachments/abc123/download.jpg HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
Content-Type : application/octet-stream
Update of an attachment
PUT .../classes/Building/cards/64/attachments/abc123 HTTP/1.1
[various headers]
Content-Type : multipart/form-data
Notes:
• the mehod uses “multipart/form-data” content-type
• it uploads file and sets properties
Deletion of an attachment
DELETE .../classes/Building/cards/64/attachments/abc123 HTTP/1.1
[various headers]
Version 2
Endpoint
http://hostname:port/cmdbuild/services/rest/v2
Dates format
All dates (time, timestamp and date attributes) uses the format "yyyy-MM-dd'T'HH:mm:ss".
Session management
Access to the various resources is subject to the opening of a session that have associated some
privileges. Each session is identified by an alphanumeric string or "token".
Access to those resources requiring a session
After a session has been created or updated, its identifier must be used for all those resources that
require it. The identifier should be sent within request's header.
GET .../classes/foo/cards/ HTTP/1.1
[various other headers]
CMDBuild-Authorization: 0123456789ABCDF...
If the resource requires a session and the token is not sent or is not correct then the answer will
be:
HTTP/1.1 401 Unauthorized
[various headers]
Creation of a session
This is the only one method that does not require a session.
POST .../sessions/ HTTP/1.1
[various other headers]
{
username : ...,
password : ...
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id : ${SESSION}
username : ...
password : null
role : ...
}
}
Reading a session
GET .../sessions/${SESSION}/ HTTP/1.1
HTTP/1.1 200 OK
[various headers]
{
username : ...
password : null
role : ...
}
Paying attention to the attribute role, if valued with "null" or absent then you will have some partial
authorizations, otherwise you will have full authorizations. If the user has only one role, then
already after creating this will be present within the session. Alternatively you will need to update
the credentials.
Update of a session
PUT .../sessions/${SESSION}/ HTTP/1.1
[various other headers]
{
role : ...,
}
You can change the role associated with a session (thus passing from a session with partial
authorizations to complete and vice versa).
Deletion of a session
DELETE .../sessions/${SESSION}/ HTTP/1.1
[various other headers]
HTTP/1.1 204 OK
[various headers]
HTTP/1.1 200 OK
[various headers]
{
data : [foo, bar]
}
Lookup management
Reading of all types
GET .../lookup_types HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_id : ...,
name : ...,
parent : ...
},
...
{
...
},
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id : ...,
name : ...,
parent : ...
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_type" : AlfrescoCategory,
_id" : 703,
code" : null,
description" : Document,
parent_type" : null,
active" : true,
number" : 1,
default" : false,
parent_id" : null
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_type" : AlfrescoCategory,
_id" : 703,
code" : null,
description" : Document,
parent_type" : null,
active" : true,
number" : 1,
default" : false,
parent_id" : null
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [
{
_id : Asset,
name : Asset,
description : Asset,
parent : Class,
prototype : true
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id : Asset,
name : Asset,
description : Asset,
description_attribute_name : Description,
parent : Class,
prototype : true
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
lookupType : null,
index : 1,
group : General data,
unique : false,
scale : null,
editorType : null,
targetClass : null,
active : true,
description : Code,
type : string,
displayableInList : true,
values : [],
length : 100,
name : Code,
_id : Code,
flter : null,
mandatory : false,
precision : null,
defaultValue" : null,
inherited" : true
},
...
{
...
}
]
}
Creation of a card
POST .../classes/Building/cards HTTP/1.1
[various headers]
{
Code = test,
...
}
HTTP/1.1 200 OK
[various headers]
{
data : 3217
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
Room : null,
Description : Acer - AL1716,
Notes : null,
Workplace : null,
ScreenSize : null,
Brand : 138,
PurchaseDate : null,
SerialNumber : null,
AcceptanceNotes : null,
Code : MON0001,
TechnicalReference" : null,
FinalCost : null,
AcceptanceDate : null,
Model : AL1716,
_id : 550,
_type : Asset,
Assignee : 134,
Type" : null,
Supplier" : null
},
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
Room : null,
Description : Acer - AL1716,
Notes : null,
Workplace : null,
ScreenSize : null,
Brand : 138,
PurchaseDate : null,
SerialNumber : null,
AcceptanceNotes : null,
Code : MON0001,
TechnicalReference" : null,
FinalCost : null,
AcceptanceDate : null,
Model : AL1716,
_id : 550,
_type : Asset,
Assignee : 134,
Type" : null,
Supplier" : null
}
}
Update of a card
PUT .../classes/Building/cards/3217 HTTP/1.1
[various headers]
{
Code = test,
...
}
Deletion of a card
DELETE .../classes/Building/cards/3217 HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [
{
_id : WorkplaceComposition,
name : WorkplaceComposition,
description : Workplace composition
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
data" : {
_id : WorkplaceComposition,
descriptionMasterDetail : Asset,
sourceProcess : false,
descriptionInverse : belongs to workplace,
descriptionDirect : includes assets,
destinationProcess : false,
name : WorkplaceComposition,
source : Workplace,
destination : Asset,
cardinality : 1:N,
description : Workplace composition
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : 1
},
data : [
{
targetClass : null,
editorType : null,
unique : false,
description : Default Group,
index : 1,
defaultValue : null,
lookupType : null,
active : true,
precision : null,
inherited : false,
displayableInList : true,
name : DefaultGroup,
mandatory : false,
type : boolean,
group : null,
scale : null,
values : [],
_id : DefaultGroup,
flter" : null,
length" : null
}
]
}
Creation of a relation
POST .../domains/UserRole/relations/ HTTP/1.1
[various headers]
{
_sourceType : User,
_sourceId : 123,
_destinationType : Role,
_destinationId : 456,
DefaultGroup : false
}
HTTP/1.1 200 OK
[various headers]
{
data : 789
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_destinationDescription : Helpdesk,
_sourceDescription : Jones Patricia,
_sourceType : User,
_sourceId : 678,
_destinationType : Role,
_type : UserRole,
_destinationId : 677,
_id : 681
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id : 681,
_destinationId : 677,
_destinationType : Role,
_destinationDescription : Helpdesk,
_sourceId : 678,
_sourceDescription : Jones Patricia,
_type : UserRole,
DefaultGroup : null,
_sourceType : User
}
}
Update of a relation
POST .../domains/UserRole/relations/123 HTTP/1.1
[various headers]
{
date : {
DefaultGroup : true
}
}
Deletion of a relation
DELETE .../domains/UserRole/relations/123 HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [
{
_id : RequestForChange,
name : RequestForChange,
prototype : false,
parent : Activity,
description : Request for change
}
...
{
...
}
]
}
Read of the details of a process
GET .../processes/RequestForChange HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
date : {
name : RequestForChange,
statuses : [
6,
7,
8,
10
],
description : Request for change,
description_attribute_name : Description,
prototype : false,
_id : RequestForChange,
parent : Activity,
defaultStatus : 6
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
name : Dummy,
scale : null,
_id : Dummy,
inherited : false,
precision" : null,
description : Dummy,
editorType : null,
type : string,
unique : false,
targetClass : null,
defaultValue : null,
values : [],
flter : null,
group : null,
lookupType : null,
length : 100,
mandatory : false,
index : 0,
active : true,
displayableInList : false
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : 1
}
data : [
{
_id : RegisterRFC,
description : Register RFC,
writable : true
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
attributes : [
{
mandatory : true,
_id : Requester,
index : 0,
writable : true
},
{
writable : true,
index : 1,
_id : RFCDescription,
mandatory : true
}
],
instructions : ...,
description : Register RFC,
widgets : [],
_id : RegisterRFC
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
description : Formal evaluation,
_id : foo,
writable : true
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
widgets : [
{
type : .OpenAttachment,
active : true,
_id : widget-57a9a9d9,
required : false,
date : {
...
},
label : Attachments
},
...
{
...
}
],
_id : FormalEvaluation,
attributes : [
{
mandatory : false,
writable : false,
_id : RFCStartDate,
index : 0
},
...
{
...
}
],
instructions : ...,
description : Formal evaluation
}
}
HTTP/1.1 200 OK
[various headers]
{
data : 1460
}
According with the value of the "_advance" attribute, an instance can be advanced or just saved.
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [
{
Category : null,
FinalResult : null,
RFCEndDate : null,
ExecutionEndDate : null,
RFCDescription : test,
Requester : 123,
...
_type : RequestForChange,
_name : null,
_id : 1460,
_status : 6
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
FinalResult : null,
RFCEndDate : null,
ExecutionEndDate : null,
RFCDescription : test,
Requester : 123,
...
_type : RequestForChange,
_name : null,
_id : 1460,
_status : 6
}
}
Update of an instance
PUT .../processes/RequestForChange/instances/1460 HTTP/1.1
[various headers]
{
Requester : 123,
RFCDescription : test,
_advance = true
_activity = CurrentActivityName
}
According with the value of the "_advance" attribute, an instance can be advanced or just saved.
Deletion of an instance
DELETE .../processes/RequestForChange/instances/1460 HTTP/1.1
[various headers]
Menu management
Reading of the menu
GET .../menu HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
date : {
menuType : root,
children : [
{
menuType : folder,
objectId : 0,
children" : [
...
],
...
},
...
{
objectDescription : Employee,
children : [],
objectType : Employee,
objectId : 0,
index : 34,
menuType : class
},
]
}
}
Configuration management
Reading of all attachments categories
GET .../confguration/attachments/categories HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_id : Document,
description : Document"
},
...
{
description : Image,
_id : Image
}
]
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
length : null,
index : 0,
editorType : null,
targetClass : null,
inherited : null,
...
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_id : 6,
description : Open,
value : open
},
...
{
...
}
]
}
Privileges management
Reading of all privileges for a role
GET .../roles/Foo/classes_privileges HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
name : UPS,
description : UPS,
mode : w,
_id : UPS
},
...
{
name : License,
_id : License,
description : License,
mode" : r
}
]
}
Attachments management
It is applied in the same way as reported for process instances. So, by replacing
.../classes/${CLASS_ID}/cards/${CARD_ID}
with
.../processes/${PROCESS_ID}/instances/${PROCESS_ID}
you will have the same capabilities.
Upload of an attachment
POST .../classes/Building/cards/64/attachments HTTP/1.1
[various headers]
Content-Type : multipart/form-data
HTTP/1.1 200 OK
[various headers]
{
data : abc123
}
Notes:
• the mehod uses “multipart/form-data” content-type
• uploads file and sets properies
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [
{
_name : test.jpg,
_id" : "abc123,
_version : 1.3,
_description : this is a test,
_modifed" : 2014-12-16T12:35:12,
_category" : Image,
_created" : 2014-11-20T14:20:04,
_author" : admin
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_category : Image,
_created : 2014-11-20T14:20:04,
_description : this is a test,
_author : admin,
_id : abc123,
_version : 1.3,
_modifed : 2014-12-16T12:35:12,
_name : test.jpg
}
}
Download of an attachment
GET .../classes/Building/cards/64/attachments/abc123/download.jpg HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
Content-Type : application/octet-stream
Update of an attachment
PUT .../classes/Building/cards/64/attachments/abc123 HTTP/1.1
[various headers]
Content-Type : multipart/form-data
binary
====
Notes:
• the mehod uses “multipart/form-data” content-type
• it uploads file and sets properties
Deletion of an attachment
DELETE .../classes/Building/cards/64/attachments/abc123 HTTP/1.1
[various headers]
CQL query
Query execution
GET .../cql?... HTTP/1.1
[various headers]
Parameters:
• filter: it includes the expression
{
CQL: ...
}
• sort: it includes the organized list of the attributes to execute the order
[
{
property: Description
direction: ASC
},{
property: Code
direction: DESC
}
]
• limit: it includes the number of the returned results
• start: it includes the offset from the beginning of the list
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [
{
_id : Asset,
name : Asset,
description : Asset,
parent : Class,
prototype : true
},
...
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id: ...
name: ...
description: ...
from: ...
to: ...
cc: ...
bcc: ...
subject: ...
body: ...
notifyWith: ...
noSubjectPrefx: ...
account: ...
keepSynchronization: ...
promptSynchronization: ...
delay: ...
}
}
E-mail management
It is applied in the same way as reported for process instances. So, by replacing
.../classes/${CLASS_ID}/cards/${CARD_ID}/emails
with
.../processes/${PROCESS_ID}/instances/${PROCESS_ID}/emails
you will have the same capabilities.
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
}
data : [ received, draft, outgoing, sent ]
}
In order to send an e-mail, it should be set as "outgoing". At that point you cannot change it
anymore.
Creation of an e-mail
POST .../classes/Building/cards/64/emails HTTP/1.1
[various headers]
{
from: ...
to: ...
cc: ...
bcc: ...
subject: ...
body: ...
status: ...
notifyWith: ...
noSubjectPrefx: ...
account: ...
template: ...
keepSynchronization: ...
promptSynchronization: ...
delay: ...
}
HTTP/1.1 200 OK
[various headers]
{
date : 123
}
E-mails are always created in a “draft” status. In order to send e-mails, you have to update them
after their creation and set the “outgoing” status.
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
from: ...
to: ...
cc: ...
bcc: ...
subject: ...
body: ...
status: ...
notifyWith: ...
noSubjectPrefx: ...
account: ...
template: ...
keepSynchronization: ...
promptSynchronization: ...
delay: ...
},
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
from: ...
to: ...
cc: ...
bcc: ...
subject: ...
body: ...
status: ...
notifyWith: ...
noSubjectPrefx: ...
account: ...
template: ...
keepSynchronization: ...
promptSynchronization: ...
delay: ...
}
}
E-mail update
PUT .../classes/Building/cards/64/emails/123 HTTP/1.1
[various headers]
{
from: ...
to: ...
cc: ...
bcc: ...
subject: ...
body: ...
status: ...
notifyWith: ...
noSubjectPrefx: ...
account: ...
template: ...
keepSynchronization: ...
promptSynchronization: ...
delay: ...
}
Deletion of an e-mail
DELETE .../classes/Building/cards/64/emails/123 HTTP/1.1
[various headers]
Management of functions
Reading of all functions
GET .../functions?start=...&limit=... HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
name: ...
description: ...
},
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
name: ...
description: ...
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
type: ...
name: ...
description: ...
...
},
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
type: ...
name: ...
description: ...
...
},
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
...
},
{
...
}
]
}
Report management
Reading of all reports
GET .../reports?start=...&limit=... HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_id: ...
description: ...
},
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id: ...
title: ...
description: ...
}
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
type: ...
name: ...
description: ...
...
},
{
...
}
]
}
Download of a report
GET .../reports/123/somename.someextension?extension=...¶meters={“foo”: “FOO”,
“bar”: “BAR”, ...} HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
Content-Type : application/octet-stream
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_id: ...
description: ...
},
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id: ...
description: ...
nodes: [
{
_id: ...
parent: ...
metadata: {
...
}
},
...
]
}
}
Management of images
Reading of all folders
GET .../flestores/images/folders HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_id: ...
name: ...
parent: ...
},
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id: ...
name: ...
parent: ...
}
}
HTTP/1.1 200 OK
[various headers]
{
data : bar
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_id: ...
name: ...
parent: ...
},
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
_id: ...
name: ...
parent: ...
}
}
Download of a file
GET .../flestores/images/folders/foo/fles/bar/download HTTP/1.1
[various headers]
HTTP/1.1 200 OK
[various headers]
Content-Type : application/octet-stream
Deletion of a file
DELETE .../flestores/images/folders/foo/fles/bar HTTP/1.1
[various headers]
Icons management
JSON model of the icon:
{
_id: ...
type: ...
details: {
...
}
image: {
type: ...
details: {
…
}
}
}
type: it represents the kind of icon to upload. The supported types are
• class
• process
details: according to type
• type: class
id has to include the class name
• type: process
id has to include the process name
Creation of an icon
POST .../icons HTTP/1.1
[various headers]
{
type: ...
details: {
...
}
image: {
type: ...
details: {
…
}
}
}
HTTP/1.1 200 OK
[various headers]
{
date : 123
}
HTTP/1.1 200 OK
[various headers]
{
meta : {
total : ...
},
data : [
{
_id: ...
...
},
{
...
}
]
}
HTTP/1.1 200 OK
[various headers]
{
date : {
...
}
}
Update of an icon
PUT ..../icons/123 HTTP/1.1
[various headers]
{
...
}
Deletion of a file
DELETE .../icons/123 HTTP/1.1
[various headers]
APPENDIX: Glossary
ATTACHMENT
An attachment is a file associated to a card.
In order to manage the attachments, CMDBuild uses in embedded mode any document system
which is compatible with the standard protocol CMIS (or the DMS Alfresco until the version 3
through its native webservice).
The management of the attachments supports the versioning of those files that have been uploaded
a few times, with automatic numbering.
WORKFLOW STEP
"Activity" means one of the steps of which the process consists.
An activity has a name, an executor, a type, possible attributes and methods with statements
(CMDBuild API) to be executed.
A process instance is a single process that has been activated automatically by the application or
manually by an operator.
See also: Process
ATTRIBUTE
The term refers to an attribute of a CMDBuild class.
CMDBuild allows you to create new attributes (in classes and domains) or edit existing ones.
For example, in "supplier" class the attributes are: name, address, phone number, etc..
Each attribute corresponds, in the Management Module, to a form field and to a column in the
database.
See also: Class, Domain, Report, Superclass, Attribute Type
BIM
Method with the aim to support the whole life cycle of a building: from its construction, use and
maintenance, to its demolition, if any.
The BIM method (Building Information Modeling) is supported by several IT programs that can
interact through an open format for data exchange, called IFC (Industry Foundation Classes).
See also: GIS
CI
We define CI (Configuration Item) each item that provides IT service to the user and has a
sufficient detail level for its technical management.
CI examples include: server, workstation, software, operating system, printer, etc.
See also: Configuration
CLASS
A Class is a complex data type having a set of attributes that describe that kind of data.
A Class models an object that has to be managed in the CMDB, such as a computer, a software, a
service provider, etc.
CMDBuild allows the administrator - with the Administration Module - to define new classes or
delete / edit existing ones.
Classes are represented by cards and, in the database, by tables automatically created at the
definition time.
See also: Card, Attribute
CONFIGURATION
The configuration management process is designed to keep updated and available to other
processes the items (CI) information, their relations and their history.
It is one of the major ITIL processes managed by the application.
See also: CI, ITIL
DASHBOARD
In CMDBuild, a dashboard corresponds to a collection of different charts, in this way you can
immediately hold in evidence some key parameters (KPI) related to a particular management
aspect of the IT service.
See also: Report
DATABASE
The term refers to a structured collection of information, hosted on a server, as well as utility
software that handle this information for tasks such as initialization, allocation, optimization,
backup, etc..
CMDBuild relies on PostgreSQL, the most powerful, reliable, professional and open source
database , and uses its advanced features and object-oriented structure.
DOMAIN
A domain is a relation between two classes.
A domain has a name, two descriptions (direct and inverse), classes codes, cardinality and
attributes.
The system administrator, using the Administration Module, is able to define new domains or
delete / edit existing ones.
It is possible to define custom attributes for each domain.
See also: Class, Relation
DATA FILTER
A data filter is a restriction of the list of those elements contained in a class, obtained by specifying
boolean conditions (equal, not equal, contains, begins with, etc.) on those possible values that can
be accepted by every class attribute.
Data filters can be defined and used exceptionally, otherwise they can be stored by the operator
and then recalled (by the same operator or by operators of other user groups, which get the
permission to use them by the system Administrator)
See also: Class, View
GIS
A GIS is a system able to produce, manage and analyse spatial data by associating geographic
elements to one or more alphanumeric descriptions.
GIS functionalities in CMDBuild allow you to create geometric attributes (in addition to standard
attributes) that represent, on plans / maps, markers position (assets), polylines (cable lines) and
polygons (floors, rooms, etc.).
See also: BIM
GUI FRAMEWORK
It is a user interface you can completely customise. It is advised to supply a simplified access to
the application. It can be issued onto any webportals and can be used with CMDBuild through the
standard REST webservice.
See also: Mobile, Webservice
ITIL
"Best practices" system that established a "standard de facto"; it is a nonproprietary system for the
management of IT services, following a process-oriented schema (Information Technology
Infrastructure Library).
ITIL processes include: Service Support, Incident Management, Problem Management, Change
Management, Configuration Management and Release Management.
For each process, ITIL handles description, basic components, criteria and tools for quality
management, roles and responsibilities of the resources involved, integration points with other
processes (to avoid duplications and inefficiencies).
See also: Configuration
LOOKUP
The term "Lookup" refers to a pair of values (Code, Description) set by the administrator in the
Administration Module.
These values are used to bind the user's choice (at the form filling time) to one of the preset
values.
With the Administration Module it is possible to define new "LookUp" tables according to
organization needs.
MOBILE
It is a user interface for mobile tools (smartphones and tablets). It is implemented as multi-platform
app (iOS, Android) and can be used with the CMDB through the REST webservice.
See also: GUI Framework, Webservice
PROCESS
The term "process" (or workflow) refers to a sequence of steps that realize an action.
Each process will take place on specific assets and will be performed by specific users.
A process is activated by starting a new process (filling related form) and ends when the last
workflow step is executed.
See also: Workflow step
RELATION
A relation is a link between two CMDBuild cards or, in other words, an instance of a given domain.
A relation is defined by a pair of unique card identifiers, a domain and attributes (if any).
CMDBuild allows users, through the Management Module, to define new relations among the
cards stored in the database.
See also: Class, Domain
REPORT
The term refers to a document (PDF or CSV) containing information extracted from one or more
classes and related domains.
CMDBuild users run reports by using the Management Module; reports definitions are stored in the
database.
See also: Class, Domain, Database
CARD
The term "card" refers to an element stored in a class.
A card is defined by a set of values, i.e. the attributes defined for its class.
CMDBuild users, through the Management Module, are able to store new cards and update /
delete existing ones.
Card information is stored in the database and, more exactly, in the table/columns created for that
class (Administration Module).
See also: Class, Attribute
SUPERCLASS
A superclass is an abstract class used to define attributes shared between classes. From the
abstract class you can derive real classes that contain data and include both shared attributes
(specified in the superclass) and specific subclass attributes.
For example, you can define the superclass "Computer" with some basic attributes (RAM, HD,
etc.) and then define derived subclasses "Desktop", "Notebook", "Server", each one with some
specific attributes.
See also: Class, Attribute
ATTRIBUTE TYPE
Each attribute has a data type that represents attribute information and management.
The attribute type is defined using the Administration Module and can be modified within some
limitations, depending on the data already stored in the system.
CMDBuild manages the following attribute types: "Boolean", "Date", "Decimal", "Double", "Inet" (IP
address), "Integer", "Lookup" (lists set in "Settings" / "LookUp"), "Reference" (foreign key), "String",
"Text", "Timestamp".
See also: Attribute
VIEW
A view not only includes the whole content of a CMDB class, it is a group of cards defined in a
logical way.
In particular, a view can be defined in CMDBuild by applying a filter to a class (so it will contain a
reduced set of the same rows) or specifying an SQL function which extracts attributes from one or
more related classes.
The first view type maintains all functionalities available for a class, the second one allows the sole
display and search with fast filter.
See also: Class, Filter
WEBSERVICE
A webservice is an interface that describes a collection of methods, available over a network and
working using XML messages.
With webservices, an application allows other applications to interact with its methods.
CMDBuild includes a SOAP and a REST webservice.
WIDGET
A widget is a component of a GUI that improves user interaction with the application.
CMDBuild uses widgets (presented as "buttons") that can be placed on cards or processes. The
buttons open popup windows that allow you to insert additional information, and then display the
output of the selected function.