Systems MOD009CJK New from DB 39.5.7

Information

• In the Systems module, you have the chance to create systems in order to define the interface parameters system specifically.
• All systems created in this module are displayed in the Interface Parameters module, in which both default interface parameters and the system specific parameters of the respective interface can be defined.
• When carrying out a configuration, the parameters of the active system are used. If no system is active, the default parameters of the interface are used.
• In order for a system to be marked as an active system, it is checked whether all conditions defined in the system are fulfilled, i.e. whether the values of the Condition is fulfilled and Expected parameters are the same for all check classes of the system.
  • In the Systems module, the check result is visible after reselection (F7), otherwise the conditions are checked when running the configuration in order to identify an active system securely and use its parameters upon execution.
    • In the Standard, PLANTA provides some readily predefined check classes. For this purpose, see interface library. Furthermore, individual check classes can be created. For more information on this, see Customize Individual System Check Classes.

Procedure

• If no systems have been defined yet, click on the Insert button.
• Select the required system from the listbox.
• Insert a system condition record by right-clicking on the system record and selecting the System condition command from the context menu.
• Select the required check class from the listbox in the Check class field.
• Depending on the selected class, the Current value field is filled with the respective value of the current system.
  • If a class is not found, it is displayed in the Current value field as well.
• Enter the value that is to apply to the required system in the Expected value field.
  • This value is checked against the Current value immediately after input and clicking out of the field and the result is displayed in the Condition is fulfilled field
    • Condition is fulfilled = yes: the values match.
    • Condition is fulfilled = no: the values do not match.
• Define what the expected result is to be - the fulfilled or unfulfilled condition - by activating/deactivating the checkbox in the Expected field,
  • This parameter enables the user to negate the fulfillment of the condition and hence define the negative check result as expected result.
• Define further systems in the same way if necessary.
• After saving and reselection, the conditions are checked, i.e. whether the values of the Condition is fulfilled and Expected parameters are the same for all check classes of the respective system, and the system which satisfies these conditions is marked as an active system.

Technical details

• If individual classes are used, they must be included in the check.py file under /py/customer/ppms/interface/parameter/conditional, and the PLANTA service must be restarted.
  • The BaseConditional class here defines for the interface, how individual subclasses are to be implemented.
  • An example, how an individual class is to be customized, can be found here.