Let us know how we can make Jedox even better!
This idea has been merged into another idea. To comment or vote on this idea, please visit JS-I-308 Check In / Check Out mechanism for workbooks in Jedox Web (+versioning).
Everyday when developing in Jedox it's common to backup reports, database and ETLs. So in worst case you'll lose one day of work done. There are three huge advantages by implementing version control:
-time: you don't need to backup data manually, just push the current state to cloud via version control system. The time for pushing should be very little, since version control systems only push files where changes have been made since the last push
- multiple states of each day: You can push the new state multiple times a day, whenever you want to
- historic list of changes and therefore almost endless backups
Of course databases may be too huge in size for version control, but at least reports, ETL projects and SVS files, where we're talking about kilobytes per file should be considered.
In an on-premise solution this could also be done manually. But if it's not integrated to Jedox, every designer would need access to the server (and therefore all databases) and version control system, which is not acceptable in most cases.
Connect the Jedox internal Project/ETL repositories to an external hosted version control system like GIT, Subversion to make the deployment between Development- / Testsystem and Production system more easy. The collaboration between all developers is more easy and you can branch / transport versions between Development and Production.
I submitted this feature request already, but the request seems to be gone.