DT511 User

Below, you will find descriptions of individual user parameters (user data fields).

DI010323 User ID

Code (ID) of the system user. This code is queried upon program start.

DI040533 User

Name of the user, composed of: name and first name

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

DI025589 Full name

Name of the user, composed of: name and first name. The name of the corresponding person is automatically entered in this field during the creation of person properties. It can only be changed by changing the name of the person.

DI025637 from

Date on which a person was defined as a user.

Modifiable

• in the Persons module,
• provided that the modifying user possesses the required rights

Details

• This parameter is used to control the activation/deactivation of the user accounts.
  • If the field is filled with a date, the account of the user only becomes active on this very date, i.e. the user can only log in to PLANTA from this date on.
  • If the field is not filled, the account of the user is always active, provided that in the up to field nothing to the contrary is defined.
• When you create the "user” property for a person, the field is automatically filled with the creation date, however, you can change it manually.

DI025638 to

Date from which on the "user" property of a person stops being valid.

Modifiable

• in the Persons module,
• provided that the modifying user possesses the required rights

Details

• This parameter is used to control the activation/deactivation of the user accounts.
  • If you enter a date in this field, the account of the user will only be active up to this very date, i.e. the user will only be able to log-on to PLANTA up to this date 
  • If you do not fill this field, the account of the user is always active, provided that in the from field nothing to the contrary is defined. 
• If you enter a leaving date of the person in the Left on field in the Persons module, it will automatically be copied to the up to field. This ensures the consistency of the dependent data.

Note

• If necessary, you can use DI026381 End time stamp, which can be included individually in the Usersmodule, to define the time up to which the user can log in on the defined up to date.

DI010421 Person ID

ID of the person assigned to the corresponding user

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

DI010616 Startup macro

ID of the macro which defines the startup module of the user which is loaded automatically when you start the program or when you select the Extras → Home menu item.

• A user startup module is one of two options for defining the startup module of a user. This variant serves to define a module as a fixed startup module for a particular user without granting write rights to the user. This variant can also be used to specify an individual module as a startup module for a particular user.
• The second option is the definition of a startup module based on roles. Role startup modules enable the automatic and simultaneous opening of several modules for a user upon program start, since, unlike in user startup modules which can only be specified once per user, here several roles can be assigned to a user. Unlike the user startup module, which is permanently stored by the administrator and can neither be turned off nor be changed by the user, the role startup module allows you to change the default preset made by the administrator, i.e. to define whether and which of the default startup modules are loaded. For further information, see Load Startup Module.

Procedure

• A user startup macro is automatically stored in the User module module when you select the corresponding macro on the user record in the MOD (startup macro) field. Exception: Macro 009A1W Startup of all Role Modules. If you want to use the second variant (role startup module), you have to select this macro. 
• For further information on the definition of the role startup modules, see the description under Role Startup MOD.

Notes

• In the listbox on the MOD (Startup Macro) field, only macros which are assigned to the 01100111 Startup macros work area (PLANTA standard) are offered for selection.
  • The startup macro work area 01100111 is entered as a value in the @M33 manual search list variable. If another work area is to be used on the part of the customer than that used in PLANTA standard, the specification must be adjusted in the variable.
• If you have created an individual macro, you can simply specify it here. There is no input via listbox.

DI058247 User startup module

Name of the macro which defines the startup module of the user which is loaded automatically when you start the program or when you select the Extras → Home menu item. For further information on the definition of the user startup macro module, please refer to the startup macro which is used to select the corresponding module.

DI010633 Department ID

Code (ID) of the department for which the current user acts as a department manager. For description, see DI058249

DI058249 Department

Name of the department for which the logged-on user carries out management tasks or for which he/she acts as a department manager.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

Details

• The entry made here determines which resources are displayed in the modules of the department board: My Department and Resource Planning modules in his/her own employee board.  

• The Department parameter does not necessarily have to be the department to which the user belongs. You can also enter a superordinate department if the user is to be responsible for all subordinate departments. In such a case, please make sure that the correct structure code is entered in the Resource access field, so that it does not contradict the entry made here and possibly restricts resource access.
  
  • The structure code of the department entered here has to be identical to the value in the Resource access field or the value in Resource access must imply the structure code of the department entered.
    • Example: If the structure code of the entered department is 1.4.1, the entry in Resource access must be 1.4.1, 1.4.1*, 1.4* or 1*.
• For all users to whom the resource manager role is assigned it is mandatory to specify a department since otherwise the department board cannot be opened.

DI041522 Startup macro name

Name of the startup macro of the user. For description, see Startup macro name.

DI010618 Object rights ID

Code of the object right of the user. For description, see Object Rights.

Details

• The code is written in the system variable @31 which can be used as a filter criterion in modules.

DI058251 Object rights

Object rights of the user. The parameter controls, along with other parameters (e.g. Modification access, Manager, etc.) the Modification rights of the user for data and functions of the planning objects (ideas, proposals, projects, programs) and portfolios. In input mode, a listbox for selection of an object right is displayed on the respective field.

