Users

You access the Users form from the Users option on the Admin - Security menu. The Users form is where you enter and maintain information about the people who will be using the application. 

VPM Enterprise encrypts the data you enter on the Users form before storing it in the Users table SDATAUsers. See User Data Encryption on page 484 to learn how to work with the encrypted data.

Tip: When a user logs into an application, the fields in the userís encrypted record are available as properties of _SCREEN.oApp.oSec, the security object. See User Data Record Layout and oSec Properties for the name of each fieldís _SCREEN.oApp.oSec property.

Click the New button on the toolbar and enter a new userís information in the fields shown. The fields on the Users form are described below.

∑       User Number: A 20 character field used to identify the user in the organization.

∑       User ID: A 20 character field which identifies the user to the application. You enter your User ID on the Login dialog when you run the application.

∑       Login Status: Checked if the user is currently logged into the Application.

Tip: If a user is logged-in when the application is abnormally terminated due to a power failure, rebooting, etc., the contents of this field may be incorrect. If the user has not been given Multiple Login rights as described below, the user will not be allowed to re-enter the application. In this case, another user will have to uncheck the userís Login Status check box so that the user can re-enter the application.

∑       Multiple Login: If checked, the user can login to the application from more than one computer at the same time. The user can also re-enter the application if it terminates abnormally as described above. If unchecked, the user can only login if the Login Status field is unchecked. 

Multiple Login Tip: At least one user should be given this right so that all users would not be locked out of the application if there is a power failure, etc.

∑       Report Manager Type: Select the Report Manager functionality you want for the user. You have the following two choices:

∑       Edit & Run: The Report Manager will allow both editing and running reports.

∑       Run Only: The Report Manager allows only running reports.

Tip: When the ďBy UserĒ Report Mgr Type is selected for an application on the Environment dialog (see Environment), the Report Manager will configure its functionality based on the Report Manager Type selected for the user on the Users form. If User Access Security is not on when the application runs, the Report Manager functionality will default to Edit & Run.

∑       First Name: A 30 character field for the userís first name.

∑       Middle Name: A 30 character field for the userís middle name.

∑       Last Name: A 30 character field for the userís last name.

∑       Field Help Edit: Check the Field Help Edit check box if the user should have the right to edit F3 Field Help text while editing data on a form. If User Access Security is off, defaults to checked.

∑       Global Conditions Add/Edit: Check the Global Conditions Add/Edit check box if the user should have the right to create global conditions that will appear in the Condition Builder for all users.

∑       Picklist Add/Edit: Check the Picklist Add/Edit check box if the user should have the right to edit F2 Picklist Help while editing data on a form. If User Access Security is off, defaults to checked.

∑       Access Level: Access Levels Security helps secure access to the security options in an application. You turn on Access Levels Security by entering an ďAĒ in the Access Level check box for a user on the Users form. If you are the system supervisor or the developer, make sure that the first user for whom you enter an ďAĒ is you. See Access Levels Security.

∑       Temporary Password: When a user is first added on the Users form, enter a temporary password in this field. Then, when the user enters the application for the first time, the user will be prompted to enter a new password of the userís own choosing. 

Temporary Password Tip: Any time you make an entry in this field, the next entry into the application by the user will require the user to enter a new password.

∑       Password Last Change Date: This field contains the date of the last password change. 

Password Last Change Date Tip: Blanking-out this field will cause the user to be required to enter a new password upon the next entry into the application.

∑       Password Period: This field contains a 3-digit number that represents the number of days that, when added to the Password Last Change date, is the date on which the user must next change passwords. Use this field to enforce your password change requirements.

Password Period Tip: An entry of zero means that the user can keep the same password indefinitely.

∑       Control Permissions Group: A 3 character field used to assign the user the same control permissions as all other members of the same group. This way, individual control permissions do not have to be assigned to each member of the group. See Controls Security on page 476.

∑       Control Individual Button: The Control Individual button brings up the Control Permissions dialog where you can assign control permissions to the individual user (as opposed to assigning the user to a Control Permissions Group). If there is no entry in the Control Permissions Group field, you can click the Control Individual button to select control permissions for this individual user. If there is an entry in the Control Permissions Group field and you click the Individual button, the Control Permissions dialog will only display the permissions assigned to the group. You may not change these assignments. The groupís control permissions may be changed through the Control Permission Groups dialog accessed from the Admin - Security menu. See Controls Security on page 476.

∑       Field Permissions Group: A 3 character field used to assign the user the same field permissions as all other members of the same group. See Field Security.

∑       Menu Permissions Group: A 3 character field used to assign the user the same menu permissions as all other members of the same group. This way, individual menu permissions do not have to be assigned to each member of the group. See Menu Security on page 472.

∑       Menu Individual Button: The Menu Individual button brings up the Menu Permissions dialog where you can assign menu permissions to the individual user (as opposed to assigning the user to a Menu Permissions Group). If there is no entry in the Menu Permissions Group field, you can click the Menu Individual button to select menu permissions for this individual user. If there is an entry in the Menu Permissions Group field and you click the Individual button, the Menu Permissions dialog will only display the permissions assigned to the group. You may not change these assignments. The groupís menu permissions may be changed through the Menu Permission Groups dialog. See Menu Security.

Tip: The UserData_cControlPermissionGroup, UserData_cFieldPermissionGroup and UserData_cMenuPermissionGroup properties of the VPME Security object contains the three group codes, if any, of the current user. These properties will be useful to you if you need to know the security groups of the current user at some point in your application.

∑       Additional Information: A 70 character field used to store information about a user. You can use this field to store any information you need.

Tip: When a user logs into an application, the contents of the Additional Information field are stored in the UserData_cFiller property of the Security object so that you can use the field contents without having to extract it from the encrypted User record.

     Example - Using the Additional Information Field: Letís say you need to add a menu pad and popup to the main menu for users who are Administrators. The added popup might have options restricted to the administration of the system. You could use an ďAĒ in the first character position of the Additional Information field to identify the user as an administrator. In the RunMainMenu method of the applicationís PROApp class, you could add the administration popup to the main menu if the first character of the UserData_cFiller property is an ďAĒ. Your code would look like this:

   DODEFAULT()
IF SUBSTR(_SCREEN.oApp.oSec. UserData_cFiller,1,1) = ĎAí
         DO Admin.mpr
ENDIF

More:

Passwords