"A new report’s template creation is very often manipulation of a user’s layout of a report. A report can be ready in a day or less, once stored procedures are created as per sections in the report."
"There is flexibility in laying out tables that is akin to UI front-end design."
"To generate these same tabular formatted reports with a code-only solution would have taken a lot longer to implement than the Docmosis template-based approach. Docmosis templates were easier to design as we were able to use Microsoft Word to create them. The templates made it easy to make any changes to reports and provided flexibility in our design approach."
"Since our initial development, this feature has required very little maintenance. And when changes are requested, it is rather easy to change a Word document template and new staff can be quickly trained to modify a report."
"Globally, the ability to create document templates in several formats by using a rich syntax is simple and clear to understand."
"The ability to embed, and dynamically repeat, templates within each other is a very simple yet extremely powerful tool."
"The most valuable features of the solution are the various scenarios the product offers and its stability."
"The “Business Model & Mapping” layer in the Administration Tool, because the maintenance and evolution processes are greatly facilitated."
"The setup isn't too difficult."
"A great feature of the solution is its stability."
"The visualization is very good."
"It has a lot workaround in order to do the report. data blending, and getting information from big data sources."
"For me, it makes the difference is in terms of our users being able to take advantage of a product which allows you to get access to data, reports, make decisions quickly, and have better insights regarding operations."
"The most valuable feature of Oracle OBIEE is it's designed for Oracle. It works well in the Oracle environment and can sit on top of any application."
"We are facing new challenges such as internationalization. The next big challenge will be to offer even more date formats and numbers that cover the majority of countries. It will be to also think about features, such as number to text conversion, or the reverse which is currently only available in English but is in great demand by our international customers."
"It would be great to have improved diagnostic and debugging tools. When report templates are complex, sometimes any minor modification needs to be thoroughly tested to ensure that it does not disrupt a previously designed template."
"Version control and restricted access to some users for template editing could be a useful addition."
"The challenge in usage when we developed the reports four years ago was the limited logic that can be applied to manipulate and display data. That functionality was largely transferred over to the database layer in creating the data output that was to be displayed."
"Even though we have a feature to enable the physical query to be seen in the log, in case of any issues, it is challenging to debug and see or identify where is the issue. For example, we designed the OBIEE repository and deployed it into the server, and we are now accessing and creating a report. For some reason, if the report is not working as expected, it is very difficult to identify the issue. We have a feature to see the physical query that is being generated in the central OBIEE server. I feel that this feature should have been available at the repository level so that while designing the repository, we can select the presentation columns and the query it is going to create. This will avoid the additional task of deploying a feature into the server and then testing the report. It will also make the implementation process friendly if, while designing the repository, we can see: How is a feature working? Are any of the presentation columns selected? How is the query being generated? Which query is being generated? Are any joints used? What kind of joints are used? Having this kind of information will make Oracle OBIEE more powerful and developer-friendly."
"The documentation in Oracle OBIEE can be more user-friendly."
"The ability to migrate from one version to another, such as doing so from version 11 to an upgraded 12 of Oracle business environment, can be difficult."
"The performance could be better."
"There's a lot of redundancy, especially in relation to creating the code."
"Expanding beyond pure data reporting and into analytics, or expanding data science, would be areas for improvement."
"It should have more self-service capabilities."
"The development effort takes longer than other BI tools currently on the market."
Earn 20 points
Docmosis is ranked 2nd in Document Generation Tools while Oracle OBIEE is ranked 3rd in BI (Business Intelligence) Tools with 154 reviews. Docmosis is rated 9.0, while Oracle OBIEE is rated 7.8. The top reviewer of Docmosis writes "Easy to integrate this solution into an existing system". On the other hand, the top reviewer of Oracle OBIEE writes "A solution that is easily accessible, scalable and requires a straightforward initial setup process to get started". Docmosis is most compared with Windward Core, whereas Oracle OBIEE is most compared with Microsoft Power BI, SAP BusinessObjects Business Intelligence Platform, IBM Cognos, Tableau and Oracle Analytics Cloud.
We monitor all Document Generation Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
