===============================================================================
41. About Version 5.0
=====================

41.1 Behavior changes
---------------------

- OrgaTEX version 5.0 requires a new hardlock module where module release
  "OrgaTEX 5.0" is included. The "dongle" of OrgaTEX 4.x can NOT be used !
- The module releases "Support for foreign controller" and "Support for not
  connected machines" do NO longer allow an unlimited number of these kind of
  machines. These releases in the hardlock are only the basic requirement for
  using the feature. The possible number of these machines is limited by a code
  number which is generated by SETEX.
- Language "Portuguese (Brasilan)" is NO more supported (existing installations
  using Brasilan are automatically moved to normal Portuguese). Nevertheless
  customer specific Crystal Report printouts (for SETEX "Production recipe",
  "Batch queuing list" and "Product weighing label") must be manually renamed
  before or after the update (e.g. RCP702XB.RPT -> RCP702XP.RPT).
- Batch parameter 20 is NO more automatically set by the recipe calculation
  to the tank volume of a Foulard machine. To activate this feature (that was
  used very seldom), you have to put a line "Parameter20IsPrepVolume=1" in
  section "RECIPE" in file "ORATEX.INI" (located in OrgaTEX binaries folder).
- The volume of a Foulard trough is NO more automatically added by the recipe
  calculation. To activate this feature (that was often used for Foulards with
  one tank), you have to check it manually in "Machine Configuration".
- Recordset functions "OpenResultSet"/"Execute" of the "Formula Editor" language
  have now an additional 3rd parameter "Use connection pool". Existing formulas
  using these functions must be manually adapted ! The parameter should be
  "true" for real SQL data sources (e.g. "Pervasive", "SQL-Server", "Sybase")
  and "false" for file based data sources (e.g. Excel sheets, CSV files, ...).
- Errors in batch formula calculation will from now on result in an error during
  program generation. If this check is not desired it can be switched off (see
  "System Configuration") and then the controller tries to do the calculation
  again as before (but most probably with the same error result).
 

41.2 Changes and Enhancements
-----------------------------

41.2.1 Miscellaneous
--------------------

- NEW: Revised document "OrgaTEX Installation on Windows 2003 Server"
  in DOC\ENGLISH\OT2003E.PDF of installation CD.
- NEW: Revised documentation "OrgaTEX Integration Database" in file
  "IntegDB_2_28.PDF" in subdirectory DOC of the installation CD.
- NEW: Microsoft File & Print Services for NetWare (FPNW) in subdirectory FPNW
  of the installtion CD (downloaded from Microsoft free download area).
 

41.2.2 Main installation (Server part)
--------------------------------------

- FIX: Language "Portuguese (Brasilan)" is NO more supported (existing install-
  ations using Brasilan are automatically moved to normal Portuguese). Neverthe-
  less customer specific Crystal Report printouts (for "Production recipe",
  "Batch queuing list" and "Product weighing label") must be manually renamed
  before or after the update (e.g. RCP702XB.RPT -> RCP702XP.RPT).
 

41.2.3 Workstation installation
-------------------------------

- NEW: Support for Windows Vista.
- NEW: Better support for restricted user (already included in the installation
  and no executing of a separate batch needed as before).
- NEW: Due to support for Pervasive SQL 9 and Pervasive Backup Agent (see next
  chapter) the Btrieve 6.15 local engine settings in registry are adjusted by
  workstation installation. So when using one of these 2 environments the work-
  station installation must be done even for an update (at least at the server).
- NEW: New version of MFC/C/C++ runtime DLLs (for internal improvements).
 

41.2.4 Miscellaneous concerning all OrgaTEX applications
--------------------------------------------------------

Changes concerning databases:
- - - - - - - - - - - - - - -

- NEW: Support for Pervasive SQL 9 (as internal OrgaTEX data source as well as
  for the integration database).
- NEW: Support for Pervasive Backup Agent. To enable this, you must insert an
  entry OPEN_CRITICAL_BRTV_FILES_WITH_LOCAL_ENGINE=1 in section [BTRIEVE] in
  file ORGATEX.INI in OrgaTEX binaries directory (e.g. F:\OT\BIN\ORGATEX.INI).
 
Changes concerning list boxes with modifiable column widths:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 
- NEW: Standard keyboard shortcuts "Ctrl+A" (Select all), "Ctrl+C" (Copy) and
  "Ctrl+Ins" (Copy) can now be used.
- FIX: Mouse double click didn't work in single selection lists if a tool tip
  (little yellow bubble window) was shown and the double click was done while
  the mouse cursor was over the tool tip.
- FIX: Double click on divider between column headings was supposed to set the
  optimal width (like in Windows), but set by mistake a very small width.
- FIX: Selection in single selection list is now always in the visible area of
  the list (the same way how simple lists of Windows do it).
- FIX: Warning "Margins are set out of the printable area" avoided when printing
  was switched to landscape mode or paper size was changed.

Changes concerning controller:
- - - - - - - - - - - - - - - -

- NEW: Support for Windows CE based conti controller 848TC.
- NEW: The applications use now for Windows CE disconti controllers (e.g. 757)
  the controller function icons and group/resource icons (instead of the host
  icons) because they usually look better (because of possible 16 million
  colors [TrueColor] instead of 16 colors [Standard VGA]).
- FIX: Up to now only at maximum 20 characters were put into comment lines for
  program headers even though 30 are now possible on a Windows CE controller
  (e.g. 757, 626).
- FIX: If the SECOM TCP/IP Gateway service was used, there was a Windows General
  Protection Fault in the client part of the gateway under some certain error
  conditions (e.g. if Microsoft DOT.NET 2.0 framework was used and by mistake
  an empty name was set as computer with SECOM Gateway service running).

Changes concerning other things:
- - - - - - - - - - - - - - - - -

- NEW: It's now possible to give back the ownership of a document (for documents
  in "Online State", "Batch Scheduler", "Batch Report, etc.). This could be
  useful because under some situations an application is started without OrgaTEX
  login and an owner would make problems (e.g. "Batch Scheduler" with "/start"
  command line option).
- FIX: If an online help file is not available in the OrgaTEX language, auto-
  matically the English online help is shown if it is available.
 

41.2.5 Online State
-------------------

- NEW: "Actions buttons" and "User keys" (to change PLC values or set values)
  implemented for process pictures.
- NEW: Intervention mode for conti process pictures implemented where you can
  modify set values and double words.
- NEW: Process picture field type "Frame" implemented (only for Windows CE
  controllers e.g. 757, 626).
