Skip to main content
Skip table of contents

DT405 Module

DI000123 MOD

ID of a module: Automatically incrementing number.which is formed from the license number and an incrementing counter.

DI001588 Module

Title of a module. In user view, the module title is displayed in the title bar and possibly in the user menu if

DI057816 Panel

Title of a module panel.

  • If a panel title exists, it is displayed in the panel title bar or in the user menu; otherwise, the module title will be displayed.

See also: Customize Module Panel

DI028116 Main module

Here you can define whether the module is the main module or a submodule in a module panel.

Values

  • : The module is a main module
  • : The module is a submodule

Note

  • In order for submodules of a module to be opened as well, the Main module parameter must be activated in this module.
    • I.e.: if the Main module parameter is deactivated for a module to which submodules are assigned, or if the module is opened as a submodule via Python, the submodules of the module are not opened.

See also: Customize Module Panel

DI000127 Class

Serves to classify the modules. This parameter is decisive for particular program-internal processes.

Values

  • 1: Module for print areas
  • 3: User menu
  • 4: "Normal" data editing (standard)
  • 6: Macro module (plain macro module without data areas)
  • 12: Dialog module

DI002946 Copy from

Here, you can enter the ID of the module which is used as a source module when copying modules.

  • The modules are copied during saving.
  • Copying only works upon new creation, not when copying to a particular module.

DI040819 Macro

In this data field you can store a Python macro for a module.

See also: Python API Reference

DI002955 Repeat macro

This parameter influences the behavior of macros (Python macros or macro lines) when clicking on the F7 Close/reset button:

Values

  • Macro lines
    • - When pressing F7, the macro will be run again.
    • - When pressing F7, the macro will not be run again, i.e. the module remains empty.
  • Python macros with on_reset()
    • - No effect; when pressing F7, the code in the on_reset() function will be run
    • - No effect; when pressing F7, the code in the on_reset() function will be run
  • Python macros without on_reset()
    • - No effect; when pressing F7, the code in the on_load() function will be run
    • - When pressing F7, no code will be run, i.e. the module remains empty.

DI001824 Changed by

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

DI000395 Created on

Upon creation of a record, the time of creation is automatically entered here.

DI000396 Changed on

When a record is modified, the modification date is automatically entered here.

DI001823 Created by

When a record is created, the ID (code) of the logged-on user is automatically entered in this field. The creating user is also the owner of a record.

DI026089 No. of work areas

Number of work areas to which a module is assigned. A module should be assigned to at least one work area.

Details

  • A traffic light is stored on the field which signalizes whether this module
    • is assigned to at least one work area which is to be translated (green),
    • or is assigned to a work area which is not to be translated (yellow),
    • or is not yet assigned to a work area at all (red).

DI065818 Number of general module variants

Number of general module variants of a module

Details

  • A traffic light is stored on the field, which signalizes whether the module has at least one general module variant (yellow).

Info

  • PLANTA project distinguishes between general and user-specific module variants.
    • General module variants are visible to all users but they can only be created, modified, or deleted by users with customizing rights.
    • User-specific module variants are only visible for and can only be modified or deleted by the user who created them.

See also: General Information on Module Variants (in the Introduction and Program Operation help area), Change Module Variants via Customizer

DI065819 Number of user-specific module variants

Number of user-specific module variants of a module

Details

  • A traffic light is stored on the field which signalizes whether the module has at least one user-specific module variant (yellow).

Info

  • PLANTA project distinguishes between general and user-specific module variants.
    • General module variants are visible to all users but they can only be created, modified, or deleted by users with customizing rights.
    • User-specific module variants are only visible for and can only be modified or deleted by the user who created them.

See also: General Information on Module Variants (in the Introduction and Program Operation help area), Change Module Variants via Customizer

DI000146 No. of macro lines

Number of macro lines of a module

DI041424 Module status

Here you can enter the state of development of a module

Values

  • In process
  • Rollout
  • Test
  • Test module

