Access restriction for business objects in same solution
Requirement: I have one single solution with 4 modules. 1 module is common and other 3 are industry specific. When i roll it out to a customer, i what restrictions on Business Objects. So that i can roll out single or combination of modules as per requirement.
Hence the configuration requirement would be as follows:
- We need one core configuration for the entire solution which will have the Common Scope part included in it.
- We need industry wise configuration ( could be business configuration )
- Script level screen restriction.
We tried creating a BAC element with Business Topic and Business Options and tried to link BO's to it. But we are finding a problem with this solution, even a user will be able to change the configuration and get access to a module which he didn't pay for.