- NEW: Reading bitmaps for process pictures optimized.
- NEW: If a correction treatment is appended, the functions "Addition Start" and
  "Addition End" are automatically added if they are not contained in the treat-
  ment. By this feature, it's possible to use exactly the same treatment for
  the normal part of the process and the correction part.
- NEW: Better messages for "Show offline reason" e.g. for cases when
  - SECOM Gateway client doesn't work due to problems with the Windows registry.
  - Direct SPX/IPX communication fails (when no Gateway client is used).
  - Controller is shown offline due to old time of .CST [controller state] file.
- NEW: Checking state of controllers ("Polling") is now done in the background
  so that the application is no more "blocked" during the "polling" (which was
  formerly sometimes a big problem e.g. editing a program in "Online Editor"
  was sometimes difficult because of the annoying polling).
- NEW: New menu entry for confirming "voice alarms" (alarms for which a sound
  file is played). Before there was only a - mostly unknown - keyboard shortcut.
- NEW: Selecting a batch in window "Batch list" is possible in more situations
  than before. Before it was only possible for batches with state "Created". Now
  it's also possible for "Stopped" and already "Selected" ones. This could be
  e.g. useful if the controller has lost the batch state due to a SECOM software
  update and therefore the already once selected batch has to be selected again.
- NEW: Opening view for "Show/Edit Current Program" & "Start on Step" optimized.
- NEW: Steps, which still have the flag "Active" in PLC, although they also have
  the flag "Confirmed" there, are now shown with a gray light bulb. Before there
  was a yellow light bulb for active steps (no matter if confirmed or not).
- FIX: If a lot of parallel functions were changed with "Step Jump in Run mode",
  then the actual changes on the controller were sometimes shown a little bit
  late. This is improved now.
- FIX: "Edit Current Program" and "Start On Step" optimized. The PRG file for
  the controller was generated twice instead of once (respectively once instead
  of none).
- FIX: Refreshing view for "Show/Edit Current Program" and "Start on Step"
  optimized (the PRG is now only requested from the controller, if it's seen in
  the controller state, that something remarkable has changed).
- FIX: When deleting active steps in "Online Editor", the grid in the display
  in the window wasn't deleted.
- FIX: When inserting steps behind active steps in "Online Editor", by mistake
  the yellow light bulb was copied for parallel functions with the attribute
  "Copied" (but it was just a problem in the display in the window).
- FIX: If there was a time difference (outside the limits) between PC and SECOM
  (and this was displayed) and then the time was o.k. again and then there was
  again a time difference, then it was by mistake not shown a 2nd time (it was
  only shown if the application was restarted in the meantime).
- FIX: If there was an error regarding communication between SECOM and PLC (and
  this was displayed) and then the communication was o.k. again and then there
  was again an error, then it was by mistake not shown a 2nd time (it was only
  shown if the application was restarted in the meantime).
- FIX: In dialog windows "Start on step (without Online Editor)" and "Step Info"
  the left list box with the resource icons wasn't scrolled if the scrolling was
  done using the mouse wheel.
- FIX: In the following cases the window view and the list box in it (with the
  separate lines for the machines) were shifted against each other horizontally
  (so that there was a white space on the left and some columns missing on the
  right) if the window view was scrolled to the right and one of the following
  things happened:
  - The size of the window frame for the view was changed.
  - Each time the number of the machines in the list box changed (e.g. by using
    dialog "Machine Setup" or changing selection filters or a machine state
    used in selection filters changed).
  - Pressing "Cancel" in dialog "Setup columns".
- FIX: When using selection filters, the currently highlighted machine could
  change automatically to another due to "polling" (this was sometimes strange
  because the highlighted machine should normally change only by user action).
- FIX: If a batch parameter/info word wasn't configured for a specific machine
  on the one hand, but was selected as column (because it was configured in the
  default configuration on the other hand), then drawing the machine list was
  extremely slow.
- FIX: Reading/displaying data in machine list for columns of type "Alarm name",
  "Alarm text", "Function name", "Machine group name", "Batch parameter", "Info
  word", "Procedure name", "Program name" and "Treatment name" optimized.
- FIX: "Start on step" for parallel lines/"Step Jump" did by mistake only work
  for controllers, which were online at the moment when the document was opened.
- FIX: Batch related time values are no longer shown in process picture view
  if currently no batch is running on the controller (up to now the current time
  was shown for absolute time values which was a little bit annoying).
- FIX: In TypeConf Tool there are 2 ways to define a scaling (used e.g. for
  values shown in process pictures): one with 2 values for "Factor/Offset", one
  with 4 values for "Displayed/Measured". OrgaTEX now uses always "Factor/
  Offset" (even if this is shown disabled in TypeConf Tool) to avoid problems
  of TypeConf Tool (that wrong values for "Displayed/Measured" are stored).
- FIX: Under bad timing circumstances, there could have been texts in ERROR.LOG
  on controller, that it couldn't write file e.g. F:\OT\MACHINES\MA01\BATCH.TMP
  and in this case, the batch header information for a machine was maybe empty
  or still the one of the former batch even if a new one was started.
- FIX: In theory the sorting of several weighings/dispensings for one product
  could have been randomly in "Extended Recipe Printout" (although this has
  never been seen with any of the supported systems for integration database).
  Now it's guaranteed to be ordered by the time of the individual weighings/
  dispensings.
- FIX: If a production recipe printout for SETEX recipe was exported to WinWord,
  then for blank lines a nonsense text (the current time) was exported.
- FIX: Working with user right "Info" was improved. Formerly some menu items
  were enabled which were not really suitable for the level "Info".
 

41.2.6 Process Diagrams
-----------------------

- NEW: Display of definition of function group times (which function is in what
  function time group).
- NEW: Opening view for "Display Program" optimized.
- FIX: With background colors other than white (e.g. black), the description for
  the scales for digital values was not visible (in TrueColor screen settings).
- FIX: The (left) view with the scales wasn't filled completely with background
  colors other than white (e.g. black).
- FIX: Printing from print preview (by using its tool bar) did work only, if the
  preview was opened from the time/temperature curve view (and not, if e.g. the
  view with the executed functions had the focus - meaning: was the active one).
- FIX: In "Short print" of "Mixed display mode", the digital values were not
  correctly printed. The 2nd digital value was only printed partly on the paper
  and the scale description of digital values were also not printed correctly.
- FIX: Sometimes the lower scrollbar wasn't visible if the window was maximized,
  then "Save Setup" was done and then the next logging file was opened. From now
  on this is corrected and furthermore, the window is automatically maximized if
  it couldn't be opened in the saved size (e.g. because "Save Setup" was done
  from another PC with different screen resolution).
