9.5.2       Import an XML into a Version (Plane)

You can import an XML to create a new copy of the trial design. Importing can also be used to migrate a trial into a different environment. For example, from Quality Assurance Testing to User Acceptance Testing.

 

Notes:

·         During import, the validation engine only processes client-side in-form edits and depends on the VTS (Validation Task Service) to execute the remaining edits.

·         Patients with the same subject number and unique value are not imported when the following validation errors occur:

o      Unique value required error

o      Edit script error (ex. Edit JavaScript has a programming error)

o      Data value error (ex. when characters entered in integer type textbox)

·         If you only want to import export templates (see Import Export Templates for more information).

·         You can also copy from another trial using TrialBuilder to create a new copy of the trial design. (See "Copy from Trial" in the TrialBuilder 5.1 online help/user manual for more information.)

To import an XML into a version (as part of a new trial build promotion or Mid-Study Change deployment):

1.      Access the Trials page. (See View Trials for guidance.)

2.     Click the Versions link of the applicable trial under the Action column.

The Versions page displays.

3.      Click the Import link of the applicable (unlocked) version under the Action column.

The Import dialog displays.

4.     Do the following to complete the dialog:

·         Click the Choose File button and open the import file. The file name displays next to the Choose File button.

·         Accept the default Use VACE (Value Auto Correction Engine) as checked. This option corrects the imported XML data according to TrialBuilder’s object value constraints.

·         Select the Clear the version content first check box. This will clear the objects in the current trial version and replace them with the latest study design in the imported XML.

 

Important: Do NOT select the “When internal ID doesn’t match use” check box as this will result in the import XML contents being merged into the latest trial version/protocol plane.

·         Click the Finish button. The text box at the bottom of the dialog displays the import status.

·         When "Publish Version Completed" displays in the text box, click the Finish button. If there were conflicts during the import, a window displays, listing each conflict and prompting you with the following options for resolving them, depending on the conflict type:

o      Discard – leave the existing object in place.

o      Overwrite – replace the existing object with the incoming object.  Not available for OID conflicts on already-published objects.

o      Rename – import the incoming object but enter a new name in the “New Values” field (see the following image).

o      AutoRename – import the incoming object but add a suffix of “_1” to its current name (if “_1” is taken, it will add “_2” and so on).

·         If you had a conflict, after choosing an option for each conflict, click OK. (To resolve all conflicts having the same Object Type and Conflict On, select Apply to similar conflicts.)

5.      Click the Go Back button at the top left of the Versions page to return to the Trials page.