Views:

This article covers common issues and questions with the Fortis to DocuWare Migration.
Please email fortissupport@docuware.com with feedback.

Fortis 6.11 NEW Migration Tools:

IMPORTANT! - After applying SP1, you MUST right click, Run As Admininstrator on the Fortis Database Administration station shortcut on the FIRST TIME opening it to complete the install.
The Fortis File Cabinet Migration tool should only be fully run through one time. You have the ability to save your work but once it has been fully run once, you will be unable to run it a second time to make changes to the DocuWare File Cabinet. The File Cabinet will need to be manually deleted from DocuWare, then the tool can be run again.
If two fields have the same name but different type, two fields will be created in DocuWare with a suffix of the field type. For example, CustomerID_Int, CustomerID_Char
Full text and Versioning can be turned on/off per File Cabinet.

Behavior:

500 Internal Server Error (The system storage path is not defined.)


Solution:

In DocuWare Administration under DocuWare System - General, enter a location for "System storage path".  See this article - https://www.docuware.com/support_faq/?solution_id=4555

Behavior:

500 Internal Server Error (Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries.)


Solution:

Apply SP2 for SQL 2012 or SP1 for SQL 2014

Behavior:

DocuWare fields are truncated because of length of Fortis Database name combined with Field Name.


Solution:

If possible, shorten Fortis database name prior to running Migration Tool.  Here are some character limits in DocuWare:

  • Database name - 50 characters
  • Select List name - 50 characters
  • Group name - 32 characters
  • Keyword fields - 256 characters
  • Real Numbers - default is set to 4 decimal places
Also, FortisBlue picklists will be migrated with a prefix of "FortisBlue - ".  Fortis picklists will be prefixed with the Fortis database name.  The recommendation is to shorten the names prior to running Migration Tool.

Behavior:

Annotations look different after they have been migrated to DocuWare.


Solution:

If an annotation is off the page in Fortis & FortisBlue, the Migration Tool will pull it onto the page prior to importing into DocuWare.  (DocuWare cannot have annotations off the page). 
Fortis Redactions will NOT be migrated to DocuWare.  The expected behavior of the Migration Tool is - 
  • If user does not have rights to remove the redaction in Fortis, skip the document 
  • If user does have rights to remove redaction, migrate the document without redactions 
  • If the user is the Fortis DB Owner, migrate without redactions
Stamps, Signatures, Related Links will NOT migrate to DocuWare.

Behavior:

Will my users and groups get migrated from Fortis or FortisBlue to DocuWare?


Solution:

The behavior of the Migration Tool is as follows:
Fortis
  • For LDAP authenticated systems – Do not Copy Users and Groups
  • For Mixed Mode authenticated systems – Do not Copy Users and Groups
  • For Fortis authenticated systems – Copy Users and Groups
FortisBlue 
  • For Domain authenticated systems – Do not Copy Users and Groups
  • For Win/NT Local authenticated systems – Copy Users and Groups
  • For FortisBlue Users and Groups authenticated systems – Copy Users and Groups
Behavior:

Archive size grows after migrating to DocuWare.

Solution:

Documents in Fortis are compressed and when migrated, will be decompressed to their original format.
The following table shows the expansion rate for several common formats.  Image formats such as TIFF and JPG will be 75% to 100% larger in their original formats where PDFs will only expand by 25%.  Microsoft Word documents will be nearly unchanged.  
 Orignal Format    Expansion (from MAG) 
 .DOCX  0% to (-1)%
 .PDF  25%
 .TIFF  75% to 100%
 .JPG  75% to 100%

The DocuWare database will also grow 150-200% larger than the Fortis database.
Comments (0)