- FIX: The color of the text in the tool bar for operator calls, corrections and
  alarm is now no more always black, but depends on the color defined for the
  event (because e.g. "Black" on "Dark red" for event "Operator call" was very
  hard to read).
- FIX: Several bugs regarding scrolling by mouse wheel or keyboard in dialog
  windows "Step State" and "Show Program (old)" fixed.
- FIX: Wrong display of mouse cursor icon in windows for batch info and
  analogue values corrected.
- FIX: Several optimizations of reading batches in dialog "Batch open".
- FIX: Optimization of reading data for an individual logging curve.
- FIX: If an alarm started before a batch and ended during the batch, then the
  window "Alarm list" showed by mistake the end timestamp as start timestamp.
- FIX: If the logging file of an active batch was shown and the application
  tried to refresh the display in order to show things that were logged after
  the initial reading of the file, then this failed, if there were more than
  32767 records in the logging file. With a logging cycle of 30 seconds, this
  happened after ca. 270 hours run time, with 2 seconds after ca. 18 hours.
- FIX: In theory the sorting of several weighings/dispensings for one product
  could have been randomly in "Extended Recipe Printout" (although this has
  never been seen with any of the supported systems for integration database).
  Now it's guaranteed to be ordered by the time of the individual weighings/
  dispensings.
- FIX: If a production recipe printout for SETEX recipe was exported to WinWord,
  then for blank lines a nonsense text (the current time) was exported.
 

41.2.7 Alarm Monitor
--------------------

- FIX: The waving of the red error flag looked odd if there were several
  documents opened at the same time.
- FIX: Alarm names for alarms on foreign controllers were shown wrong (the short
  name of maximum 20 characters of the TypeConf Tool instead of the up to 80
  characters defined in integration database) in case the machine protocol data
  was stored in an internal OrgaTEX table (and not in the integration database).
 

41.2.8 Batch Scheduler
----------------------

General changes:
- - - - - - - - -

- NEW: If the production calendar of the new structure is used, then up to 10
  shifts are possible per day (even if more than 4 is really strange ;-)
- NEW: The shift colors for the bars can be influenced in file ORGATEX.INI (in
  OrgaTEX binaries directory) in section [OLN420] with entries SHIFT_COLOR_1 ..
  SHIFT_COLOR_10. The value is the RGB value of the color.
- NEW: Up to now only for operator calls the "active" operator call (the last
  one that was started, but not yet ended) was shown (it was shown up to the
  current time). Now this is done also for corrections and offline sections.
  Furthermore the fact, that it's active is also shown in the yellow tool tip.
- NEW: Now the duration of corrections is also shown (formerly only for operator
  calls and offline sections).
- NEW: Batch comment can be shown in yellow bubble information window.
- NEW: Modifications on certain fields of a batch are now allowed also for
  active/finished batches and batches with the state "In preparation":
  - For active/finished ones: comment, date of delivery, production deadline.
  - For ones "In preparation": additionally field "Not start before", batch
    attributes for process and type, flags "Load release" and "Ignore shift
    times" as well as batch progress state.
- NEW: Opening view for "Show actual program" optimized.
- NEW: Checking state of controllers ("Polling") is now done in the background
  so that the application is no more "blocked" during the "polling" (which was
  formerly sometimes a big problem e.g. creating a batch was sometimes difficult
  because of the annoying polling).
- NEW: Selecting a batch in window "Batch list" is possible in more situations
  than before. Before it was only possible for batches with state "Created". Now
  it's also possible for "Stopped" and already "Selected" ones. This could be
  e.g. useful if the controller has lost the batch state due to a SECOM software
  update and therefore the already once selected batch has to be selected again.
- NEW: "Batch queuing list" can be also printed for only the selected batch
  (formerly all batches of one/all machines, eventually only for some days).
  This can be useful, because the actual report for the "Batch queuing list" can
  be easily customized for individual customer needs and so extended batch
  information can be integrated into "Batch Scheduler".
- FIX: Under very, very rare timing conditions, there could have been a Windows
  General Protection Fault, when the yellow bubble information window was shown
  and the list of batches was automatically refreshed by the application.
- FIX: Up to now, when the mouse cursor was moved while it was over a batch,
  there could have been a CPU usage up to 90%. This is optimized so that now the
  CPU usage while moving the mouse is nearly not noticeable.
- FIX: An internal function for retrieving the time for a batch was optimized so
  that simply moving of the batch could no longer lead to 100% CPU usage. By
  this optimization also drawing the batches in the window is noticeably faster.
  (Before you could have seen sometimes how the individual batches were drawn on
  the screen after scrolling or window switching. Now it's simply there).
- FIX: An internal function for retrieving the active batch on a machine was
  optimized which also reduces CPU usage.
- FIX: Reading data for operator calls, offline sections and corrections
  optimized. It's now 3 times up to 20 times faster than before.
- FIX: Reading data for batch ends optimized so that the Pervasive database
  can make better usage of the database cache (the cache is no more flooded with
  eventually not needed data).
- FIX: If the vertical scrollbar wasn't scrolled to the uppermost position and
  another batch was selected, the target cursor on the formerly selected batch
  wasn't completely removed (but it was only a pure display problem).
- FIX: Errors in batch formula calculation will from now on result in an error
  during program generation. If this check is not desired it can be switched off
  (see "System Configuration") and then the controller tries to do the
  calculation again as before (but most probably with the same error result).
- FIX: In the error message (during creation of dye program) regarding value of
  text parameter outside min/max limits, the number of the function parameter
  was shown and not also its name (like it was intended).
- FIX: Working with user right "Info" was improved. Formerly some menu items
  were enabled which were not really suitable for the level "Info".

General changes concerning OrgaTEX integration database:
- - - - - - - - - - -  - - - - - - - - - - - - - - - - -

- NEW: New feature down times (stop reasons). It requires module release
 "Production data acquisition"). The following options are available for it:
  - Down times can be entered manually on the controller (only for Windows CE
    controllers like 757, 626, etc.).
  - Down times can be set automatically by the PLC program on behalf of
    certain conditions.
  - For older "Non Windows CE" controllers (like 737, "not connected" machines),
    down times can be entered here in the "Batch Scheduler" manually.
  - Existing down times can be modified and deleted.
  - Down times, started on the controller, can be ended here.
  - All down times can be confirmed here.
  - The machine and time range for displaying the down times can be selected.
  - The list of downtimes can be configured/sorted/printed/... (in the usual way
    for lists in the OrgaTEX).
  - Several down times can be merged.
  - The list of down times is available via integration database (for external
    systems to access it or for customer-specific "Expert" reports in OrgaTEX
    report programs).
