January 2012
Developments currently under way - for the release of version 1.5 - will include:
- structural changes to prepare the review of the workflow system
- review of some of the "widget" already used to configure the workflow and release of a new calendar "widget"
- introduction of "widget" concept on cards (as well as on workflow) with the initial release of the first two or three implementations
- other interface improvements
- bug fixing
And also
:
- the release of the Technical Manual in English language
- new Russian localization
- new Brazilian Portuguese
Second Quarter 2012The roadmap for 2012 includes workflow refactoring with:
- migration to Enhydra Shark engine 4.1 (XPDL2.0)
- implementation of parallelism feature
- UI improvements
Since this is a major revision , with migration from Shark 2 to Shark 4 and XPDL 1.0 to 2.0, we'll switch to CMDBuild 2.0 Version 2.0 will also include:
- a new version of the internal query language (CQL2 - CMDBuild Query Language 2.0)
- a first integration of dashboards to check results coming from CQL2 queries
There's more
We expect to work on the following improvements:
- Dashboard: define and present in the CMDBuild menu some dashboards
- Views definition and permission management: define views on the CMDB by using CQL2 expressions . Views could be stored and made available to users as a additional menu elements, with their associated permissions. Views could have read-write or read-only access - we're still thinking about this. With views it could be possible to manage single row permissions , as requested by many CMDBuild users . Using appropriate filters you could define permissions for a subsets of cards ( for example, limit data for specific user groups).
- New card navigation: see the last-viewed cards
- Form customization, validation and calculated fields: some new features for CMDBuild forms :
- attributes grouping
- multiple column layout
- text and background colors
- patterns to display data
Define custom compilation and validation logic:
- default values (today's date, default boolean value, etc.)
- default values related to other attributes
- validation using static data (greater than "100", less than "10", ecc)
- validation using dynamic data related to other attributes (end-date greater than begin-date, no assigment for invalid asset, etc.)
Define view-only attributes (created automatically by concatenating other attributes and custom strings, thus solving common problems related to "Reference" selection).
External contributions
With your help we could work on complex features like:
- 3D GIS: GIS features in CMDBuild allow you to geo-reference objects on maps or plans but it's not possible to "move" within three-dimensional spaces. The creation of a 3D extensions could be based on some new standards, such as IFC (Industry Foundation Classes - International Alliance for Interoperability). IFC is an open standard, BIM oriented (Building Information Modeling) and is supported by many companies and tools , including for example BIM Server (http://www.bimserver.org).
-
Semantic analysis: we could integrate a semantic analysis to obtain "derived" informations. In particular we could obtain suggestions from the database ( "what if" analysis) or identify trends to improve service quality. The system could be based on RDF triples extracted from the CMDBuild database , it could use a "reasoner" as engine and include a user interface .
The roadmap is purely indicative, and may change depending on managers decisions and customer requests.