Short explanation for permanent entry history:
What it does is to filter records associated with the user login (PSW) and the table that's selected to filter (permanent entry). Let's use a table ORGAN for this example, that holds all the Organization records as the permanent entry that we want to set.
So, in order to create a permanent entry history, there's the need to create a table that can relate the user login to the area that its associated with the login. Let's use USERS for this example. Users will be related to the ORGAN table, so we can have a representation of individuals that work for an Organization.
So, user logins will be related to the ORGAN table via USERS table.
When a user logs in, it will be automatically set which organism(s) its related to, and therefore any list for any table that its related to the ORGAN table will only show records that pass the filter that can be set in Genio for the permanent entry history:
Options to set the filter are many (this isn't more than setting the SQL WHERE clause that will select the group), but in short, it will allow the settings needed to compare the fields that are related to the user login (USERS) and the table that records need to be filtered (ORGAN).
This will select the group of ORGAN records between all that are available. Then, when displaying lists from tables that are related to ORGAN (or ORGAN itself) will only show records that have relation with this group of records.
Modules by level list is available in order to set in which module and user level this permanent history entry will apply.
About the Community
|Asked: 3/16/19, 8:09 AM|
|Seen: 1053 times|
|Last updated: 10/3/19, 4:02 PM|