Categories
Repository/Session variable with hostname for Drill Down
Comments
-
Hardcoding means we must update every report when using Deep Links and changing PODS. This is a huge amount of wasted effort.
0 -
This will help in dynamically linking to get deep links from OTBI pages.
0 -
This would allow users to have action links derive the environment.
0 -
This is a very important requirement, everytime we clone the non Prod environment from Prod, we have to edit all report definitions in order to point instance specific action links
0 -
This will help to include the Pod name in the reports.
0 -
We need this variable, too. Manually editing all the links post-migration to another environment is insanity. ORACLE, PLEASE MAKE THIS HAPPEN!
0 -
Thank you Vincent,
There's another solution proposed, for Oracle to add in OTBI a new Action Link type (e.g. "Naviate to a Current POD") that's automatically adding current POD root at the beginning of URL for DeepLink usage:
It will have the same effect as the variable, but on OTBI application level, maybe easier to implement for Oracle.
Thank you all for supporting the idea (and struggling with migration). Rest of the world didn't mature enough to realize the potential :-)
0 -
Vincent,
Unfortunately your idea is not doable.
When I've created a variable and used the way you intended
OTBI sent an error:
and it's understandable why, it may compromise the security.
We can't use the variable in the root of URL.
Despite OTBI update is required from Oracle side, a new Action Type will work for sure:
This idea is not longer required.
0 -
we need this functionality too - to remove need to update URLs for every POD refresh.
enhancement request "SR 3-31263643601" doesn't seem to be publicly visible
0 -
Severity 1 Enhancement Request 35411931 was opened based on our recent SR (see text below) and can be tracked in MOS. Please alert your CSMs about this ER and have them add pressure to Development.
Hopefully Oracle will see this simple change as a big win for us customers and make it happen ASAP.
===============
The burden of hard-coding Action Link and Deep Link URLs in OTBI SaaS is unreasonable. This vastly increases the risk of incorrect reporting if the URLs are not manually changed when migrated to another POD.
For on-premises, a Location Alias can be added to the ActionFrameworkConfig.xml file in each of the PODs to reflect the current domain.
<Oracle Middleware Home>\user_projects\domains\bi\config\fmwconfig\biconfig\actions\ActionFrameworkConfig.xml
[Fusion Middleware Release Notes for OBIEE 12.2.1.4]
[Fusion Middleware Integrator's Guide for OBIEE 12.2.1.4]
[https://docs.oracle.com/middleware/12213/biee/BIEIT/actions.htm#CHDIAFCD]
We request that the following Location Alias be added for each of our PODs:
====EXAMPLE====
PROD:
<location-alias>
<alias>ofchost</alias>
<actual>PODNAME.fa.us2.oraclecloud.com</actual>
</location-alias>
===============
0
