We are excited to announce the release of DATAGERRY version 2.2.0! Starting with this update, packages for the current and future versions will be available through Packagecloud. Click here to download DATAGERRY.
These are the new functions of DATAGERRY Update 2.2.0 in detail:
Multi Data Sections (MDS)
The new feature “Multi Data Sections” allows users to create a group of fields (a section) in the type configuration which then can store multiple value sets This functionality can be accessed by simply using the new Structure Control “MultiDataSection” in the type configuration and configuring the section as usual. This new feature enhances data management flexibility and functionality.
Let’s have a look at how Multi Data Sections can be set up for a type.
Picture: Multi Data Section (“Hard drives”) vs Section (“Management”)
Adding Multi Data Section to Types
Before we can add a MultiDataSection to a type we first need to go to Framework => Types and open the type configuration of an existing type or create a new type. Inside the type configuration we need to switch to the Content step where we will find the new Structure Control “Multi Data Section” in the left sidebar It can be dragged and dropped into the type like all other elements of the sidebar.
You can include multiple Multi Data Sections in a single type.
Picture: Structure Control – Multi Data Section
Adding Fields to Multi Data Sections
After the MultiDataSection was dropped in the type, we can drag and drop fields from the Basic and Special Controls (except “Location”). Fields which are dropped into a MultiDataSection will have an additional checkbox at the top (“Hide this field as column in object view/edit mode”). By checking this checkbox it is possible to remove fields from the table overview, which can be useful to keep the table compact by just displaying the relevant data. When creating or editing an entry for the MultiDataSection these fields will still be visible in the popup forms.
Once all necessary fields are added to the Multi Data Section, you can save the type configuration.
Picture: Adding fields to a Multi Data Section
Adding Objects with MDS
When creating a new object of a type with a MultiDataSection all fields (except the fields which were marked as hidden in the type configuration) of the corresponding MDS will be displayed as table headers with an additional header “Actions” where the entries can be modified. To add a new entry press the “+Add” button in the top left corner of the table.
Picture: Adding objects with Multi Data Sections
A popup will be displayed where values for all fields (also the fields which are marked as hidden for the table overview) can be filled out. After pressing the “Add” button the entry will be created in the MDS-table. This process can be repeated to create multiple entries.
Picture: Adding an entry to a Multi Data Section
All created entries will be displayed in the table with pagination for more than 10 entries, and each entry will have actions such as Preview, Edit, and Delete.
Preview
● Display of the current values of the entry in a pop-up window
Edit
● The current values of the entry are loaded into a pop-up form where they can be edited
Delete
● The corresponding entry is deleted (a confirmation pop-up is displayed)
Picture: Multiple entries in a Multi Data Section
Important Notes
Saving: MultiDataSections are only saved in the backend when the object itself is saved.
At the current state of development there are some restrictions to MultiDataSections of which some are intended and some will be implemented in later releases
- Objects with MDS can only be exported/imported in JSON format
- MDS entries cannot be used in the DocAPI
- MDS entries do not interact with exportd
- MultiDataSections are not displayed in bulk changes
- MDS fields cannot be used as summary fields in the type configuration
Changes in the version 2.2.0
For a complete list of changes and bugfixes visit the DATAGERRY forum.
DATAGERRY is no longer compatible with RHEL8. The build package of version 2.2.0 and following will use RHEL9.
Here is the detailed changelog
DATAGERRY 2.2.0 (deutsch)
[Neues Feature]
Neue Structure Control “Multi Data Section” in der Typenkonfiguration
[Anpassung]
Support für RHEL 8 wurde eingestellt
[Anpassung]
Das Datum in Datumsfeldern kann per Tastatur eingefügt werden, Details zum Format befinden sich im Hinweis unter dem Datumsfeld
[Anpassung]
Der “Cancel”-Button in der Objekt-Bearbeitungsansicht navigiert jetzt zurück zur Objektübersicht-Tabelle anstatt zur Objektübersicht des jeweiligen Objektes
[Anpassung]
Das “ATTACHMENTS” popup verfügt nun über einen “Cancel”-Button
[Anpassung]
Die “About”-Sektion von DATAGERRY wurde leicht überarbeitet
[Anpassung]
Die Nachricht im Backend wurde angepasst, welche darauf hinweist, dass das Schema von Objekten/Typen durch ein Update angepasst werden muss
[Anpassung]
Es wurden zusätzliche Logs in der Konsole hinzugefügt, wenn bei der Verbindung zu RabbitMQ Fehler auftreten
[Bugfix][DAT-257]
Trotz korrekter Erstellung eines PDF-Dokumentes wurde aus der DocAPI ein Fehler angezeigt
[Bugfix][DAT-276]
Manche deutsche Sonderzeichen wurden in der DocAPI nicht korrekt angezeigt
[Bugfix][DAT-456]
Manche deutsche Sonderzeichen wurden nicht korrekt aus CSV-Dateien importiert
[Bugfix][DAT-469]
Manchmal wurden Referenzen aus einer CSV-Datei nicht importiert
[Bugfix][DAT-689]
Die “Rows” von “Textarea”-Controls wurden nicht gespeichert
[Bugfix][DAT-776]
In der Objektansicht konnten “External Links” nicht geöffnet werden
[Bugfix][DAT-777]
In der Objektansicht konnten “Documents” nicht geöffnet werden
[Bugfix][DAT-778]
In “Attachments” wurde ein falscher Zähler angezeigt
[Bugfix][DAT-779]
Beim Bearbeiten einer PDF-Vorlage wurde ein Fehler angezeigt
[Bugfix][DAT-780]
Das Label von Special Control “Reference” wurde nicht gespeichert
[Bugfix][DAT-792]
Ein Fehler wurde behoben, welcher beim Erstellen eines neues DocAPI Dokuments auftrat. Weiterhin wurde ein Bug behoben weswegen Template-Inhalte nicht korrekt dargestellt wurden
[Bugfix][DAT-800]
Ein Bug wurde behoben, welcher fälschlicherweise einen Fehler angezeigt hatte, wenn das Dateiformat ausgewählt wurde, während Objekte importiert wurden
[Bugfix][DAT-803]
Ein Bug wurde behoben, welcher fälschlicherweise einen Fehler angezeigt hatte wenn Objekte importiert wurden
[Bugfix][DAT-825]
Änderungen am “Identifier” von Sektionen und Feldern wurden nicht gespeichert
[Bugfix][DAT-833]
Ein Bug wurde behoben, welcher fälschlicherweise einen Fehler angezeigt hatte, wenn eine neue Vorlage in der DocAPI erstellt wurde
[Bugfix][DAT-834]
Ein Fehler in der DocAPI wurde behoben, wo es möglich war zum nächsten Schritt zu gelangen ohne alle benötigten Felder auszufüllen
[Bugfix][DAT-835]
Ein Bug wurde behoben, durch den es möglich war eine Typenkonfiguration zu speichern, obwohl eine enthaltene “Section” keinen validen Zustand hatte
[Bugfix][DAT-836]
Die ausgewählten Spalten einer Tabelle konnten nicht in einer Konfiguration gespeichert werden
[Bugfix][DAT-854]
Das Klicken auf ein Passwortfeld in einer Tabelle löste eine Weiterleitung anstatt das Passwort anzuzeigen
[Frontend]
Mehrere Pakete wurden geupdated, um Sicherheitslücken zu schließen
[Frontend]
Angular wurde von Version 15 auf Version 17 geupdated
[Frontend]
Mehrere Module wurden neu strukturiert
[Frontend]
Mehrere Pakete wurden geupdated um Sicherheitslücken zu schließen
DATAGERRY 2.2.0 (english)
[New feature]
New structure control “Multi Data Section” in type configurations
[Changed]
Dropped support for RHEL 8
[Changed]
Dates in date fields can now be copy pasted via keyboard, see the hint below date fields for more details on the format
[Changed]
The “Cancel” button in object edit-mode page navigates back to the objects overview table instead of the objects corresponding view-mode page
[Changed]
The “ATTACHMENTS” modal view in the object overview now has a “Cancel”-Button to close it instead of only be able to press the “x” in the top right corner to close it
[Changed]
The “About”-Section of DATAGERRY was slightly reworked
[Changed]
Changed the displayed message in backend when DATAGERRY informs the user that an update needs to be executed to update the objects/types schema due to a previous misleading message
[Changed]
Added additional backend console logs for RabbitMQ connection exceptions
[Bugfix][DAT-257]
Fixed a wrongfully thrown error when generating a PDF from DocAPI although the PDF was generated correctly
[Bugfix][DAT-276]
Fixed an issue where some special characters were not rendered correctly in the DocAPI
[Bugfix][DAT-456]
Fixed an issue where german special characters were not imported correctly from a CSV file
[Bugfix][DAT-469]
Fixed an issue where sometimes references were missing when importing from a CSV file
[Bugfix][DAT-689]
Fixed an issue where the value of rows for textarea controls was not saved in the backend
[Bugfix][DAT-776]
Fixed an issue in object view-mode where the “External Links”-Button would throw an error instead of opening
[Bugfix][DAT-777]
Fixed an issue in object view-mode where the “Documents”-Button would throw an error instead of opening
[Bugfix][DAT-778]
Fixed a bug where the “Attachments” in object view-mode showed a wrong counter
[Bugfix][DAT-779]
Fixed a bug which raised an error when editing a PDF template
[Bugfix][DAT-780]
Fixed an issue where changes to the label for the Special Control “Reference” were not saved
[Bugfix][DAT-792]
Fixed an occurring error when adding a new DocAPI document. also fixed an issue where sometimes the template content section was not working as desired
[Bugfix][DAT-800]
Fixed an occurring error when selecting the file format when importing objects
[Bugfix][DAT-803]
Fixed an occurring error when importing objects
[Bugfix][DAT-825]
Fixed an issue where the identifier of sections and fields was not saved in the type configuration
[Bugfix][DAT-833]
Fixed a falsely displayed error message in DocAPI when creating a new template
[Bugfix][DAT-834]
Fixed an issue in DocAPI where it was possible to proceed to the next step without all required fields having valid values
[Bugfix][DAT-835]
Fixed a bug where it was possible to save a type configuration with an invalid section state
[Bugfix][DAT-836]
Fixed a bug where the configuration of selected columns in tables were not saved
[Bugfix][DAT-854]
Fixed a bug where a click on the password field in tables triggered a redirection instead of showing the password
[Frontend]
Several package bumps to fix security issues
[Frontend]
Updated Angular from Version 15 to 17
[Frontend]
Several modules have be refactored
[Frontend]
Several package bumps to fix security issues
DATAGERRY in action – Live demo of the CMDB
DATAGERRY is an open source CMDB & Asset Management tool that leaves the definition of a data model entirely up to the user. This webinar will show you the first steps in the tool and DATAGERRY in action.
Blog
Related blog articles
DataGerry: The smart solution for flexible and schemaless IT documentation
DataGerry is the flexible open source solution for modern IT documentation – schemaless, automatable and user-friendly. Whether cloud or on-premise: companies of all sizes benefit from a future-proof, customizable CMDB.
DataGerry now as SaaS: More flexibility for your IT management
DataGerry is available as a SaaS solution, giving you the choice between a cloud or on-premises deployment. Regardless of this, DataGerry remains completely open source.
Decision support in IT management: Interview with the experts from DATAGERRY
Which CMDB tool is right for your company? We spoke to the experts behind DATAGERRY. Jakob Semere, Head of Applications at becon GmbH, and Kai Schubert-Altmann, Senior Consultant and Web Application Manager at becon GmbH, share their experiences with CMDB & Asset Management.
Don’t miss any more news!
Follow us on our social media channels where we will keep you updated.
Get in touch with us!
We look forward to hearing from you.
Do you have any questions or are you facing a particular challenge? Our dedicated team will be happy to provide you with a no-obligation consultation.