After an upgrade, the following routine tasks are recommended:
Additional migration tasks may be required where outlined in the release details for each version.
See here for bug fixes.
CM4D licensing is now compliant with FIPS (Federal Information Processing Standards) regulations.
Requires ATS Licensing Server 4. If you are running the ATS Licensing WCF Host Communicator service, see here for the required configuration setting.
See here for bug fixes.
This hot fix significantly effects the CM4D Results Services and may require some additional configuration for the services to start.
To support custom deployments of the Results Services, some options were added to the appsettings file. Some of these settings are specific to the type of Transport you are using with the services, e.g. Azure Storage Queues.
See the topic Configuring the Results Services for more details.
See here for bug fixes.
This version requires a schema update to the CM4D Site (25e) and Results databases.
Filters are now available on the starting page of CM4D Peruse. At this time, buttons are displayed for any configured Routine filters.
See the topic Home Page to review the functionality.
Annotation templates used for the Annotation Sets introduced in the previous version have been expanded to support some graph types. Additionally, the annotation templates are now used as Reports.
See the following topics to review the functionality:
Peruse Users - Report Panel in Peruse
Peruse Admins - Peruse Report Configuration
The CM4D variables supported for use in CM4D Peruse annotations has been expanded to include nearly all CM4D variables, with a few exclusions.
See the topic Peruse Annotation Template Variables to see the complete list.
Subroutine information stored in the Results database now includes references to any 3D models associated to its parent Routine(s). Duplicate models are not generated or stored.
The appearance of CM4D Peruse has received a cosmetic update to make the interface more visually pleasing with better contrast. Two themes are available for the user to select a preference, either Light or Dark.
Dark Theme |
Light Theme |
See the topic Peruse User Options to review the functionality.
Original CM4D functionality, View Spectrum, is returned using the HOOPS 3D engine upgraded in the initial release of v25. While most of the configuration options have returned as they were in v24 and earlier, the arrow type 'Label' has been deprecated.
Spectrum Type: Color with multiple Feature Types (Feature Mode - Feature Specific) |
Spectrum Type: Color with multiple Feature Types (Feature Mode - Sphere) |
See the topic Spectrum to review the functionality.
A configuration option has been added to CM4D Managed DataSources in the CM4D Configuration plugin which allows you to select which Routines, if any, are to be completely excluded from the data transfer. In addition to selecting Routines by label, you can use Filter arguments to designate Routines for exclusion. The filter builder is only available if the selected Managed DataSource has Routine Filters configured.
See the topic Configure Results Exclusions to review the functionality.
The Results Sender service processes the database changes in CM4D for export. Distributed installations with databases in different regions that are organized within a single Site may cause inefficiencies. For example, if a Results Sender service in Europe processes changes for a database in Asia. A configuration option is now available which allows you to restrict a Results Sender instance to process only specified Managed Datasources. It is possible to configure a datasource by DataSource label or to specify a Site and include all Datasources within that Site. The Results Sender appsettings.json file has a configuration setting "ProcessDatasources" that takes an array of definitions.
See the topic Results Services to review the functionality.
Some enhancements have been added to the CM4D Configuration plugin.
A tab has been added to the Site Settings section of the CM4D Configuration plugin which lets you synchronize security and user information between ATS Security Manager and CM4D Site Manager. The synchronized data includes users, roles (groups) and rights (privileges).
See the topic Site Management - Site Settings to review the functionality.
The three database types used by CM4D - Site, CM4D, Results - have some degree of automation available when managed via the CM4D Configuration plugin. Each of these database types have options for both creating new databases or updating existing databases to the latest schema.
Alternately, you may choose to run the update scripts manually in SSMS (legacy method) or run the corresponding Database Utility (new - see next section).
See the following topics to review the functionality:
Site Management - Managed Datasources
Site Management - Results Database
Creating and updating databases for CM4D can be a lengthy process when done manually, so we have provided tools with the CM4D Server and CM4D Results Services installers to make this type of database maintenance easier. Instead of locating the scripts and running each script individually on each database (and in the right order), you can simply run each tool and select an action.
See the topic Database Utilities to review the functionality.
The following ATS CM4D modules support Windows or Linux Docker deployments:
The available docker images can be found on the ATS Product repository on Docker Hub.
See the topic Docker Installations to review the functionality.
EventSmith SMTP has been upgraded to a separate installer and now supports password encryption by using NServicebus with SQL Transport infrastructure with queue tables created by the services in the Site database. The new EventSmith services (EventSmith Mailer and EventSmith Queue Processor) are a separate installer in order to allow for flexible deployments. CM4D creates event entries in the table EventQueue in the Site database, which are then picked up by the EventSmith services for processing through the Processing Queue and Mailer tables.
See also:
Known Issues - SMTP_Mail_Server_Authentication_Username.
See here to see the release notes for previous versions.
Can we improve this topic?