DI000142 No. of data areas

Number of the data areas assigned to a module. Data editing modules must contain at least one data area.

Note

  • If you try to start a module with Class = 4 "Normal" data editing to which no data areas are assigned, the module data area assignment was not found message will be displayed.

DI006624 Grid line

This parameter defines whether in modules with hierarchic structure (tree structure), e.g. the Schedule (0099AN) module, grid lines are to be displayed in the areas of the structure tree. The effect of the parameter is controlled via the client-skin setting. If the respective client parameter (HideTreeStructureLines) is activated, the Grid line parameter is activated. If the client parameter is deactivated, the activated Grid line parameter does not take effect.

Details

In PLANTA standard, the client parameter is not activated, so that no grid lines are displayed in normal modules with tree structure. Modules with graphical structure display (data areas with DA class = 11), e.g. WBS (009ACB) module, are exempt from this. The Grid line parameter must be activated for these modules and its effect is independent of the client setting. See also Customizing of a Module with Graphical Structure Display

The Grid line parameter can only be used in combination with the activated Tree structureparameter.

DI006623 Tree structure

Here you can define for the module whether areas for which the Tree parameter is activated are to be indented automatically and thus give a representation of the hierarchic structure.

Details

  • If the Grid line checkbox is activated in addition, the grid line will be displayed between the areas in the structure tree additionally.
  • If the Grid line checkbox is not activated, only the +/- symbols of the tree structure will be displayed.

Notes

DI001965 Sub class

This module class is decisive for particular program-internal processes.

Values

  • For Class = 4:
    • 0: Normal data editing
    • 2: Replanning (this code should only be used by one module in the system)

DI000133 Print

Switch function for the menu item Data → Print directly and Data → Print via options. It serves to turn the menu item on or off per module.

For a description of the menu items, see here.

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

DI000129 Insert

Switch function for the Edit → Insert menu item. It serves to turn the menu item on or off per module.

For a description of the menu items, see here.

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

DI000130 Filter

Switch function for the Data → Filter menu item. It serves to turn the menu item on or off per module.

For a description of the menu items, see here.

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

DI000143 Extras: Filter criteria

Switch function for the Extras → Filter Criteria menu item. It serves to turn the menu item on or off per module.

For a description of the menu items, see here.

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

DI000136 Save

Switch function for the Edit → Save menu item. It serves to turn the menu item on or off per module.

For a description of the menu items, see here.

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

DI000137 Calculation of the schedule

Switch function for the Edit → Calculate Schedule menu item. It serves to turn the menu item on or off per module.

For a description of the menu items, see here.

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

DI000139 Unloading

Switch function for the Edit → Unload schedule menu item. It serves to turn the menu item on or off per module.

For a description of the menu items, see here.

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

DI000140 Delete

Switch function for the Edit → Delete menu item. It serves to turn the menu item on or off per module.

For a description of the menu items, see here.

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

DI002947 Default zoom page width

Switch function for the Zoom to page width menu item which can be found under Data → Print Preview. It serves to turn the menu item on or off per module.

For a description of the menu items, see here.

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

DI025609 Paper format

Here you can preset the paper format for printing.

Values

  • A4
  • A3
  • A2

DI001789 Zoom print preview

Percentage specification for the zoom preset for print preview. It is overwritten by the Default zoom to page width parameter.

DI025610 Portrait format

Defines the default portrait/landscape format print setting for the module.

DI001382 Release


DI006101 Time recording lock

Parameter with which you can define for each module how the Locked / Task locked, and the Time recording key date model parameter set on the projects are to take effect.

Values

  • 0: Key date and project/task lock take effect
  • 1: Key date is canceled
  • 2: Project/task lock canceled, key date takes effect
  • 3: Project/task lock canceled and key date canceled

DI001788 Zoom W1 - W3

Defines the zoom factor in a module

DI001958 Width W1

Width window 1: The value specified here is no size indication. The value merely serves to calculate the window width, i.e. the window share of the total screen width.

