This section allows the user to specify options that will be applied to all mappings:
Notes on Add Missing Custom Tables/Fields options (Service Now Instance Migration Only)
Caution - use of these options may create additional fields and these may be visible to end users through the default table view. Use with care in a production environment.
These actions will only be carried out on the tables selected in the Form Selection section of the wizard.
Precision Bridge will ONLY create tables that are prefixed u_ and do not exist on the target server. All fields on custom tables will also be migrated.
Similarly, Precision Bridge will only create fields that are either:
- prefixed u_ and do not exist on the target server
- belong to a custom table (u_ prefixed) and do not exist on the target server
Precision Bridge will create a field on the target server with:
- The same name and default label as the source
- The same type and length as the source
- If a reference or list field, the same referenced table as the source
No other field properties will be migrated, including any choice values. These will need to be added manually.
The fields will be added to the default view only for the table only. They will always be added at the bottom of the view.
Notes on the Delta Migration Option
The delta migration option is intended to provide a project that will only migrate records that were created or updated since the last migration.
- For ServiceNow instance migration projects, the following source filter will be added to all mappings:
- For ServiceNow instance migration projects, If a parent record has been specified for the table in the Mapping Options section, the following inclusion filter will be added to ensure that only records where the parent record exists on the target are migrated.
- For Remedy to Remedy (Replatforming) projects, a similar source filter will be added to restrict the migration to updated records, using the source field with ID=8 (usually named Last Modified Date)
For example, if the incident and journal entry tables are selected, with incident being identified as the parent of journal entry, only journal entries for incidents that exist on the target will be migrated, preventing 'orphan' journal entries from being migrated to the target server.
Saving the Definition
At this stage, if required you can save the current definition model, as defined in the tabs as an XML file by using Save Definition button.
- If the definition was loaded using the ‘browse’ option on the load tab, the default save location should be the loaded file.
-
If the no definition was loaded, or was loaded from an OTB template, the default folder should be <User Documents>/Precision Bridge Projects/Form Mapping Templates.
Next Step
Once all required options have been selected, click 'Generate Mappings' to start the process of adding the requested mappings to the project.
Related Articles
Comments
0 comments
Please sign in to leave a comment.