Hi
i have a question:
let s assume that i need to install the mashboard application
within a company.
depending on the job of each user (I.E. accounting,Sales,HR...)
each of these users got no right to see the data they want.
the question is
How could i filter out the portlets seen into the dockable spam
depending on the logged user?
is there a way to do so?
or must i create a Mashboard application for each department into this company?
thanks for answers
Arno
Page 1 of 1
giving different portlet depending on user rights
#2
Posted 29 May 2009 - 05:21 AM
Hi Arno,
When you configure the mashboard, you create a configuration file called a "mashconfig" file. This file is intended to configure a Mashboard experience for an individual group of users or roles (as defined on the iServer). You can have as many unique mashconfig files stored on the iServer as your application requires. Each one represents a unique user experience.
Once the config file is stored on the iServer, you grant users access to the configuration by giving the rights to the file on the iServer itself. The Mashboard polls the iServer at login and grabs the mashconfig file(s) that the supplied user has rights to. That can be a single configuration representing all the content the user should see, or a group of file that when taken as a whole create the users experience.
This can be as simple a setup (single mashconfig) or as complex (multiple mashconfig files) as you want. We can discuss implementation scenarios as needed. I just wanted to start by giving you a feel for for how the files are allocated per user on the server.
There is a video tutorial that covers creating unique user experiences on a Mashboard deployment. It may hep you get things going as well: Actuate Mashboard "How To" Video Series -- Part 4 - Tutorials - BIRT Exchange
Good Luck!
When you configure the mashboard, you create a configuration file called a "mashconfig" file. This file is intended to configure a Mashboard experience for an individual group of users or roles (as defined on the iServer). You can have as many unique mashconfig files stored on the iServer as your application requires. Each one represents a unique user experience.
Once the config file is stored on the iServer, you grant users access to the configuration by giving the rights to the file on the iServer itself. The Mashboard polls the iServer at login and grabs the mashconfig file(s) that the supplied user has rights to. That can be a single configuration representing all the content the user should see, or a group of file that when taken as a whole create the users experience.
This can be as simple a setup (single mashconfig) or as complex (multiple mashconfig files) as you want. We can discuss implementation scenarios as needed. I just wanted to start by giving you a feel for for how the files are allocated per user on the server.
There is a video tutorial that covers creating unique user experiences on a Mashboard deployment. It may hep you get things going as well: Actuate Mashboard "How To" Video Series -- Part 4 - Tutorials - BIRT Exchange
Good Luck!
Page 1 of 1




MultiQuote
