PDF reports which existed the day before are now missing.

If CM4D finishes generating a report, but the overall print job is not completed (print spooler is stopped), the existing report is deleted without being replaced with a new report.

In previous versions, if a document was opened that was already opened by another instance of CM4D, a message box would appear stating so. That message box no longer appears, and is causing issue when a user makes changes and then tries to save.

There are some CM4D documents that give an error message when saving, reporting that the document may be open for changes elsewhere.

NOTE: If the document extension (.4dc) was uppercase (.4DC), we would get the error. The workaround is to change the extension to lowercase (.4dc).

Vector lines are shown on the image where they did not appear in previous versions.

Solution: In v20, there was a bug in the Nominal type of View Feature Mode which caused the feature markers to not display properly. Once it was fixed the markers now appear, which some customers migrating to v21 do not want. See New Features to implement solution.

Scheduler Manager becomes unresponsive with multiple launcher client connections.

Solution: A performance improvement has been made, but it will require a Site Schema change from 21b to 21c. Update Site Schema script is provided with the installation of this version.

In specific cases, loading a routine causes CM4D to freeze.

When a template that has event alarms set up is run through Scheduler, CM4D crashes.

Undoing the AutoReport Layout causes CM4D to crash.

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.

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.

The Format options of the Cell Style properties of a Table are not applied when using a DataSet as the DataSource.

In a table, unchecking the Base option in the Cell Styles Format tab causes the ~feat,label~ variable to resolve as ‘0.00’ instead of the label string.

Rotating a large .wyr image is extremely slow, almost to the point where it is impossible to move the image at all.

There is a difference how a formula used for setting the scale of a chart is shown in CM4D Classic and how it is shown in CM4D Interactive.

If the Sort Rows option is enabled in the DataSet General properties, the modified sorting is not reflected when the DataSet is viewed in the Grid.

Annotation are not pointing to Feature Markers in the View. When the Purge Unused Features option is enabled on the View, but the DataSet is using the Sort Rows function, annotation are not reflecting the sorting. As a result annotation are not syncing with the feature markers being shown in the View, and at times have a leader line that connects to a point without a feature marker.

The DataStack Evaluation – Score resulted in an incorrect answer, particulary for scores that used highest value binning.

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

When a measurement file with a routine that is not pre-selected in the 4dc document arrives, Workcell is not sending this routine to the Errobox. The files remains in the "available" folder.

The Significance of a Feature characteristic is not included in the archive file.

The image path of a Routine is not included in the archive file.

Any changes made to a Sample Filter label or a Feature Filter lable does not get updated in the database.

When an Animated Alignment view is printed as a GIF, it is not showing the animation.

Note: This issue was on the Known Issues list for previous v21 releases.

When a Scheduled or Web report is generated that has an Animated Alignment for its Thumbnail, it is currently creating PNG files. A GIF should be created in place of the PNG if the View in the thumbnail sheet is set for animated alignment.

When using Views that have the Feature Mode set to Actual or Animate, only one View will display properly, the others will not show the Feature Markers (Actual) or the animation (Animate). This is per instance of CM4D.

The Uncross Leaders option is not staying checked for Views.

When a multi-threaded Scheduler is opening and closing documents at a very fast rate, in rare cases one CM4D client may clean up temporary files prematurely, resulting in another job not completing.

When using Oracle, DataProcessed Scheduled Jobs are not being triggered when samples are processed using DataSmithBatch.

When using the date parameter in the ~sample~ variable, the date formatting is not being applied when resolved.

Blank DataSet errors are appearing in the trace window, even when there are no blank DataSets in the document.

In the Feature Editor, changes are not being saved when the dialog is closed.

When a new CM4D Web user is added to the Site, submitted reports sit in the queue without processing. The Scheduler services must be restarted before new users can successfully print web reports.

The sheetset order in the managed reports is not being maintained properly during the migration from v20 to v21. Does not effect new installations.

The SPC variable ~siftrule,n>1,cpk~ (where the sift rule is designated by number, and that number is greater than 1) does not resolve.

If you select a new Routine for an existing Query, the label of the Query changes to the label of the Routine. In addition, this does not update references in the document, such as from DataSets.

When an unmanaged database is used, there is an isntant crash when Routine selector is opened.

CM4D documents are very large, and are slow to open/save.

Animated 3D images in a view change the position and depending on when you leave view Edit mode it keeps the current position. Part should return to Nominal position after exiting Edit Mode.

When an Animated Alignment view is printed, it is not showing the animation.

When trying to open the View Feature Markers Material dialog, CM4D crashes if there is no part image loaded.

If a Managed Document has internal scripting that opens a dialog is used in Scheduler, the job will not complete successfully.

Solution: Any scripting that opens a dialog cannot be used for Scheduler jobs.

Always use extreme care when using internal scripting in documents that will be used by Scheduler, since Scheduler sometimes handles documents in a different way than when the document is opened manually in Classic.

Scheduler Jobs with the “Event” Report Type are not migrating.

Solution: Required a change to the v21PreMigrator to allow for Event jobs. If you have already run the PreMigration Analysis, re-run using v1.0.0.7 of the PreMigrator tool provided with this release.

Crash in SiteManager log when re-initialize migration for removing broken Managed Documents.

There was a known drawing issue in CM4D on Windows 8 and Windows 10 where leader lines cause rectangular patches to obscure the View.

When a large number of jobs (1350+) are running with a large number of managed documents (9200+) included in the Managed Reports, the client information in the Scheduler Monitor tab does not refresh when there is more than 1 CM4D Client running.

