Component security

[former_member199573]

Hi,

We have a dashboard with 2 buttons.

The first one is submit, it triggers a planning sequence to save data.

The second button is approve, it triggers another planning sequnce to copy data to a final version.

What are the options of providing this dashboard to different set of users?

We plan to have a copy of the same dashboard but, without the Approve button to be used by end users and the 2nd dashboard with Approve button by the Reviewer user group.

In case, the URL of the application is shared byt the Reviewer to the end user, the BW security will prevent the end user from Approving the data as they do not have authorization for the 2nd planning sequence.

Please let me know if there are any other options.

We actually 3 sets of users and 3 buttons on the dashboard.

user group 1 - button 1

user group 2 - button 1 and 2

user group 3 - button 1,2 and 3.

Thank you.

Raj.

[Karol-K · Accepted solution]

Hi Raja,

with permission check on data source / planning sequence you are on save side.

you can also maintain permissions on the platform level (NW / BIP) to block the access on application level, but this is just to assure that other users cannot see the application. Design Studio application are also "objects" which can have permissions, eg. in NW case it is the authorisation object on TLOGO level. In BIP you can maintain permissions on folder level.

Final check should be on data source (BW) level.

Karol

[former_member199573 · Accepted solution]

Hi Karol,

Thank you for your response.

please help me understand the solution.

1.you can also maintain permissions on the platform level (NW / BIP) to block the access on application level, but this is just to assure that other users cannot see the application.

---- Yes, We plan to have seperate BI folders in launchpad for different user groups.

2.In BW security, the authorization to execute a specific planning sequence is provided by an inidividual role. So, the roles will be assigned to the corresponding user group.

I was trying to find an option to hide the buttons(Submit,Approve and Unlock) based on user group/authorization on a single dashboard, so that it would avoid having 3 dashboards for the 3 user groups.

Thanks again for your response.

Raja.

[Karol-K · Accepted solution]

Hi Raja,

for this you would need to have the information inside the application. What would be possible, is to define some extra variable in the query, which is NON-INPUT READY and will get the value via customer exit which is then coded based on the user group.

Then, in DS, you could ask for the value DS.getVariableValue() and decide in an IF statement if the button should be visible or not.

It is just an idea.. but should work.

or, you make a special planning function, which would be executed on startup - and the  planning function has some result value on PF.execute().

Returned Value

Boolean. True if the planning function executed correctly, false if an error occured while executing the planning function.

If the user cannot see the button, you need to assure that the backend code will return false in this case.

I hope some of those will work for you.

Karol