|
Visual Intercept 4.0 provides administrators with an Import Wizard that assists with the migration of Visual Intercept 3.5 data into the Intercept 4.0 database. Using the Import Wizard, administrators can map specific categories of incidents to different classes of issues in Intercept 4.0 or simply import the existing incidents to the incident class.
To use the Visual Intercept Import Wizard logon with the IssueNet Administrator to the Intercept 4.0 database that you want to import to. Select the File | Import... menu option. Select the Visual Intercept 3.x format in the Format Selection dialog and click the OK button.
The Visual Intercept Import Wizard will follow these steps;
      
Visual Intercept Database Import Options
Select the Visual Intercept 3.x data source name from which data should be imported. Provide the Visual Intercept 3.x administrator user name and password. You should have a client installation of the Visual Intercept 3.x product on the same machine that you are performing the import from to have access to the Visual Intercept 3.x SDK. Additionally, the client installation of the Visual Intercept 3.x component will handle configuration settings such as data source and document directory values that are used during the import process.
Visual Intercept Import Incident Mapping
Intercept 4.0 expands the definition of an incident to include a variety of issues such as defects, requirements, general issues, or your own custom types. During the import process the old incidents are converted to the new issue types by using the incident category. In this way you can import Visual Intercept 3.x incidents to the different Intercept 4.0 issue types in a single pass.
If you simply want to replicate all incidents into the new Intercept 4.0 database or you are doing a quick evaluation of the changes in Intercept 4.0 and wish to use your historical data as a sample select the Use Default Mapping option. This will import all the incidents as an Intercept 4.0 incident item that is mapped to the Visual Intercept 3.x definition.
If you simply want to import your incidents into your own custom class or to a variety of new Intercept 4.0 issue classes, select the Select mappings options.
Visual Intercept Import Custom Mapping
If you select the Select mappings option you will then be able to select which Intercept 4.0 issue type to create for an incident based on its category. Select the Issue Class that you wish to create, then select the incident categories to map to that class in the category list. Click the Appy Mapping button to associate the issue class with the incident category. Follow this procedure until all incident categories have been mapped to an appropriate issue class.
Visual Intercept Import Options
During the import process Intercept 4.0 tasks will be generated for the imported issues. These tasks will be created on a default project. The Visual Intercept 3.x status promotion model will be converted to an Intercept 4.0 workflow that will be related to this default project. Additonally, IssueNet resources will be generated for all the Visual Intercept 3.x users that are imported and related to the default project as well.
Intercept 4.0 enforces property values based on type which may cause failure on import from historical Visual Intercept 3.x data such as malformed email addresses. Select the Ignore invalid property values option if you wish the import process to proceed regardless of data format issues. The output window will include the information needed to clean up the property values.
Visual Intercept Default Options
Document attachments in Visual Intercept 3.x will be imported into a Native Document Store in Intercept 4.0. Select the Document Store to place the imported attachments into.
Related source code information in Visual Intercept 3.x will be imported into a SCCS Database reference. This data is only a reference. No actual source code will be imported. Select the SCCS Reference to place the imported references under.
|