As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
If your user customized his dashboard environment, you can see exactly his dashboards when you log into the "business intelligence view builder", choose users management , check the relevant user and then choose to edit the contents.
A simple solution would be to add a footer in the report in each dashboard. Example: "Run from dashboard XYZ on date"This message has been edited. Last edited by: Kevin Patterson,
Kevin Patterson Appalachian State University WebFOCUS 7.7.03 Windows, All Outputs
I have an HTML form that I present to my user. If the user accesses the report from one portal I want to conditionally remove some of the user's options vs them accessing it from another portal.
The report is complex and I would rather not have to maintain two versions.
I simply would like to be able to determine programatically the portal the user has accessed.
I am looking into adding cookies, but I dont really like the thought of having to maintain a cookie.
I implemented the passing of a paramater via cookies to my HTML page based on the launch page from where the user accessed the portal.
I didnt really like this method as I was concerned about users browsers etc.
I then decided to take a poke around the portal using my old friend Mr Firebug. I noticed that when WebFOCUS displays the portal in the frame based page, that the frame with the report in it is addressed with a number of parameters including one called WORP_MPV which is the internal id of the portal.
Using this parameter and a little bit of javascript within my launch page I can now either restrict data access based on the portal accessing my report, or I can limit the launch page paramaters themselves.