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.
We are looking to create portals with metrics dashboards. Our users need to be able to select their specific organization or timeframe or whatever else we have as parameters. These selections should be the default the next time they come into the portal, instead of the standard defaults that everyone sees.
How are others doing this? I don't want to create x numbers of dashboards that all have the same metrics.
Thanks!This message has been edited. Last edited by: <Emily McAllister>,
Are you referring to HTML controls placed within a portal panel, or the actual content? Content customizations are saved per user ID after each session. If that user comes back in to view the portal, any content they added, or whichever page they were on before, is where they will be and what they will see within the new session.
As for controls, you can utilize the &IBIMR_user variable value to determine which external procedure request is used within a fex to populate the control(s). This may be tedious if done individually for many, but can be helpful if you want to customize for a few people.
Logic example:
-IF &IBIMR_user EQ [userID] .... THEN GOTO labelForSpecificPersonOrGroup ELSE GOTO blah;
-label1
TABLE FILE blah
...
ON TABLE PCHOLD FORMAT XML
END
-label2
TABLE FILE blah
...
ON TABLE PCHOLD FORMAT XML
END
etc....
Hope this helps.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
Yes I am referring to the portal panel. So if I select department ABC and you select DEF, it keeps those as the selected defaults the next time you or I go to that page.
This could potentially be needed for many users so I would not want to hardcode values.
Thanks for the suggestion. I will see where this leads me.
I have a table which contain the user id and their security for different field (department, store, region, etc)
Then I have a fex (which is included in the _universal_profile) that assigned global variable which then be used in fex to filter displayed data.
So each time a particular user log in, then its "security profile" is assigned and everything he's accessing (dashboard, report, drop list, ...) is filtered based on the global variables.
Unfortunately, you need to include the variables in every fex and maintain the security table. But the WHERE condition can easily be copied from one fex to another and it become kind of standard to have those kind of filter. And security table is not so a pain to maintain since we don't have to create users everyday. Also, in the security table we put the "common and general" security parameters only; not too much specific.
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
Our environment is quite complex, but what we have done is add a "Save Preset" option to the page and save the parms with the option (not done yet) to flag one if the "presets" as default values.
We do this, but I control the portal page.. Meaning, it's one FEX on the main page of the portal and I add the fexes within. I store in SQL when the user changes their preferences for sort order or if they don't want to see a panel. Basically, I wrote my own framework within webfocus to handle it.
This message has been edited. Last edited by: GavinL,
- FOCUS Man, just FOCUS! ----------------------------- Product: WebFOCUS Version: 8.1.04 Server: Windows 2008 Server