Alderstone cmt product release notes Product Release Notes Alderstone cmt 2.0 Alderstone Consulting is a technology company headquartered in the UK and established in 2008. A BMC Technology Alliance Premier partner focusing exclusively on the IT Service Management sector, oering high quality consultancy for Program, Project, Technical and Operational Management Technical Architecture, Design and Development Systems Integration
document info Document Info Alderstone Customer Move Tool (CMT) oers unparalleled speed and reliable data migration capabilities for BMC Remedy ITSM applications. Enabling you to rapidly upgrade to the latest version of BMC Remedy ITSM, seamlessly migrate to the cloud or manage ITSM as a service. These release notes provides a detailed overview of the new features and improvements in Alderstone CMT release 2.0. page 1
what s new overview What s New Overview CMT 2.0 is a major upgrade with a significant expansion in both core capabilities and with new features. Our focus in this release has been on making installing and configuring CMT faster and easier, making data migration faster and we ve also added a huge suite of tools for the ITSM data migration engineer; improving the overall quality and speed of upgrades and migration to the cloud. CMT 2.0 provides significant improvements or new features in the following areas; Easier, faster configuration and set up Single, bundled installer Set up & validation wizards Automated database integration & configuration discovery Faster, more flexible data migration Multi-threaded import & export Tree based or flat export Configurable incremental deletion checking lists Migration Lists Custom Field Mapping Improved exception management Unique Index Violation Error analysis Migration Overview & searchable Export audit Improved application navigation Pre-defined Reports & export to CSV Data validation & reconciliation support Form Count discovery, reporting & comparison Application data discovery and comparison page 2
new features & enhancements New Features & Enhancements Please find below a detailed breakdown of the new features and enhancements in CMT 2.0. Please click any item to read more. Accelerated Installation & Set Up Simplified Installation PostgreSQL Repository Java 8 Set Up Wizard Alderstone CMT Services Automated Database Integration Set Up Database Character Set discovery File System Configuration File System & Connection Entities Easier Set Up Test Export to and Import from File System Discover & Build Application Data Remedy API Connectivity Discover & Build Workflow for SLA Targets, Agreements & Data Sources Discover & Build Workflow for Approval Notifications & Chains Form Data Reconciliation Compare & Reconcile Form Counts and Configuration Form Data between remote or local systems Application Data Discovery & Comparison Discover Application Data for key ITSM configuration Forms Compare Application Data, identify dierences & migrate selected records Server References Server Reference Discovery & Transformation Purge Data Improved Data Dictionary Discovery Current Flag to identify the latest valid discovery Discovery Dialog Run Discovery from System Configuration Multi-Threaded Discovery Data Migration Performance Multi-Threaded Data Migration Flat & Tree Based Migration Modes Data Migration Management Data Chunking Import Error Analysis Migration Overview Export Form Audit Migration Lists Create, Modify, & Modify with Qualification Stage Data Unique Index Violation Analysis Data Mapping & Migration Packs Easily create and add Migration Parameters Migration Pack Build Options Remove Unused Form Mappings Improved Field Mapping Controls Field Mapping Issues Report Data Enrichments Enhancements Custom Field Mapping Workbench UI Enhancements System Administration interface Runtime Templates radio buttons Improved Tool Bar Navigation Report to CSV Show/Hide columns User Preferences Multiple Select for Tables Embedded User Manual Entity name changes Full Screen Mode Remote System Archive Data page 3
accelerated installation & set up Accelerated Installation & Set Up Simplified Installation Previously CMT required a number of prerequisites to be installed and configured, including MySQL and Tomcat. Integration with these third-party components was manual and frequently challenging. The CMT 2.0 installation only requires Java 8 to be installed prior to the installation and will automatically install and configure embedded Tomcat and PostgreSQL. Optionally, the install package will also install the Microsoft command line tools to enable exports from MS SQL databases. This is one of the most frequently requested enhancements and will significantly improve the user experience of the installation and configuration of CMT 2.0. PostgreSQL Repository CMT 2.0 now uses PostgreSQL as the underlying database for the CMT Repository. PostgreSQL provides enhanced performance and features. Previous versions of Alderstone CMT used MySQL for the CMT Repository This change means that any data in your existing CMT Repository will be lost as part of the upgrade to CMT 2.0. Alderstone recommends that you export all Migration Packs, Data Enrichment Templates and Data Dictionaries (Versions) from CMT 1.5 prior to the upgrade. This data can be safely imported into your new CMT 2.0 installation. Java 8 CMT 2.0 now uses Java 8. Set Up Wizard CMT 2.0 provides enhanced support for the initial configuration including Welcome page with link to User Guide & Configuration Wizards Configuration Wizards for Analysis and Data Migration The configuration wizards can be accessed from the Help tab on the Home Page, please find an example illustrated below. page 4
accelerated installation & set up Alderstone Services An installation of Alderstone CMT will now create three services; Alderstone CMT Engine Alderstone CMT Repository Alderstone CMT Workbench Automated Database Integration Set Up Alderstone CMT requires a database user and database objects to be set up on the database before discovery or data migration can be performed. In Alderstone CMT 2.0, these scripts can be run by the CMT Engine to accelerate your initial set up. CMT also allows you to cleanly remove the cmt user and associated functions from the system. The database system administrator user name and password are required to set up the new user and create the associated database objects. This new feature can be accessed from the Action menu on the System page, as illustrated in the examples below. Database Character Set discovery Alderstone CMT 2.0 also allows you to quickly discover the database character set/collation. Select Get Database Character Set from the Action menu on the System page to run a query against the database server to get the details and save them for the selected Remedy system. If this detail is successfully obtained then the System will automatically be set to Available for Data Migration. page 5
file system configuration File System Configuration File System & Connection Entities Alderstone CMT migrates data by extracting to and from file systems The file system configuration is a key component in data migration, which in previous versions needed to be defined in several dierent locations in the application. File System connection may be used by the following actors File System CMT Engine, when creating Data Package folders and reading Data Package definitions. Database server when exporting or importing data to and from file CMT Engine or BCP when exporting or importing data to and from file In CMT 2.0, the file system configuration has been made easier to configure and understand. It is no longer necessary to define a path for a Remedy System or to set up the Engine for local export. Additionally, it will not be necessary to rescan a shared File System on import. File System Connection You may now define a File System entity and then define the connections to that entity from the CMT Engine and Database Servers in one location. Please find an example illustrated below. Easier Set Up Alderstone CMT now provides a detailed explanation about the mechanism for migrating data between your Remedy systems depending on the underlying database and file system configuration. Please find an example illustrated right. page 6
file system configuration A new interface enables you to define and save the specific migration path between two systems. Please find an example illustrated below. Test Export to and Import from File System Alderstone CMT 2.0, now allows you to validate your file system and database configuration, without needing to perform an end-to-end data migration. You may now validate; Exporting data from a Remedy System to a file system Importing data from a file system into a Remedy system These tests will use the same mechanism as would be used for a real data migration. For example, when testing Oracle to Oracle migrations,then CMT will test that the source Oracle database can export to the export file system and the target Oracle database can read from the import file system. Alternatively, when testing MS SQL to MS SQL migration, then CMT will validate that BCP can extract data from the source MS SQL to the export file system, and that the target MS SQL database can read from the import file system. page 7
discover & build application data Discover & Build Application Data Remedy API Connectivity Alderstone CMT now enables Remedy API connections to support the triggering of Remedy API actions such as workflow creation for migrated SLA or Approval objects. The Remedy API connection is not used to migrate or extract data which will continue to be migrated at the database layer. The Remedy API connection may be configured by enabling a System for API connectivity. A Remedy Administrator user should be provided to enable full access to Remedy data objects. Please find an example illustrated below. The connection details may be validated by selecting Test Remedy API Connectivity from the Action menu.. page 8
discover & build workflow for sla targets, agreements & data sources Discover & Build Workflow for SLA Targets, Agreements & Data Sources SLA Targets, Agreements and Data Sources may be safely migrated by Alderstone CMT. After migration, it is necessary to trigger these objects to be built by Remedy workflow. Previously in CMT, this was a manual activity, however CMT 2.0 provides the ability to discover the status of and selectively trigger the Remedy system to build the workflow objects for these migrated objects. Please find illustrated below an example of discovered SLA Target data for a Remedy system. Alderstone CMT now allows you to selectively trigger the build of SLA Targets, Agreements and Data Sources. You may choose to build only SLA objects which need to be built, or define your own qualification or (re-)build all SLA objects. Please see an example of the SLA Object build dialog illustrated right. page 9
discover & build workflow for approval notifications & chains Discover & Build Workflow for Approval Notifications & Chains Approval Chains and Approval Notifications may be safely migrated by Alderstone CMT. After migration, it is necessary to trigger these objects to be built by Remedy workflow. Previously in CMT, this was a manual activity, however CMT 2.0 provides the ability to discover the status of and selectively trigger the Remedy system to build the workflow objects for these migrated objects. Please find illustrated below an example of discovered Approval Chain data for a Remedy system. Alderstone CMT now allows you to selectively trigger the build of Approval Chains and Notifications. You may choose to build only objects which need to be built, or define your own qualification or (re-)build all objects. Please see an example of the Approval Chain build dialog illustrated right. page 10
form data reconciliation Form Data Reconciliation Compare & Reconcile Form Counts and Configuration Form Data After a data migration operation, its important to verify that the results of the migration are as expected. For example, when performing a full system upgrade migration, using previous versions of Alderstone CMT, we used a database script to get the number of records in each Form, manually ran this and extracted to a spreadsheet which was used to help validate that all data had been successfully migrated. Alderstone CMT 2.0 provides automation and support for this process of data validation; Run a form data discovery to get the number of records, maximum create date, maximum last modified date and, optionally, the number of records created after a specific create date for each Regular Form in your Remedy application. Compare Form counts to each other. For example, compare the counts between a source and target system and record actions and notes. Review data in four dierent ways; Individual - review the data for an specific discovery. Compare - compare two discovered form counts. For example from a source and target system or two discoveries for the same system over a time period. Three Way Reconciliation - compare three discovered form counts. For example between a source, target and the target prior to data import. Compare versus Compare - compare two discovered form counts with a previous comparison. For example, a source and target after a delta data migration compared to the same source and target after a previous data migration. Filter Forms in Comparison to include all forms, exclude Forms which have not had data imported or which are not in a Migration Pack. Quickly filter comparisons to identify discrepancies, hide and show columns in the comparison and export comparisons to CSV so they can be shared for wider review. Save comparisons reports so they can be reviewed over time or compared with each other. Export and import discovered counts to and from file. This allows these discovered counts to be imported and reviewed in another instance of CMT. This is useful when migrating from on-premise to the cloud where typically there will be two separate installations of CMT. Easily add a Form to a Migration List to enable rapid, targeted migration of data. page 11
application data discovery & comparison Application Data Discovery & Comparison Discover Application Data for key ITSM configuration Forms For the vast majority of Forms in Remedy ITSM, Alderstone CMT can be used to easily migrate data without impacting the data held in the new ITSM 9.1 application. However, there are a number of Forms in Remedy ITSM which hold data which needs to be carefully managed as part of an upgrade data migration. Some of these Forms hold data which cannot be changed via the standard application user interface and which are closely tied to ARS workflow changes and is only changed directly by a developer as part of an application customization. Alderstone CMT 2.0 now enables data for these Forms to be extracted into the CMT Repository and compared. The set of Forms and Fields to be extracted is fully configurable, and Alderstone templates are available. Please find illustrated below, the dialog used to trigger application discovery and a list of discoveries and summary of the form data extracted for each Form in the discovery. Compare Application Data, identify dierences & migrate selected records CMT allows discovered Form data to be viewed and compared with other discovered Form data. Please find illustrated right, an example of a comparison between AP:Form data on two systems. This shows source-only and targetonly and records which are matched between the two discoveries. For matched records CMT will compare core and non-core fields to identify those with dierences. The field by field comparison is shown right. It s possible to define the criteria by which records are matched, for example you may use Request ID, or Instance Id, or any combination of fields. The default matching is copied from the Form Mapping Match On clause. CMT also allows you to extract the data for any discovered data or comparison to CSV so it can be shared with a wider audience. Selected records may be added to a Migration List for targeted migration of application configuration data between systems. page 12
server references Server References Server Reference Discovery, Transformation, & Purge Data held within Remedy ITSM systems may have specific environment or system references which are no longer valid when migrated to another environment. For example, when copying your ARS Database from Production to Development, you do not wish the AR Email Mailbox Configuration to continue to refer to the Production environment. Alderstone CMT 2.0 now provides the ability to identify, review and transform ITSM data with server references, to support both data migration and the copying of ARS databases between environments. Furthermore, CMT also provides the capability to delete data from both Remedy Forms and database tables to ensure that server-specific data is not copied between environments. CMT oers the following advantages over other utilities which help manage environment references; Remedy ITSM is highly inconsistent in the use of references. CMT identifies the references which are actually in the data, rather than assuming the values which need to be updated. CMT performs the discovery and transformation at the database layer. This avoids having to start a Remedy system with incorrect server references in it which may cause service-impacting issues. CMT enables purging of data from both Remedy Forms and underlying database tables Alderstone provide pre-prepared templates, which are fully configurable, which identify the Forms and Fields where server reference data may be held and the Remedy Forms and data should be purged. Please find illustrated below an example of a discovery of environment references for a system. Please find illustrated below an example of the Purge Data and Transform Server References functionality. The tables and Remedy Forms in the Purge Job are defined in the Alderstone Template and may be enabled or disabled. The Transform Job enables you to identify the values you wish to replace in each Form and Field from which data was discovered. page 13
data migration performance Data Migration Performance Multi-Threaded Data Migration Typically, Alderstone CMT is able to migrate data as fast as the database and infrastructure will allow it to using just one data export or import thread. However in some environments, additional threads can improve performance. Previously, it was possible to run multiple jobs in parallel to enable multi-threaded export. However, this required a high level of configuration eort. CMT 2.0 allows you run a data export or import operation with multiple threads. Please find illustrated below an example of the new Create Migration dialog showing the ability to select multiple threads for the export operation. You may turn CMT threaded migration up to a maximum of 11. In the majority of cases, multi-threading will not be necessary, but this capability can make a significant dierence to overall processing time in some cases e.g. out-of-row-clobs, or can help to reduce the time of a final cutover data migration. Please note that multi-threading will significantly increase the impact on the infrastructure in both processing load but also on disk space as the number of temporary tables which are in use at the same time will be increased. page 14
flat & tree based migration modes Flat & Tree Based Migration Modes Alderstone CMT enables any related set of Remedy data to be safely migrated between Remedy systems. The ability of CMT to perform tree-based migration of related data is unique to CMT and enables a range of (previously impossible) use cases to be supported. For example, we can add a date range parameter to the HPD:Help Desk node in the tree to include only Incidents created within the last 6 months. CMT will automatically cascade this filter down the tree, so that only the Work Logs which belong to those Incidents are included in the scope of migration. CMT will only migrate the data within the scope of the migration tree. Remedy ITSM does not enforce data integrity in the ITSM application which means that orphaned data is very frequent. For example, your Remedy ITSM system may have some Work Logs which do not have a parent Incident, these may have been created for an Incident which was never submitted and which the Remedy ITSM application did not clean up. The benefit of using CMT is that all of this orphaned data was left behind; CMT automatically improves data quality as part of the data migration. However, some Remedy systems have a very high level of orphan data, which when performing a Remedy system upgrade resulted in discrepancies which took time to investigate, identify as an orphan and then explain and get the sign o of the business to leaving behind junk data which they can t see or use! Alderstone CMT 2.0 now allows you to perform a Flat or Tree based migration. Tree-based migration will work exactly as it does now. Flat migration will behave dierently; If possible CMT will export ALL data for a a Form, this will ignore the parent qualification, and eectively take all data including orphan records If a Form exists in multiple locations in the tree then CMT will only extract the data once If a Form or its parent has runtime qualifications then the export will continue to be processed using the tree-based method. Typically there will be mixture of Flat and Tree-based Form exports when a Flat Export is requested. CMT will show the export mode for each Form in the Export Job. Performance for flat export operations will be significantly faster than for a tree-based export. The tree-based export requires CMT to run qualifications against the database, flat export will simply take all data. Incremental export must use the tree-based method as the tree structure is essential for safe migration of deletions The key benefits of this enhancement are; Faster exports Less time managing orphaned data discrepancies The only disadvantage of using flat export is that orphaned data will be carried forwards to the new system. page 15
data migration management Data Migration Management Data Chunking It is possible to select individual Forms with very high volumes of data and restrict the number of records which CMT will export for that Form in any single operation. All in-scope data for the Form will be exported, but the load on the database will be reduced by chunking the data export. Forms which have been exported with data chunking will also be imported in chunks. The minimum chunk size is 500,000 records. Migration Overview CMT 2.0 provides a new view for the Migration Job which shows provides the following overviews; Export - Summary per Form showing the total number of records exported, number of times the Form is in the export and the result of the export Import - Summary per Form showing the total number of records imported, number of times the Form has been imported and the result of the import Exported Versus Imported - For each node which was exported, shows the total number of records exported and imported, the number of import attempts and indicates whether the number of records exported matches the imported records. Data Package Forms - shows number of records, total size of data files for the exported form for each form in a Data package These views makes it much easier to identify which Forms have not yet been migrated successfully in complex migration scenarios or where multiple imports have been attempted. Please find illustrated below an example of the Exported Versus Imported report for a Migration Job. page 16
export form audit Export Form Audit Alderstone CMT provides a search-able audit of all import and deletion activities. CMT 2.0 extends this capability to enable the Export audit to be searched. This capability is available on the Audit tab of the Home page. Please find an example illustrated below. Migration Lists Alderstone CMT is very good at migrating large data sets defined in the Migration Packs. However, it has previously been cumbersome to re-migrate individual records or Forms. Alderstone CMT 2.0 makes it easy to create a custom migration for selected Forms or records. It is now possible to create a Migration List and to add Forms or records into the Migration List. A Migration List can be converted to a Migration Job which will use the defined Form Mappings defined in the Migration Packs. Please find illustrated, left, an example showing defined Migration Lists available on the Form Data Reconciliation page. You may add Forms or individual record(s) to a Migration List. When adding a Form you may choose to include the child Forms in the tree or migrate only the Form data. You may apply a Qualification to filter the data for a Form, and check the number of records which will be returned by your qualification. page 17
create, modify, & modify with qualification Create, Modify, & Modify with Qualification Alderstone CMT 2.0 allows you to define the Import behavior for a Remedy Form. By default, all migrated records will be merged into the target Form; any records which do not exist will be created and any records which exist will be updated. In Alderstone CMT 2.0, you may override this default behavior by setting the Import Action. Please find illustrated below an example of the Import Action dialog which enables you to set the import behavior for a Form Mapping. The import action will be shown on the Form Mapping as illustrated in the example below which shows that AAS:Activity is configured to only modify records where the Last Modified Date of the imported record is greater than the Last Modified Date of the target record. Please note that Create is disabled, therefore any records which do not match records in the target system will not be imported. This feature provides very powerful and flexible control over the import behavior. page 18
stage data Stage Data Alderstone CMT 2.0 allows you to load the T-table data for any Form in a Data Package as a temporary table on a Remedy database. This feature allows you to examine and compare the data to help resolve import errors. Please find illustrated below the Stage Data button which is now shown for the data package and the staging dialog which allows you to define the name of the temporary table which will be created and even limit the number of records which will be staged. CMT 2.0 allows you to subsequently drop these staged tables from the System Administration interface. You may also discover and drop any staged tables which may have been created by CMT. Please note that CMT will always remove any temporary tables after an export or import operation, but in the event of a catastrophic failure, this facility allows you to conveniently remove any temporary tables from the database. page 19
unique index violation analysis Unique Index Violation Analysis CMT 2.0 now enables the analysis of unique index violation errors when importing data to identify the root cause of these issues. Unique Index violations can occur for a variety of reasons; new unique indexes are added to the new application, or when moving from a case insensitive to a case sensitive environment. When a unique index violation error occurs, CMT will enable you to review the details of the failure as illustrated in the example below. The Unique Index Analysis dialog will show the following details; Identification of the root cause and the unique index which prevented the import Details of the data mapping and match on clause Evaluation of common causes of unique index violations. Please see example, right. All unique indexes on the target, explicitly identifying with any new unique indexes which do not exist in the source system CMT 2.0 enables the specific records which are causing the unique index clash to be extracted from the imported and target data set for comparison within CMT. This is a significant enhancement for engineers using CMT which will accelerate and de-skill the fault finding process which occurs when performing migrations which tend to result in unique index violations such as cross database migrations. page 20
data mapping & migration packs Data Mapping & Migration Packs Easily create and add Migration Parameters Alderstone CMT 2.0 makes it much easier to add parameters to a Migration Pack. Previously, you had to define the Migration Parameter before being able to add a filter to the tree. You may now dynamically define a Custom Qualification to add to a Form in the tree, or select from the predefined parameters. Please find illustrated below, the new dialog which enables you to configure a Custom Qualification and the new display of parameters for a selected Form in the tree. Migration Pack Build Options In CMT 2.0, when copying a Migration Pack, you may optionally choose to remove any unused Form Mappings as part of the copy operation. page 21
data mapping & migration packs Remove Unused Form Mappings The ability to remove unused Form Mappings, is now also available from the Data Mapping page. This action will remove any Form Mapping which is not being used in the Migration Tree. Improved Field Mapping Controls CMT 2.0 supports a range of new automated field mapping management capabilities; Ignore Unmapped Fields - automatically sets all source and target unmapped fields to Ignore Ignore All Errors - automatically sets all field mapping issues with errors or warnings to Ignore Auto Map All Unmapped Fields - automatically maps any unmapped fields Field Mapping Reporting Alderstone CMT 2.0 now enables you to output a list of mapping related reports a CSV file. Field Mapping Issues Report - list of all fields which have a mapping issue which needs review e.g. a target field is smaller than the source field being mapped to it. Enum Mapping Issues Report - list of all enum fields which have enum mapping issues and the details of the enum mappings which are aected e.g. Status field has been customized with additional values on source which do not exist in the target system. Custom Mappings Report - list of all fields mappings which are non-standard e.g. transformed, mapped to a dierent field id Data Enrichments Enhancements Alderstone CMT 2.0 provides a number of enhancements to the Data Enrichment feature; Target Data Enrichments may now be configured with dynamic, multi-level joins Data Enrichment Templates support all types - Data Enrichment Templates may now be configured for Source and Target Data Enrichment types. Previously this was limited to Mapping Data Enrichments only. Data Enrichment Templates now support dierent source and target Data Dictionaries. It was previously only possible to use one Data Dictionary as a template when creating a Data Enrichment Template. Filter Data without mapping a field - Data Enrichments can be used to filter the data which is exported or imported by configuring an INNER join to the data mappings. This filtering was previously only applied if there was a field mapping from the data enrichment. In CMT 2.0 this filtering will work regardless of whether there is a field mapping for the data enrichment. This now allows you to filter data based on a source or target lookups from a dynamically created multi-level join. For example, you can exclude an Incident from an archive data migration if there is a relationship to an open Change. Modify Data Enrichment - you may now modify key details for a previously created data enrichment. page 22
custom field mapping Custom Field Mapping Alderstone CMT 2.0 introduces a new, powerful field mapping type. The Custom field mapping allows multiple fields, data enrichments and transforms to be combined. This feature enables field concatenation or arithmetic operations involving any combination of source fields, data enrichments and transformation. Please find an example of a field using the Custom field mapping type, illustrated below. page 23
workbench ui enhancements Workbench UI Enhancements System Administration interface The new System Administration interface provides a single user interface enabling access to the following range of functions for a Remedy system. Data Dictionary Management Approval Chains Discover & Build Approval Notifications Discover & Build SLA Data Source, Agreements & Target Discovery & Build Export Jobs Import Jobs Server Reference Discovery & Transform Data Analysis Discovery & Review Data Updates Staging Tables created by CMT Runtime Templates radio buttons Runtime templates are now displayed on a Migration Pack as a set of radio buttons rather than a table. Improved Tool Bar Navigation The toolbar has been completely reorganized to make it easier to navigate around the expanded application. page 24
workbench ui enhancements Report to CSV Alderstone CMT 2.0 allows you to export the content of any table to a CSV file. Right-click on a table and then select Export Data. Only the visible columns and rows will be exported i.e. any data filtering applied to the table will be reflected in the exported csv file. Show/Hide Columns Alderstone CMT 2.0 allows you to hide and show columns in tables. These changes are persistent and will be stored in your browser cookies. A number of tables in the application have additional columns which are not visible by default, for example Data Mapping Fields and Form Data Comparisons. User Preferences You may now define the your application User Preferences from the toolbar User Account Preferences Enable Animation - you may disable animations within the application which can slow down the user experience when using CMT over a Remote Desktop connection. Error Messages - by default error messages are only displayed for a short period before being dismissed. Setting this option to Manual Dismiss will not hide error messages until they are manually closed. page 25
workbench ui enhancements Multiple Select for Tables Alderstone CMT 2.0 now enables you to select multiple records. This feature is enabled only for key tables where multiple select is eective. The example illustrated below shows multiple-select on the Add Forms table of the Migration Pack. Embedded User Manual The Alderstone CMT user manual is now bundled in the application. Context sensitive links will link from the application to the relevant section of the documentation when the icon is clicked. Please see the example illustrated below which shows the welcome page for a new installation. Full Screen Mode On both the Form Reconciliation and Data Mapping pages you may enable Full screen mode which will use the full width of the available screen. This enables easier management of the data displayed in the tables on these pages. Entity name changes Alderstone CMT 2.0 makes the following changes to entity names; Version Data Dictionary Export Package Data Package page 26
archive data Remote System Alderstone CMT 2.0 enables a System to be flagged as Remote. A Remote System represents a system which cannot be connected to from the local installation of CMT. This feature is intended to provide better support for On Premise to Cloud migrations. A Remote system is displayed dierently throughout the application, as displayed below-left.. There are fewer required fields when configuring a remote Remedy System, as illustrated in the example right. Archive Data Alderstone CMT 2.0 now allows you to flag Migration Packs and Migration Jobs as archived. After being flagged as archived, these Jobs and Packs will no longer be visible within in the application. The imports and exports for a Migration Job will continue to be visible in the audit. The new archive console allows you to review archived data and restore it. page 27
improved data dictionary discovery Improved Data Dictionary Discovery Current Flag to identify the latest valid discovery CMT 2.0 allows you to set a Data Dictionary with a Current flag. Only Data Dictionaries set with the Current flag are available in application menus. Discovery Summary A summary of the number of Forms, Overlaid and Custom Forms, Fields, Data Field, Overlaid & Custom Fields, Enums and Indexes is now displayed for a Data Dictionary. Discovery Notes CMT 2.0 allows notes to be recorded for a Data Dictionary. Discovery Dialog CMT 2.0 provides a new Data Dictionary discovery dialog which enables the newly discovered Data Dictionary to be set as the Current, or to open and track the discovery progress. Run Discovery from System Configuration Data Dictionary Discovery can be initiated from the System configuration page. Select a system and then select Discover Data Dictionary from the Action menu. Multi-Threaded Discovery Alderstone CMT 2.0 now uses multi-threaded discovery to improve the overall performance of discovery. page 28