LAUA security to custom table

What I have also tried to do is use an element security and that does not seem to work. In my dbdef my cost center has the associated element "acct unit" so in laua I set the element "acct unit" to "123" and it still does not seem to work.

I presume since you have created a custom table, you also have some custom
4GL form that users use to access the data in your custom table.?.??

If this is true, are you certain your code is making calls to the Lawson
security api's and handling the data correctly?

What do you mean by the phrase "header table?" Header to what?"

Have you thought about just using the built-in element for acct-unit in
your table then use the from-process-level-to-process-level security in the
system code where you have defined your custom table?


On Fri, Nov 18, 2011 at 3:46 PM, wrote:

> [image: LawsonGuru.com Logo] <https://www.lawsonguru.com/> S3 Security
> Forum Notification A message was posted to a thread you are tracking. *LAUA
> security to custom table* Posted by: *ISO Dan*
> 11/18/2011 03:39 PM I have created a custom table which has cost
> center as a field. I want to create a security class so that only people
> assigned to the cost center can view their data.
>
> For example I have a header table with a field called Cost_Center. I have
> created a security class called CC123, when I use record level security I
> have Coster_Center = "123" however when I view the data I can still see
> everyones' data.
>
> Does anyone know how to set this up or is there something that I am
> missing?
>
> Thank you,
> ------------------------------
>
> To view the complete thread and reply via your browser, please visit:
>
> https://www.lawsonguru.co...ity-to-custom-table/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
>

Have you tried using the field name "acct-unit" in your custom table then
set data security for the from-to company and process-levels within the
system code where your table is defined.

Also, verify using a standard lawson form (GL40) that your security is
working at all.

Run the command "lawsec" at the command line and verify security is on.


On Fri, Nov 18, 2011 at 4:16 PM, wrote:

> [image: LawsonGuru.com Logo] <https://www.lawsonguru.com/> S3 Security
> Forum Notification A message was posted to a thread you are tracking. *RE:
> LAUA security to custom table* Posted by: *ISO Dan*
> 11/18/2011 04:13 PM What I have also tried to do is use an element
> security and that does not seem to work. In my dbdef my cost center has the
> associated element "acct unit" so in laua I set the element "acct unit" to
> "123" and it still does not seem to work.
> ------------------------------
>
> To view the complete thread and reply via your browser, please visit:
>
> https://www.lawsonguru.co...ity-to-custom-table/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
>

Also, ensure that you added the element name to the $LAWDIR/system/security.cfg file.

Lawson does NOT know to treat your element with C+P security if you don't tell it to.

I will try to answer all the questions:

1. I have created a custom table and custom 4GL screen, it mirrors PO20 data but we have it customized because our users wanted additional validation checks prior to loading into PO20
2. I am not sure it is making calls to the Lawson security API, I don't even know what that those are.
3. As defined above my header and detail table mirror PO20's header and detail information
4. I current am using the built-in element for acct-unit, it does not seem to be workingly properly and have defined my cost center in the "Element Security" section of laua
5. My security is turned on
6. I have not tried using a standard form, I will try that next.

I appreciate the comments and help.


Have you thought about just using the built-in element for acct-unit in
your table then use the from-process-level-to-process-level security in the
system code where you have defined your custom table?

1. I have tried add the process level, but I am not sure I did it correctly, I looked at the GL20 and formated the process level according to the level structure I saw for the acct-unit.

2. In my element security made it act-unit = 301

3. Looked at GL40 and still saw a line item with 301 in it.

4. In my custom 4GL program, I cannot access any records