Conflict Resolution - Workflow - English - Foundation 22.1 - OnBase - Premier - external - Standard - Premier - Standard

Workflow

Platform
OnBase
Product
Workflow
Release
Foundation 22.1
License
Premier
Standard

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

  • a Unity Life Cycle

  • queue

  • Document Type Group

  • Document Type

  • document templates

  • Keyword Type

    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.

  • custom queries

  • file types

  • folder types

  • folder templates

  • 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, if you choose to Replace or Map a VBScript to an existing VBScript that has the same name, the scope specified for the incoming VBScript must match the existing VBScript.

  • E-Forms

  • user forms

  • Unity Forms 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.

    Note:

    If an imported Unity Form template has the same name as a Unity Form template that already exists in the destination database, but is associated with a different document type, the user will not be able to use the Map to Same Name button.

  • Unity Forms Data Sets

  • Unity Form Themes

  • icons and bitmaps

  • 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

  • Form Letter Templates

  • 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

  • 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

  • reading groups

  • approval groups

  • Application Server Gateways

  • HL7 messages

  • HL7 destinations

  • DocPop URLs

  • content sources

  • Collaboration Templates

There are two dialog boxes associated with conflict resolution: Workflow Conflicts Resolution dialog box and Naming Conflicts for “Name of Life Cycle” dialog box.