E9.0 tr 8.98.4.0 and security not working

jkappert

Member
hi,

we migrated recently from E8.10/ tr 8.97 to E9.0/ tr 8.98.4.0
The security did not changed, but doesn't work the way it dit in 8.10

Our setup is like this:
*public action security (1) everything set to N.
Only ok/select=Y (change=N)
This way nobody can add/ delete or change anything.
On Role level we reverse above, for example:
Role AMW, PHL0430 action security (1) all to Y.

Now someone without the role AMW has the add and delete button in the PHL0430.
Anybody???
 
We have seen issues with lower case 'y' causing the security to not be picked up when we switched to 9.0.

We have a custom app for managing security which allowed the lower case 'y' to be entered.

Worth checking in the base tables though.
 
i've found it.
This user has a lot of roles assigned to him. For one of these roles with a higher status the f00950 said
*all objects, security type 1 all set to y.
Case closed and it took me a week, security is a monster...
 
If you make a change to this record does it do anything? in other words can you prove the record at the role level is effective?
 
Back
Top