- NEW: Feature "Manual Recipe" for entering "one-time" production recipes here
  in the "Batch Scheduler" for e.g. redyes. The following options are available
  for it:
  - Available for SETEX recipe system and also for external recipe systems
    if they provide a list of possible products.
  - Simple list of dyestuffs/chemicals with basic functionality to add/modify/
    delete (like it's currently available for correction recipes).
  - List of dyestuffs/chemicals can be copied from the original batch.
  - Special features of base recipe like subrecipes, treatments and their
    parameters, texts, formulas, etc. are NOT possible for it (so a procedure or
    program must be directly attached to it).
  - In case treatments and their parameters and/or formulas are used in the base
    recipe of the original batch, this feature may not be the best way to make
    redye recipes, but extra normal base recipes should be preferred.
- NEW: Make it possible to print all lines in SETEX recipe printout (means: also
  with treatment parameter and blank lines) even if they are normally suppressed
  by a switch. Used to check if recipe is calculated correctly - even with a lot
  of treatments from formulas.
- NEW: Coupled machines are now possible in recipe reschedule groups so that
  batches can be moved from one machine to another even if manual weighing was
  already started. Only in case of weighing orders for automatic weighing
  systems it's not possible (because the automatic can't divide up a bucket).
- NEW: In dialog window "Manual request for preparation" already successfully
  finished calls can be repeated (if it's configured this way in "System
  Configuration").
- FIX: If the "Batch Scheduler" was set up to do the actual recipe calculation
  instead of the "Service/Report Task" (very seldom), then some records weren't
  deleted from table "BatchChain" in case the recipe calculation reported an
  error for a newly created batch (leading to some superfluous rubbish data).
- FIX: For a batch that was canceled on the controller, the possible flag "In
  preparation" wasn't deleted (even though the requests were actually deleted
  from the preparation table). This made it hard to make modifications on the
  batch or moving it to a different machine, etc.
- FIX: The check of preparation numbers between recipe and procedure/program
  that is limited to only batches which were created with base recipes of state
  "Release" had a bug, so that the check didn't work correctly for correction
  recipes.
- FIX: In theory the sorting of several weighings/dispensings for one product
  could have been randomly in "Extended Recipe Printout" (although this has
  never been seen with any of the supported systems for integration database).
  Now it's guaranteed to be ordered by the time of the individual weighings/
  dispensings.
- FIX: If a production recipe printout for SETEX recipe was exported to WinWord,
  then for blank lines a nonsense text (the current time) was exported.
 

41.2.9 Production Calendar
--------------------------

- NEW: The "Production Calendar" can now use internally a new structure for
  saving its data. This new structure is completely relational (SQL) and can be
  stored in internal OrgaTEX data source or in integration database. So it's
  available for external systems and for customer-specific "Expert" reports in
  OrgaTEX report programs.
- NEW: The arrangement into the levels "Company", "Section" and "Machine" is
  still the same. But it's now possible to make changes not only in the
  currently shown level: e.g. if you are in the level "Machine", you can modify
  data of the levels "Section" or "Company" without switching to these other
  levels.
- NEW: If the production calendar of the new structure is used, then up to 10
  shifts are possible per day (even if more than 4 is really strange ;-)
- NEW: If the production calendar of the new structure is used, then the
  following features are no longer available (because they were so rarely used
  that there were doubts if they are really useful at all ;-):
  - Attribute "Ignore company info" (was "display only" in this application and
    had no further use).
  - Attribute "User defined shift" on level "Section" (could be replaced by a
    "normal" shift).
  - Attribute "Overtime" on level "Machine".
- NEW: If the OrgaTEX feature "Product data acquisition" is activated, then the
  machine failures and maintenances (down times) of the corresponding tables are
  taken into account. Otherwise machine failures and maintenances are handled as
  before.
 

41.2.10 Program Editor
----------------------

- NEW: Printing of time/temperature curve implemented.
- NEW: In formula selection for disconti function parameter and conti set value
  parameters it's now also possible to select "Editor formulas" of the "Formula
  Editor" (before, only batch formulas of TypeConf Tool were possible).
- NEW: Formula selection for conti text parameters is now possible in Edit Mask
  form (before, it was only possible in list view for conti parameters).
- NEW: Option "Machine and Machine Groups" in dialog window "Synchronize
  Integration Database" does now also fill tables "LogType" and "LogTypeDef" for
  the machines (if the module release "Production data acquisition" is used).
- FIX: Since OrgaTEX 4.1 there was an error in export/transfer conti programs:
  the generated PRG was by mistake invalid (without any error message), if the
  type configuration for the machine group contained at least one set value
  parameter with an ID > 200.
- FIX: Setting a value to the maximum limit if it's greater (after the user has
  confirmed to do so) didn't work in Edit Mask forms (by mistake the minimum
  limit was set after the message).
- FIX: Since OrgaTEX 4.0 the dialog window "Edit parameter" (in which you could
  select e.g. formulas) didn't display the unit for normal values (only for
  function parameters where you assigned a treatment parameter).
- FIX: If the window "Insert step" was open and then the menu item "Calculate
  preparation numbers" was selected for a program, the display of the program
  was messed up.
- FIX: Optimizations of display of dialog bar with tree control with all
  programs/treatments/procedure so that it's faster in case of a lot of items.
 

41.2.11 Formula Editor
----------------------

- NEW: New formula type "Editor formula". An editor formula can use all the
  elements of a global formula and besides predefined variables for e.g. the
  following, where all variables can be used to get data and some can be used to
  set data (e.g. batch data, step data):
  - Batch parameters/texts, general batch information.
  - Machine master data.
  - Quality master data (currently only if SETEX recipe system is used).
  - Step/function/function parameter data where value and step comment can be
    written (for disconti batches).
  - Conti parameter data where the set value can be written (for conti batches).
  - An array with all steps for all resources.
  The following features are implemented for this new type "Editor Formula":
  - These formulas are executed during program generation for a batch as well
    as when correction treatments are appended to the program of a batch.
  - Calculation requires module release "Formula use in program editor".
  - Creating/modifying these formulas here in "Formula Editor" requires module
    release "Formula edit rights for program editor".
  - An "Editor Formula" can have the type "Selectable", "Default" or "Fix":
    * A selectable formula has to be selected manually in "Program Editor".
    * A default formula is automatically pre-selected when inserting a new
      function in "Program Editor", but the user can select a different
      formula if he doesn't like the default.
    * A fix formula is automatically used for all functions which use a function
      parameter, to which this formula is assigned. A fix formulas can not be
      de-selected by the user when modifying the function. Fix formulas are use-
      ful for guaranteeing a specific behavior even which a lot of existing
      functions or e.g. for automatically generated CDC dispensing programs.