If you select a new Routine for an existing Query, the label of the Query changes to the label of the Routine. In addition, this does not update references in the document, such as from DataSets.

When an unmanaged database is used, there is an isntant crash when Routine selector is opened.

When using an unmanaged database, DataUtility will not open.

The image does not rotate with the view.

The Run Auto Report check box (for Scheduler Managed Documents without a View) is missing after SheetSet Property dialog redesign for v21 features.

Scheduled Reports that included Auto Reports fail if the number of Sheets in the originally saved document was greater than the number of Sheets generated by the AutoReport when the job was run.

Scaling set on 3D images is not being applied in CM4D.

If the Report Paths map file “Report Name Prefix” field is used, and is missing the trailing backslash, the resulting report ends up with the Prefix as part of the PDF file name instead of creating the correct subfolder.

Changing a Depository Label in the Migration Map file, but not the Depository Path, results in a legacy duplicate depository.

During Migration, if a document fails to migrate, the Fail counter does not reflect this.

When CM4D creates default Managed Reports, it is using the File Name in the Managed Report label. This should use the Managed Document Name in the Report name.

If a Managed Report includes a SheetSet from a Managed Document that has a Query that fails to load (e.g., Routine was deleted), the report fails to print in Web.

Data collected from plants in a different time zone than the plant receiving the data is not being processed correctly. The Sample Cutoff Dates are not using UTC.

This fix was also delivered as a Hot Fix in v20.3.0.

Annotations are not moving to the opposite side of the Image, causing crossed up leader lines.

When a misspelled variable, such as ~samp,date,%D/%M~, is used in a Text or Table annotation, CM4Dc crashes.

After running Test Align in the Alignment setup, samples that were recomputed for the Alignment test are not being reset to their original values once the test run is complete.

Standard Reference Features (not Constructed Reference Features) are not showing up in the Data tree bar.

When running an Internal Script, completed scripts are not being recognized as finished. Status does not show that the script has finished.

When attempting to load Selected Samples for Constructed Features, and those samples cannot be found in the database, CM4D locks up.

When selecting Reference Features for a Constructed Feature, Subroutine Features are not available.

When Feature Marker Text is enabled on a View and that View contains Constructed Features (such as Range), putting the view into Edit Mode crashes CM4D.

The parameter for the name of the Sift Rule is not resolving correctly.

In the Feature Select dialog, clicking on the column headers does not sort the list of Features by that column.

In the Routine Properties dialog, the Apply button is always disabled.

Solution: Removed non-functional button.

There is the Note That everything is updated to the database once you click OK, but the Updates Pending flag still appears on the DataSource.

Solution: Note has been removed from the dialog, as changes are updated to the Database when Update to Database is performed.

When PDFs are printed, the green “desktop” behind the white Sheet area is being printed on the top and bottom of reports.

This fix was also provided as a Hot Fix in v20.4.3.

When features are selected in a View and then the menu item “Push Features to Reference” is used, CM4D crashes.

The *.err files do not get removed/replaced when a file size limit is reached, causing crashes.

Solution: See the enhancements section on Logging.

CM4D Scripts are limited to 30000 bytes. This is proving to be too small.

Solution: Extend limit 100,000 bytes. If scripts are larger than that, they must be split into script modules.

When editing the "Embedded Paths" grid for "Annot Load Filenames", if you use the "fill" function, the grid updates properly, but the change is not applied to the annotation. If you re-enter the grid, the settings are the same as before.

In the Feature Properties dialog, the option to change Feature Filter values allows you to type in a value even if the filter is Restricted (should be a dropdown list).

When using “Assign Cause” to mask data, the “Change Log Comment” window does not appear and we do not have ability to trace who made changes.

Delete log comment entry in Process Change Log Viewer does not work.

Takes long time to open/load database when creating Queries.

Solution: Removed multiple extraneous resolves to improve load times.

The ReportTweak toolbar (used for Sticky reports) is missing from the View/Customize menu so that cannot be re-enabled if it has been closed.

When used as a User-defined Row Variable in the Report Properties, the variable ~nom,label~ will not resolve in the DataSet grid.

When an image is deleted from a Routine, CM4D instantly crashes.

This fix was also provided as a Hot Fix in v20.4.3.

Double-clicking anywhere in the yellow area would load whatever what highlighted. This causes heavy re-load times if the wrong node was highlighted.

Solution: The action of a click will now only be triggered when a node/item is clicked directly. This same principle applies to CM4D Classic as well.

The settings in the Cm4d.ini file for the grid defaults are not being read when CM4Di loads.

Solution: The order of the sections of the ini file were the issue, so a new default ini file will be provided with this release.

Terminology in CM4Di tree does not match CM4D Classic.

Assigning the Reference Feature association does not put anything into the database.

When the result of the Mangle function needs to be a variable (for example, a user variable to prefix the server name on the image file name), DataSmith does not handle the tilde character properly.

When two files are placed in the Inbox at the same time and for the same Sample, the data from one of the two files does not show up in the database.

This fix was also delivered as a Hot Fix in v17.5.

Translators that would create Subroutines when run manually through DataSmith would not create those Subroutines when run through DataSmith Batch.

If the Site connection was lost, the connect was never restored but Batch would keep trying to process files, and would end up sending everything to the error box. The Batch service would need to be restarted manually.

When using the Replicate Routine function in Data Utility all the information copies over correctly, except the Feature Description and the Lower Spec & Reasonable Limits.

CM4D Scheduler client and CM4D Web client should not consume a Server license.

Two data files with in the same sample in the same routine put into the Inbox at the same time could result in some of the information not processing correctly.