This page (revision-9) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
9 26-Nov-2021 10:22 1 KB kparrott to previous
8 26-Nov-2021 10:22 1 KB JEscott to previous | to last
7 26-Nov-2021 10:22 914 bytes JMyers to previous | to last
6 26-Nov-2021 10:22 915 bytes JMyers to previous | to last
5 26-Nov-2021 10:22 604 bytes JMyers to previous | to last
4 26-Nov-2021 10:22 624 bytes Administrator to previous | to last
3 26-Nov-2021 10:22 635 bytes Administrator to previous | to last
2 26-Nov-2021 10:22 624 bytes Administrator to previous | to last
1 26-Nov-2021 10:22 159 bytes Administrator to last

Page References

Incoming links Outgoing links
IMOS
IMOS

Version management

Difference between version and

At line 4 changed one line
text on form
The Establish Object Security (IMOS) screen allows you to define access to a specific object for a role or a user (but not both).
At line 6 changed one line
;[FieldNameInHdr]:description
Object security done by data source, which can be a table or view.
For example, we wanted to restrict a user so that they could not see wage rates wherever they are in the system, we would do this through IMOS.
We'd select EASD in the object field and Wage_Rate as the attribute. You'd then set the Security Access to 'No View' and define the user you which to restrict.
This page (revision-9) was last changed on 26-Nov-2021 10:22 by kparrottTop