- NEW: The following new predefined variables can be used for recipe formulas:
  - For all subclasses in folder "Quality": _Absorption (the absorption
    capacity of the article).
  - For all subclasses in folder "Recipe": _PrinterForAutoprint (printer for
    automatic printing of production recipe. Useful if, depending on e.g. the
    machine, a printer in yarn or fabric/piece dyehouse should be used).
  - For all subclasses in folder "Recipe": _SuppressAutoprint (if "true" then
    production recipe is never printed automatically for this batch. Useful if
    e.g. dummy batches are calculated just for getting the costs).
  - For subclass "Text macro": _TextMacroName (the name of the text macro).
  - For subclass "Text macro": _TextMacroText (the text of the text macro).
  - For subclass "Recipe link": _LinkLiquorRatio (liquor ratio of recipe link
    as defined in the "Extended properties" of the link in "Recipe Editor").
  - For subclass "Recipe link": _BreakCallOff (determines if a new preparation/
    call should begin after the recipe link or not).
  - For all subclasses except "Recipe" in folder "Position": _arrCallOffData
    (an array with data of all lines of the current preparation/call).
  - For all subclasses except "Recipe" in folder "Position": _RepeatCallOff
    (with this variable the whole preparation/call can be suppressed or made
    one or several times).
- NEW: A fix recipe formula can be executed before/after each recipe calculation
  (Currently there's not yet a user interface for this feature. The internal
  formula ID has to be searched by "SELECT ID, Name FROM Formula" in internal
  "OrgaTEX-32" data source and then entered as value for entry "FormulaPre=" or
  "FormulaPost=" in section [RECIPE] in file "ORGATEX.INI" in e.g. F:\OT\BIN.)
- NEW: Recordset functions "OpenResultSet"/"Execute" of the formula language
  have now an additional 3rd parameter "Use connection pool". Existing formulas
  using these functions must be manually adapted ! The parameter should be
  "true" for real SQL data sources (e.g. "Pervasive", "SQL-Server", "Sybase")
  and "false" for file based data sources (e.g. Excel sheets, CSV files, ...).
- NEW: Undo (e.g. with "Ctrl+Z") does now also work, if tree control with all
  possible formula elements has the keyboard input focus.
- NEW: Standard keyboard shortcut "Ctrl+A" (Select all).
- NEW: Last used font size is stored when leaving the application.
- NEW: New menu item "Allow changing formula subclass".
- FIX: New formulas were not directly in the list of "most recently used"
  formulas in menu "File", but only after the first open. This is o.k. now.
- FIX: On some PCs (especially with Windows XP), the window of a just opened
  formula was completely empty (e.g. white instead of the tree control with all
  possible formula elements on the left and the source code windows on the
  right) and was only normal, if Windows repainted the window (e.g. because the
  application was maximized). This bug is corrected now.
- FIX: During formula execution there was the error message "It isn't possible
  to convert value from 'ARRAY' to 'STRING'" if an ARRAY with another ARRAY as
  element was used as parameter for calling a formula/function.
 

41.2.12 Batch Report
--------------------

- NEW: Modification of batch comment is now allowed for active/finished batches.
- NEW: Display of definition of function group times (which function is in what
  function time group).
- FIX: Since OrgaTEX 4.0 another start/execution of a normal report didn't show
  the values from the previous execution in window "Define variable query
  operands", but the default values set up in the document. This bug is fixed.
- FIX: Up to now it could theoretically happen that the list of values, which
  is shown on 1st page of printout of graphical charts, was not sorted correctly
  by the caption column.
- FIX: If a character string column with numbers was used as value column for a
  graphical chart, then by mistake the post-comma digits were ignored, if the
  language specific decimal separator wasn't the dot (but e.g. the comma like in
  German). Note: String columns with numbers are very unusual and happen only in
  special cases e.g. expert documents and UNION keyword in SQL statement.
