Form Mapping Options

To define additional options for a given Form Mapping, navigate to the Options tab for the selected Form Mapping. The following General options are presented and explained in more detail in the table below:

Field	Options	Description
Enabled	Checked; Unchecked	If checked the form mapping is migrated otherwise it is skipped during execution.
Business Hours Restriction	None; Migrate Out of Hours Only	If set to migrate out of hours only, then this form mapping will not be migrated during the specified business hours.  See the later section on defining business hours.
Entry Exists on Target Action	Define at Execution; Error & Continue; Skip Entry; Update Entry;	If Define at Execution is selected, the global execution options for this apply, (see section on Execution Options).  Otherwise, the specified option for this form mapping takes precedence over the global setting.
No Entry Exists on Target Action	Define at Execution; Error & Continue; Skip Entry; Create New Entry;	If Define at Execution is selected, the global execution options for this apply, (see section on Execution Options).  Otherwise, the specified option for this form mapping takes precedence over the global setting.
Migration Method (Remedy Target Servers)	Define at Execution; Set & Create Merge	If Define at Execution is selected, the global execution options for this apply, (see section on Execution Options).  Otherwise, the specified option for this form mapping takes precedence over the global setting.  Only applies to target Remedy servers.
Migration Method (ServiceNow Target Servers)	Direct; Import Set (Field Mappings)Import Set (Scripted)	If Define at Execution is selected, the global execution options for this apply, otherwise specified option defined here takes precedence. Direct performs direct inserts/updates on the target tables; No import sets are used. Import Set(Field Mappings) uses import set with mapped fields to migrate the data; If this option is selected then the option to run business rules is also available; Import Set (Scripted) uses a transform map script to migrate the data. If this option is selected then the option to run business rules and the option to migrate Sys Ids are also available.  See separate article on use of Execution Option Import Set (Scripted)
Run Business Rules (ServiceNow Target Servers)	Define at Execution; Yes; No;	If Define at Execution is selected, the global execution options for this apply, otherwise specified option defined here takes precedence.  Only applies when migration method is Import Set (Field Mappings) or Import Set (Scripted).
Migrate Sys ID’s (ServiceNow source and target servers)	Define at Execution; Yes; No;	If Define at Execution is selected, the global execution options for this apply, otherwise specified option defined here takes precedence.  Only applies when the migration method is Import Set (Scripted).
Reporting Level	Define at Execution; None; Errors & Warnings; Un-migrated Entries and Warnings; All Entries	If Define at Execution is selected, the global execution options for this apply, otherwise specified option defined here takes precedence to control the type of errors and warnings for this mapping that will be included in the reporting output.
Report Source Field	All fields from the source table	Leave blank to use the default (Sys-ID for ServiceNow or unique identifier for other platforms).  The selected field will appear in all reports generated by this project and will be saved in the corresponding xml report file.  Care should be taken when using this option to avoid any data privacy issues regarding storage of sensitive data.
Report Target Field	All fields from the target table	Leave blank to use the default (Sys-ID for ServiceNow or unique identifier for other platforms).  The selected field will appear in all reports generated by this project and will be saved in the corresponding xml report file.  Care should be taken when using this option to avoid any data privacy issues regarding storage of sensitive data.
Ignore NULL Target Values	Define at Execution; Yes; No;	If Define at Execution is selected, the global execution options for this apply, otherwise specified option defined here takes precedence.
Attachment Migration Option	No Attachments; Selected Attachments; All Attachments; Attachments from URL (CSV Source Only);	See separate section on Migrating Attachments for further information

In addition, there are some advanced options, shown below. These are explained in the table:

