The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.
TWiki> CurrentEN Web>PLANTALinkDocumentation>PLANTALinkDataFields>DT560InterfaceConfiguration

DT560 Interface Configuration New from S 39.5.4

DI062638 UUID

Universally Unique Identifier of the interface configuration (primary key)

From DB 39.5.9

Modifiable

From DB 39.5.7

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

Up to DB 39.5.6

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

DI062738 Name

Name of the interface configuration

From DB 39.5.9

Modifiable

From DB 39.5.7

Modifiable
  • in the Archive and Configuration modules,
  • provided that the modifying user possesses the required rights

Up to DB 39.5.6

Modifiable
  • in the Archive and Configuration modules,
  • provided that the modifying user possesses the required rights

DI062821 Transaction type

ID of the transaction type

DI062823 Transaction type name

Name of the transaction type

Values

From DB 39.5.8

  • Load data from source to target via pool NEW
  • Load data from source to pool NEW
  • Load data from pool to target.
  • Load data from source to target.

Up to DB 39.5.8

  • Load data from source to pool NEW
  • Load data from pool to target.
  • Load data from source to target.

    • Modifiable

    From DB 39.5.7

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

    Up to DB 39.5.7

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

    • Note

    • In "Load data from source via pool to target", transfer to the target is not carried out when there have already been problems when importing to the pool. E.g. when 5 of 1000 records which are to be loaded from source via pool to target fail when trying to import to the pool, the remaining 995 are not written in the target.

    DI062775 Copy of: name

    Name of the configuration from which was copied

    DI062770 Copied from

    UUID of the configuration from which was copied

    DI062769 Template

    Checkbox with the help of which you can define whether the configuration is to be used as a template

    Modifiable

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

    DI062773 Pool module name

    Name of the module in which the transfer data is temporarily stored

    DI062774 Target module name

    Name of the module to which data is transferred

    DI062771 Copied on

    Date on which this configuration was copied

    From DB 39.5.9

    DI062768 Completed

    Checkbox with which you can indicate whether the configuration has been completed due to the configuration data having been transferred successfully or the configuration having been set to "Completed" manually. The completed configurations can be viewed via the Completed Configurations module.

    Modifiable

    Note

    • This parameter is automatically activated after the transaction has been carried out successfully, or you can activate it manually.

    From DB 39.5.8

    DI062768 Transfer

    Checkbox with which you can mark whether the configuration has been transferred and is therefore completed. This configuration is therefore archived and can only be viewed via the Archive module.

    Modifiable

    Note

    • This parameter is automatically activated after the transaction has been carried out successfully, or you can activate it manually.

    From DB 39.5.7

    DI062768 Transfer

    Checkbox with which you can mark whether the configuration has been transferred and is therefore completed. This configuration is thus archived and can only be looked at via the Archive module.

    Modifiable

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

    Note

    • This parameter is automatically activated after the transaction has been carried out successfully, or you can activate it manually.

    Up to DB 39.5.6

    DI062768 Transfer

    Checkbox with which you can mark whether the configuration has been transferred and is therefore completed. This configuration is therefore archived and can only be viewed via the Archive module.

    Modifiable

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

    Note

    • This parameter is automatically activated after the transaction has been carried out successfully, or you can activate it manually.

    DI062625 Target module

    ID of the module to which data is transferred

    Modifiable

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

    From DB 39.5.8

    Note
    • Only existing module IDs can be entered.
    • NEW A listbox has been added on the data field which
      • shows the modules edited within the last 30 days.
      • shows the Reusable modules area in which the modules that can be used in several interfaces are displayed, e.g. module 009C7H which is used for CSV transfers.
    • NEW To extend a listbox, the required module is assigned to the 01100195 "PLANTA link: reusable modules" work area.

    New from S 39.5.7

    Note
    • Only existing module IDs can be entered.

    DI062623 Copy from

    ID of the configuration from which was copied

    DI062624 Source module

    ID of the module from which data is transferred

    From DB 39.5.9

    Modifiable

    From DB 39.5.7

    Modifiable
    • in the Archive and Configuration modules,
    • provided that the modifying user possesses the required rights

    Up to DB 39.5.6

    Modifiable
    • in the Archive and Configuration modules,
    • provided that the modifying user possesses the required rights

    From DB 39.5.8

    Note
    • Only existing module IDs can be entered.
    • NEW A listbox has been added on the data field which
      • shows the modules edited within the last 30 days.
      • shows the Reusable modules area in which the modules that can be used in several interfaces are displayed, e.g. module 009C7H which is used for CSV transfers.
    • NEW To extend a listbox, the required module is assigned to the 01100195 "PLANTA link: reusable modules" work area.

    New from S 39.5.7

    Note
    • Only existing module IDs can be entered.

    DI062811 Source module subclass

    Python module subclass of the source module

    New from S 39.5.7

    Notes
    • If the Python submodule class stored in the module is invalid, this is indicated by a red frame. The valid Python module subclasses of the PLANTA link can be found here.

    DI062809 Pool module subclass

    Python module subclass of the pool module

    New from S 39.5.7

    Notes
    • If the Python submodule class stored in the module is invalid, this is indicated by a red frame. The valid Python module subclasses of the PLANTA link can be found here.

    DI062772 Source module name

    Name of the module from which data is transferred

    DI062636 Pool table

    Number of the pool table

    Modifiable

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

    New from S 39.5.8

    Note
    • A UUID column must be contained as a primary key in order to be able to use this table in the interface.

    DI062767 Pool module

    ID of the pool module

    Modifiable

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

    From DB 39.5.8

    Note
    • Only existing module IDs can be entered.
    • NEW A listbox has been added on the data field which
      • shows the modules edited within the last 30 days.
      • shows the Reusable modules area in which the modules that can be used in several interfaces are displayed, e.g. module 009C7H which is used for CSV transfers.
    • NEW To extend a listbox, the required module is assigned to the 01100195 "PLANTA link: reusable modules" work area.

    New from S 39.5.7

    Note
    • Only existing module IDs can be entered.

    From S 39.5.9

    DI062826 Completed on

    Point in time at which this configuration was transferred successfully (= completed) or the Completed checkbox was activated manually.

    From S 39.5.7

    DI062826 Transferred on

    Point in time at which this configuration was transferred successfully (= completed) or the Copy checkbox has been activated manually

    Up to S 39.5.7

    DI062826 Transferred on

    Date on which this configuration was transferred (completed) successfullyPoint in time at which this configuration was transferred successfully ( completed) or the Completed checkbox was activated manually

    DI062810 Target module subclass

    Python module subclass of the target module

    New from S 39.5.7

    Notes
    • If the Python submodule class stored in the module is invalid, this is indicated by a red frame. The valid Python module subclasses of the PLANTA link can be found here.

    DI062803 Log level name

    Name of the log level. Log level means the degree of detail of the log entry.

    Modifiable

    From DB 39.5.7

    Up to DB 39.5.7

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

    • Values

    • Debugging info
      • This value is only visible for customizers (Customizer rights = Checked)
      • All log messages, as well as function names, line numbers, and module names are written into the log file.
      • If an error occurs, a complete stack trace is written in the log
    • Information
      • Contains useful information that may help you to comprehend the interface.
    • Warning
      • Only writes warnings and errors in the log.

    Note

    • The displayed log messages always contain the current level including all lower levels.
    • The Debugging info value generates a huge amount of data and is intended for debugging incorrect interfaces.
    • If an interface is switched to productive, we recommend that you set the log level of the template to "warning".

    New from DB 39.5.8

    DI063846 Log type name

    Here you can define where the log entries are written; in a file or in the PLANTA data table.

    Values

    • PLANTA table
    • File

    Modifiable

    When defining the log type you have to consider that writing log entries in a log file on the server is substantially more performant than writing in a PLANTA table, then again, the log entries written in PLANTA can be searched more comfortably in the Logging module designed for this purpose. The log file can be found in the log folder of the PLANTA server. The name is composed of the name of the interface and the UUID.

    DI062801 Pool table name

    Name of the pool table

    DI062820 Mapping type name

    Auxiliary field for generating mappings

    Values

    • Import: The data areas of the target module are viewed and source + target mapping elements are created with possible associated pool mapping elements.
    • Export: The data areas of the source module are viewed and source + target mapping elements are created with possible associated pool mapping elements.
    • Python ID: The source and target module data areas are viewed. If the Python ID matches, a source + target mapping element is created with possibly associated pool mapping elements.
    • Position: The target module data areas are viewed. A mapping between the first DI in the source module and the first one in the target module is created, etc.

    New from DB 39.5.7

    DI0663667 Hidden

    This parameter defines whether the configuration in the configuration listbox of the Configuration module is to be displayed.

    New from DB 39.5.7

    DI063666 Locked

    This parameter defines whether the configuration is to be locked and can therefore not be run or used as a copy source.

    New from DB 39.5.9

    DI064050 Cancelation limit (seconds)

    With this parameter you can define the maximum duration of an interface transfer is determined in seconds. If the duration of the transaction reaches the value defined in the Cancelation limit (seconds) field, the transaction is canceled.

    New from DB 39.5.9

    DI064051 Cancelation limit (%)

    With this parameter you can define at which value the interface transfer is canceled. As soon as the number of non-transferred records in the interface transfer reaches the percentage value of the Cancelation limit (%) field, the transaction is canceled.

             PLANTA project







     
    • Suche in Topic-Namen

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