The lines and borders in a printed report appear thicker than in previous versions using eDoc Printer.

The config files for the standalone version of EventSmith SMTP contain connection information such as database strings, usernames and passwords. These files are not encrypted an may expose sensitive information.

The 3D view does not load the feature markers until the template is refreshed (Query - Refresh From Database).

Alignment is reporting incorrect XYZ. Results of alignment in CM4D are different from CMM measurements.

Note: This change also addresses an issue reported where the error was magnified the further away the point was from perpendicular to a major plane.

Fixed in v24.2 and provided here as a hot fix.

Some Scheduler reports are printed out of order.

Scheduler CM4D clients appear to hold onto memory even if the jobs have finished.

When using scripts to create objects (such as chart or graph annotation) and then printing the report results in some of the newly created objects not showing in the printed report.

Note: The bug was a refresh issue with printing documents with unsaved changes via scripts, not a problem with whichever printer was used to generate the PDF.

Variables with # and ^ (for example: {#~dev~}) are not working for text and chart annotations.

When using Print or Print Direct, the ATS CM4D Printer creates a file without a name (file extension only).

Some Scheduler reports printed with ATS CM4D Printer are missing pages.

Jobs are processed only by one Client at one time (even if more are available) when reports are printed by ATS CM4D Printer.

There is no way to sequence (order) the manually select samples from Sample selection Dialogue box, if we select the samples manually from Right hand side to left hand side of the dialog.

Solution: A new ‘Order by’ option has been added to the Sample Load dialog. See New Features above for details.

DataSmith crashes when adding a file to a Config that uses the RTF preprocessor option.

Values of constructed features do not match previous version in same template and database.

On open, a specific document generates an infinate loop of access violations when attempting to connect to the database.

CM4D crashes after creating a new document and loading all Subroutines in a query.

The size options for the Hatch brush style are obsolete; there is only a default hatch size. The option has been removed from the dialog.

Sift Rules are not applied correctly for combinations of Primary, Secondary or Tertiary with Toleranced or Significant.

The Mangle option for Lookup from File does not work.

The Routine name is not set correctly using the following API calls:

• query.OracleRoutineLabel
• query.DataSourceRoutineLabel
• query.SQLRoutineLabel

NOTE: This bug was only present in v21.5.1.901.

The variable formatting option ‘Leave Empty’ in the Document Defaults does not display correctly if the DataSet is empty. For a DataSet with no rows, the unresolved variable remains in the annotation.

There is an error in a Table that has the DataSet Setup option ‘Col Header’ selected and set to ‘Percent of Event Conformers/Non-Conformers’. Using this setup, the column headers display the percent sign twice.

CM4D Print option 'Print Document' prints only last page of document when eDocPrinter is used.

Scheduler Report contains only the last page of document when eDocPrinter is used. Same issue is also seen in CM4D Web reports.

Variables in a table are not displayed correctly. The table is configured with one cell with the following variables/string:

Total: ~dataset,totalcount~ Hi: {(~dataset,hi~)*2} Lo: {(~dataset,lo~)*2} No. OOT: ~dataset,nonconformcount~

This same variable configuration in a text box displays correctly.

The Export Data option 'Content of Dataset cells into CSV' does not format the csv file properly.

TFS #63069

When you export to *.csv file from Features page, three columns (Mark Align, Mark Material and Violator Analysis Type) are exported as question marks.

TFS #60396

Strings are not returned when ‘obj.Doc.ShowDocument();’ is commented out.

The picture object does not allow .PNG files to be loaded.

Setting the scale on charts and graphs via the API does not appear to be working.

Note: The QaDoc API method to update the document is overkill for many situations as it resets both annotations and datasets (very expensive for performance). API code that just changes annotations, for example, has no need to update datasets. Added individual methods to update just annotations or just datasets to the QaDoc object:

• UpdateAnnots();
• UpdateDataSets();

CM4D crashes on document open if there is a View with Auto-Orient set to Zoom Feature and only one Feature is loaded.

Zoom to features zooms in too close if only one feature is selected.

Picture annotation does not load any 2D image formats (JPEG, GIF, PNG, BMP). Existing images are not loaded, and you cannot load an image file in a new picture annotation.

Trend charts are only displaying the first digit of the sample deviation value for the first reported sample. All other samples are showing the proper number of digits and decimals. The charts are using the ~dev~ variable for the horizontal plot space.

A translator that has sample month and year associated separately always exports the month as January, regardless of what month value is picked up from the data file.

Align variables are showing zeros instead of text in existing templates

Lead Character None is not working properly.

Opening the Array sheet can take a long time to load in Classic or print in Scheduler.

See the New Feature – Feature Cache.

The variable ~cell~ does not resolve.

In existing documents, the following Count variables are not resolving the correct value (always show zero):

• ~count~
• ~subgroup~
• ~totalcount~
• ~validcount~
• ~invalidcount~
• ~nospeccount~
• ~outofspeccount~

Variable ~sample,label~ gives wrong results in existing template (showing text but not integers).

