Module D


A CMDBuild added value is the possibility to configure customized workflows, which can be used to execute in a collaborative and monitored way the IT infrastructure activities. This ensures:

  • the certainty to correctly update the CMDB, with which the system is fully integrated
  • a driven and standardized working procedure, for all involved operators
  • a control support system, which highlight the actual status of the service carried out
  • a repository of all past activities, to retrieve statistics related to SLA negotiated with customers

Just like the data model, even the workflow definition system is completely customizable according to each user specific needs. The user will be able to visually define the workflows both in terms of processed information and management flow design.


The Module D is designed to introduce:

  • the general criteria for defining a workflow, drawn externally with a visual editor and then run into CMDBuild as interaction environment
  • CMDBuild technical choices: XPDL (WfMC standard) as definition language, Enhydra TWS (Together Workflow Server) as workflow engine, Enhydra TWE (Together Workflow Server) as visual editor, CMDBuild as interaction environment
  • the methodology to follow to implement a new workflow:
    • formalizing the conceptual analysis through the definition of the involved actors, the design of the flow (suggested editor: yEd), the choice of the information to be managed and of the automatisms to be implemented
    • creating the persistence elements in CMDBuild (classes, attributes, domains) and exporting the XPDL template
    • configuring the flow using TWE editor and importing in CMDBuild the resulting XPDL descriptor
  • the TWE editor features and characteristics:
    • tool configuration
    • roles and other basic features
    • processes, subprocesses, activity blocks
    • interactive activities, automatic activities
    • different transition kinds, with or without flow conditions
  • CMDBuild pre-set elements to interact with workflows:
    • different widgets kinds
    • API to act on the CMDB or to use other expected functionalities
  • TWE usage to configure workflows to be executed in CMDBuild:
    • interactive activities configuration, by selecting the CMDBuild attributes to be shown and their using mode (read-only, write, mandatory)
    • placement of the widget identified in the conceptual analysis phase
    • configuring automatic activities, by writing the needed scripts and using the APIs available within CMDBuild
  • workflow testing and debugging
  • advanced functionalities for configuring a workflow:
    • CQL language usage
    • interaction between workflows
    • interaction between a workflow and external systems, via script (SOAP methods execution, system commands execution, etc.)
    • scheduling
  • executing a workflow starting from different interfaces:
    • CMDBuild GUI Framework
    • Liferay portlet
    • mobile interface
    • custom solutions, interfaced via webservice to CMDBuild workflow engine


7 sessions of 4 hours each


  • a good knowledge of the CMDBuild application and of its data model (Module B)
  • a good knowledge of relational databases and of the SQL language
  • knowledge of a scripting language

Teaching Methodology

The course will be conducted by:

  • frontal lessons
  • explanation of use of the proposed tools
  • individual and group exercises

Other conditions

Training activities can be carried out using remote collaboration tools, in Italian or English during the working days, from 9 a.m. to 6 p.m. (CET) in 4 hours per session.

The training requires the trainees have:

  • a working CMDBuild installation, including the Liferay portal, on a physical or virtual server that meets technical requirements
  • one or more PC clients (depending on the number of people involved) with access to:
    • the CMDBuild application (using a web browser)
    • the PostgreSQL database (using the PgAdmin tool)
    • the Enhydra TWE tool for the design of the workflows

Every course would have a maximum of three persons attending.


At the end of the course the trainees:

  • will know the philosophy CMDBuild for the use of workflow and will be able to produce the conceptual analysis needed to implement a new workflow
  • will know the tool Enhydra TWE
  • will be able to use the tool Enhydra TWE to implement, test and debug a simple workflow
  • will be able to start and advance a workflow from the Management Module interface or from other external interfaces available in the CMDBuild system

back to training modules