Field	Options	Description
Migration Chunk Size	Numeric Value	Where an inclusion filter is not used, this defines the number of records that will be fully processed (retrieved, transformed and migrated - optionally with attachments) at a time before further records are retrieved. Leave this set to 0 (zero) to use the default global value defined at execution (see Execution Options section)
Migration Inclusion Chunk Size	Numeric Value	Where inclusion filter is used, this defines the number of 'parent' records whose 'child' records will be retrieved for before processing the records found. (transformed and migrated - optionally with attachments) before further records are retrieved. Leave this set to 0 (zero) to use the default global value defined at execution (see Execution Options section)
Max Retrieval Size	Numeric Value	Defines the maximum number of records that can be retrieved from the server in a single call.  This can be useful for very large records, where timeouts on the source server is an issue, or where the source server limits the number of records that can be retrieved. If the chunk size is less than this, the chunk size will take precedence. Leave this set to 0 (zero) to use the default global value defined at execution (see Execution Options section)
Batch Submit Size	Numeric Value	This option only applies to target servers that support batch operations when submitting or updating records. Defines the maximum number of records that can be submitted to the target server in a single call.  This can be useful for very large records, where timeouts on the target server is an issue. If the chunk size is less than this, the chunk size will take precedence. Leave this set to 0 (zero) to use the default global value defined at execution (see Execution Options section)
Batch Source Delete Size	Numeric Value	This option only applies to migrations that support source deletions Defines the maximum number of records that can be processed in single deletion operation.  This can be useful for very complex or slow deletions, where timeouts on the target server is an issue. If the chunk size is less than this, the chunk size will take precedence. Leave this set to 0 (zero) to use the default global value defined at execution (see Execution Options section)
Max Retrieval Threads	Numeric Value	This option only applies to migrations where the source server supports multithreading of data retrieval. Defines the maximum number of threads that can be utilized to retrieve data from the source server within a chunk. Each thread will retrieve the amount of data specified by the Max Data Retrieve Size but run concurrently to improve performance when retrieving the data. See Multi-threading for data extraction for more information. Note that the Max Retrieval Threads can also be set in the execution settings on the Performance Tuning tab If non zero, the form mapping options setting takes precedence over the Execution setting. This option only applies to migrations with a Service Now source server.
Max Submit Threads	Numeric Value	This option only applies to migrations where the target server supports multithreading of data inserts/updates. The Max Submit Threads defines the maximum number of threads that can be utilized to create or update data on the target server within a chunk. Each thread will submit the amount of data specified by the Batch Submit Size but run concurrently to improve performance when creating or updating the data. See Multi-threading for data creation and updates for more information. Note that the Max Submit Threads can also be set in the execution settings on the Performance Tuning tab If non zero, the form mapping options setting takes precedence over the Execution setting.
Max Source Delete Threads	Numeric Value	This option only applies to migrations that support Source Deletions (for example Service Now -> Database) The Max Source Delete Threads defines the maximum number of threads that can be utilized to create or update data on the target server within a chunk. Each thread will submit the amount of data specified by the Batch Submit Size but run concurrently to improve performance when creating or updating the data.  Note that the Max Source Delete Threads can also be set in the execution settings on the Performance Tuning tab If non zero, the form mapping options setting takes precedence over the Execution setting.
Import Set and Scripted Web Service Application	Define at Execution; global; ITSM Bridge HR Migrator; Precision Bridge Remedy Migrator; Instance Migrator; Archer Migrator;	If Define at Execution is selected, the global execution option for this applies (see article: Defining Advanced Migration Options), otherwise specified option defined here takes precedence. Controls which application to use to store the corresponding import set for this mapping. Applies to Service Now targets only.
Use this application's role	Checkbox	If selected, the role for the corresponding application will be used to migrate data for this form mapping.
Verify Source IDs		This option only applies to migrations with a Service Now source server. Performs additional verification to ensure all source records are retrieved when migrating from an active source server where source records could be created, updated or deleted during the migration. This option requires additional memory during processing.
Append Source ID to Attachment File Names	Checkbox	This option only applies to migrations from Remedy->Service Now If multiple attachments with the same name are recorded on a single record, you can force the file name on the target server to have the ID of the attachment appended to it to ensure it is unique. This can prevent attachments not being migrated due to PB thinking that they already exist on the target server.
Force Execution in Sequence	Checkbox	This option is only relevant if the execution options allow multiple form mappings to be executed in parallel. If this checkbox is checked, the execution of this form mapping will never start before all earlier ones have completed execution.