Export data and reports from versiondog for import into other systems and for further processing.
The ExportModule is an optional add-on for the versiondog system. It provides you with an easy way to export data and reports from versiondog. The information can be exported at any chosen time and organized in importable file formats (CSV/XML). This straightforward and open method of data exchange creates numerous possibilities for cross-operability between versiondog and the other systems and software that you have in place, maximizing your opportunities to analyze your data and optimize your processes.
With project paths, IDs, master data and component information.
With project paths, IDs, master data and version histories.
With project paths, IDs, comparison results and archive paths.
The ExportModule allows you to extract information gathered by the versiondog system and export it to a universal file format (XML/CSV).
Your versiondog system is a valuable source of information. When the tools you use to analyze that information are external, the ExportModule is a flexible way to extract it and put it to the best possible use, for example to generate production KPIs. You already have the data, why not use it?
There is also the potential export data that can help you improve your versiondog workflow, save time and maximize the efficiency gains that the system offers.
Defining and automating exports and the processing of exported information is quick and straightforward. The following examples are two common customer use cases for the ExportModule. Perhaps they will inspire you to think of others.
This production KPI can be generated from a cyclical export that looks for job runs where there is a difference between the latest version of the programming project on the server and the program currently running on the device.
The next step is to process the information so that it becomes a useful performance indicator and present it in an easily-comprehensible form. You could use, for example, a traffic light system:
It is recommended that users apply a lock state to components when they are working on them. This prevents other users from working on them at the same time and removes the potential for versioning conflicts.
Lock states are set in the UserClient or EasyClient. When other users see a lock state, they know that they need to wait until a new version is checked in or the lock state is removed before working on the project. The lock state comment gives them additional information.
Sometimes users forget that they have applied a lock state to a component and are in fact not editing the project at all. This wrongly prevents other users working on the project.
Feel free to contact us with your ideas so that we can devise a solution together.
We'll be very pleased to hear from you!