Categories
- All Categories
- Oracle Analytics Learning Hub
- 19 Oracle Analytics Sharing Center
- 18 Oracle Analytics Lounge
- 231 Oracle Analytics News
- 44 Oracle Analytics Videos
- 15.9K Oracle Analytics Forums
- 6.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 86 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture
Oracle Fusion OTBI (Transactional BI) and BI Publisher - Integrated Git Version Control
RVohra
Rank 6 - Analytics Lead
Currently, Oracle Fusion OTBI (Transactional BI) and BI Publisher lack a native version control system or DevOps pipeline integration.
To promote analytics content (reports, dashboards, data models) across environments (Dev → Test → Prod), customers must rely on manual export/import of .catalog files.
This leads to:
- Limited traceability (no commit history, diffs, or rollback)
- Risk of human error during migrations
- Uncontrolled direct edits in Production
- No automated approval or review workflow
- Lack of alignment with modern DevOps and GitOps practices
Enhancement Request to introduce a “Fusion Analytics DevOps Extension” a native integration layer that provides
- Allow OTBI and BI Publisher objects (reports, dashboards, data models) to be stored as XML/JSON definitions instead of binary
.catalogfiles. - Enable direct check-in / check-out from the OTBI web UI to a configured Git repository (GitHub, GitLab, OCI Code Repo, etc.).
- Include metadata in commits (object name, owner, timestamp, change summary).
- Automatically version content in Git when saved in OTBI.
4