Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

Status Future consideration
Workspace Jedox Platform
Created by Guest
Created on Apr 25, 2024

Development life cycle (Deployment, Versioning, GIT, Comment, Testing,)

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.

  • ADMIN RESPONSE
    May 17, 2024

    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.

3 MERGED

Application Life Cycle Management Tool

Merged
Context: Customer maintains multiple Jedox environments - DEV, TEST, PROD. Changes to application models are released to PROD after they are unit tested in DEV, UAT in TEST and then MTP post sign off. Current Process: Currently model builders main...
almost 2 years ago in Jedox Platform / Other 0 Future consideration
6 MERGED

Git Integration for application development

Merged
Hi, what about a Git Integration for application development (integration, reporting, data model). This helps multiple consultants working on one project.
over 1 year ago in Jedox Platform / Other 0 Future consideration