Resolving Other Conflicts - Workflow - English - Foundation 22.1 - OnBase - Premier - external - Standard - Premier - Standard

Workflow

Platform
OnBase
Product
Workflow
Release
Foundation 22.1
License
Premier
Standard

There are many other types of conflicts that can occur in addition to life cycles, queues, and document types. They include:

  • Calendars

  • Document Composition Categories

    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.

  • Document Type Group

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

  • custom queries

  • document templates

  • file types

  • folder types

  • folder templates

  • fonts

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

  • print formats

  • print queues

  • XML formats

  • XML format ports

  • notifications

  • currency formats

  • Org Charts

  • Roles

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

  • user groups

  • note types

  • VBScripts

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

  • 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

  • SAP Servers

  • actions that transition documents to another queue

  • reading groups

  • approval groups

  • HL7 messages

  • HL7 destinations

  • DocPop URLs

  • content sources

  • Collaboration Templates

  • WorkView Class DTAs

  • WorkView Filter DTAs

  • Managed Folder Types

    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

To resolve other conflicts:

  1. Select the category in the Naming Conflicts for “Name of Life Cycle” dialog box.
    Note:

    For conflicts with actions that transition documents to another queue, they will not be listed in the Naming Conflicts for “Name of Life Cycle” dialog box. They will open in their own Workflow Conflicts Resolution dialog box. Skip to step 3 for this type of conflict.

  2. Click Resolve.
  3. The Workflow Conflicts Resolution dialog box displays.
  4. Select the conflict to obtain a description of the conflict on the right side of the dialog box.
    Note:

    Actions that transition documents to another queue will have the life cycles to which they belong displayed in brackets next to the conflict item and the item in the Mapping/Replacing Choices box.

  5. Resolve the conflict in any of the following ways:
    • Map the currently selected conflict to an existing item in the database by selecting an existing item to map to in the Mapping/Replacing Choices list and clicking Map.

      Note:

      When resolving a WorkView Class DTA or a WorkView Filter DTA, you can only map to an existing DTA. You cannot create a new DTA or replace an existing DTA with the imported DTA.

    • Replace the current item with the newly imported item by selecting a item from the Mapping/Replacing Choices dialog box and clicking Replace.

    • Rename the conflict by clicking Create New and supplying the new name. The maximum number of characters allowed is 50.

    • Map all selected imported document types to existing document types that match in name by clicking Map to Same Name.

    Note:

    When resolving queue references, if you select multiple queues that do not belong to the same life cycle and multiple queues with the same name exist but in different life cycles and click Map to Same Name, you will be prompted to resolve the mappings individually.

    CAUTION:

    Use care when selecting Map All to Same Name. All dependencies within the mapped item will also be mapped to existing configurations and may result in errors.

  6. Click Save when all conflicts have been resolved for the life cycle.
    Note:

    If you select the Show Mapped Objects, mapped items will be displayed. If you select Show Replacing Objects, items replacing existing items will be displayed. If you select Show New Objects, items that are created as a new object will be displayed. When these options are not selected, the corresponding objects will not be displayed in the dialog box.

    Note:

    Some object types do not have the Replace button available by design. For these object types, you must create a new object or map the object to an existing object.