- FIX: Up to now only space characters, but not tabulator characters were
  allowed before the comment signs (//,#) in window "SQL Query String" for
  "Expert Mode" documents.
- FIX: If the dialog window "SQL Query String" was closed and it contained a
  formula reference for a where-clause-formula which doesn't exist in the system
  (e.g. $$F_000041), because the formula was removed or the document was copied
  from another installation, then the formula reference itself was silently
  removed formerly. Now it's kept.
- FIX: In theory the sorting of several weighings/dispensings for one product
  could have been randomly in "Extended Recipe Printout" (although this has
  never been seen with any of the supported systems for integration database).
  Now it's guaranteed to be ordered by the time of the individual weighings/
  dispensings.
- FIX: If a production recipe printout for SETEX recipe was exported to WinWord,
  then for blank lines a nonsense text (the current time) was exported.
 

41.2.13 Machine Report
----------------------

- NEW: Report of down time groups:
  - Requires module release "Production data acquisition".
  - Like the alarm groups the down time groups can be evaluated.
  - Down times are stored like alarms as machine protocol data. This means that
    they appear as alarm in the assigned alarm group.
  - But for down times there are furthermore additional distinguished groups
    possible. These down times are then shown divided up by these groups.
- NEW: Support for the production calendar in the new structure (where more than
  3 shifts are possible).
- NEW: From now on at each place where the batch no. is shown, the redye no. is
  also shown (because only both together uniquely identify a batch).
- FIX: Calculation of report field "Production time" was wrong, if a controller
  for a machine was offline between batch selection and batch start. In this
  case the relative efficiency values depending on the production time (e.g.
  "Machine utilization" and "Percentage production time) were also wrong.
 

41.2.14 Alarm Report
--------------------

- FIX: Alarm names for alarms on foreign controllers were shown wrong (the short
  name of maximum 20 characters of the TypeConf Tool instead of the up to 80
  characters defined in integration database) in case the machine protocol data
  was stored in an internal OrgaTEX table (and not in the integration database).
 

41.2.15 Batch Assistant
-----------------------

- NEW: Confirmation message before reporting a batch manually as ready.
- NEW: Deleting of manual recipe (see this feature in "Batch Scheduler") if a
  batch with such a recipe is deleted here.
 

41.2.16 Background Service Task
-------------------------------

General changes:
- - - - - - - - -

- NEW: Setup of tasks extended in a way, that it can be configured, which tasks
  should be executed in which instance of the application (used e.g. to run the
  CDC-task "Central Dyekitchen Control" in a separate process). This was already
  possible since OrgaTEX 2.0 Rel. 1.8, but now there's a comfortable graphical
  user interface for that (before, it had to be set up in an INI file).
- NEW: New task "Delete old files from Dosing and Reports directory" which
  deletes old, no longer used files e.g. files that were renamed in case of
  errors, files that were never used by OrgaTEX at all, files written by OrgaTEX
  that were not deleted by SECOM because it's already in a different state, ...
- FIX: Confirmation question on closing the application improved. If due to some
  error message, the view/document was opened a second time and it now worked
  o.k. (because e.g. the problematic task was removed in the setup), then the
  confirmation message was missing when closing the application.
- FIX: Errors in batch formula calculation will from now on result in an error
  during program generation. If this check is not desired it can be switched off
  (see "System Configuration") and then the controller tries to do the
  calculation again as before (but most probably with the same error result).
- FIX: In the error message (during creation of dye program) regarding value of
  text parameter outside min/max limits, the number of the function parameter
  was shown and not also its name (like it was intended).
 
General changes concerning OrgaTEX integration database:
- - - - - - - - - - -  - - - - - - - - - - - - - - - - -

- NEW: All information that the SECOM controller collects (alarms, down times,
  operator logins/logout, function times, consumptions, analogue/digital values,
  controller states, operator calls, corrections, etc.) can now be duplicated
  from the Btrieve .LOG file into the integration database. In the following
  some details of this feature:
  - This feature needs module release "Production data acquisition".
  - This new structure is completely relational (SQL) so it's available for
    external systems and for customer-specific "Expert" reports in OrgaTEX
    report programs.
  - To which extent the data should be duplicated into the integration database
    can be set up in "System Configuration".
  - The "cyclic" data (analogue/digital values which are recorded in a fix time
    interval e.g. each 30 seconds) is stored in the same tables as it is done
    for foreign controllers:
    * LogValueFloat
    * LogValueBit
    For each type of recorded values there are the following 2 configuration
    tables:
    * LogType
    * LogTypeDef
    For a description of these tables, you can take a look at document
    "ConnectionOf3rdPartyControllers.pdf" on the OrgaTEX CD.
  - The "non-cyclic" data is stored in the following tables:
    * MachineOperatorLog
    * MachineAlarm
    * DatalogFunction
    * DatalogStatus
    * DatalogOperatorcall
    * DatalogAddition
    * MachineConsumption
- NEW: Task "Delete old batch and production recipe data" now deletes old data
  from all the tables mentioned above (this means, it also deletes old "cyclic"
  data for foreign controller, which wasn't done at all before).
- NEW: Batch import transfers the values of columns "NotStartBefore" and
  "ProductionDeadline" from table "Dyelots" into internal OrgaTEX batch table
  (so that they can be influenced by an external system).
- NEW: The automatic printout of the production recipe can be influenced with
  the column "PrinterForAutoprint" of table "Dyelots". Useful if, depending on
  e.g. the machine, a printer in yarn or fabric/piece dyehouse should be used.
- NEW: The automatic printout of the production recipe can be influenced with
  the column "SuppressAutoprint" of table "Dyelots". If "true" then production
  recipe is never printed automatically for this batch. Useful if e.g. dummy
  batches are calculated just for getting the costs.
- NEW: If a correction treatment is appended, the functions "Addition Start" and
  "Addition End" are automatically added if they are not contained in the treat-
  ment. By this feature, it's possible to use exactly the same treatment for
  the normal part of the process and the correction part.
- NEW: The columns "Dyelot_Adds.TotalVolume" is filled by OrgaTEX whenever it
  inserts records in this table (e.g. recipe calculation). The value used is the
  bath volume (the value which is used for calculating the absolute amount out
  of units like "ml/l"). Could be useful e.g. when conti recipes are calculated
  for not connected machine and manual dosing requests are then done.
- NEW: Support for dosing requests of SECOM conti controllers. They have the
  following 2 additional fields (in a 2nd line in R2 file) compared to disconti
  requests: "Required call off (total) volume" and "Fill water mode" (see also
  "Machine Configuration" for details).
- NEW: In task "Process calloff-requested/finished-messages for dispensing"
  already successfully finished calls can be repeated (if it's configured this
  way in "System Configuration").
- FIX: Controller state files (extension .CST) are no longer deleted in task
  "Process controller state (for ext. interface)" after they were processed,
  because "Online State" and "Batch Scheduler" also use these files.
- FIX: If Pervasive.SQL V8 was used as integration database and the integration
  database was used for machine protocol data (the latter currently only needed
  for module release "Support for foreign controller"), then the task "Delete
  old batch and production recipe data" was extremely slow (hint: no known
  customer has currently this combination of Pervasive with foreign controller).
- FIX: Option "Check only these batches with recipe where the state of the base
  recipe is 'Release'" for checking preparation numbers between recipe and
  procedure/program of "System Configuration" was already available in OrgaTEX
  4.1 SP 5 with an INI switch. If the feature was used, it worked wrong for
  corrections (it checked, when it shouldn't check and vice versa).

Changes concerning CDC (Central Dyekitchen Control):
- - - - - - - - - - - - - - - - - - - - - - - - - - -

- NEW: A dosing controller operated by CDC can now also generate (dye) batch
  independent consumptions even when the dosing batch is running. (This very
  specific feature was requested by one very special customer in Germany ;-)
- FIX: If there was an error during set time calculation for dosing batches,
  then the reason was up to now not logged. From now it's written into the error
  log file of the application.
- FIX: If there's a problem converting from one unit to another (e.g. from liter
  to kilogram and the specific weight is missing), then the displayed error
  message does now always contain the product name (so that it's easy to correct
  the problem in product data management).
- FIX: From now on the following situation will result in an error code sent to
  the controller and an entry in error log file: If a call request is done and
  the call contains some CDC products and some products for another external
  dosing system. Formerly this disallowed combination was silently ignored by
  the CDC and the call stayed on state "Requested".
 

41.2.17 Backup
--------------

- FIX: If a batch data archiving was aborted (manually by the user or due to an
  error), then the internal batch state was already set to "Archived" (so that
  the batch was e.g. no longer shown in "Batch Scheduler") even though the
  archiving was unsuccessful.
 

41.2.18 Machine Configuration
-----------------------------

- NEW: Coupled machines are now possible in recipe reschedule groups so that
  batches can be moved from one machine to another even if manual weighing was
  already started. Only in case of weighing orders for automatic weighing
  systems it's not possible (because the automatic can't divide up a bucket).
- NEW: New machine field "Allow modification of data in process pictures".
- NEW: New machine field "Add Foulard trough to liquor amount". Used by SETEX
  recipe calculation. Useful for Foulards with one bath/trough, but should be
  switched off for Foulards with several baths (for them, the fix amounts for
  the different Foulard troughs should be added by recipe formulas).
- NEW: New machine field "Machine sends information about the required call off
  volume". If this option is set, then "Dyelot_Adds.TotalVolume" will be set by
  the value given by the machine, otherwise the value written by the recipe
  system will be kept. This could be used together with the flag of the next
  paragraph. Mainly useful for dosing for conti machines (like the next flag).
- NEW: New machine field "Machine sends information about who should fill with
  water". If this option is set, then "Dyelot_Adds.FillWaterMode" will be set by
  the value given by the machine, otherwise the value from the new tank property
  "Dosing system fills with water" is used. Value 0 means: machine itself fills
  water, 1 means: dosing system must fill with water up to the total amount.
- NEW: If a controller is using DHCP for getting the IP address (flag "Use host-
  name instead of fixed IP address" set), then the dialog window "Automatic
  machine configuration" does no longer appear, if only the IP address given by
  the DHCP server has changed (because in case of DHCP, this IP address is never
  used by OrgaTEX directly).
- FIX: A temporary directory wasn't deleted (e.g. in F:\OT\TEMP) if an error
  happened or a controller was offline while trying to compare type/machine
  configuration or PLC program in dialog window "Transfer Configurations".
 
 
41.2.19 System Configuration
----------------------------

- NEW: Each user configured in the OrgaTEX, can now be used as operator for the
  new Windows CE controllers (e.g. 757, 626):
  - The user configuration is extended for setting up the default/max user level
    and the passcodes for the different user levels.
  - This information can be used directly by the controller (read e.g. on
    startup).
  - To each operator you can assign the controllers that the operator should be
    allowed to use.
  - The user list is furthermore stored in integration database table "Employee"
    if module release "Production data acquisition" is activated (so that
    reports on external systems or customer-specific "Expert" reports in OrgaTEX
    report programs can easily connect information from user logins/logouts/
    alarms/down times on the controller with the full long user name).
- NEW: New dialog window "Select character set (font)" where you can select a
  character set that the operating system supports. This enables OrgaTEX to
  display even non-English special characters correctly in an English OrgaTEX.
  This could be used e.g. for Baltic or Thai.
- NEW: New switch "Error in batch formula calculation will result in an error
  during program generation (otherwise the batch can be sent to the SECOM and
  it again will try to calculate the batch formulas)".
- NEW: New switch "Limit number of batches that are transferred to host batch
  selection list of the machine" and a value if switch is on. Only needed if
  you have otherwise problems. (Problems have been seen on OrgaTEX on Pervasive.
  SQL V8 with some old SECOMs with more than ca. 50 records in QUEUE.BTD that
  the controller messed up the file after it made a modification on it).
- NEW: New switch "Count of days for which the production calendar is used"
  for the past (in settings for "Batch Scheduler").
- NEW: New switch "Activate product data acquisition" in dialog window "Extended
  settings integration database". If it's enabled, then it can be configured
  which of the following data is transferred to integration database when a
  batch is finished:
  - Cyclic log data
  - Function status
  - Controller status
  - Additions
  - Operator calls
- NEW: New option "Switch off security check that a successfully finished call
  can only be repeated using explicit manual intervention in 'Preparation
  Assistant'". Useful only in cases where a function on the controller is
  programmed in the PLC in such a way, that it internally repeats itself
  several times and does intentionally use the same call no. each time.
- NEW: New option "Check only these batches with recipe where the state of the
  base recipe is 'Release'" for checking preparation numbers between recipe and
  procedure/program in dialog window "Settings dosing system".
- NEW: New dialog window "Licensing" for entering license codes. License codes
  are needed since OrgaTEX 5.0 for using machines of types "Foreign controller"
  and "Undefined (not connected)".
- FIX: After saving a menu entry (or when creating a new one), line feeds
  (entered as "\n" in the icon text) where shown wrong afterwards.
 

41.2.20 Product Data Management
-------------------------------

- NEW: To each product group a fix formula can be assigned. This formula is
  executed for each line in a base recipe that contains a product of this
  group (when the production recipe is calculated).
- NEW: New tab raider "Formula" for selecting a fix product formula. This
  formula is executed for each line in a base recipe that contains this
  product (when the production recipe is calculated).
- NEW: The fix product formula can be shown in the product lists (configurable
  column).
- NEW: Worth of stock (stock amount multiplied price for costing) can be shown
  directly in "Product overview" (configurable column).
- FIX: The filter bar is only shown for the view "Product data" and no more for
  "Stock transactions", "Product overview" and "Consumptions" (it was senseless
  there anyway).
- FIX: Keyboard shortcuts like e.g. "Ctrl+S" didn't work before when one of the
  tabbed dialog windows of "Product data" had the keyboard input focus.
 

41.2.21 Recipe Editor
---------------------

- NEW: New menu item "Use template for new recipes" which specifies if a
  template should be used when creating new recipes or not.
- NEW: New flag "Subrecipe" in recipe header. To search for these recipe is the
  default when showing the list of possible recipes for a recipe link. Further-
  more these subrecipes can NOT be used/selected for creating batches.
- NEW: New batch state "Redye (besides the existing ones "Theoretical",
  "Laboratory" and "Practical"). Can be used to identify these kind of recipes
  later (e.g. for deleting all one-time-redye recipes) or in formulas.
- NEW: Recipe header bar (normal/complete) made a little bit wider.
- NEW: User rights improved: Up to now users with user rights "Production" and
  "Info" were only allowed to read recipes (and configuration options) and for
  "Edit" everything was allowed. From now on it's also allowed for "Production"
  to create/modify/delete "normal" recipes (means: not a subrecipe or template).
- NEW: Up to now a treatment, that was inserted as line in the recipe, was only
  allowed to have at maximum 20 treatment parameters. Now this limit is removed
  in dialog window "Edit treatment parameters". The window now uses for the
  treatment parameters the same list box as in other parts of the OrgaTEX and
  shows now also always min/max limits and the name of a selected formula.
- NEW: Menu item to correct base recipes with a discrepancy in the used treat-
  ments regarding the used treatment parameters. (On the one hand there could be
  new treatment parameters which are not yet filled in the base recipe. On the
  other hand there could be treatment parameters, that are still used in the
  base recipe, but which are removed from the treatment).
- NEW: New switch "Print blank lines" in dialog window "Production recipe setup"
  (default: on). Can be used to have a small production recipe e.g. for the
  dyekitchen, but blank lines for structuring the base recipe.
- NEW: Customer specific production recipe "Crystal Reports" printouts can now
  have further file names: before they had to match the pattern "rcP702??.RPT",
  now also a 'Q', 'R', 'S' or 'T' can be used instead of the 'P'.
- NEW: Default formulas for all kinds of line items (Currently there's not yet a
  user interface for this feature. It has to be set up same way as fix pre/post
  recipe formulas - see "Formula Editor" - only the entry in INI has to be one
  of: DEF_FORMULA_CHEMICAL=, DEF_FORMULA_DYESTUFF=, DEF_FORMULA_MACRO=,
  DEF_FORMULA_TEXT=, DEF_FORMULA_TREATMENT=,DEF_FORMULA_RECIPELINK=).
- FIX: If several formulas were assigned to a treatment, then the units for the
  treatment parameters were shown in the wrong line.
- FIX: By mistake it was possible even with a lower user right than "Edit" to
  modify a formula assignment or the pass through level for a formula.
- FIX: Show "Pickup %" instead of "Liquor Ratio l/kg" in extended properties for
  a recipe link, if it's a recipe for a Foulard.
- FIX: If text was entered in one of the edit fields in windows "Open Recipe"/
  "New Recipe"/"Delete Recipes", then a changed setting for options "Template"
  and "Case sensitive search" was reset by mistake if the button "Query" was not
  pressed in the meantime.
 

41.2.22 Customer/Quality Management
-----------------------------------

- NEW: New quality property "Absorption capacity/carry over". Value can be used
  e.g. by recipe formulas.
- NEW: New substrate property "Wettability factor". Value can be used e.g. by
  recipe formulas via database queries.
- FIX: Keyboard shortcuts like e.g. "Ctrl+P" didn't work before when one of the
  tabbed dialog windows of "Product data" had the keyboard input focus.
 

41.2.23 SECOM File Manager
--------------------------

- NEW: Support of long filenames: more than "old fashioned" MS-DOS 8.3 notation.
- FIX: Before there were problems when the application was used on several PCs
  at the same time, because all shared one file ("syn117.dat") for exchanging
  data with the controllers. This could have lead to wrong files being copied,
  display of wrong directory contents on controller and even to a total lock up
  of the application with message "Can't write seq. file."
 

41.2.24 Scaling Station
-----------------------

- NEW: It's now possible that different PCs with the application also display
  different products to weigh (up to now all of them displayed the same things).
  This is done by defining products of which stations (set up in "Machine
  Configuration") are allowed to be weighed on a specific scale (e.g. one
  for dyestuff and one for salt).
- NEW: Setting, if "Load release" should be given, if everything is completely
  weighed on the scale, can now be set separately for each "Scaling Station" PC
  (so it can be achieved, that "Load release" is given after the dyes are
  weighed and not, after the salt is weighed).
- FIX: If there's a problem converting from one unit to another (e.g. from liter
  to kilogram and the specific weight is missing), then the displayed error
  message does now always contain the product name (so that it's easy to correct
  the problem in product data management).
 