The DataSource dropdown is not fully shown in the toolbar.

Region settings that use a comma as the decimal symbol have issues when inputting numeric values in documents.

Solution: See New Feature: Document Locale Setting.

When you are creating new SheetSet and use Sheet Propagation CM4Dc crashes.

Solution: This option is now disabled when creating a new SheetSet. It does not make sense to run the Sheet Propagation until the content of the first Sheet is configured properly.

CM4Dc crashes after opening Assign Material to this Feature dialog.

In the Line properties, the input fields do not accept a decimal separator (period or comma).

Transposed DataSets are not supported in CM4Di reports. A report using a transposed DataSet appears differently in Classic than it does in Interactive.

Solution: Transposed DataSets can only be used in SheetSets with the Interactive Usage Type - Summary.

If you run job in Scheduler Manager with an *.xgl image in a region that uses a comma as the decimal separator, it shows an error message in trace and printed pdf is without image.

If you select an *.xgl image in a region that uses a comma as the decimal separator, it shows an error message and does not load the image preview

Setup for Evaluation Dataset Variable, Evaluation Row variable and Evaluation Sift Rule Variable is not persistent.

If you enter a variable in the Setup and save the document, after reopening the Setup dialog is empty and DataStack does not work.

Some improvements have been made to make Scheduler more efficient in the way it processes jobs through the queue and communicates with its clients.

This modification will not speed up the job processing time. However, large Scheduler implementations with many Jobs and multiple Launcher clients should see better efficiency in the way the system runs and fewer bottlenecks in the job queue.

PDFs generated with Scheduler (via QuickPDF) are not readable due to the low-resolution quality.

Solution: Re-instated eDoc PDF Printer.

Views in PDFs reports have a faint gray background instead of the white sheet color.

Solution: Re-instated eDoc PDF Printer.

All annotation settings, styles and DataSources are saved even if those settings are not used. Temporary table cells are saved with the document when not necessary.

Solution: Not saving the unused components significantly decreases the .4dc file size and increases the load/save load times. To apply this fix, open the CM4D document, save it in this version and close the document. On re-open, you will see the performance increase.

The variable ~load,imagetime~ does not return a value.

PDFDPI = 600

Enter a value for the resolution (for example, '600' is 600dpi). You may need to try different resolutions to determine the best quality and system performance. Note that a higher resolution will result in larger PDF file sizes.

• Conditional Styles

• DataSet Formats

• DataStack Evaluation Scores

• MSA Results

• Score Styles

• Sift Rule Conditions

• Sift Rule Sorting

The Config property for setting a decimal separator has been removed. The Locale setting will now determine what symbol is used as the decimal separator in the data file to be read into the database. DataSmith uses the default settings for the selected locale, not the Windows system locale settings.

Note: This change may require changing your translator config properties to use a locale if you relied on the decimal separator in past versions. When a translator is opened for the first time in this version, a warning message will appear: “Configurations no longer support the decimal separator setting. Please check and set each Configuration local as appropriate!”

Adjust the Config properties as needed to the correct Locale and save the translator to clear the warning message. See here for information on the Config Locale Settings.

Undoing an AutoReport Layout causes CM4D to crash.

The variable ~dev~ is not working for the Spectrum functionality.

CM4D crashes when a routine with multiple JT images is loaded.

When a document has routine (which has 3d image assigned) and there is no View on the currently active sheet it crashes cm4d on Trying to open Edit Feature dialog.

When editing Subroutine Features, the Create/Edit Limits button in the Feature Editor does not work.

When selecting Features of a Subroutine in the Alignment dialog, the Feature key includes the Subroutine Key. For Features relying on Handedness of a source Routine, it is impossible to differentiate the Features when selecting them as Alignment datums.

Note: Now the Source Routine Key will be shown instead of the Subroutine Key.

If the Query Control dialog is opened via the “Find Routine” right-click option in the nav tree, the Sticky Report dropdown list for that Routine appears empty.

Views go into Edit Mode using a single click, so features cannot be selected within the view.

Variables such as ~rout~, ~samp~ and ~samp,active~ are not resolving when used as part of Managed Report Name.

In v20, Managed Documents could be checked/unchecked for a job in Scheduler Manager using the spacebar on the keyboard. Once Managed Reports replaced Managed Documents in v21, the spacebar can no longer be used to select Managed Reports for a job.

When PDF reports with multiple SheetSets are printed, only the last SheetSet is printed.

The Format options of the Cell Style properties of some Tables are not applied when using a DataStack (Merge: Append or Collate) as the DataSource.

Histogram and Normality charts are showing a difference between CM4D Classic and CM4D Interactive.

When the DataSet General Additional Processing option “Sort Rows” is used, the grid does not show the applicable sorting. Instead of sorting by the entered variable, it remains sorting by the default alphabetical.

Double-clicking on a View no longer puts the view into Edit mode to allow for active manipulation of the 3D image.

Using the Advanced Excel Library (Excel Free) Preprocessor, cells in the Excel file containing long strings appear in scientific notation when processed by DataSmith.