This release has an initial version number of 8.0.15.
If an existing version of Precision Bridge is installed, this version will be installed alongside it.
Users upgrading to 8.0 from earlier versions will need to request a new licence from Precision Bridge.
Listed below are the enhancements included in this release:
List of Enhancements
1. Improvements to Source Record Deletion for Database Archiving
It is now possible to configure multiple threads to perform the source deletions when archiving records in Precision Bridge. In tests, this has resulted in a 1000% improvement in performance when performing source deletion operations.
It is also possible to configure the number of source deletion operations that are performed at a time. This enhancement is intended to prevent timeout issues when performing deletions and related checks.
These configuration options are on the Performance Tuning tab of the Execution options. More information can be found in the articles:
Performance Tuning in Precision Bridge
2. Ability to write Precision Bridge report data to a ServiceNow server.
In addition to the ability to write reports to a database, it is now also possible to write the reports to a ServiceNow instance. Included in the Precision Bridge install is a Service Now update set file containing all of the table and UI definitions required for this feature. This feature will prove useful to all users that are migrating to/from a service now instance
Further information can be found here:
Reporting to a Service Now Instance
3. Remedy to JSM Migration Templates
Templates are now available providing a framework of mappings that migrate ITSM ticket and CMDB definition data from BMC Remedy into Service Now.
More information on how to use these templates can be found here:
All BMC Remedy ITSM to Jira Templates
4. Ability to write Field Mapping Reports to Database
It is now possible to write the form and field mappings for any project to the reporting database. The user can then query the database to:
- compare different versions of a project
- report on how fields are mapped, or which are not mapped.
Oracle, SQL Server, Postgres and MySQL databases support this feature.
Further information can be found here:
Writing Field Mappings to the Reporting Database
4. Licencing Changes
Precision Bridge Licencing has changed significantly in version 8.0
Trial Licences (previously Evaluation licences) give full access to all features of Precision Bridge for 10 days. There is however a limitation that only a maximum of 50 records can be migrated for each for mapping.
Subscription Licences (previously Rental licences) require the user to identify the source and target connections they will be migrating from and to when requesting a licence. There is a cost associated with each production server licenced. For each production server licenced, Precision Bridge typically allows 2 additional non-production servers to be licenced at no additional cost.
When requesting a licence, the user will need to add all the connections for the production and non-production servers/instances that want to migrate to/from.
Further information can be found here:
New or Updated Templates
The following additional templates were added in this release:
| Source->Target Server | Name | Notes |
| Remedy->Jira | Service Requests | This template can be used as a basis for developing a project to migrate BMC Remedy Service Requests, together with related work orders, tasks, attachments and Work Information records into a JSM Project. JSON files are also generated to allow the comments/worknotes and status of the created service requests to be easilly imported onto the JSON server. |
| Remedy->Jira | CMDB | This template can be used to replicate a BMC Remedy CMDB in a Jira Asset Schema. Class Inheritance is maintained and all cmdb fields are added as object type attributes in Jira. |
| Remedy->Jira | Incident, Problem & Change | This template can be used as a basis for developing a project to migrate BMC Remedy Incident, Problem and Change tickets, together with related tasks, attachments and Work Information records into a JSM Project. JSON files are also generated to allow the comments/worknotes and status of the created service requests to be easilly imported onto the JSON server. |
Notice of Support Termination
With the release of Precision Bridge 7.3, support was withdrawn for Precision Bridge 6.3 and below. Customers still using these versions are advised to upgrade to a later release.
Currently, supported versions of Precision Bridge are: 8.0, 7.4, 7.3, 7.2, 7.1 and 7.0.
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 8.0. 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 and above will still work with Precision Bridge 8.0 with no changes required.
Comments
0 comments
Please sign in to leave a comment.