The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.
TWiki> CurrentEN Web>CustomizingDocumentation>CustomizingDataFields>DT511User

DT511 User

From DB 39.5.12

DI010323 User ID

Code (ID) of the system user. The ID is queried when the program is launched.

Up to DB 39.5.12

DI010323 User

Code (ID) of the user. The ID is queried when the program is launched.

From DB 39.5.12

DI040533 User

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

Modifiable

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

Up to DB 39.5.12

DI040533 User name

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

Modifiable

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

From DB 39.5.10

DI025589 Full name

Name of the user, composed of: name and first name. The field is automatically filled with the name of the respective person when the person attributes are created. It can only be changed by changing the name of the person.

Up to DB 39.5.10

DI025589 Name+first name

Last and first name of the user

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

From S 39.5.28

  • NEW 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-on 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 creating the "User" property for a person, the field is automatically filled with the creation date, however, it can be changed manually.

Up to S 39.5.28

  • The parameter has no functional but only a merely informational character.
  • It is automatically filled with the date on which the person receives the "User" property, however, it can be changed 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

    From S 39.5.28

    Details
    • NEW 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 is only active up to this very date, i.e. the user can only log-on to PLANTA up to this date. In the End timestamp field, you can additionally define the time up to which the user can log-on on the defined up to date.
      • 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. In the course of this the possibly existing entry in the End timestamp field is ignored.
    • If a leaving date is entered in the Leaving date field in the Persons module, it is automatically copied to the to field of the respective user when saving. As a result, the consistency of the dependent data is ensured.

    From DB 39.5.11

    Details
    • The field has no functional but only a merely informational character.
    • NEW If a leaving date is entered in the Leaving date field in the Persons module, it is automatically copied to the to field of the respective user when saving. As a result, the consistency of the dependent data is ensured.

    Up to DB 39.5.11

    Details
    • The field has no functional but only a merely informational character.

    From DB 39.5.12

    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

    Up to DB 39.5.12

    DI010421 Person

    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 startup macro of the user. For description, see Startup macro name.

    DI058247 Startup macro name

    Name of the startup macro of the user. The startup macro selected/displayed here defines which module/s is/are loaded automatically when the user logs on.

    • Exception: macro 009A1W Startup of all Role Modules.
      • This macro must be selected if modules from several roles are to be loaded for the user. In this case,

    Modifiable

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

    Details

    • There are two ways to assign a startup module to a user: via the user itself or via its role.

    Procedure 1

    Procedure 2

    • Create a role in the Roles module and specify a startup module in the Startup MOD field.
    • Assign the role to the user in the Users module.
      • To select the startup module of one or several roles, macro 009A1W Startup aller Rollenmodule must be selected in the Startup macro name field.
      • In this case, the Load startup module checkbox must be activated and the Startup MOD field must be filled to define from which role the modules are to be loaded.
    Notes
    • In the startup macro name listbox, only macros which are assigned to the 01100111 Startup macros work area (PLANTA Standard) are offered for selection.
      • The Startup macros work area 01100111 is entered as a value in the @M33 manual search list variable. If another work area is to be used on part of the customer than in PLANTA Standard, the specification must be adjusted in the variable.

    DI010633 Department (default)

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

    DI058249 Department name (default)

    Name (incarnation) 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 department entered here does not necessarily have to be the department the user belongs to (see parent resource field in the Resource Data Sheet).
      • The structure code of the department entered here has to be identical to the value in the Resource access field or Resource access is to imply the structure code of the department entered. If the structure code of the department is 1.4.1, the entry in Resource access must either be 1.4.1, 1.4.1*, 1.4* or 1*.
      • The way the department manager is displayed in the My Department module depends on the values entered in both fields:
        • If the department structure code is identical to the value in the Resource access field, only this department and its resources are displayed in the My Department module.
        • The department utilization diagram is displayed in the My Department module if the value in the Resource access field implies the department structure code, however, all resources to which the user has access are listed.
        • If completely different values are entered in each field, no department utilization diagram is displayed in the My Department module, but all resources to which the user has access are displayed.
    • The code (ID) of the department selected from the listbox is displayed in the Department (default) field.

    DI041522 Startup macro name

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

    DI010618 Object rights

    Code of the object right of the user. Together with the parameters (e.g. Modification rights, Manager etc.), the Object rights parameter controls the write rights for planning object data and functions. The code is written in the @31 system variable which can be used as a filter criterion in modules.

    Details

    • The object right is defined for each user by making a selection in the Object rights name field in the Users module.
    • For the description of individual rights, see Object rights name.
    • For a complete overview of rights control in PLANTA, see here.

    DI058251 Object rights name

    Name (incarnation) of the object right of the user

    Modifiable

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

    From DB 39.5.10

    Code Name Authorizations Explanation
    0 No multi-project manager The user has no right to create new planning objects and to edit the data of the planning objects (all fields are set to output). The behavior can be influenced by different parameters and settings. For more information, see Write Rights for Planning Objects and Resources.
    1 Multi-project manager The user has multi-project manager rights, i.e., he/she is authorized to create and delete new PLANTA project planning objects and resources and to modify the data of all such planning objects and resources (all modification fields are set to input). This setting is dominant, i.e. it cannot be influenced by any other write rights parameters.

    For the creation of ideas and proposals, the following applies:

    • No object right is needed if the corresponding modules for object creation can be accessed directly.
    • If ideas and proposals from the overview modules (e.g. Overview by Type) are created, they are checked for Object right = 1, 2 or 4.
    2 Multi-portfolio manager The user has multi-portfolio manager rights. This authorization also implies multi-project manager right 1, i.e. the portfolio manager is allowed to create and delete new PLANTA project planning objects, resources, portfolios, and requests and to change all planning object data (all editing fields are set to input). This setting is dominant, i.e. it cannot be influenced by another write rights parameter.
    3 Multi-request manager The user has multi-request manager rights, i.e. he/she is allowed to create new requests and to change all request data (all editing fields are set to input). This setting is dominant, i.e. it cannot be influenced by another write rights parameter.
    4 Multi-project/request manager The user has multi-project/multi-request manager rights, i.e. he/she is allowed to create ideas, proposals, and requests and to change the data of all these planning objects (all editing fields are set to input). This setting is dominant, i.e. it cannot be influenced by another write rights parameter.

    From DB 39.5.7

    Code Name Authorizations Explanation
    0 No multi-project manager The user has no right to create new planning objects and to edit the data of the planning objects (all fields are set to output). The behavior can be influenced by different parameters and settings. For more information, see Write Rights for Planning Objects and Resources.
    1 Multi-project manager The user has multi-project manager rights, i.e., he/she is authorized to create and delete new PLANTA project planning objects and resources and to modify the data of all such planning objects and resources (all modification fields are set to input). This setting is dominant, i.e. it cannot be influenced by any other write rights parameters.

    For the creation of ideas and proposals, the following applies:

    • No object right is needed if the corresponding modules for object creation can be accessed directly.
    • If ideas and proposals from the overview modules (e.g. Overview by Type) are created, they are checked for Object right = 1, 2 or 4.
    2 Multi-portfolio manager NEW
    (The name has changed but the content of the authorization has not)     		The user has multi-portfolio manager rights. This authorization also implies multi-project manager right 1, i.e. the portfolio manager is allowed to create and delete planning objects, resources, and portfolios and to change all planning object data (all editing fields are set to input). This setting is dominant, i.e. it cannot be influenced by another write rights parameter.
    3 Multi-request manager The user has multi-request manager rights, i.e. he/she is allowed to create new requests and to change all request data (all editing fields are set to input). This setting is dominant, i.e. it cannot be influenced by another write rights parameter.
    4 Multi-project/request manager The user has multi-project/multi-request manager rights, i.e. he/she is allowed to create ideas, proposals, and requests and to change the data of all these planning objects (all editing fields are set to input). This setting is dominant, i.e. it cannot be influenced by another write rights parameter.

    Up to DB 39.5.7

    Code Name Authorizations Explanation
    0 No multi-project manager The user has no right to create new planning objects and to edit the data of the planning objects (all fields are set to output). The behavior can be influenced by different parameters and settings. For more information, see Access rights.
    1 Multi-project manager The user has multi-project manager rights, i.e., he/she is allowed to create and delete new PLANTA project planning objects and resources and to change all data of these planning objects and resources (all editing fields are set to input). This setting is dominant, i.e. it cannot be influenced by other parameters

    For the creation of ideas and proposals, please note the following:

    • No object right is needed if the corresponding modules for object creation can be accessed directly.
    • If ideas and proposals from the overview modules (e.g. Overview by Type) are created, they are checked for Object right = 1, 2 or 4.
    2 Portfolio manager The user has portfolio manager rights. This authorization also implies multi-project manager right 1, i.e. the portfolio manager is allowed to create and delete planning objects, resources, and portfolios and to change all planning object data (all editing fields are set to input). This setting is dominant, i.e. it cannot be influenced by other parameters.
    3 Multi-request manager The user has multi-request manager rights, i.e. he/she is allowed to create new requests and to change all request data (all editing fields are set to input). This setting is dominant, i.e. it cannot be influenced by other parameters.
    4 Multi-project/request manager The user has multi-project/multi-request manager rights, i.e. he/she is allowed to create and delete new PLANTA planning objects, resources, and requests and to change all data of all these planning objects (all editing fields are set to input). This setting is dominant, i.e. it cannot be influenced by other parameters.

    Legend

    From DB 39.5.0

    • Planning objects are
      • in PLANTA project: ideas, proposals, projects, and NEW programs
      • In PLANTA portfolio: ideas, proposals, projects and portfolios
      • In PLANTA request: Requests

    Up to DB 39.5.0

  • Planning objects are
    • in PLANTA project: ideas, proposals, projects
    • In PLANTA portfolio: ideas, proposals, projects and portfolios
    • In PLANTA request: Requests

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

    DI010619 Bar coloring allowed

    DI010620 Object protection class

    The content of this data field is set to the user object protection class of the creating user.

    In case an entry has been made for the user and the data table in question in the User: Object Protection/Data Table module, the OPC field from this entry is used.

    An object protection class can belong to several users. Doing so, several program users are combined in a so called group.

    The object protection class is not related to the user class of a user.

    Modifiable

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

    DI010621 Customizer class

    DI010622 Currency

    DI010624 Authorizations

    Combined value covering the various user authorizations. These are represented bitwise. The values for the individual functions are summed, and this sum is entered as authorization.

    Modifiable

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

    Details and notes on Authorization = 32 and 35, which enable the deletion of actual postings, see here.

    Note

    • Value 2 and accordingly part of value 3 are temporarily inactive.

    DI010627 OS login

    Enables a user to be logged on automatically using the Windows user name. For this purpose, enter the Windows user name in this field.

    Modifiable

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

    Notes

    • The number of characters for the User name field in Windows is limited to a maximum of 21.
    • Additionally, you can check whether login via Windows is permitted.
      • For this purpose, information on domain and login procedure of the Windows session is transmitted via client to the user server. The user server checks the authenticity of the login information by calling up a Python method.
      • In delivery condition, no check is performed and the login is permitted analogous as before.
      • By implementing a certain logic in the ppms.os_login.os_login_verify() method, the login data can be processed and checked randomly. The method call code and documentation can be found in ppms/os_login.py.

    DI010636 Project access

    Here, the cost center structure code of the projects to which the user has access, is entered. This value is saved in the @53 system variable. In user modules, the @53 variable is used as a filter criterion for the Cost center structure code field.

    Modifiable

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

    Example

    • The user shall have access to all projects of the Construction total cost center and 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 subpoints of the point marked with the asterisk.
    Further examples

    Note

    • For a complete overview of rights control in PLANTA project, see Access control.

    DI010635 Resource access

    From DB 39.5.0

    Here, the structure code of the resources and NEW skills to which the user shall have access is entered. This value is stored in the @32 system variable when the user logs on. The variable can be entered as a filter criterion in the Resource structure code and Skill structure code fields in user modules.

    Up to DB 39.5.0

    Here, the structure code of the resource to which the user shall have access is entered. This value is stored in the @32 system variable when the user logs on. The variable can be entered as a filter criterion in the Resource structure code field in user modules.

    Modifiable

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

    Example

    • The user shall have access to all resources of the IT department. The IT resource has the structure code 1.4. Accordingly, the user has to possess the structure code 1.4 in the Resource access field.
      • Wildcard "asterisk" (*) means: all following subpoints of the point marked with the asterisk.
    Further examples

    See also: Rights Control in PLANTA project

    DI010638 Language Code

    Code (ID) of the user language

    DI058245 Language

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

    Modifiable

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

    From DB 39.5.12

    DI010662 Skin ID

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

    Up to DB 39.5.12

    DI010662 Skin

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

    From DB 39.5.12

    DI058241 Skin

    Name of the user skin. The user skin controls particular elements of the user surface.

    Modifiable

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

    Details

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

    Up to DB 39.5.12

    DI058241 Skin name

    Name of the user skin. The user skin controls particular elements of the user surface.

    Modifiable

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

    Details

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

    DI025834 Date format

    Here the ID of the date format in which dates are to be represented system-wide for the user for which the format was defined is specified.

    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 on data item level in the format ID parameter
      • or on data field level in the format ID parameter

    DI025835 Currency format

    Here the ID of the currency format in which currencies are to be used system-wide for the user for which the format was defined is specified.

    Modifiable

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

    Details

    • The user currency 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 on data item level in the format ID parameter
      • or on data field level in the format ID parameter

    DI025836 Number format

    Here the ID of the number format is specified, 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 on data item level in the format ID parameter
      • or on data field level in the format ID parameter

    From DB 39.5.12

    DI027382 User

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

    Up to DB 39.5.12

    DI027382 User name

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

    DI042151 PID

    Here, the process ID of the current client is displayed.

    DI059001 PPID

    From DB 39.5.0

    This parameter is no longer used.

    Up to DB 39.5.0

    In case the server is running on Unix and forking is activated, the PID of the parent process is displayed in this field. If the system is not set up as a forking server, the PID of the xinetd process is displayed here. In Windows, this field is empty.

    DI024649 Server

    In this field, the server changeset is displayed.

    Note

    DI059301 Database changeset

    Here, the entire PLANTA project version with the data base changeset is specified.

    Note

    DI010632 Logbook

    From S 39.5.12

    This DI has been deleted.

    Up to S 39.5.12

    This parameter defines whether the performance history evaluation is (de)activated, i.e. whether the session shall be recorded or not.

    Values

    • no entry - no logbook entries: the session is not recorded.
    • 1 - log performance history: the session is recorded.

    DI024343 License

    The user license is displayed here.

    From DB 39.5.0

    DI060058 DBMS

    In this field, the database system used is displayed.

    DI025749 Database name

    From S 39.5.0

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

    Up to S 39.5.0

    In this field, the name of the database currently accessed by the user is displayed.

    DI059258 Database user

    In this field, the ID of the user currently logged on to the database is displayed.

    DI025757 Work directory

    In this field, the work directory of the logged on user is displayed.

    DI058248 Department name (default)

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

    Details

    • The department displayed here does not necessarily have to be the department the user belongs to (see parent resource field in the Resource Data Sheet) module. In this case you have to make sure that the correct structure code is entered in the Resource access field.
    • The code (ID) of the department is displayed in the Department (default) field.

    DI025746 E-mail

    In this field, the e-mail address of the user can be entered.

    Modifiable

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

    Details

    From DB 39.5.16

    • 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.
    • NEW For the above mentioned reason, the E-mail address of the person is automatically transferred to the user and saved in this field.

    From DB 39.5.14

  • NEW 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.
  • This e-mail address is used for sending messages as well as for resetting temporary passwords.

    • Up to DB 39.5.14

  • This e-mail address is used for sending messages as well as for resetting temporary passwords.

    • Note

    From DB 39.5.0

    DI060055 Customizer rights

    NEW This parameter controls whether switching from the user view of modules to the customizing view via CTRL + F3, F9, and via the links in the Data Field Information module is allowed.

    Attention

    • Furthermore, users that have the checkbox activated possess all modification rights on 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

    • Users for which the parameter is activated receive the Problems in system customizing dialog message when logging in, pointing out errors in the system customizing, should there be any. Further information

    Note

    • The Customizer data field corresponding to the DI is contained in the Users module, from version 39.5.0 by default. If it has been adopted in the course of individual customizing, it has to be deleted so that it does not exist twice in the module.

    New from S 39.5.0

    DI060055 Customizer rights

    Users for which the parameter is activated receive the Problems in system customizing dialog message when logging in, pointing out errors in the system customizing, should there be any. Further information

    Note

    • In order for the parameter to be available in the system, the optional packet 10139 has to be executed when updating to S 39.5.0. As a result, the DI is inserted in DT511 and the parameter is activated for all users that have access to the Modules module.
    • Subsequently, the parameter can be assigned individually to the requested module, e.g., the Users module,.

    New from S 39.5.0

    DI062216 Session-ID

    The session ID can be used to identify an individual session. It is equal to the thread ID.

    Notes

    • This ID is also displayed in the Server log files. This way, a log file can be assigned to a particular session.
    • The Python API offers different methods for Session monitoring.

    New from S 39.5.7

    DI063175 MV creation

    Via this parameter, creation, editing, and deletion of individual module variants can be switched off user related. 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

    • Checked - Creation, editing, and deletion is switched on
    • Unchecked - Creation, editing, and deletion is switched off

    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 can not create, edit, or delete individual module variants; not even for modules for which the MV creation parameter is activated.
      • if the MV creation user parameter is activated for a user, this user can create, edit, or delete individual module variants; not even for modules for which the MV creation parameter is activated.

    From DB 39.5.10

    DI063247 Parallel sessions

    Via this parameter, the maximum number of parallel sessions per user can be set.

    Modifiable

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

    Note

    • If this number is overrun, the following dialog message is 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 click here.
    • For this parameter, NEW "3" is set as a value by default, which can be changed if necessary.

    See also: Technical FAQs

    New from S 39.5.11

    DI063247 Parallel sessions

    Via this parameter, the maximum number of parallel sessions per user can be set.

    Modifiable

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

    Note

    • If this number is overrun, the following dialog message is 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 click here.
    • For this parameter, "1" is set as a value by default, which can be changed if necessary.

    See also: Technical FAQs

    DI010625 Function

    Field for free entry. Can be used for arbitrary purposes/to provide arbitrary information.

             PLANTA project







     
    • Suche in Topic-Namen

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