ProENTRY Echelon IV version 4.30.0569

4.30.0569.01 2009-04-10

• Bug: An error message was sometimes posted when selecting Spec-Group content in the order update window. The error was mistaken and benign. Fixed.
  
• Enhancement: The client page in the Order Wizard is now suppressed when the client selected is "Client Not Specified".
• Enhancement: A licensed user option has been added to permit the Job Name and Description to be suppressed in the Order Wizard.
  
• Enhancement: The Spec-Group Description field may now be suppressed.
  
• Enhancement: The Order Wizard's Purchase Order field now permits mixed case entry.
• Enhancement: Line Items may now be re-sequenced and renumbered in the main order update window.
  
• Enhancement: The main order relation tree now includes an option to replace the order description with the dealer's purchase order when appropriate.
  
• Bug: Several spell checker issues where words which ended with punctuation were not being spell-checked correctly. Fixed.
• Enhancement: Image editing changes include new compression options for JPEG and PNG, RGBF support for TIFF, Vista icon support. Also, the library has been updated with the new libtiff (3.9.0), libpng (1.2.29), libMNG (1.0.10) and OpenJPEG (1.3.0) libraries.

4.30.0569.00 2009-04-07

• Regression: Order wizard required the Description field to be completed even when the "Order Description required" option was not checked. Fixed.
• Bug: When applying custom report attributes including certain default values, some totals appeared ad dark blocks in ProENTRY IV reports. Fixed.
• Regression: The order contents relation tree in the main order update window was not properly formatted after an upgrade. Fixed.
• Regression: Modification prices were not included in order totals since the introduction of the MESSAGE() function. Fixed.
• Enhancement: Revisions to the parts computation process now permit ProENTRY IV to uncover user defined parameters at any level including any level of recursive expressions.
• Enhancement: User defined MESSAGES() may be used in expressions in order to display information or query operators during order entry and capture their input.  This may be used to supplement the existing enforcement of minimum and maximum values.
  
  An expression like this:
  
  
  
  Might produce a MESSAGE() window like this:
  
  
   

Known issues

• The revised expression engine and parts generator have undergone recent overhauls and are still undergoing testing; therefore, the potential exists that errors might be encountered. Please report any such errors encountered.