Ignore:
Timestamp:
Dec 16, 2009, 2:29:50 PM (13 years ago)
Author:
Nicklas Nordborg
Message:

Fixes #1437: Base1PluginExecuter should store 'value' instead of 'key' for enumerated parameters

Note that this fix only affects jobs that have been executed after this fix has been installed. Existing jobs will still store (and display) the 'key' values.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/src/docbook/appendix/incompatible.xml

    r5060 r5204  
    4343    </para>
    4444  </note>
     45 
     46  <sect1 id="appendix.incompatible.2.15">
     47    <title>BASE 2.15 release</title>
     48
     49    <bridgehead>
     50      Base1PluginExecuter and enumerated parameters
     51    </bridgehead>
     52   
     53    <para>
     54      Enumerated parameters as handled by the Base1PluginExecuter consists
     55      of key/value pairs, for example 0=No, 1=Yes. The 'value' is what the user
     56      sees in the GUI while running jobs and the 'key' is what is sent to
     57      the plug-in in the parameter file. Starting with BASE 2.15 the 'value'
     58      is saved in the database instead of the 'key'. At runtime, a reverse
     59      lookup is used to convert the 'value' into the 'key' that is written
     60      to the parameters file. <emphasis>The reverse lookup only works
     61      if all values are unique.</emphasis> BASE will check for this at
     62      configuration time and throw an exception if this is not the
     63      case. To solve this problem the plug-in should be reconfigured.
     64    </para>
     65   
     66  </sect1>
    4567 
    4668  <sect1 id="appendix.incompatible.2.13">
Note: See TracChangeset for help on using the changeset viewer.