The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.

Users MOD003689

Access path

Information

  • In this module it is possible to
    • edit the data of existing users,
    • assign roles to users
    • define user rights

Notes

  • You can create and edit persons in the Persons module in the course of the person properties creation. To prevent possible data inconsistency, users should not be created independent of persons in the Users module.
  • If you have PLANTA project installed with PLANTA demo data, several demo users are already available in the program.

New from DB 39.5.13

Module Variants
Base Users the persons of which have not left the company, i.e. which have no entry in the Leaving date field, are displayed.
Persons left Only users the persons of which have left the company and have an entry in the Leaving date field are displayed.

Edit User

Procedure

  • After core data of the users (code, name, start date) has been created in the course of the creation of person properties in the Persons module, further user data can be edited here via input or by changing default values in the required fields.

Note

From DB 39.5.11

  • The letter buttons refer to the names (last names) of the users.

From DB 39.5.7

  • The letter buttons refer to the names of the users.
  • Up to DB 39.5.7

  • The letter buttons refer to the user codes.
  • Assign Roles to a User

    Information

    • Via the role assignment, the user is given access rights to certain objects (modules or menu items that are grouped in work areas).
    • At least two roles have to be assigned to each user. One of them controls access to menu items and the other(s) control(s) access to modules.
    • The standard roles defined by PLANTA come with the program delivery. They can be changed or adjusted according to individual company requirements, or individual roles can be adjusted in the Roles module.
    • Further information on rights control in PLANTA project.

    Procedure

    • Right-click on the user record of the employee to whom the roles are to be defined and select Insert Role.
    • A role record is inserted.
      • Select the required role from the Role listbox and save.
      • Insert another role record and select one of the standard roles for menu items from the listbox, e.g. 01100192 R39 MI All.
        • It is obligatory to assign a menu item role to each user. Without such a role, the user cannot start the program. When attempting to log on with a user that has no access to menu items, the following message is displayed: IEmenu_send(): menuitems couldn't be fetched. Closing application. (See log file for further information)
    • Save.

    Define User Rights

    Information

    Define Startup for Users

    Information

    • The administrator can specify for each user which module(s) is/are automatically opened from the assigned roles when this user starts the program or clicks on the Extras Home menu item.
    • There are two different startup variants:
      • Startup without modification rights for the user:
        • The administrator defines a macro for the required user that contains a particular startup module.
      • Startup with modification rights for the user:
        • The administrator defines a startup module for each role of the required user and activates it. Afterwards, the user can specify him/herself which of the defined startup modules are loaded and which not by making particular settings in the Load Startup Module module.

    Startup without Modification Rights for the User

    Procedure

    Startup with Modification Rights for the User

    Procedure

    • Step 1:
      • Select the required startup modules from the Startup MOD listbox of the required role records in the Roles module.
      • Save.
    • Step 2:
      • Switch to the Users module.
      • Assign the 009A1W Startup of all role modules startup macro to the required user in the Startup macro name field.
      • Activate the Load startup module checkbox for roles the startup modules of which are to be loaded.
      • Save.

    Notes

    • When a user logs on, all panels which contain startup modules for which the Load startup module checkbox is activated are loaded.
    • A user can partially change some settings made by the administrator.
      • Via the Extras Change Startup Modules menu item, the user can open the Load Startup Module module and define him/herself whether all role startup modules activated by the administrator are loaded or not by activating/deactivating the Load startup module checkbox. However, without administrator rights, the user cannot change the startup modules assigned to each role by the administrator.

    Create Temporary Password (Reset Password)

    Procedure

    • Click on the Reset password button for the required user in the left window in the Users module.
    • Confirm the Are you really sure? message with Yes
      • If the e-mail address of the user is staored in the module,
        • the newly created temporary password is automatically sent to this e-mail address.
      • If no e-mail address is stored in the module,
        • another dialog message is displayed, showing the temporary password with the Please enter an e-mail address to which the password is to be sent prompt.
        • Enter the user's e-mail address and click on OK.
          • If you do not want the password to be sent via e-mail, click on the Cancel button.
            • The following prompt is displayed: E-mail cannot be sent, reset password anyway?
            • Confirm with OK.
            • A dialog box with the newly created password is displayed. Write down the password and make it available to the respective user.
            • If you have closed the dialog box by mistake before writing down the password, you have to repeat the entire procedure.
    • The user receives the temporary password via e-mail or from the administrator and enters it upon his/her next login. He/she must then change the temporary password.

    Notes

    From DB 39.5.7

    • If the new password is sent via e-mail, you have to make sure that
      • the e-mail address of the recipient is stored in the Persons module.
      • the specified e-mail address is correct. e-mail addresses are not validated in PLANTA project, so if you enter a wrong address, the respective recipient will not receive the e-mail containing the password but the password is changed regardless.
      • the correct IP address of the smtp server is entered for the smtp_server_address parameter in the Alpha (120) field in the Global Settings module.
        • NEW If no or no valid IP address is entered, the following message is displayed when trying to reset the password: E-mail cannot be sent. Reset password anyway? If the query is confirmed, the new password is created but cannot be sent automatically via e-mail.

    From DB 39.5.4

  • If the new password is sent via e-mail, you have to make sure that
    • the e-mail address of the recipient is stored in the Persons module.
    • the specified e-mail address is correct. NEW E-mail addresses are not validated in PLANTA project, so if you enter a wrong address, the respective recipient will not receive the e-mail containing the password but the password is changed regardless.
    • the correct IP address of the smtp server is entered for the smtp_server_address parameter in the Alpha (120) field in the Global Settings module.
  • Up to DB 39.5.4

  • If the new password is sent via e-mail, you have to make sure that
  • See also: User Workflow from DB 39.5.0, UserDataWorkflow up to DB 39.5.0, Change Password

             PLANTA project









     
    • Suche in Topic-Namen

    • Suche in Topic-Inhalten
    This site is powered by the TWiki collaboration platform Powered by Perl