Home → Using LincDoc 3.0 → eForm Administration → Import/Export forms

4.12. Import/Export forms

LincDoc allows you to export your document packages and eForms to a compact, portable archive file that can then be imported into another client ID or LincDoc installation.

Exporting an eForm or Document Package

To export a document package or eForm, perform the following steps:  

  1. Select from the drop down list the document package or eForm that you wish to export. 
  2. Select admin, then select export.You will be presented with the Export Document Package window (as shown at right).
  3. Review the information, then click the Export button.
  4. When the export completes, you will be presented with a link to the archive file that contains your exported document package (see right).  Click the file link to download the export file to your local system.
  5. Close the Export window by clicking the Cancel button. 

 

Your downloaded file will have a file extension of LDAR to identify it as a LincDoc document package archive. The name of the archive file is based on the Client ID, the document package ID, and a randomly generated four-character value, separated by underscores.

 

Importing a Document Package Archive

You can import downloaded document package archives to a new client ID or LincDoc installation by completing these steps:

  1. Select admin, then select import.
  2. The file upload window will appear (shown at right). Click the upload button to select the desired document package archive from your local file system. Then click the Open button to send the archive file to the LincDoc server and begin the import process.
  3. If there are no problems found with the import, a message will display informing you that the import was successful. Click OK to return to LincDoc. Make sure to log out and back in to refresh any changes.
  4. If the import process encountered problems, you'll be presented with a window that enumerates the problems and allows you to choose how to solve them (shown below). Choose the solutions that suit your needs, and click the Import button to complete the import process (see below for a fuller discussion of import problems and how to solve them). After the import process is complete, log out of LincDoc and log back in to refresh any changes made.

Resolving Import Issues

A resolution list is reported when an item in the import file (a document package, business rule, code list or source document) has the same name as one that is already in the system. For each problem item, your choices to resolve the problem are:

  1. Rename the imported item. This will give the imported item a new, unique name so that it no longer conflicts with the existing item.
  2. Replace the existing item. This will overwrite the existing item with the item in the import file.
  3. Keep the existing item. This will cause import process to skip the item in the import file. The imported document package will use the item that is already in the system.

An example will help to make the choices clearer.  Let's say you're importing a new document package that uses a code list called "beverageTypes", which includes the codes "Coffee", "Tea" and "Soda". When you start the import process, a problem is reported, indicating that a code list called beverageTypes already exists in the system. The beverageTypes code list currently in the system includes the codes "Hot", "Dairy", and "Carbonated". If you choose the Rename option, the beverageTypes code list in the import file will be renamed to beverageTypes2. After the import, you will have a beverageTypes code list with "Hot", "Dairy", and "Carbonated", and a beverageTypes2 code list with "Coffee", "Tea" and "Soda". The newly imported document package will use the beverageTypes2 code list. If you choose the Keep option, the beverageTypes code list in the import file will be discarded, and the newly imported document package will use the existing beverageTypes code list with the "Hot", "Dairy", and "Carbonated" codes. If you choose the Replace option, the existing beverageTypes code list will be overwritten with the one in the import file. After the import, you will have a beverageTypes code list with the codes "Coffee", "Tea" and "Soda". Any existing document packages that use the beverageTypes code list will now show "Coffee", "Tea" and "Soda" as the available choices.

Knowledge Tags
import  /  export  / 

This page was: Helpful | Not Helpful
← 1. eForms design