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

Modules MOD000855

Access path

From DB 39.5.7

  • Customizer Module Customizer Modules Modules
  • Menu items: Tools Edit activated module (F9) Confirm the Load customizing for the activated module? dialog message Modules

Up to DB 39.5.7

  • Customizer Module Customizer Modules Global Settings
  • Menu items: Tools Edit current module (F9) Confirm the Load customizing for the activated module? dialog message Modules
  • In this module it is possible to

    See also: Module Customizing Tutorial Level 1

    Module Header

    From DB 39.5.15

    Module parameters (in the module header)
    • In the module header, different important module parameters can be edited.
      • Further module parameters can be looked at and edited via the Open further module parameters button.
    • NEW In the Standard MV or User MV fields, the number of standard or user module variants of the respective module is displayed.
      • Via the links on the fields, the respective module variants can be looked at in the Module Variants module.
    • In the Work area field, the number of work areas to which the module is assigned is displayed.
      • Via the link on the field, the work areas in the Use module variant can be looked at.

    Up to DB 39.5.15

    Module parameters (in the module header)
    • In the module header, different important module parameters can be edited.
      • Further module parameters can be looked at and edited via the Open further module parameters button.
    • In the Work area field, the number of work areas to which the module is assigned is displayed.
      • Via the link on the field, the work areas in the Use module variant can be looked at.

    Buttons (in the module header)

    From DB 39.5.15

    • Via Start module, the module which is displayed here in the customizer can be opened in the user view.
    • Via Set data area positions, the positions and parent areas of the data areas are automatically set in accordance with the previously created structure.
    • Via Open module variant, the Module Variants module is opened. Here, the already existing variants of the selected module can be displayed and edited.
    • Via Display other module parameters, you can open the Other Module Parameters module.
    • Via Edit Python macro, the Python Macros module is opened, in which the Python macro of the module (if existing) is displayed. If there is no Python macro in the module yet, click on the Insert template button which causes a template macro to be copied in automatically. For the template, please click here.
    • Via Edit Python macro in editor, an editor is opened.
      • Here, the behavior equates to that of the Edit Python macro button:
        • If a Python macro already exists, it will be displayed in the editor.
        • If there is no Python macro yet, click on the Insert template button to insert the default macro. For the further approach, see above.
        • If no Python editor is stored in the Global Settings, the following message is displayed when you click on the button: Please specify an editor!
        • If a wrong editor is specified, the Error executing python script: The System cannot find the specified file message is displayed.
    See also: Example for Python Macro Customizing in Module Workflow Level 1, Python API

    From DB 39.5.13

    • Via Start module, the module which is displayed here in the customizer can be opened in the application.
    • Via Set data area positions, the positions and parent areas of the data areas are automatically set in accordance with the previously created structure.
    • Via Open module variant, the Module Variants module is opened. Here, the already existing variants of the selected module can be displayed and edited.
    • Via Display other module parameters, you can open the Other Module Parameters module.
    • Via Edit Python macro, the Python Macros module is opened, in which the Python macro of the module (if existing) is displayed. If there is no Python macro in the module yet, NEW click on the Insert template button which causes a template macro to be copied in automatically. For the template macro, please click here.
    • Via Edit Python macro in editor, an editor is opened.
      • Here, the behavior equates to that of the Edit Python macro button:
        • If a Python macro already exists, it will be displayed in the editor.
        • If there is no Python macro yet, NEW click on the Insert template button to insert the default macro. For the further approach, see above.
        • If no Python editor is stored in the Global Settings, the following message is displayed when you click on the button: Please specify an editor!
        • If a wrong editor is specified, the Error executing python script: The System cannot find the specified file message is displayed.
    See also: Example for Python Macro Customizing in Module Workflow Level 1, Python API

    From DB 39.5.11

    • Via Start module, the module which is displayed here in the customizer can be opened in the application.
    • NEW Via Set data area positions, the positions and parent areas of the data areas are automatically set in accordance with the previously created structure.
    • Via Open module variant, the Module Variants module is opened. Here, the already existing variants of the selected module can be displayed and edited.
    • Via Display other module parameters, you can open the Other Module Parameters module.
    • Via Edit macro, the Python Macros modules are opened, in which the Python macro of the module (if there is any) is displayed.
    • If there is no Python macro in the module yet, the following message will be displayed: No macro text available: Do you want to insert a template? If the message is answered with Yes, a macro template will be copied in automatically: For the template macro, please click here.
    • Via Edit Python macro, an editor will be opened.
      • Here, the behavior equates to that of the Edit macro button:
        • If a Python macro already exists, it will be displayed in the editor.
        • If there is no Python macro in the module yet, the message mentioned above will be displayed. For the further approach, see above.
        • If no Python editor is entered and saved in the Global Settings, the following message appears when you click on the button: Please specify an editor!
        • If a wrong editor is specified, the Error executing python script: The System cannot find the specified file message is displayed.
    See also: Example for Python Macro Customizing in Module Workflow Level 1, Python API

    From DB 39.5.9

    • Via Start module, the module which is displayed here in the customizer can be opened in the application.
    • Via Open module variant, the Module Variants module is opened. Here, the already existing variants of the selected module can be displayed and edited.
    • Via Display other module parameters, you can open the Other Module Parameters module.
    • Via Edit macro, the Python Macros and Macros module is opened, in which the Python macro of the module (if existing) is displayed.
      • If there is no Python macro in the module yet, the following message will be displayed: No macro text available: Do you want to insert a template? If the message is answered with Yes, a macro template will be copied in automatically: For the template macro, please click here.
    • Via Edit Python macro, an editor will be opened.
      • Here, the behavior equates to that of the Edit macro button:
        • If a Python macro already exists, it will be displayed in the editor.
        • If there is no Python macro in the module yet, the message mentioned above will be displayed. For the further approach, see above.
        • If no Python editor is entered and saved in the Global Settings, the following message appears when you click on the button: Please specify an editor!
        • If a wrong editor is specified, the Error executing python script: The System cannot find the specified file message is displayed.
    See also: Example for Python Macro Customizing in Module Workflow Level 1, Python API

    From DB 39.5.4

    • Via Start module, the module which is displayed here in the customizer can be opened in the application.
    • Via Open module variant, the Module Variants module is opened. Here, the already existing variants of the selected module can be displayed and edited.
    • Via Display other module parameters, you can open the Other Module Parameters module.
    • Via Edit macro, the Python Macros and Macros modules are opened, in which the Python macro of the module (if existing) or macro lines are displayed.
      • NEW If there is no Python macro in the module yet, the following message is displayed: No macro text available: Do you want to insert a template? If the message is answered with Yes, a macro template will be copied in automatically: For the template macro, please click here.
    • Via Edit Python macro, an editor will be opened.
      • Here, the behavior equates to that of the Edit macro button:
        • If a Python macro already exists, it will be displayed in the editor.
        • If there is no Python macro in the module yet, the message mentioned above will be displayed. For the further approach, see above.
        • If no Python editor is entered and saved in the Global Settings, the following message appears when you click on the button: Please specify an editor!
        • If a wrong editor is specified, the Error executing python script: The System cannot find the specified file message is displayed.
    See also: Example for Python Macro Customizing in Module Workflow Level 1, Python API

    Up to DB 39.5.4

    • Via Start module, the module which is displayed here in the customizer can be opened in the application.
    • Via Open module variant, the Module Variants module is opened. Here, the already existing variants of the current module can be displayed and edited.
    • Via Display other module parameters, you can open the Other Module Parameters module.
    • Via Edit macro, the Python Macros and Macros modules are opened, in which the Python macro of the module (if existing) or macro lines are displayed.
      • If there is no Python macro in the module yet, you can create a new macro.
    • Via Edit Python macro, an editor will be opened which is stored in the Global Settings module.
      • If the module has
        • a Python macro, it will be displayed in the editor and can be edited if required.
        • has no Python macro yet, the following template will automatically be copied.
    #MacroTemplate
    
    mod_obj = ppms.get_target_module()
    
    def on_load():
        pass
    
    def on_initial_focus():
        mod_obj.menu(11)
    
    def on_focus():
        pass
    
    def on_reset():
        on_initial_focus()
    
    def on_before_mv_switch(old_mv, new_mv):
        pass
    
    def on_after_mv_switch(old_mv, new_mv):
        pass

    • If no Python editor is entered and saved in the Global Settings, the following message appears when you click on the button: Please specify an editor!
    • If a wrong editor is specified, the Error executing python script: The System cannot find the specified file message is displayed.
    See also: Example for Python Macro Customizing in Module Workflow Level 1, Python API

    Context Menus

    Context menu on the module

    From DB 39.5.15

    • By right-clicking on the module button, the following actions can be carried out:
      • Edit the Python module subclass via the context menu command of the same name.
        • If a Python module subclass has been selected from the listbox on the field of the same name, it is opened in the corresponding editor.
        • If no Python module subclass has been selected, you will be asked to name and thus create a new subclass.
      • Via the context menu command of the same name, assign the module in the Assign Work Area module to a work area.
      • The Macros module in which the required macro lines can be edited is opened via the Edit macro lines context menu command.
      • NEW The Check use entry provides a means to check the use of the module.
        • When you select the command, a dialog message will be displayed asking you to select the area to be checked for use.
        • Afterwards, the respective data is opened in the Object Use module.

    From DB 39.5.9

  • By right-clicking on the module button, the following actions can be carried out:
    • Via the context menu command of the same name, assign the module in the Assign Work Area module to a work area.
    • Edit the Python module subclass via the context menu command of the same name.
      • If a Python module subclass has been selected from the listbox on the field of the same name, it is opened in the corresponding editor.
      • If no Python module subclass has been selected, you will be asked to name and thus create a new subclass.
    • NEW The Macros module in which the required macro lines can be edited the Macros module is opened via the Edit macro lines context menu command.
  • Up to DB 39.5.9

  • By right-clicking on the module button, the following actions can be carried out:
    • Via the context menu command of the same name, assign the module in the Assign Work Area module to a work area.
    • Edit the Python module subclass via the context menu command of the same name.
      • If a python module subclass has been selected on the field of the same name, it is opened in the corresponding editor.
      • If no Python subclass has been selected, you will be asked to name and therefore create a new subclass.
  • Context menu on a data area

    • By right-clicking on the required data area and selecting the corresponding command, you can
      • open and edit the corresponding data areas in the Data Areas module.
        • If several data areas are to be edited at once,
          • mark the appropriate data areas,
          • right-click on one of the marked data areas,
          • select Edit data area.
          • All marked areas are opened in the Data Areas module where they can be edited.
      • have a look at the data area usage in the Data Area Use module of the same name.
        • The Data Area Use module can also be opened via the link on the VH field.

    Note

    From DB 39.5.6

    • If you open the listbox on the MOD field in the empty Modules module, all modules and macros that have been created within the last 30 days, or for which changes have been made to the following areas, are displayed: header data (DT405), NEW submodule assignments (DT404), NEW data area assignments (DT406), NEW data areas (DT410) and NEW data fields (DT411).

    Up to DB 39.5.6

  • If you open the listbox on the MOD field in the empty Modules module, all modules and macros that have been created within the last 30 days, or for which changes have been made to the following areas, are displayed:
    • This does not apply to changes made to submodules or data area assignments.
  • Module Variants

    Display behavior Contains the parameters that control the display behavior of the data areas in the module
    Area behavior Contains the parameters that control the area behavior of the data areas in the module
    Data field search After selecting this module variant, the module is empty. Via the Filter Criteria module, you can search for attributes on data field level.
    Layout Contains the parameters that control the data area layout in the module
    Macro Displays the Python macro
    Module DF Additionally displays the data areas and data fields below the data area assignments
    Parameter Displays the data fields from the Other Module Parameters module
    Heading/print Displays the parameters for headings and print settings
    Connections Displays the parameters for the connections
    Use Displays the work areas/roles to which the module has been assigned

             PLANTA project









     
    • Suche in Topic-Namen

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