The parameter can be edited in the following modules by users with modification rights:

• Users

Values

Notes for customizers

• Multi-project manager rights are now checked for @31 = "1", "2", and "4".
• The check is performed using the current_user_is_mpm method in the project_rights Python module.

DI066271 Can delete actual postings

Defines whether the user can delete actual postings. If the checkbox is deactivated and the user tries to delete actual postings, a message will be displayed which indicates that the user is not allowed to delete actual postings.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

DI010627 OS login

OS login is no longer supported by PLANTA. In order to ensure secure authentication, PLANTA offers Kerberos or PLANTA secure. If you have any questions, please contact your PLANTA consultant.

DI010636 Object access

Here you can enter the cost center structure code of the planning objects (projects, ideas, proposals, programs) to which you want the user to have access. This setting serves to control the project access of this user. 

How is the user’s access to objects controlled?

• The structure code entered here is stored in the @53 system variable when the user logs on. The variable can be entered as a filter criterion on the Cost center structure code field in user modules. For detailed information, please see Rights Management.

Example

• The user shall have access to all projects and portfolios of the Construction total cost center and of all of its child cost centers. The Construction total cost center has 2 child cost centers and the structure code 0111. Therefore, the user must possess structure code 0111* in the Project access field.
  • Wildcard "asterisk" (*) means: all following subitems of the item marked with the asterisk.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

DI010635 Resource access

Here you can enter the structure code of the resources and skills to which you want the user to have access.

How is the user’s access to resources and skills in PLANTA project controlled?

• The structure code entered in Resource access is saved in the @32 system variable when the user logs in. The variable can be entered as a filter criterion on the Resource structure code and Skill structure code fields in user modules. For detailed information, please see Rights Management.

Example

• You want a user to have access to all resources of the IT department. The IT resource has structure code 1.4. Accordingly, the user must possess structure code 1.4 in the Resource access field.
  • Wildcard "asterisk" (*) means all following subitems of the item marked with the asterisk.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

DI066581 Resource structure code

Here, the resource structure code of the resource which corresponds to the user is displayed. The value cannot be changed and is used for adjustment when the Resource access parameter is filled. This parameter serves, along with the Resource structure code parameter, to control the user’s access to particular resources. The resource structure code is set in the Resource Structure module.

Details

• Since the structure code entered in the Resource access parameter must correlate with the resource structure code, a traffic light is implemented on the Resource structure code field which turns yellow if the following discrepancies occur: 
  • the Resource access field does not coincide with the value in the Resource structure code field when exact values are specified, e.g. Resource access = 1.5.1,  Resource structure code = 1.5  
  • for entries with *, the value in the Resource access field is not in the same structure tree as the Resource structure code, e.g. Access to resources = 1.6*, Resource structure code = 1.7.1  
  • if the value in the Resource access field is empty. Although this does not constitute a contradiction in the access logic, in PLANTA an empty Resource accessfield means that the user is allowed to see all resources. Here, the traffic light serves to indicate that this setting grants very extensive access rights.

For in-depth information on resource access control, please refer to Rights Management.

DI010638 Language code

Code (ID) of the user language

DI058245 Language

Name of the user language. The PLANTA project surface is displayed to the current user in this language.

Customizing details

• DI058245 is an incarnation which enables you to add a listbox for selection of a language to this field in user modules.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

DI010662 Skin ID

Code (ID) of the user skin. For description, see Skin.

DI058241 Skin

Name of the user skin. The user skin controls certain elements of the user interface.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

Details

• An individual user interface, which may deviate from the Skin system parameter, can be assigned to the user here.

DI025834 Date format

Here you can specify the ID of the date format in which dates are to be displayed system-wide to the user for which the format was defined.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

Details

• The user date format overrides the system-wide date format defined in the skin (in the Date format parameter).
• In some fields, the user date format may be overridden by the field date format if such a format has been defined for the fields in question:
  • either at data item level in the Format ID parameter
  • or at data field level in the Format ID parameter

DI025835 Currency format

Here you can specify the ID of the currency format in which currencies are to be displayed system-wide to the user for whom the format was defined.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

Details

• The user date format overrides the system-wide currency format defined in the skin (in the Currency format parameter).
• In some fields, the user currency format may be overridden by the field currency format if such a format has been defined for the fields in question:
  • either at data item level in the Format ID parameter
  • or at data field level in the Format ID parameter

DI025836 Number format

Here you can specify the ID of the number format which is to be used system-wide particularly for the user for which the format was defined.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

Details

• The user number format overrides the system-wide number format defined in the skin (in the Number format parameter).
• In some fields, the user number format may be overridden by the field number format, if such a format has been defined for the fields in question:
  • either at data item level in the Format ID parameter
  • or at data field level in the Format ID parameter

DI027382 User

