Hi Team,

How are you handling presenting different portals to your users, especially in cases where security rules will prevent some users from seeing some portals?

-Do you send out discrete URLs for each portal?

    
Pros: Tight control of user experience. 
Cons: Maintenance / Sustainability headache.

-Do you allow the users to see the ibi_apps landing page, and rely on them to pick the right portal?

  
Pros: Security handles showing who sees what. 
Cons: Welcome to WebFOCUS 8 image takes up 2/3 of the screen and I can't figure out how to change it. 

-Do you send them all to a general portal and get them to use the utilities link for Portals to change to a different portal?

  
Pros: Tight control of user experience 
Cons: I've always found the utilities links to be easy to miss / hard to see

-Do you have a portal with a resource tree or a portal tree?

  
Pros: This allows you to create an analogue of the ibi_apps page where it's possible to replace the Welcome to Webfocus 8 image with something else (two column panel with a resource tree and another object). 
Cons: The portal that you create shows on the portal tree, which is circular and useless.  I've been unable to find a 'Run but Don't List' permission setting to solve this

I'm about to migrate my users from a single WF7 BID, to WF8 with several portals. I'm not quite sure how to present the content for the best user experience, and would appreciate your ideas.

Cheers,

Joey

This message has been edited. Last edited by: <Kathryn Henning>,

Hi Joey,

We've been in production with WF8 for a while now and are using this approach:
- Tomcat configured to forward root to ibi_apps
- WF8 configured to show default portal when logging in
- Default portal configured with 3 sections:
+ resource & portal tree
+ report output
+ general information (help, examples, planned outages...)

This way users have an easy URL to remember (http://myWFServer) with a default view giving them access to their content and my information.

It's worked out so far...

Regards,
Peter

Hi Peter,

Could you elaborate a bit more on how you configured WF8 to go directly to your custom default portal, instead of the generic "Welcome Page"? I've been unable to find any documentation on how to do just that.

Thanks,
Leo

You can change it in the admin console

As far as I can tell, this will redirect all users to the default welcome page. Is there a way to allow administrators access to /ibi_apps/ and everyone else gets redirected?

As far as I can tell answer to Francis question is no. For example we added additional Page to landing page what only Dev/Administrators see where you see whole content tree. Other users see list of portals ( Custom portal selecting HTML )

quote:

Custom portal selecting HTML

I am quite interested in this. Did you use a web service or did you write a report to read the Content metadata? Care to share?

Currently we have it as a static list of portals. I will check tomorrow, I might have some script how to get portal list from Content metadata. ( Tried to solve the problem how to get pages/panel/report name(id) or what ever information )

Easier would be get it through Rest call, then it will most probably get same list, when you add the Portals panel.

Just a thought, but I've never done it. Have one portal, that everyone can log into, page 1 is a custom fex, that takes what ever user they logged in as and redirect them to the portal they have access to. As long as all portals they don't have access to are hidden, this should work. This also allows you to build other portals/updates without affecting the existing user/portal. Then when it's time, change your data to point at the new portal. As people log on the next time, they are redirected to the new portal.

EDIT: By the way, doing this by groups instead of users is the best way.

quote:

Originally posted by GavinL:
Just a thought, but I've never done it. Have one portal, that everyone can log into, page 1 is a custom fex, that takes what ever user they logged in as and redirect them to the portal they have access to. As long as all portals they don't have access to are hidden, this should work.

Your idea sounds good as long as all users have access only to 1 portal. In our case some Managers have access to multiple portals and we cannot make decision where to redirect them. What we could do is build list of portals where he can access. In Portal designer there is one "Panel" portallist, what we would like to present nicer way.

You could just have a default portal per group.

quote:

You could just have a default portal per group.

How do you do this?