Considerations for Importing Configuration Items - Change Control - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Change Control

Platform
OnBase
Product
Change Control
Release
Foundation 22.1
License
Standard
Essential
Premier

Keep in mind the following items when importing certain configuration item types into the destination database:

  • Before importing an export package, ensure Disk Groups are properly configured.

  • It is highly recommended that export packages are exported and imported using the same database version and OnBase version.

  • Disk Groups can only be mapped during import, and cannot be created or used to replace existing Disk Groups.

  • When a Keyword Type is mapped, only those Keyword Types sharing the same Data Type in the destination database are displayed (i.e., you do not have the option to map an alphanumeric Keyword Type to a numeric Keyword Type).

  • When mapping an Alphanumeric Keyword Type, it is considered a best practice to ensure the length of the imported Keyword Type matches the length of the Keyword Type in the destination database.

  • When a Keyword Type is replaced, Keyword Type Data Set values from the imported Keyword Type are imported only when the Keyword Type in the destination database contains no existing Keyword Type Data Set values.

  • When an encrypted Keyword Type is imported, the encryption is removed. You are notified that the encryption of the Keyword Type is modified upon verifying your import changes.

  • You cannot replace AutoFill Keyword Sets or Cascading Data Sets using AutoFill Keyword Sets or Cascading Data Sets from an export package. This is because once these sets are created, you cannot modify the Keywords contained within them.

  • External AutoFill Keyword Sets using a WorkView filter can only be mapped to an existing AutoFill Keyword Set; they cannot be created or used to replace another existing AutoFill Keyword Set.

  • External AutoFill Keywords Sets using an EIS data source can be created or mapped to an existing AutoFill Keyword set; they cannot be used to replace another existing AutoFill Keyword Set.

  • When importing Folder Types, understand the parent/child relationship between folders and how import actions can affect the relationship. For example, if you select Create to create the parent folder in the destination database but select Map to map a child folder to another folder in the destination database, the relationship between the two folders is broken. The child folder becomes either a parent or a child of another folder, depending on how it was mapped.

    CAUTION:

    When importing a Folder Type from an export package created in OnBase 15, the respective file cabinet is created but not linked to a Folder Type. As a result, some folder configuration, such as auto-foldering, is not maintained after import. As a best practice, do not select to create Folder Types from an export package created in OnBase 15; however, if this does occur, ensure the created file cabinet is linked to a Folder Type to avoid unexpected behavior.

  • Some older export packages may contain Unity Form templates or Document Composition templates with missing document references. While it is no longer possible to export these configuration items with missing document references, older packages containing missing references can be partially successful during import (i.e., import will not fail due to missing references, but it will not be successful in importing the required template document).

  • When a process is imported for the Document Import Process or COLD Processor, process paths are not imported. They must be properly configured in the destination database.

  • Environment values are not imported, but are displayed in the Post-Import Report and logged in the import verification report document archived in the destination database. Environment values must be properly configured in the destination database.

  • When Users are set to Create, they are not assigned to User Groups in the destination database. User security must be explicitly configured by system administrators.

  • If a Unity Script is owned by a deactivated user, upon importing, the MANAGER group will be assigned as owner.

  • When importing packages created prior to OnBase 18, passwords for imported user accounts must be manually reset.

  • Translation strings of Map Only configuration items are not imported.

For module-specific import considerations, see the appropriate module reference guides.