The Import specifications dialog

ClosedTo access this dialog:

On the Configuration tab of the Administration module, select Configuration > Import.

Use these settings to import specifications:

Select file to import from

The .dox file to import from.

Select specifications to import

Specification name

The name of the specification.

Type

The type of specification.

ClosedSolutions available for import.

System specifications, templates and solution specifications.

When you import a solution specification, all dependent specifications (documents, productions tasks, etc) are automatically included.

ClosedInformation on templates

In the Type column, both field templates and classifier templates are labeled as "Field templates".

If you have a solution with a lot of classifier templates, and need to find your classifier templates more easily, name all your classifier templates with the same prefix, for example:

  • ClassTemp - Document A

  • ClassTemp - Document B, etc.

Then, in Import/Export, sort by Specification name, and all your classifier templates will be grouped together under ClassTemp.

Built-in

Whether the specification is built-in or user-defined.

Database version created

The date and time the specification was created in the database.

Database version modified

The date and time the specification was modified in the database.

Database version

The versions of the specification in the database.

File version created

The date and time the specification was created in the file.

File version modified

The date and time the specification was modified in the file.

File version

The versions of the specification in the file.

Merge conflict

The type of conflict:

  • None – the specification does not exist in the database.

  • ID – an identical specification already exists in the database.  

  • Name – another specification with the same name already exists in the database.

See also: Managing conflicts between a specification to be imported/exported and an existing one

Merge action

How to resolve the conflicts:

  • Add – adds the specification to the database.

  • Keep – preserves the specification in the database because it is newer than the version in the file.

  • Replace – replaces the specification in the database with the newer version from the file.

  • Rename – names the imported version of the specification "Copy of <OriginalName>". If the database already contains a specification with this name, the new copy is named "Copy(2) of  <OriginalName>", etc. This renaming occurs automatically, but ideally you should give them a meaningful name after importing.

Normally, the most suitable resolution is selected by default. However, in most cases you can click the word and change it, if needed. See Managing conflicts between a specification to be imported/exported and an existing one.

Import

Selects the specification for import.

Dependent specifications – displays the specifications that are dependent on those selected above

Lists required specifications, which are also imported, for a specification selected above.

Number of selected specifications

The number of manually selected specifications.

Total number of specifications

The total number of selected specifications, plus their dependent specifications, to import.

Create a backup file

Creates a backup (a .dxb file) of the existing configuration database before importing the new specifications. (Only available during import.)

This file is saved to the location from which the .dox file is fetched. If you do not want that backup file, deselect Create a backup file.

Include sample documents

Includes the sample documents found in the selected solution(s).

Total number of sample documents

The total number of sample documents found in the selected solution(s).

Import

Imports the selected and dependent specifications.

Note:

Import and Export: Overview

Backing up the configuration database

Restoring a database