Project and Portfolio Management
Version 27 Version 26 39.5.25 39.5.23 39.5.22 39.5.21 39.5.20 39.5.19 39.5.18 39.5.17 German English
Version 27 Version 26 39.5.25 39.5.23 39.5.22 39.5.21 39.5.20 39.5.19 39.5.18 39.5.17 German English

User MOD003689

Introduction

  • Settings → Master Data → Users, Roles, Resources→ User

Information

  • In this module you can

    • edit the data of already created users, e.g. language, skin, etc.,

    • assign person groups to the users,

    • define user rights,

    • reset user passwords.

Notes

  • You can create and edit persons in the Persons module in the course of the person attributes creation.

    • To prevent possible data inconsistency, users should not be created independently of persons in the Users module.

  • If PLANTA project is installed with PLANTA demo data, several demo users are already available in the program.

In order for employees of a company to be able to work with PLANTA project, they must have been entered as persons in the PLANTA system. Three attributes will subsequently be recorded for each person:

  • User: is required for the login of the respective person to the PLANTA program. Furthermore, all parameters which the respective person requires for program operation are stored on the user (e.g. login data, authorizations, language, etc. as well as user-specific menus with modules and menu items).

  • Stakeholder: is required to compile project teams

  • Person resource: is required for the planning the respective person as a resource in projects


Module Variants

Base

Persons who have not left the company, i.e. persons which have no entry in the Leaving date field, or the leaving date of which lies in the future, are displayed.

Users left

Only persons who have left the company and have an entry in the Leaving date field which does not lie in the future will be displayed.

Synchronization

In this module variant you can define via the PLANTA pulse and Jira Server checkboxes which users are to be synchronized in automatic pulse synchronization or manual Jira synchronization.

  • Automatic pulse user synchronization is started, e.g. as soon as you save in this module.

Search Users

  • Using the Search user field you can filter for users the user name or user ID of whom contains the entered search string.

  • You can search for a complete name, a complete user ID, or for parts of a name or user ID.

    • Asterisks (*) in the search string serve as placeholders:

      • An asterisk at the end of a search string finds users the name or user ID of whom starts with the search string: Johan* finds Johanna, Johannes, Johannsen, Johansson, etc.

      • An asterisk at the beginning of a search string finds users the name or user ID of whom end in the search string: *ller finds Müller, Mueller, Miller, etc.

      • An asterisk at the beginning and end of a search string finds users the name or user ID of whom contains the search string: *ndre* finds Andrea, Andreas, Ondrej, etc.

    • A search string without asterisk is treated like a search string with asterisk at the beginning and at the end.

Details

  • By clicking on the All button you will get an overview of all existing users.

Edit Users

Procedure

  • The core data of the user, e.g. Code, Name, Start date, etc., is created in the course of the input of person properties in the Persons module.

  • Further user data or attributes are edited in the Users module by entering or changing the default values in the required fields.

Here you will find a list and description of all user fields/parameters.

Assign Person Groups to Users

Information

  • The visibility of the navigation points in the user menu is controlled by the assignment of person groups, which happens in the new design (web client) by clicking the Assign person groups button in the User module, which opens the Assign Person Groups to Users module.

  • One or more person groups can be assigned to a user. When assigned to multiple person groups, navigation access results additively from the sum of all assigned person groups; each navigation point appears exactly once in this case.

  • Several users can be selected simultaneously before clicking on the button: The dialog module then displays all selected users together for editing.

When migrating from older systems with the existing users, the old user roles are displayed in gray for information purposes.

For more information on the overall concept, see Rights Control.

Assign Menu Items to Users

Information

  • To access menu items, each user still needs exactly one menu item role. Like before, this is assigned to him is the User module.

  • The access to modules and work areas is no longer controlled by roles, but by person groups (see section Assign Person Groups to Users further below) Existing roles for module control are no longer analyzed for this purpose.

  • In the new design (web client) all roles that are not menu item roles are shown in gray (cannot be edited); in the native client, they remain editable as before. The corresponding roles are renamed to Roles (old) and Work Areas (old) respectively.

  • Several standard menu items defined by PLANTA are included in the scope of supply of the PLANTA software. If needed, these can be adjusted in the Roles (old) module or new individual module item roles can be created.

Procedure

  • Right-click on the user record of the employee to whom the menu item role is to be assigned and select Insert → Role.

  • A role record is inserted.

    • Select a standard role for menu items, e.g. 01100192 R39 MP Total, from the list box in the Role field.

      • The assignment of a menu item role to each user is mandatory. Without such a role, the user is unable to start the program. When attempting to log in with a user who has no access to menu items, the following message will be displayed: IEmenu_send(): menu items couldn't be fetched. Closing application. (See log file for further information)

  • Save.

Define User Rights

Information

Here you can find a complete overview of rights control in PLANTA project.

User Passwords

For security reasons, no automatic passwords are generated for newly created users. As long as no passwords exist yet for the users, the latter cannot log in to the system and the User or password unknown. message is displayed when they try to log in. If no other security login concept, e.g. single sign-on, is used, PLANTA project administrators must immediately generate a temporary password for newly created users and make it available to them.

Create Temporary Password (Reset Password)

Information

  • In PLANTA project, each user can change their password themselves anytime.

    • The button with the user name (in the lower area of the user menu) → Change password.

    • Click on the PLANTA logo (in the header area of the user menu) → Menu item Extras → Change password.

  • For the first log in of the newly created user, or in case an existing user forgot their password, a PLANTA project administrator can create temporary passwords, with the Reset password function.