Name of the user, composed of: name + first name

DI042151 PID

Here, the process ID of the current client is displayed

DI059001 PPID

This parameter is no longer used.

DI059301 Database version

Unlike the server field in which the server changeset number is displayed by which the version of the PLANTA project server can be identified, the actual version of the PLANTA project database is specified here.

DI010632 Logbook

This DI has been deleted.

DI024343 License

The user license is displayed here.

DI060058 DBMS

In this field, the database system used is displayed.

DI025749 Database name

This field refers to the hibernate.cfg.xml config file.

DI059258 Database user

This field shows the name of the user logged-in to the database.

DI025757 Work directory

In this field, the server work directory of the logged-in user is displayed.

DI025746 E-mail

In this field you can enter the e-mail address of the user.

Modifiable

• in the Persons and Users modules,
• provided that the modifying user possesses the required rights

Details

• Messages (also messages which concern the user, e.g. passwords) are always sent to the e-mail address which is specified for the person in the E-mail field, regardless of which e-mail address is specified for the user.
• For the above mentioned reason, the e-mail address of the person is automatically transferred to the stakeholder and is saved in this field when person attributes are created.

Notes

• To use e-mail dispatch directly in PLANTA, you have to make sure that
  • the e-mail addresses of all PLANTA persons concerned (sender and recipient) are specified in the E-mail field in the Persons module.
  • the specified e-mail address is correct. E-mail addresses are not validated in PLANTA project, so in case you enter a wrong address, the recipient will not receive the e-mail.
  • the global parameters required for e-mail dispatch are set in the Global Settings module.

DI060055 Customizer rights

This parameter controls whether the user has customizer rights and is thus allowed to switch from the user view of the modules to the customizer view of the modules (via CTRL + F3, F9, and via the links in the Data Field Information module) in order to consult the customizing of the respective module or to make the required adjustments.

Caution

• Furthermore, users for whom the checkbox is activated possess all modification rights at user level, regardless of other rights which may be defined for them. See also Modification Rights.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

Details

• If there are errors in the system customizing, users for which this parameter is activated receive the Problems in system customizing dialog message immediately after logging on to PLANTA. Further information.

DI062216 Session ID

The session ID serves to identify an individual session. It is the same as the thread ID.

Notes

• This ID is also displayed in the server log files. It allows you to assign a log file to a particular session.
• The Python API offers different methods for session monitoring.

DI063175 MV creation

Via this parameter, creation, editing, and deletion of individual module variants can be switched off for particular users. The parameter can be found in window 9 (hidden) of the Users module and is activated by default.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

Values

• - creation, editing, and deletion are enabled
• - creation, editing, and deletion are disabled

Notes

• When using the MV creation user parameter, the MV creation module parameter must be considered as well.
• The MV creation user parameter dominates the MV creation module parameter. I.e.:
  • if the MV creation user parameter is deactivated, this user cannot create, edit, or delete individual module variants; not even for modules for which the MV creation module parameter is activated.
  • if the MV creation user parameter is deactivated, this user cannot create, edit, or delete individual module variants; not even for modules for which the MV creation module parameter is activated.

DI063247 Parallel sessions

Via this parameter, the maximum number of parallel sessions per user can be set. If this number is exceeded, the following dialog message will be displayed: The maximum number of opened sessions has already been reached. Before logging in again, the available clients of this user must be closed. For further information, please see here. For this parameter, "3" is set as a value by default, however, this value can be changed if necessary.

Modifiable

• in the Users module,
• provided that the modifying user possesses the required rights

Note

• In addition to this user-specific limit, there is also an absolute limit for parallel sessions which determines that only a particular number of sessions can connect to the server simultaneously. This limit is controlled via the parallel_sessions parameter in globals.conf. If you exceed this number and try to start a new client, the following message will be displayed and the client will be closed again: The new session is denied since the maximum number of simultaneously opened sessions has been reached. 

DI010625 Function

Field for approval. It can be used for arbitrary purposes/to provide arbitrary information.

DI010634 Message via e-mail

Checkbox which determines whether the user receives e-mails on Resource Planning with Requests/Approvals.

Values

• - the user will receive e-mails on Resource Planning with Requests/Approvals
• - the user will not receive any e-mails on Resource Planning with Requests/Approvals

The parameter can be edited in the following modules by users with modification rights:

• Persons
• Users

DI066671 Synchronize with PLANTA pulse

Defines whether a user is to be synchronized with PLANTA pulse. If you save in the modules mentioned below, automatic synchronization is started by all users for which the parameter was activated.

The parameter can be edited in the following modules by users with modification rights:

• Users (Synchronization module variant)
• User Synchronization

DI066672 Synchronize with Jira Server

Defines whether a user is to be synchronized with Jira Server. If you click on the Create user in Jira or Link user button in the User Synchronization module, synchronization is started for all users for which the parameter has been activated.

DI010619 Bar coloring allowed

DI010622 Currency