Details

  • The calculation is carried out in accordance with the following formula: Share W1 = Width W1 : (Width W1 + Width W2 + Width W3).

Example

  • Width W1 = 20, Width W2 = 20, Width W3 = 40 means that window 1 1/4, window 2 also takes up 1/4 and window 3 takes up half of the screen.
    • The same relation can also be reached through other absolute numbers. E.g. Width W1 = 100, Width W2 = 100, Width W3 = 200

Notes

  • If an arbitrary numeric value is specified for one of the three windows, this means that only the respective window will be visible and its size will correspond to the total screen size.
  • If the Width W1 field is filled but has no Window = 1 in the module, window 1 is displayed (empty) anyway.
  • In order to prevent too much free window space after width calculation, the window width will additionally be adjusted to the width of the actually displayed windows.
  • I.e.: If, due to the data fields, the required width is smaller than the width according to the specified share, the width of the windows is adjusted to the actually required width. If the required width is greater, the width is displayed in accordance with the share.
    • Example: if the values in Width W1 and Width W2 were to result in a window split of 50% / 50%, while window 1 only requires 25% due to the width of the displayed data fields, window 1 will be adjusted to a width of 25%.

DI001959 Width W2

Width window 2: The value specified here is no size indication. The value merely serves to calculate the window width, i.e. the window share of the total screen width.

Details

  • The calculation is carried out in accordance with the following formula: Share W2 = Width W2 : (Width W1 + Width W2 + Width W3).

Example

  • Width W1 = 20, Width W2 = 20, Width W3 = 40 means that window 1 1/4, window 2 also takes up 1/4 and window 3 takes up half of the screen.
    • The same relation can also be reached through other absolute numbers. E.g. Width W1 = 100, Width W2 = 100, Width W3 = 200

Notes

  • If an arbitrary numeric value is specified for one of the three windows, this means that only the respective window will be visible and its size will correspond to the total screen size.
  • The Width W2 field must be filled if at least one data field in the module has Window = 2.
  • If the Width W1 field is filled but has no Window = 2 in the module, window 2 is displayed (empty) anyway.
  • In order to prevent too much free window space after width calculation, the window width will additionally be adjusted to the width of the actually displayed windows.
  • I.e.: If, due to the data fields, the required width is smaller than the width according to the specified share, the width of the windows is adjusted to the actually required width. If the required width is greater, the width is displayed in accordance with the share.
    • Example: if the values in Width W1 and Width W2 were to result in a window split of 50% / 50%, while window 1 only requires 25% due to the width of the displayed data fields, window 1 will be adjusted to a width of 25%.

DI001960 Width W3

Width window 3: The value specified here is no size indication. The value merely serves to calculate the window width, i.e. the window share of the total screen width.

Details

  • The calculation is carried out in accordance with the following formula: Share W3 = Width W3 : (Width W1 + Width W2 + Width W3).

Example

  • Width W1 = 20, Width W2 = 20, Width W3 = 40 means that window 1 1/4, window 2 also takes up 1/4 and window 3 takes up half of the screen.
    • The same relation can also be reached through other absolute numbers. E.g. Width W1 = 100, Width W2 = 100, Width W3 = 200

Notes

  • If an arbitrary numeric value is specified for one of the three windows, this means that only the respective window will be visible and its size will correspond to the total screen size.
  • The Width W2 field must be filled if at least one data field in the module has Window = 3.
  • If the Width W1 field is filled but has no Window = 3 in the module, window 3 is displayed (empty) anyway.
  • In order to prevent too much free window space after width calculation, the window width will additionally be adjusted to the width of the actually displayed windows.
  • I.e.: If, due to the data fields, the required width is smaller than the width according to the specified share, the width of the windows is adjusted to the actually required width. If the required width is greater, the width is displayed in accordance with the share.
    • Example: if the values in Width W1 and Width W2 were to result in a window split of 50% / 50%, while window 1 only requires 25% due to the width of the displayed data fields, window 1 will be adjusted to a width of 25%.

