This release has an initial version number of 7.2.11.
Listed below are the enhancements included in this release:
List of Changes
1. Enhanced Form Mapping Generation for Service Now Instance Migration
The Generate Form Mappings wizard for ServiceNow to ServiceNow instance migration has been enhanced to allow:
- Load and Save of a mapping generation definition
- Definition of Parent/Child relationships between mappings, so that only 'child' records for the migrated parents are themselves migrated. This is implemented using a Precision Bridge Inclusion Filter.
- Configure migration of attachments
- Creation of a Reference Mapping for any reference field in the project to handle situations where the sys_id of the referenced record on source/target are different.
- Creation of custom tables and fields on the target server where customizations have been made to the source server (global scope customizations only)
- Define whether the project is for a 'delta migration' (where only records added or changed since the last migration should be migrated)
Further information can be found here: Generate Form Mappings for Service Now Instance Migration
2. Migration to Jira Instance
Migration of data into a Jira instance from any supported source platform is now supported. This includes the following support:
- Issue Migration (includes Incident/Problem/Change and Service Request issue types)
- Issue Attachment migration
- Issue comment migration
Note that subsequent releases will be extending the capability of this to include additional areas of Jira Service Management and other Jira applications.
Further information can be found here: Migrating data to Jira Service Management
New and Updated Templates
The following templates are new or updated in the May Release of Precision Bridge 7.2:
| Template | Description |
|
NEW: Cherwell to Ivanti -> Knowledge |
Migrates Knowledge Article Data into Ivanti |
Advice To Users Upgrading from Precision Bridge 7.0 or earlier
The Use Server ID's Key Mapping option was removed from Precision Bridge 7.1. If this Key mapping option has been used in a project built with Precision Bridge 7.0 (or earlier), the Key Mapping option will default to 'No Key Mappings' when opened in Precision Bridge 7.1 or later.
Note that none of the Precision Bridge Templates used this option in earlier or current versions of Precision Bridge. If you have projects that use this option, be sure to select an alternative key mapping option to use (such as by selecting Key Field Mappings) before executing the project with Precision Bridge 7.2. Failure to do this may result in duplicate records being created if the project is run a second time to update existing records.
Other than the above, projects built using Precision Bridge 7.0 will still work with Precision Bridge 7.2 with no changes required.
Licences for 7.0 and 7.1 will still work for 7.2.
Comments
0 comments
Please sign in to leave a comment.