Oracle Transactional Business Intelligence

Products Banner

Is there a way to include Prompt Description in BI Publisher?

87
Views
2
Comments

Summary

Looking for insight on how to include custom help tips on BI publisher prompts for user to understand what the prompt is

Content

When creating a report in OTBI, you have the ability to define a description on your report Prompts that when the user hovers over the prompt it will popup with this custom description/sentence you wrote in order to better allow users to understand whatever note you want to user to have regarding the prompt. 

In BI Publisher, it appears this "Description" field is not available and thus there is no way for you to give this short one or two sentence descriptor the user could view when running the report.   

Below is an example of something we would want to convey to a user assuming we have 3 report prompts named "GL Date", Transaction Date", "Creation Date"    If a user hovered over these respective prompts on the report, we would like the below descriptions to be available for the user. 

"GL Date is the date in which the transaction hit the General Ledger. When ran with dates that coincide with period begin and end, this will substantiate your GL activity and balance" 

"Transaction Date is the date the user placed on the transaction when entering in the Interface. Transaction dates can be backdated and thus cause balancing issue if backdated into a close costing period."

"Creation Date is the date in which the user performed the act of creating the transaction"

 

Version

Oracle Cloud

Example.jpg

Comments

  • Nathan CCC
    Nathan CCC ✭✭✭✭✭

    Jacob, If you put your report on a dashboard page then you can make it use your dasboard prompt prompts instead. All you have to do is make it so the presentation variable name in the dashboard prompt is the same as the parameter name in the data model for your report. The limitation is that on you need to keep tour dashboard prompts simple. For example keep operator to default equal to/is in. If you had set operator is prompt user then the data model wont understand if the user does is not null and likes etc. Give it a go. In my opinion this is the best user experience in the first place. Everything on a dashboard whether it is a publisher report or an analysis. Give it a go! Regards, Nathan

  • Thank you Nathan for the reply, I have provided your response to our reporting experts and they are looking into it.  They did say that dashboard prompts did not work well when they were attempting to use them early in our Oracle Cloud implementation, but im hopeful they can figure something out now.