table access

we are converting security from laua to LS.. trying to figure out what is the best way to provide access to tables instead of adding all the tables related to each and every program to the class.. any ideas or suggestions??

example: we have created class with AM20.1, AM23.1 and PO64.1.. and added the tables related three programs which comes around 100.

i feel like it's take forever if we approach this way... so i have avoided by adding below conditional rule.. but that is giving access to all the tables and full access to tables... is there any better approach??

if(SystemCode==('AM')||SystemCode==('PO'))
'ALL_ACCESS,'
else
'NO_ACCESS,'

Find more posts tagged with

Comments

Derick Safarian

Please refer to the "Lawson Administration: Resources and Security" guide for instructions on how to write rules to do this.

Here is an extract from Chapter 24: Writing Simple Rules:

"Conditional "By Type" Rules

You can assign access to all securable objects of a particular type. This is a powerful way to quickly open up the system for power users and administrators.

The containment policy for Security Type rules require that users have access to the product lines and system codes in order to get access to the group of the Securable Type objects. For example, if you chose to write a Grant All Access rule to the Securable Type TABLES, but did not grant the user access to product lines and system codes in the profile, the user would still not be able to access any tables.

Lawson Security now provides the ability to write conditional rules on securable types.

This means that you can give a user access to all tables, for example, while still ensuring that the user would not have access to particular tables that they should not see. You would do this by granting access to tables but then specifying the system codes the user could or could not see.

Legacy Contributor

I'm sure I am missing something but I don't think I understand your question. You don't have to give access to ANY tables - the forms will work without table access. But users won't be able to do any drop downs, selects, or drill arounds - probably not what you want, but possibly for some forms or fields. If you want them to have ALL of the dropdowns, selects, or drill arounds, you will need to give them access to all the tables associated with the form (no conditional rules necessary). If there is nothing sensitive or confidential you could just give them access to all tables (no conditional rules necessary) in that system code. If there is something sensitive/confidential, you can deny access to certain tables (or certain fields in certain tables) if you don't want them seeing that certain data in a dropdown/select/drillaround.

Legacy Contributor

Thanks Derick and Jason..

and i should have put more information like why i am adding tables by using conditional rule .. here is an example.... "Drill Select" is not showing any values if did not add tables.

and another reason i am adding system codes is that we do not want user to get access to other tables which is not needed even the user gets access to other programs outside the system codes mentioned in conditional rule by mistakenly (just trying to avoid human errors).

Copyright © 2025 Infor. All rights reserved.