41.2.25 Data Eraser
-------------------

- NEW: The logging values for e.g. the time/temperature curve, that are stored
  for foreign controllers, are now also deleted (from the following tables of
  integration database: "LogValueFloat", "LogValueInt", "LogValueBit").
- NEW: Deleting of manual recipe (see this feature in "Batch Scheduler") if a
  batch with such a recipe is deleted here.
- FIX: If Sybase was used as integration database and the integration database
  was used for machine protocol data (the latter currently only needed for
  module release "Support for foreign controller"), then the time, before the
  progress bar was shown, was extraordinary long (hint: only one customer has
  currently this combination of Sybase with foreign controller).
 

41.2.26 Central Dyekitchen Control
----------------------------------

- NEW: New dialog window "Pipelines" which partly replaces the former dialog to
  configure "Destinations". The formerly used dialog is still used to set up the
  connections between station (or pipelines) and machine tanks. Pipelines have
  the following features:
  - They are mainly used if you have a "cross distributor" (meaning several
    dosing stations and several machine tanks and the pipes in a way that you
    have a crossing so that you can either run some stations with some machine
    tanks in parallel or one station with all tanks - e.g. in case the other
    station is locked, because it's out of order).
  - A pipeline is the connection from a list of machine tanks to one or more
    dosing stations. Each of these connections must be physically possible and
    it must be possible by the PLC to activate this pipeline by software.
  - If a pipeline is assigned to several dosing stations, these dosing stations
    can have different priorities e.g. "A" has "default", "B" has "emergency
    case". If station "A" is now locked, then automatically station "B" is used.
  - Pipelines have the advantage that, when a "cross distributor" exists, the
    system will automatically choose a working alternative route, if one dosing
    station is locked (whereas before a lot of manual re-configuration had to
    be done in the destination address setup).
  - Pipelines don't have to be used. You can still use the simple scheme as
    before.
- NEW: The dosing station to use for a call can be limited to certain stations.
  This is done the following way: For each CDC station you can (indirectly) set
  a dosing system no. The CDC station is now only used, if this no. equals field
  "Dyelot_Adds.DispensingSystem" (4th parameter) of a request. This can be used
  (e.g. with formulas) to have different dissolve stations for light/dark dyes.
- NEW: New option for chemical stations: "Do not start dispensing when one of
  the products is inside a blocked tank". This option can be used to avoid that
  a dosing is done in 2 parts (which can be a problem if dosing in 2 parts would
  produce too much rinsing water compared to a dosing in 1 part).
- NEW: Everything that was formerly only possible with user right "Supervisor"
  is now also possible with right "Production leader".
- FIX: There was a senseless Btrieve "Key not found" error message when deleting
  a stock position for a bucket/container for stations of type "Color station".
- FIX: If there's a problem converting from one unit to another (e.g. from liter
  to kilogram and the specific weight is missing), then the displayed error
  message does now always contain the product name (so that it's easy to correct
  the problem in product data management).
- FIX: Reading CDC order data optimized.
 
 
Links: