All users must pass through the LOGON screen before they can gain access to the system. This requires the entry of a User ID and Password which are validated on the Menu database.
It is possible to prevent the same User ID from being used more than once at the same time. Multiple logons can be allowed using the switch on the Menu Controls screen.
Users may be prevented from changing their passwords, or be forced to change them after a specified interval or number of logons. Refer to the Menu Controls screen.
New Passwords may be forced to conform to a particular pattern. Refer to the Menu Controls screen
User passwords may be encrypted before being stored on the database. Refer to the Menu Controls screen
The list of options (transactions) which are available can be broken down into any number of menu 'pages', with each page having its own unique identity. Refer to Appendix A.
The number of menu pages and their content can be altered by using online transactions. Any number of menu levels can be defined. A transaction can appear on any number of menus. Refer to Appendix A.
Security specifications are defined for Security Classes. Each User is assigned to one of these Classes, and inherits all the security aspects of that Class. A user can be switched from one Class to another with ease.
Module-level security - access to individual modules/transactions is granted to Security Classes by constructing a separate Transaction Access Profile for each Security Class.
The same menu structure can be shared by different Security Classes. Any menu item which is not accessible to that Class at run time will not appear in the display. Buttons within a module's navigation bar which are not accessible will be greyed out.
Each Security Class may have a different starting transaction defined. This may be any menu in the system, or may even be an application transaction.
Item-level security - each module/function is comprised of a number of data items or fields. Within specified functions access to individual items can be turned on or off for each Security Class by using an online transaction. Refer to Appendix K: Transaction Item Access Profiles for more details.
Any data item which is not accessible to a User's Security Class at run time will not appear in the display. If the item has an associated label that too will disappear.
The behaviour of certain functions can be altered by setting a value in that function's Extra Parameters within the menu database. This value is passed to the form when it is activated so that it can take the appropriate action.
Each component can have transactions defined on the menu database with alias names so that different values can be set for the component.
A function which creates new entries may accept initial values which can be defined on the Menu database.
Access to individual functions can be temporarily disabled without having to alter the details for individual Security Classes.
A User's access can be temporarily disabled without having to delete that User's details.
There is an online help facility that will show text relating to the current field and form. This can be replaced with HTML documents.
Multi-language capabilities - different language codes can be specified for individual users which then utilises the standard UNIFACE functionality to obtain field labels, button text and messages in that language. There is also the facility to provide foreign language variations for transaction descriptions for use on menu screens.
There is provision for custom processing to be performed for an application whenever the first form within the application is activated.
There is provision for custom processing to be performed for an application whenever the session terminates, either by the user logging out completely or by returning to the logon screen to start a new session.
There is the option to maintain the start and end times for each user session so that a list of currently active users can be maintained and displayed.
There is the option to turn on Audit Logging for selected database entities so that changes made to those entities can be logged. The contents of the audit log can be reviewed using online transactions.
