Jedox Ideas
Let us know how we can make Jedox even better!
Let us know how we can make Jedox even better!
Hello Together,
as a developer, I would like to be able to have a native development life cycle within jedox that enables me to synchronize specific components between my servers. Additionally, these changes should be tracked and commented.
Components I would like to synchronize:
SVS Scripts
Templates
Integrator Jobs
Templates
Files
everything that i might change on my dev server and would like to push it to a test or production server
Ideally, it should be possible to define different migration packages (branches) that contain multiple of the above-mentioned components. I can comment each component within this migration package and push this to another server. When I chose the server, I see the DIFF between both versions and can decide if I want to merge the changes.
If in the future another developer or i don't remember the change that was done within one of my tickets, i can simply trace these changes within the system and also reverse them if needed as a new migration package.
Best case would be that there is a process where i can define a uer within jedox that can test the implementation on customer side.
This way i have a continuous development process that is documented and traceable. Bugs can quickly be identified and the responsible developer / tester can be contacted in order to get more detail about it. Currently, the developer is forced to download databases and templates etc. to his local system which is a security hazard^10!!!
This is standard in other CPM / BI Tools such as Board, where every change is versioned and can be traced automatically. Here, it is even possible to select individual elements within a dimension to get synchronized.
Thank you for your great idea. While we cannot commit to a specific target version, we will consider adding it to our future internal backlog.
0
Future Consideration
Nice idea! Also, to separate the reports.
This part is actually a huge sales gap to other tools. Especially if you are dealing with larger enterprises, they know of the benefits of a continuous and documented development and merge flow. This should not be future consideration but a baseline for the next version. This is really important to have, and I think it is a no-go for a tool like jedox.
In the light of a better version management, imho it would be very beneficial, if the reports themselves would be hosted outside the jedox database. Currently everything is inside a hidden database, which is not very user/developer friendly, nor state-of-the-art.
If the reports and report items would be hosted wihtin a file system (or cloud storage), they could easily be tracked through git for a better version management. On top, this would make transport from development to production system very easy. Right now it's a pain: No comparison between the current production and development version, transport itself is also everything but easy going (unless you transfer the complete report environment).
This also affects Integrator projects, which are even not backed up in the nightly backup files.