CMDBuild Newsletter n. 65

CMDBuild Newsletter n. 65

CMDBuild Newsletter n. 65
 
 

CMDBuild Newsletter n. 65

.
CMDBuild

January  2018

SUmmarY

Work in progress

Progress of the new version CMDBuild 3.0

Multitenant management in CMDBuild 3.0

CMDBuild Reference & Case Study: S&SHIS

The testing phase of CMDBuild at ATAC Rome

.

.

 

Work in progress

After having released the CMDBuild 2.5 version two months ago, the Project Development Team is now working at some maintenance activities on the 2.x branch, and of course at the new 3.0 version currently under development.

Concerning the activities about CMDBuild 3.0, please refer to the following news.

Concerning the version 2.x, we are working on some minor implementations that, together with other improvements, will converge on the version 2.5.1.

These include at the moment:

  • control of HTML text that can be inserted in the "string" and "text" attributes of a form, to prevent XSS (Cross-Site Scripting) vulnerabilities;
  • possibility, through a specific parameter, to request encryption with AES 128 keys of the passwords present in the application configuration files on the server file system (this activity has been commissioned by TIM S.p.A.);
  • possibility, using a specific parameter, to specify whether by setting a filter on a class and modifying a data card so that it no longer respects the current filter, the system should remove the filter (current behaviour) or keep the filter by hiding the modified card (this activity has been commissioned by Trentino Network S.r.l.);
  • extension of the Mobile APP to manage "Position" attributes that read the information of the current position of the device from the onboard GPS and record it in the database.
The release date for the version 2.5.1 has not been defined yet, but is expected to be at about middle 2018.

.

Progress of the new version CMDBuild 3.0

According to the “rule” that we have given, at the release and sending of a new Newsletter we update the on line demo of the new version 3.0 under development, we have done so.

It is possible to access the demo 3.0 through this link and authenticate with user "demo" and password "demo".

Compared to the development progress at the end of November, the following innovations are now available on the GUI:

  • possibility of selecting the tenant;
  • implementation in the data cards of the details management tab;
  • implementation in the data cards of the relationship management tab.

Concerning server-side, developments were about:

  • implementation of a first set of features for Multitenant management (please check the following news);
  • providing the REST methods required by the new client functions;
  • archiving, in a new system table in the database, the operations performed by each user with the system response times;
  • archiving, in a new system table in the database, the user sessions;
  • storing application configuration parameters in a new system table, rather than on the server's file system.

We look forward to receiving your feedback about the implementations made so far, at this time feedback are particularly useful since we have enough time to work on the most requested improvements.

For the publication of the next state of progress, we plan to extend the existing features with:

  • implementation of the “Favourites” menu and the “Browsing history”;
  • implementation in the data cards of the history tab;
  • implementation in the data cards of the attachment management tab;
  • implementation in the data cards of the email management tab
.

The testing phase of CMDBuild at ATAC Rome

ATAC Rome is the Company for the Public Transport of the Municipality of Rome.

It is a complex Organization, because of the high numbers of vehicles of both surface fleet and underground, and because of the different typologies of infrastructures to be managed.

The ATAC Head of the Infrastructure Maintenance Sector, Mr. Raffaele Santulli, approached the CMDBuild solution and was impressed by its flexibility and configurability.

With an internal working team, some tests were carried out on the “translation systems”, and a more extensive testing phase has now started on all the infrastructures managed.

The first results obtained have been presented by Eng. Santulli at the “International VDI Conference - Maintenance: Data Analytics, Predictive Maintenance, Smart Services” held in Munich last November 29th. Slides can be found here.

Useful links

CMDBuild

SourceForge Project

Twitter @cmdbuild

Twitter @openmaint_org

LinkedIn Group

CMDBuild READY2USE

openMAINT

Tecnoteca

 

CMDBuild and openMAINT are open source software developed and maintained by Tecnoteca and released with AGPL license.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Multitenant management in CMDBuild 3.0

In general, the Multitenant feature will allow to partition the CMDBuild data into separate areas for each tenant, so that each tenant works with a custom virtual instance.

The implementation chosen for CMDBuild 3.0 allows both the possibility of a complete partitioning (for example different Companies using the same cloud instance) and partial partitioning (for example, each support group works on some customers, each customer works only on their own data).

The tenant list to be used can be defined by an application class of CMDBuild identified for this purpose (Offices, Companies, Customers, etc.) or by a custom database function (implementing for example the fact that every tenant sees the data of a site but the regional director sees the data of all the locations in a region).

For higher security, the data access control according to the tenant in use will be based on the RGS (Row Level Security) mechanism native in PostgreSQL.

In the normal use of CMDBuild, if the Multitenant mechanism is active, each user at login will log in with his tenant if it is unique, or he will choose one of the available ones, or he may decide to work with several tenants at the same time. It will then be possible to change the choice of the tenant without having to log out.

The operation of the system will then be such that data cards with valued tenant will be visible only to users associated with that tenant, data cards with non-valued tenant will be visible to all users, the inclusion of a new data card will automatically enhance the tenant with the current value for the user, or will ask to select one explicitly if the user has the possibility to work with multiple tenants active at the same time.

 

CMDBuild Reference & Case Study: Shropshire & Staffordshire Health Informatics Service (S&SHIS)

The Shropshire & Staffordshire Health Informatics Service (S&SHIS), is an NHS organisation which provides shared ICT infrastructure and services to many other NHS organisations within the region.

One of the biggest challenges which faces any organisation is building an effective and current reporting system of their IT asset estate.

Our approach to building a successful CMDB: we started off with what we call the “Foundation” classes, these are the base classes which almost every other class will have a relationship with; for us those were: “Location”, “Organisation” and “People”.

The quality of the data for these classes has to be from a reliable, current and managed data source. This was from an electronic staff record system, Active Directory and our in-house Service Management Tool. Federating this data and importing into the CMDBuild platform on a nightly basis, to ensure we have the most current data and the required attributes to satisfy our reporting requirements, was key to the start of our implementation.

Over the past 3 years we have developed the CMDBuild platform with automated feeds and manually managed classes, supported by internal business processes.

Currently there are 140 active users, 110.000 people records, 280 organisations, 1.300 locations and many other classes.

We have automated feeds for 21.000 live PC’s and Laptops with nightly updates showing key relationships including Owner (organisation class), Last Known User (people class), Last known Location (location class), Warranty End Dates (Dell warranty API).

We have sponsored the recent Document Management developments to include versioning features, which we use to manage our contracts and business critical policy and process documents.

The developments continue with many more on the horizon, and with the flexibility and features of the CMDBuild platform and Tecnoteca’s expertise this will continue to drive value for us and our partner organisations.

.
 
.
.

This email was sent to you because you were interested in CMDBuild support or product info.

 
.

We use cookies on this site to enhance your user experience. By continuing to browse our website you are agreeing to how we use cookies. Cookie Policy