Procedure

  • In the User module, open the context menu by right-clicking on the record of the required user in the left window, and selecting the Reset password command.

  • Confirm the Are you really sure? message with Yes

    • If no e-mail address is stored in the module,

      • the newly created temporary password will automatically be sent to this e-mail address.

    • If no e-mail address is stored for the user,

      • the following query will be displayed: E-mail cannot be sent, reset password anyway?

        • If you want to generate the password without e-mail dispatch, confirm the message 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 (reset password) procedure.

        • If you do not want the password to be created without e-mail dispatch, click on the Cancel button.

  • The user receives the temporary password via e-mail or from the administrator and enters it upon his/her next login. The employee must then change the temporary password.

Notes

  • If you want passwords be sent via e-mail, you have to make sure that

    • the e-mail address of the users is specified on the respective persons 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. The password, however, will be changed regardless.

    • enter the correct IP address of the smtp server in the SMTP server address parameter in the Global Settings module.

      • 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.

Set/Change User Language

Information

  • In the PLANTA software, the user interface language can be set individually for each user.

  • Which languages are available to your users depends on the languages you have licensed. For further information, please click here.

  • Some texts (e.g. some dialog messages) are not displayed in the PLANTA user's language but in the Windows user's language, These are messages which are stored in the client. They include, e.g., the Export to Excel and Change password dialogs or the connection settings.

  • As long as an I-text has not yet been translated into the required language, the respective position remains empty on the user interface for this language.

Procedure

  • Select the desired language for the respective user in the Language field in the Users module.

  • Save.

    • After you have logged in again, the I-text data (modules, data fields etc.) will be displayed in the corresponding language.

Details

  • In PLANTA standard, "German" is preset for all users by default.


See also: Information on Language for Customizers, Information on Language for Users

Control Creation/Editing/Deletion of Module Variants per User

Information

  • In the module, users with customizer rights have the option to enable or disable the creation, editing, and deletion of user-specific module variants via the MV creation User parameter.

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 option for the user:

      • The administrator defines a macro for the required user which contains a particular startup module.

    • Startup with modification option 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 Option for the User

Procedure

  • Select the ID of the macro which determines the module which is to be used as a startup module for the user in the Users module in the MOD (startup macro) field. If the user starts the program or if he/she clicks on the Extras → Home menu item, the module defined here is immediately opened automatically.

  • The macros listed here contain the default startup modules defined by PLANTA.

  • To define a different module as startup module, a new startup macro must be created and assigned to the user. This applies to the storage of both PLANTA standard modules and customer-specific modules.

Define Individual Startup

Information

  • The following example explains how to set up an individual startup macro.

    • The My Planning Objects module is defined as standard startup module for the Project management role in PLANTA.

    • For a user with project management role, a new macro is to be created which is not to start the My Planning Objects module as startup module but the Check Reported Hours module which is also included in the project management role.

      • To be able to customize a new macro you need access to customizing modules and additional customizing rights.

Find the ID of the Check Reported Hours module which you want to define as a startup module

  • To do so, expand role 01100219 Project management in the Roles module.

  • Open the assigned work area by clicking on the link on said work area. Now you see all the modules assigned to the work area as well as their IDs.

  • Copy the ID of the Check Reported Hours module to the clipboard.

Store the module in Global Settings

  • Since the Check Recorded Hours module already exists in the Globala Settings in the PLANTA standard system, there is nothing left to do. For custom modules, please refer to the manual for storing a module ID in the Global Settings.

Create a new startup macro

  • In the user menu, unfold the Module Customizer area.

  • Click on the Modules link; the module of the same name opens.

  • Create a new macro module:

    • For this purpose, enter a name in the Module field (e.g. Call up Reported Hours).

    • Select "6" = Macro module from the listbox in the Class parameter.

    • Save.

StartupDefinieren2.png
  • Switch to the Python Macros module by clicking on the ButtonPythonMakroBearbeiten.png Edit Python macro button.

  • Insert a Python macro with the Python ID which has been stored for the Check Recorded Hours module.

Python
from ppms import ppms_cu
mod_obj=ppms.get_target_module()
module_id=ppms_cu.Helper.get_global_setting("hour_inspection").alpha120.get_value()
ppms_cu.Action(mod_obj).call_startup_module(module_id)
  • Save, then copy the ID of the newly created macro module (in this case, 100000) to the clipboard. For further information on the customizing of a new module, please refer to the PLANTA customizer help area.

Assign the new startup module to the user

  • Go back to PM Administration → Master Data → Users, Roles, Resources → Users.

  • Enter the number of the newly created Open time control macro in the MOD (Startup macro) field in the required user record.

  • Save.

  • Result: When Ralf Schulze logs in again, the Check Reported Hours module is opened automatically.

Startup with Modification Option for the User

Procedure

  • Step 1:

    • Select the startup modules for the roles of the required user from the listbox in the MOD (Role Startup MOD) field in the Roles module.

    • Save.

  • Step 2:

    • Select the 009A1W Startup of all role modules macro in the MOD (startup macro) field on the record of the required user in the Users module.

    • Activate the Load startup module checkbox for the roles assigned to the user the startup modules of which are to be loaded automatically upon program start.

    • Save.

Details

  • If the user starts the program or clicks on the Extras → Home menu items, all modules defined by the administrator as startup modules and activated via the Load startup module checkbox are opened automatically.

  • The user can change the default 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.