In this Document I am going to demonstrate a requirement and how to implement the same.
First we will get an overview of the application.
I have an application with section access for data security.
The Section access table is shown below.
Now consider that the application is up and running as required………
1.The user Ray is able to see data for all regions and for all branches under that region.
2.The user Nadeem is able to see data for IND region and the branch DEL under that region.
3.The user Darren is able to see data for IND region and the branch MUM under that region.
All the above users are managers having access to data for their respective branches.
Now out of the blue I have a new requirement to build a scorecard sheet.
This scorecard sheet should display data for the branch manager of that particular branch as well as data of all other branches .
Eg:- When the user Nadeem Logs on he should be able to see data for DEL branch along with all other branches. Similar would be the case for the user Darren.
In order to meet the above requirement I should somehow defy the section access logic already built.
Note:- You would think that I could simply remove section access or change my section access BRANCH_NAME fields to ALL . But I still need the section access for the rest of my sheets in the application, It is just the scorecard sheet where this twist has arrived (hence the title section access with a twist .)
How to meet the requirement:-
- First we will have to identify the tables that would be used to create the scorecard KPI.
Let us consider that we have 2 tables and their names are
- 2.These two tables are currently already loaded in the application.
Now we will again load these tables and use different field names
the table Enquiry had the following fields in the data model originally
Reload the tables and rename all the fields as S.branch_name, S.Client_city, S.Enquiry_id except the field region.Similarly perform the operation for the second
Renaming these fields will cause section access to ignore any charts created using these fields in the application.
Now if we use any of the renamed fields like S.Branch_Name in our charts Section acces will not have any effect and all the branches would be displayed because in our section access configuration file we have used field name Branch_name.
The above screenshot shows that when the user Nadeem logged in, he had access to only DEL branch data hence u see only DEL in the Branch_name list box on the extreme left.
But when the field S.Branch_name is used the user Nadeem can see all the data irrespective of the section access defined for the application.
The goal of this requirement was to see where a particular Branch Manager stands and where other branch managers stand so as to fire up a competition between branches.
Thus our Goal is achieved.
Hope you liked the Content