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

DT527 Stakeholder

From DB 39.5.12

DI026560 Stakeholder ID

Code (ID) of the stakeholder. For description, see DI034521.

Up to DB 39.5.12

DI026560 Stakeholder

Code (ID) of the stakeholder. For description, see DI034521.

From DB 39.5.13

DI034521 Stakeholder

Name of the stakeholder (incarnation field). If the requested person is not offered for selection in the listbox, a stakeholder assignment is to be inserted for that person in the Persons module.

Modifiable

From DB 39.5.12

DI034521 Stakeholder

Name of the stakeholder (incarnation field). If the requested person is not offered for selection in the listbox, a stakeholder assignment is to be inserted for that person in the Persons module.

Modifiable

From DB 39.5.7

DI034521 Stakeholder name

Name of the stakeholder (incarnation field). If the requested person is not offered for selection in the listbox, a stakeholder assignment is to be inserted for that person in the Persons module.

Modifiable

From DB 39.5.0

DI034521 Stakeholder name

Name of the stakeholder (incarnation field). If the requested person is not offered for selection in the listbox, a stakeholder assignment is to be inserted for that person in the Persons module.

Modifiable

Up to DB 39.5.0

DI034521 Stakeholder name

Name of the stakeholder (incarnation field). If the requested person is not offered for selection in the listbox, a stakeholder assignment is to be inserted for that person in the Persons module.

Modifiable

DI026572 Role

Role of the stakeholder in the project team

Modifiable

From DB 39.5.7

From DB 39.5.0

  • in the
  • provided that the modifying user possesses the required rights
  • Up to DB 39.5.0

  • in the
  • provided that the modifying user possesses the required rights
  • Note

    DI026614 Comment

    Text field for a note/remark on the stakeholder

    DI026615 Modification access

    By activating/deactivating the Modification access checkbox, the project manager can allow a project team member to edit the data of a planning object (project / program / proposal) (e.g. as an absence rule).

    Values

    • Checked - Team member is allowed to edit project data
    • Unchecked - Team member is not allowed to edit project data

    Note

    • Learn more about controlling access rights for projects here.

    Modifiable

    From DB 39.5.13

    From DB 39.5.7

  • in the
  • provided that the modifying user possesses the required rights
  • From DB 39.5.0

  • in the
  • provided that the modifying user possesses the required rights
  • Up to DB 39.5.0

  • in the
  • provided that the modifying user possesses the required rights
  • DI026618 Person

    ID of the stakeholder person. For further information, see the Persons module.

    DI026625 E-mail

    E-mail address of the stakeholder. The e-mail address of the stakeholder is stored in the Internal e-mail field in the Persons module and is automatically copied to DI026625 E-mail.

    DI026709 Watcher

    Parameter which signalizes whether the stakeholder is a watcher of a selected project (or in other words: whether the stakeholder in question has added the project to his watchlist)

    DI026724 Left on

    Date from which on the stakeholder person is no longer available as a resource for projects and can therefore no longer be created as a stakeholder for projects. The date is automatically copied from the Left on parameter of the respective resource.

    DI040574 Name

    DI040611 Left on

    Date until which the corresponding person was a member (stakeholder) of a project team

    DI041493 Info distribution list type

    Inbox/outbox type, i.e. the way messages are sent and received

    Values

    From DB 39.5.13

    • E-mail: Message is received as an e-mail.
    • no info: no message reception

    Up to DB 39.5.13

    • E-mail: Message is received as an e-mail.
    • Pop-up: Message is received within the program and displayed under Receipt in the Info module. An additional pop-up message is displayed when the recipient runs PLANTA project.
      • If the user logs on later, the message is only displayed in the Info module.
    • Pop-up & e-mail: Message is received as both e-mail and information within the program.
    • none: no receipt of information

    Details

    • Find more information on the info function here.

    Notes

    From DB 39.5.13

    • To send messages via e-mail, you have to make sure that
      • the e-mail address of the recipient is stored in the E-mail field in the Persons module. If no e-mail address is stored, a message indicating this is displayed.
      • 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 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.

    From DB 39.5.6

  • If the messages are sent via e-mail, you have to make sure that
    • the e-mail address of the recipient is stored in the Persons module. NEW If no e-mail address is stored, a message indicating this is displayed.
    • 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 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.
  • From DB 39.5.4

  • If the messages are 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 in case you enter a wrong address, the recipient will not receive the e-mail.
    • 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 messages are sent via e-mail, you have to make sure that
  • Modifiable

    From DB 39.5.7

    From DB 39.5.0

  • in the
  • provided that the modifying user possesses the required rights
  • Up to DB 39.5.0

  • in the
  • provided that the modifying user possesses the required rights
  • DI057611 Category name

    Name of the category (incarnation field) to which stakeholders are copied

    Values

    • Core team
    • Supplier
    • Steeringboard

    DI057789 Function

    Function of the stakeholder within the company

    DI026626 Phone 1

    Phone number of the stakeholder person. It is automatically copied from the person data. You can create and edit phone numbers in the Persons module.

    Note

    • The corresponding field is hidden by default but can be displayed by the user if necessary.

    DI026627 Phone 2

    Second (alternative) phone number of the stakeholder person. It is automatically copied from the person data. You can create and edit phone numbers in the Persons module.

    Note

    • The corresponding field is hidden by default but can be displayed by the user if necessary.

    DI026628 Phone 3

    Third (alternative) phone number of the stakeholder person. For description, see Phone 2.

    DI024647 Full name

    The full stakeholder name is displayed.

    From DB 39.5.7

    DI026573 Max. % per day

    The DI is no longer used

    New from DB 39.5.0

    DI026573 Max. % per day

    The DI has no function

    DI057789 Function

    Field which contains the information from the field of the same name of the stakeholder user

    DI026562 Created on

    When you create a record, the creation date is automatically entered in this field.

    DI026563 Modified on

    When you modify a record, the modifying date is automatically entered in this field.

    DI026565 Created by

    When you create a record, the ID (code) of the logged-on user is automatically entered in this field.

    The creating user is also the owner of a record.

    DI026566 Modified by

    When you modify a record, the ID (code) of the logged-on user is automatically entered in this field.

    DI026725 HT: PR team PR

    DI026561 Project ID

    DI026723 Main project

             PLANTA project









     
    • Suche in Topic-Namen

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