Importing - Workflow - English - Foundation 22.1 - OnBase - Premier - external - Standard - Premier - Standard

Workflow

Platform
OnBase
Product
Workflow
Release
Foundation 22.1
License
Premier
Standard

In order to successfully import a configuration, you must resolve all conflicts displayed.

Note:

Workflow task lists are always imported as New Objects and assigned new tasklist IDs. Any existing VBScripts or OnBase API integrations referencing task lists linked to the imported life cycle will need to be updated with the new tasklist ID value.

Conflicts can occur when a life cycle being imported contains one or more of the following that have the same database identification number or name as an item in the new database:

  • a life cycle (Legacy and Unity)

    Note:

    A life cycle in the destination database that is checked out cannot be mapped to or replaced.

    Note:

    Life cycles can only be mapped to or replace another life cycle of the same work item type. For example, a life cycle that routes documents can only be mapped to or replace another life cycle that routes documents.

  • queue

    Note:

    When importing a queue that is configured for load balancing, that queue can only be mapped to or replace another load balanced queue.

  • Rule Queue

    Note:

    When importing a Rule Queue, that queue can only be mapped to or replace another Rule Queue.

  • Rule Sets

  • Document Type Group

  • Document Type

    Note:

    When there is a Document Type conflict and the imported Document Type has a Keyword Type Group assigned to it, if this Document Type is mapped to an existing Document Type in the destination database, the imported, mapped Document Type will inherit the Keyword Type configuration for the Document Type that is in the destination database. The Keyword Type Group will not be configured for the mapped Document Type.

  • document templates

  • Keyword Type

    Note:

    When importing a Keyword Type that is configured to use auto numbering, if you choose Create New, the new Keyword Type's initial value starts at 0. If you choose Map To, the Keyword Type's initial value maps to the keyword value in the destination database and will use the existing sequence value. If you map a Keyword Type that is configured with auto numbering to a Keyword Type in the destination database that is not configured with auto numbering, the mapped Keyword Type will not be configured with auto numbering because the mapped Keyword Type inherits the properties of the Keyword Type in the destination database.

    CAUTION:

    When importing encrypted keywords, these keywords will lose the encryption flag. If you wish for the imported keywords to be encrypted, you must lock the system through the Configuration module (Utils | Database Settings) and reset the encryption for the Keyword Types.

  • AutoFill Keyword Sets

    Note:

    When there are AutoFill Keyword Sets associated with a Document Type, only those keywords which were previously associated with the Document Type will be applied.

  • custom queries

  • file types

  • folder types

  • folder templates

  • Work Folders

  • fonts

  • print formats

  • print queues

  • XML formats

  • XML format ports

  • notifications

  • currency formats

  • users (only applicable to users that are used in a life cycle. For example, a load balancing queue would have associations to users.)

    Note:

    Deactivated users in the destination database are not available for selection using conflict resolution.

  • user groups

  • note types

  • VBScripts

    Note:

    On import, you can choose to Replace or Map a VBScript to an existing VBScript that has the same name, regardless of the scope specified for the incoming VBScript.

  • Unity Script

    Note:

    When a Unity Script is imported as a dependency of the life cycle and it is imported as a revision of a Unity Script in the destination database, it will create a new version of the script in the destination database and the script will be renamed to the imported script's name.

  • E-Forms

    Note:

    If a document belonging to the SYS HTML Form Document Type is imported and does not have a value for the Description Keyword Type, or it has spaces as the value, it will be imported with a unique, automatically-generated value in the format of “Eform ID nnn”, where nnn is the ID number for the form.

  • user forms

  • Unity Form Templates

    Note:

    When resolving this conflict type, ensure that the Document Type associated with the Unity Form template is assigned all the Keyword Types configured for the Unity Form template. Document Type conflicts need to be resolved before resolving Unity Form template conflicts.

  • Unity Form Data Sets

  • Unity Form Themes

  • EIS Live Projects

    Note:

    If an EIS Live Project includes an AutoFill operation, the AutoFill Keyword Set is created, but the import processor is not. The Import processor must be created after import in order for the EIS Live Project to be published.

  • EIS Messaging

  • icons and bitmaps

    Note:

    Icons and bitmaps are automatically decisioned upon import. If an icon or bitmap in the import package matches the name of one that exists in the destination database, that icon or bitmap will be mapped to the existing one in the destination database. If an icon or bitmap does not already exist in the destination database, it is automatically created.

  • Org Charts

    CAUTION:

    Be extremely careful when mapping Org Charts and Users within the Org Charts. Ensure that you do not map users in a way that would make them their own managers or their own assistant. This is not supported.

  • Roles

  • Calendars

  • Document Composition Libraries

    CAUTION:

    Security user group rights are not exported for libraries. If you use the Map or Replace options during the import for library, the user group rights will not change and will remain according to what was already on the destination system. When using the Create New option for a library, the MANAGER group will automatically be assigned to have edit access to the library.

  • Form Letter Templates

    CAUTION:

    Security user group rights are not exported for templates. If you use the Map or Replace options during the import for template, the user group rights will not change and will remain according to what was already on the destination system. When using the Create New option for a template, the MANAGER group will automatically be assigned to have edit access to the template.

  • SAP servers

  • Managed Folders

    CAUTION:

    Always resolve Managed Folders before resolving Hold Reasons to ensure you are resolving the Hold Reasons correctly and matching the Hold Reason with the correct Managed Folder.

  • Hold Sets and Hold Reasons

  • RIM Event Sets

    CAUTION:

    Always resolve Event Sets before resolving Events to ensure you are resolving the Events correctly and matching the Events with the correct Event Set.

  • RIM Events

  • RIM Retention Plans

  • RIM Retention Plan Sets

  • actions and rules that refer to another queue

  • WorkView Class DTAs

  • WorkView Filter DTAs

  • WorkView Applications

  • WorkView Classes

  • WorkView Attributes

  • WorkView Notifications

  • WorkView Filters

  • Portfolio Relations

  • Portfolio Types

  • Approval Processes

  • Approval Queues

    Note:

    When importing an Approval Queue, that queue can only be mapped to or replace another Approval Queue.

  • Approval Roles

  • Approval User Rules

  • System Tasks

  • System Events

  • Window titles

  • reading groups

  • Gateway Caching Servers

  • HL7 messages

  • HL7 destinations

  • DocPop URLs

  • content sources

  • ShareBase Profiles

  • Item Generator Sets

  • Item Generators

  • Workflow API Tasks

  • Collaboration Templates