In this field, a product logo is stored for the current module.

Details

  • When new modules are created, this field is filled with the 000704 Logo: project default logo. This is controlled via the global @G197 variable.
  • If a new product logo is employed system wide, this field is filled with the ID of the new logo in all existing modules. Accordingly, the new modules are automatically preset with the new logo as a default logo.

Information

  • The product logo is an OLE Object.
  • The product logo is displayed in the upper corner of the screen, next to the menu and symbol bars.

DI026175 Background symbol

In this parameter you can assign a background symbol for modules and a frame symbol for listboxes.

Note

  • The blue color of the listbox frames in the standard has the symbol ID 001975.

DI056952 Python module subclass

In this parameter, the path to the existing Python module subclass is stored.

Details

  • On the part of Python, a module can be an instance of a particular class instead of the module standard class.
    • The module adopts all methods from the module sub-class.
    • Thus, methods that are required in several modules do not have to be defined in the macro of each individual module but in a single module sub-class. This module sub-class is then assigned to the modules.
  • The directories in the path must not be separated by "/" or "\", but by ".".
  • The path is relative to the Python directory of the server installation,
  • It is recommended to store the module sub-class in the "ppms.module_subclasses" directory.

DI058216 Translated

Here you can indicate whether a module has been translated completely or not.

Values

  • - the module has been translated completely
  • - the module has not been translated yet or has only been translated incompletely

Module print parameters. In this field you can define the left margin.

Details

  • Default setting: 100 = 1 cm

DI059310 Margin: right

Module print parameters. In this field you can define the right margin.

Details

  • Default setting: 100 = 1 cm

DI059311 Margin: top

Module print parameters. In this field you can define the top margin.

Details

  • Default setting: 100 = 1 cm

DI059312 Margin: bottom

Module print parameters. In this field you can define the bottom margin.

Details

  • Default setting: 100 = 1 cm

DI002276 Use frequency in work areas

In this field, the use frequency of a module in work areas is displayed.

DI063176 MV creation

This parameter serves to turn the creation, editing, and deletion of individual module variants on and off for individual modules.

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.

See also: General Information on Module Variants (in the Introduction and Program Operation help area), Change Module Variants via Customizer

DI060098 Show title bar

Defines whether the dialog module is displayed with or without title bar.

DI060069 Dialog can be moved

Defines whether the dialog module can be moved and resized using the mouse. This parameter can only be activated if Show title bar is activated.

DI060068 Dialog position

Defines the positioning of the dialog module.

DI062203 Button x (close)

Defines whether the x for closing is displayed in the title bar

DI060067 Click outside → Close

Defines whether the dialog module is closed when clicking outside the dialog module. This parameter can only be activated if Show title bar is activated.

DI064038 Dialog height

Defines the height of a dialog module in tenths of a millimeter.

Details

  • If only the height or width is specified, the other value is calculated based on the module content (displayed data fields or data).
  • If both values are not defined, both are calculated based on the module content (displayed data fields or data).

DI064039 Dialog width

Defines the width of a dialog module in tenths of a millimeter.

Details

  • If only the height or width is specified, the other value is calculated based on the module content (displayed data fields or data).
  • If both values are not defined, both are calculated based on the module content (displayed data fields or data).

DI066353 UF action

Specifies how often the module is used as an action module.

DI066354 UF listbox

Specifies how often the module is used as a listbox module.

DI066355 UF submodule

Specifies how often the module is used as a submodule.

DI066356 UF menu item

Specifies how often the module is used as a menu item module.

DI066357 UF user menu

Specifies how often the module is used in user menus.

DI066358 UF interface

Specifies how often the module is used as source/pool/target module in PLANTA link.

DI066359 UF startup

Specifies how often the module is used as a startup module.

DI066367 UF global settings

Specifies how often the module is used in Global Settings.

DI066370 UF skin

Specifies how often the module is used in the skin.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.