AIP - Archival Information Package

AIU - Archival Information Unit

BLOB - Binary large object

DB - Database

CSV - Comma separated values

CLOB - Character large object

DCTM - Documentum

DFC - Documentum Foundation Classes

DMS - Document Management System

DSS - Data Submission Session

GB - Gigabyte

GHz - Gigahertz

IA - InfoArchive

JDBC - Java database connectivity

JRE - Java Runtime Environment

JVM - Java Virtual Machine

KB - Kilobyte

MB - Megabyte

MS - Microsoft

MHz - Megahertz

RAM - Random Access Memory

regex - Regular expression

SIP - Submission Information Package

SPx - Service Pack x

SQL - Structured Query Language

XML - Extensible Markup Language

XSD - File that contains a XML Schema Definition

XSL - File that contains Extensible Stylesheet Language Transformation rules

migration-center 23.3

Features & Enhancements

• General

  • Show migset name and migset id in the importer run report (#68918)

• New Azure Blob Storage Importer (#67191)

  • Imports documents with content

  • Sets system metadata on documents

  • Sets custom metadata on documents

  • Sets blob index tags

• Box Importer

  • Create folders and metadata (#68813)

  • Optimize / reduce the number of REST API calls (#68775)

  • Validate dropdown values before submitting the request to Box (#68774)

• Cara Importer

  • Add support for Cara 5.9 (#68919)

  • Add support for setting sequence_no (#68777)

  • Partially import the documents that fails because of invalid object references (#68905)

• Exchange Scanner

  • Add support for Exchange 365 (#68960)

• OpenText Content Server Importer

  • Add support for importing into OpenText Content Server 23.3 (#68834)

• WebClient

  • Copy rules from migset (#68954)

  • Filter by Value (#68783)

  • Reset all Error Objects (#68784)

  • Migset "add new association" entry UI re-design (#68782)

  • Transformation rules clipboard can be pasted any number of times (#68785)

  • Remove dependency on ENV variables in REST API (#68642)

  • Improve Object Type section performance (#69074)

  • Improve Object Type stability during CRUD operations (#68781)

  • Improve UI performance of Adapters input (#68655)

Fixes

• Database

  • multivalueRemoveDuplicates incorrect on null / empty values (#69237)

• Alfresco Importer

  • Setting null values for aspect attributes may remove other attribute values from the aspect (#69487)

• Box Importer

  • Object Type name is being sent in all lowercase characters (#68978)

• Cara Importer

  • First line in relation_config.properties is ignored (#68907)

  • Empty lines when logging level is 2 (#68916)

  • Cara file path too long error (#67864)

  • Setting an ID field which is binded to the LATEST version fails (#67060)

  • Indexing documents is applied when indexDocuments is not checked (#68906)

  • Audittrail attribute_list and attribute_old_list are not migrated (#69106)

  • Internal attribute “title” is not set (#66927)

• Veeva Importer

  • The character \ is not visible in Veeva (#68811)

  • Import fails if one attribute value finish with "\" (#68812)

• WebClient

  • Blank page when current connection was deleted in another session (#68988)

  • Error when filtering migset target or error objects in PostgreSQL (#69621)

  • Retrieving error objects fails on Postgres when rule is associated in two objects types (#69511)

  • Migset mapping lists incorrectly shown in new migsets after importing migset from file (#69014)

  • Add association button enables when switching between object types (#64272)

  • Copying a mapping list duplicates all entries after clicking on an entry and then away (#69228)

  • Previous step not correctly displayed in IF function (#69163)

Known Issues

• Box Importer

  • Created and Modified attributes not set on folders (#69471)

• Cara Importer

  • When importing Updates and Original objs in the same migset original objs stay validated (#69404)

• WebClient

  • Refreshing source objects after filtering value on column with upper case letters fails (#69629)

  • Object filtering fails on Postgres if value contains backslash "\" (#69575)

  • Function with attribute that no longer exists does not change when setting first entry of new existing attribute list (#69713)

1. Information according to § 5 of the Telemedia Act (TMG)

fme AG Wolfenbütteler Straße 33 38102 Braunschweig Phone: +49 531 2 38 54-0 Mail: info(at)fme.de

Website: www.fme.de

Management board

Dirk Bode (Chairman), Daniel Pelke (Executive Board Member)

Supervisory board

Stefan H. Tarach (Chairman), Dr. Axel Krieger (Deputy), Dr. Markus Böhme

Registry Court: District court Brunswick

Register number: HRB 5422

Identification number according to § 27 a Sales Tax Act (UStG): DE 178236072

2. Information according to § 2 Service Information Obligations Regulation (DL-InfoV)

Our general terms and conditions apply to services provided by us. Our general terms and conditions are available at https://migration-center.com/free-evaluation-copy-license-agreement/. They stipulate that German law applies and that, as far as permissible, the place of jurisdiction is Brunswick.

3. Information according to Art. 14 Regulation (EU) 524/2013 (Regulation on consumer ODR)

Reference is made to the European Online Dispute Resolution Platform (ODR platform) of the European Commission. This is available at http://ec.europa.eu/odr.

fme AG does not participate in dispute resolution proceedings before a consumer arbitration board and we are not obliged to do so.

4. Disclaimer

We are responsible for the content of our website in accordance with the provisions of general law, in particular Section 7 (1) of the German Telemedia Act (TMG). All content is created with due care and to the best of our knowledge and is for information purposes only. Insofar as we refer to third-party websites on our Internet pages by any means (e.g. hyperlinks), we are not responsible for the topicality, accuracy and completeness of the linked content, as this content is outside our control and we have no influence on its future design. If you consider any content to be in breach of applicable law or inappropriate, please let us know.

The legal information on this page as well as all questions and disputes in connection with the design of this website are subject to the law of the Federal Republic of Germany.

5. Data Protection

Our data protection information is available at https://migration-center.com/data-protection-policy/.

6. Copyright

The texts, images, photos, videos, graphics and Software, especially code and parts thereof, on our website are generally protected by copyright. Any unauthorized use (in particular the reproduction, editing or distribution) of this copyright-protected content is therefore prohibited without our consent (e.g. license) or an applicable exception or limitation. If you intend to use this content or parts thereof, please contact us in advance using the information provided above.

Migration Set A migration set comprises a selection of objects (documents, folders) and set of rules for migrating these objects. A migration set represents the work unit of migration-center. Objects can be added or excluded based on various filtering criteria. Individual transformation rules, mapping lists and validations can be defined for a migration set. Transformation rules generate values for attributes, which are in turn validated by validation rules. Objects failing to pass either transformation or validation rules will be reported as errors, requiring the user to review and fix these errors before being allowed to import such objects.

Attribute A piece of metadata belonging to an object (e.g. name, author, creation date, etc.). Can also refer to the attribute’s value, depending on context.

Transformation Rules A set of rules used for editing, transforming and generating attribute values. A set of transformation rules is always unique to a migration set. A single transformation rules is comprised of one or several different steps, where each step calls exactly one transformation function. Transformation rules can be exported/imported to/from files or copied between migration sets containing the same type of objects.

Transformation Function Transformation functions compute attribute values for a transformation rule. Multiple transformation functions can be used in a single transformation rule.

Job Server The migration-center component listening to incoming job requests, and running jobs by executing the code behind the connectors referred by those jobs. Starting a scanner or importer which uses the Documentum connector will send a request to the Jobserver set for that scanner, and tell that Jobserver to execute the specified job with its parameters and the corresponding connector code.

Transformation The transformation process transforms a set of objects according to the set of rules to generate or extract.

Validation Validation checks the attribute values resulting from the Transformation step against the definitions of the object types these attributes are associated with. It checks to make sure the values meet basic properties such as data type, length, repeating or mandatory properties of the attributes they are associated with. Only if an object passes validation for every one of its attributes will it be allowed for import. Objects which do not pass validation are not permitted for import since they would fail anyway.

Mapping list A mapping list is a key-value pair used to match a value from the source data (the key) directly to the specified value.

This online documentation describes how to use the migration-center software in order to migrate content from a source system into a target system (or into the same system in case of an in-place migration).

Please see the for a summary of new and changed features as well as known issues in the migration-center releases.

Also, please make sure that you have read before you install and use migration-center in order to achieve the best performance and results for your migration projects.

The supported source and target systems and their versions can be found in the page.

Migration-center is a modular system that connects to the various source and target systems using different connectors. The source system connectors are called scanners and the target system ones are called importers. The capabilities and the configuration parameters of each connector are described in the corresponding manual.

You can find the explanations of the terms and concepts used in this manual in the .

And last but not least, contains some important legal information.

Further Resources

For additional tips and tricks, latest blog posts, FAQs, and helpful how-to articles, please visit our .

In case you have technical questions or suggestions for improving migration-center, please send an email to our product support at .

Here is a list of all the versions supported by migration-center for all of our source and target systems:

A content migration with migration-center always involves a source system, a target system, and of course the migration-center itself.

This section provides information about the requirements for using migration-center in a content migration project.

For best results and performance it is recommended that every component will be installed on a different system. Hence, the system requirements for each component are listed separately.

The required capacities depend on the number of documents to be processed. The values given below are minimal requirements for a system processing about 1.000.000 documents. Please see the Sizing Guide for more details.

Database Server

Oracle

PostgreSQL

Server Components (Job Server)

WebClient

Desktop Client

Component Overview

Migration-center has 3 main components: Database component, WebClient and Jobserver component.

The Database stores all the migration-center configurations and all scanned and imported objects with their source and target metadata.

The WebClient is a web based UI where you can manage all the scanner, importer and migset configurations and you can trigger scan, import or transformation jobs. The WebClient can be installed on a machine in your network and then accessed from multiple other machines through a web browser (see System Requirements for supported browsers).

The Jobserver component receives the scan or import configuration from the Client and connects to source/target systems to extract/import objects, processes metadata into/from the Database and the content into/from the file system staging area. Multiple Jobservers can be installed.

Component installation

This is just a quick overview of the installation process. For specific details please see System Requirements and Installation Guide.

The main migration-center components can be installed either on the same machine or on separate machines, by using the installers.

Starting with version 22.1.0 the Database installer no longer requires Oracle Client. The installer will connect to the database using JDBC.

The Jobserver installer can be run on a windows machine, but to actually start the Jobserver you need Java 8 or 11 installed. The Linux Jobserver does not have an installer, it has scripts to install the service.

The WebClient installer can be run on a Windows machine as well. It will deliver a customized Tomcat that is installed as a windows service.

Component port connections

The WebClient connects as follows:

- to the Browser via port 443 - to the Database using connection via information provided by the user (port 1521 by default) - to the Jobserver via port 9700 by default

The Jobserver connects as follows: - to the Database via JDBC connection on the same Oracle port as the Client - to each source or target system differently based on the system itself

When using the Scheduler feature the job will be triggered by the Database instance itself from the Database machine by sending a socket signal to the Jobserver via the defined port (9700 by default).

Migration Process

The general process of performing migrations with migration-center is done in several steps:

The Analyze phase involves configuring a Scanner to connect to a Source System, that will extract the metadata and save it as objects in the migration-center database, and export the content to a defined Filesystem location, which acts as a staging area.

The Organize phase involves assigning Scan Runs into Migration Sets, or migsets for short.

The next 3 phases, Transform, Validate and Correct, work together and involve creating Transformation Rules by which your Source Metadata is Transformed into Target Metadata. The metadata is assigned to Target Type definitions, which can be defined in advance. And based on those definitions the metadata is Validated. If the resulting target metadata is not the desired one, you can reset the objects and repeat the process by correcting or adding transformation rules.

The Import phase, is the last step, and involves creating an Importer, which will connect to the Target System, assigning a migset with Validated Objects to it and starting the import run. You can monitor the progress in the importer run history or directly in the migsets view.

All the migration phases can be done in parallel for different batches of documents that are migrated.

Starting the Client

When you first access the link to the WebClient you will see a login window.

The default login user is fmemc and the default password is migration123.

If this is a fresh installation your Connection dropdown will be empty. You will need to configure a new connection to your Database.

This is done by going to the Manage Connections view and clicking Add Connection.

Here you will set a Connection Name and the Database Type, Host, Port and Service Name(database name) for the database you will be using. Click Create to create the connection and be able to use it when signing in.

Defining a Jobserver

Before you are able to run a scanner you first need to define a Jobserver by going to the Job Servers tab of the Configuration page.

Click the Add Job Server button and enter the Name, Location (hostname) of the machine where the Jobserver component is installed, and the Port (default is 9700). An optional description can also be added.

Creating a Scanner

Open the Scanners page and click the Add Scanner button:

Fill in the Name of this scanner, select a type and select a Jobserver where you want this scan to run.

After you have filled at least the mandatory parameters of the scanner configuration you can save it by clicking on Save.

You can run it by clicking Save & Run in the toolbar, or by going back to the list of scanners and clicking on Start Scan Job in the Right Click context menu.

Clicking on History allows you to see a list of all Scan Runs performed by the this scanner configuration.

Clicking on Source Objects shows you the objects grid for this scanner or scan run.

Creating a Migset

Open the Migration Sets page and click the Add MigSet button.

Enter a name for this migset and select the Migration Path from the Type dropdown.

In the same view, under Available you will see the scan runs corresponding to your chosen migration-path. Select which scan runs you want to include in this migset by double clicking them or by using the down arrow button.

Filtering the objects (optional)

As an optional step before clicking on the Select Objects button, there are 2 filtering options:

Simple Filtering, where you can exclude objects based on their values:

Advanced Filtering, where you can create rules by which to select the objects:

Creating Transformation Rules

With the Migset you have just created selected, click on the Transformation from the toolbar.

Regular Transformation Rules

The Rules section in the top left corner lists the Transformation Rules created so far in this migset. You can create a new one using the New button. In the middle there's the Rule Properties section where you can specify the rule Name and if it should return multi-value results.

The Transformation methods section contains a dropdown of all the Functions that you can use inside your transformation rule. These functions take Source Attributes and static values to generate a new value as a Target Attribute. Multiple functions can be linked together by processing the result of a Previous Step:

As you can imagine this is the main strength of migration-center as it allows you to create very complex rules to ensure you get the required results in your Target System.

System rules

On the bottom left corner we have the Rules for system attributes. These function the same as the regular transformation rules, except they have a fixed name and therefore serve a specific purpose during the import. Please refer to the user guide of the Importer you are using for details on what each system rule does.

Associations

On the Associations tab of the Transformation view you can associate the previously defined Transformation rules to a Target Attribute of an object type.

The Types dropdown shows you a list of all Object Type Definitions in migration-center and you can select which ones are to be used in this migset. In the screenshot above we have selected opentext_document and opentext_rm_classification.

Clicking through the list of selected types will show, on the right side, the current associations between Rules and Target attributes.

Object Type Definitions

To mange the available object types in migration-center go to Configure -> Object Types

This will open Object Types view where you can create new Types and either manually adding each of the type's attributes or importing them from a CSV file. More details are in the Client User Guide.

Transforming and Validating objects

After you have finished writing the necessary transformation rules you can save the migset, and trigger Transformation on the migset. This will also apply Validation.

Transformation will apply the rules in the migset on each object individually and will generate the target objects. The objects will move to the Transformed state.

Validation will compare the generated values against the object type definition restrictions to ensure the values fit. If successful the objects will move to the Validated state.

After doing the transformation, the Target Objects can be viewed in the Transformed Objects view.

If any issue occurred during transformation or validation, the objects will move to the Error state and can be checked in the Error Objects view.

Here is a diagram with all the states the Objects in migration-center can go through:

Creating an Importer

Open the Importers page and click the Add Importer button:

The Importers section is very similar to the Scanners one so we will only cover the differences.

After setting all necessary parameters for your import to function correctly you must go to the Selection tab which will allow you to select one or more migsets for import. After that you can save the importer and run it.

You can monitor the status of the import either in the the Jobs view, in the importer History or in the Migsets view. Each view will show the progress of the migration in varying levels of detail, with the migsets one showing the most details of the objects being imported.

When the import has finished you can see the status changed to Finished and all the objects marked as Imported. If any errors or warnings occurred you can view them either in the Error Objects view of the migset or by opening the import run log from the history of the importer.

Important Features

Creating a Scheduled Job

You can automate the migration process from Scan to Import by using the Scheduler feature. This is very useful in setting up a continuous migration of active systems where the users are still modifying and creating documents.

How it works: You create a scheduled job and select existing valid scanner, migset and importer configurations. If the Scheduler is set to active and depending on what interval settings are set, the scheduler will automatically perform the following actions: - Start the scanner - Create a copy of your migset and assign the scanned objects to it - Run Transformation and Validation - Assign the migset to the importer - Start the importer - (optional) send an email report if configured

Create a new Scheduler and enter the Name and Description.

Here, you can also select your Scanner, Migset and Importer.

Next, on the Frequency tab, you have all the options to configure when your scheduled job will trigger and when it will stop triggering. Here you can also configure the email reporting feature.

You can click Save to save the Scheduler and it will start at the scheduled time.

If you open the History tab you can see the list of all runs of the scheduler along with some information about the status of each run.

Mapping Lists

The mapping lists are a simple and very powerful feature of migration-center. They can be used for a wide variety of scenarios.

A mapping list is just a collection of key - value pairs. A mapping list can also contain multiple values for one key. You can create one globally using the Configure -> Mapping List menu. This will make the mapping list available for use in any migset.

Or you can also create it directly in a migset for use only in that migset.

To use your created mapping list you must use the mapValue() function inside a migset's transformation rules.

The value to be transformed is matched with the values in the Key column of the mapping list. If a value is found then the function returns the equivalent value from the Value column. If the value cannot be matched or the source value is null, the function will trigger a Transformation error on the object or return an empty value (depending if Report missing values is set to 1 or 0).

Migration-center uses an Oracle database to store information about documents, migration sets, users, jobs, settings and others.

This guide describes the process of creating an Oracle 19c (v19.3.0.0.0) database instance on Microsoft Windows. Even though the description is very detailed, the installing administrator is expected to have a good degree of experience in configuring databases.

Database configuration assistant

Open the Database Configuration Assistant from the Oracle program group in the Start menu. The assistant will guide you through the creation steps.

Step 1: Database Operation

Select the Create Database option and click Next.

Step 2: Creation Mode

It is recommended to go with the Advanced configuration.

Step 3: Deployment Type

For the purpose of most installations Oracle Singla Instance Database and General Purpose is sufficient.

Step 4: Database identification

Define the database name here. The name must be unique, meaning that there should not be another database with this name on the network. The SID is the name of a database instance and can differ – if desired - from the global database name. In order to make an easy identification of the database possible, a descriptive name should be selected, for instance „migration“.

You can either create it as a Container DB with a Pluggable DB inside or not, depending on preference.

Step 5: Storage Options

For use with migration-center the “File System” option is sufficient. For more information on the “ASM” method, please refer to the Oracle documentation.

Step 6: Recovery Options

This step describes the database's archiving and recovery modes. The default settings are fine here.

Step 7: Network Options

If a default listener is not already configured, you can select one here or choose to create a new one:

Step 8: Configuration Options

This step contains several tabs on which the configuration options for the new database must be specified.

Memory

The memory values of the database need to be specified here. For migration-center, user-defined settings are required. Please review the Database chapter the Sizing Guide for the recommended amount of memory allocated to the database instance.

For most projects Automatic Memory Management is a good option.

Sizing

At this point the block sizes and maximum number of user processes are defined. The default block size and maximum number of processes can be applied.

Character Sets

The Unicode character set AL32UTF8 must be selected here. This character set will ensure that all special characters of any language will be correctly saved in the database.

Connection Mode

The option Dedicated Server Mode connection type is appropriate for migration-center.

Sample Schemas

Sample Schemas are not needed so leave the option unchecked.

Step 9: Management options

To manage the database, Oracle Enterprise Manager is recommended. In Oracle 19c, databases can be managed centrally using the Grid Control or locally using the Database Control. Since the choice of database management has no influence on the operability of migration-center, this can be configured according to personal preferences or company policies. For the purposes of this guide the local Database Control will not be selected here. E-mail notification and backup can be configured separately at a later time, if necessary.

Step 10: User Credentials

Now the passwords for the Oracle system accounts SYS, SYSTEM and PDBADMIN must be entered and confirmed. These accounts with their passwords are needed for the installation of the migration-center database schema.

Step 11: Creation Option

Optionally a script can be generated which contains all the settings for the creation of this database. With this script, the setup can be repeated later if necessary. Moreover this script can be used as documentation for the settings used.

Step 12: Summary

The assistant shows a summary of the previous settings. This summary can be stored for documentation purposes in an RSP file.

Clicking on Finish will start the database creation process. This process can take some time.

Additional Information

The Oracle database Configuration Assistant generates the following tablespaces (we assume that unused tablespace is marked to be deleted):

• INDX

• SYSTEM

• TEMP

• TOOLS

• UNDOTBS

• USERS

Summary of the most important Oracle 19c installation parameters

Oracle components:

• Oracle Database

• Oracle XML DB

• Oracle Net Listener

• Oracle Call Interface

General options:

• Oracle JVM

• Enterprise Manager Repository (optional)

Initialization parameters:

• Dependent on server

Character sets:

• Database character set (AL32UTF8)

Data files:

• Use standard parameters

Control files:

• Use standard parameters

Redo log groups:

• Use standard parameters

migration-center 23.2

Features & Enhancements

• Web Client

  • Improve migset load / save performance (#67260)

  • Improve WebClient UI stability when during CRUD operations (#67053)

  • Various small UI improvements

• Job Server

  • Remove unused log4j 1.x with vulnerability from mc-database-adapter (#68606)

• CSV / Excel Scanner

  • Upgrade CSV/Excel scanner Apache POI to 5.2.3 (#67399)

• SharePoint Online Importer

  • Increase upload file size limit to 250 GB (#68607)

• Box Importer

  • Box importer improvements (#67364)

  • Validate the content integrity based on the calculated SHA1 checksum (#66631)

  • Update to SDK 4.2.1 and use App Authentication (#66632)

Fixes

• OTCS Scanner

  • Infinite cycle when scanning business workspaces (#66943)

• SharePoint Online Batch Importer

  • Required column is not ignored because the SharePoint server is set to another language than English (#67384)

• Veeva Importer

  • Relations with source_version_specific and target_version_specific are not imported correctly (#66460)

• Veeva Scanner

  • No objects are scanned if the selection document vql contains "&" (#67243)

• Web Client

  • UTF8 characters are not correctly exported to CSV from Objects Views (#68456)

  • Adding or pasting new rules before the rules are loaded, results in the new rule disappearing (#64941)

  • Migset section sends multiple transfomation requests which results in inconsisstent TR loading (#66449)

  • Refreshing or accessing via URL the Migset Object Preview results in blank screen (#66804)

  • Migset type dropdown is not disabled when copying a migset (#67320)

  • Changing selected row immediately after delete will change selection after delete finishes (#66988)

  • Getting exclusion attribtue values fails when attribtue name contains slash (#67082)

  • Previously used object table filters remain in requests after leaving and revisiting the UI (#67311)

  • The existing adapter can be save with empty value for mandatory parameter (#66613)

  • Tables are cached when switching MC databases (#60127)

  • Clicking Cancel in customize columns resets all columns to checked (#66204)

  • Creating a new rule doesn't deselect previously selected rule (#67487)

  • Adaptors cache is not refreshed when adding new adapter or parameters or when switching databases (#60180)

  • Saving a copy of a migset while being on Transformations tab does not replace the url (#62541)

  • Objects table filter has only visible columns available for filtering (#66451)

  • Associations are copied and removed from previous migset when importing migset config on the same DB (#68463)

  • Invalid migset splitting when selected objects contain both version trees and objects without versions (#66992)

  • Split Migset does not work with Audi Trails (#66454)

  • Migset UI corrupted after creating a new migset, saving and then editing again (#66807)

  • Migset exclusions modifies the displayed attribute names (#66836)

  • Object Preview returns 0 objects when using like(String) advanced filter (#66839)

Known Issues

• Box Importer

  • The \ character is not recognized as folder path separator as is / (#68448)

  • Importing to existent folder with autoCreateFolders false throws exception (#68449)

migration-center 23.1

Features & Enhancements

• Jobserver

  • Remove .gz archiving from rolling policy for Jobserver logback logs (#65728)

• Alfresco Adapters

  • Added support for Alfresco 7.3.1 (#65050)

• D2 Importer

  • Added Support for D2 22.4 (#64123)

• Documentum Adapters

  • Added support for Documentum 22.4

• Cara Importer

  • Added support for setting creation date for the content and renditions (#64721)

• OTCS Adapters

  • Added support for OTCS 22.4 (#65052, #66584)

  • Scan records management data and clasifications (#65048)

• Veeva Importer

  • Upgrade Veeva API to the latest version 22.3 (#65726)

  • Make by bypassing validation rules and reference constraints optional (#65529)

• WebClient

  • Tomcat Upgrade to latest stable version (#65733)

  • Added stop button for migset background processing (#65735)

  • New Object Search functionality (#57500)

  • Extract object to csv only with visible columns (#65724)

  • Allow returning empty values from mapping list (#66052)

Fixes

• MC Database:

  • ORA-22813: operand value exceeds system limits (#65106)

• Alfresco Importer

  • Aspect with no attributes is not set (#64266)

  • Cannot import obj with aspect that has no attributes (#65606)

• Alfresco Scanner

  • Scanners sets cm:versionType incorrectly for scanned versions (#64237)

• Cara Importer

  • Setting null values for repeating attributes may not work properly (#65736)

  • Importing structure updates makes the previous last version not be a structure anymore (#63179)

• Database Scanner

  • Database scanner is not case sensitive when scanning IDs (#65648)

• Documentum Importer

  • When i_vstamp > 999999 the object cannot be scanned (#64399)

• SharePoint Online Importer

  • Importer throws No Method Found error when CSOM component is used (#66132)

  • Importer does not throw error when importing missing mandatory attributes if managed metadata is also set (#66177)

  • People/Groups field cannot be set on another site collection than the ones from root site collection (#65146)

  • Empty file cannot be imported using spo importer (#65155)

  • Importer does not set Modified By (Editor) attribute (#64811)

  • The type SP.ListItemEntityCollection does not support HTTP DELETE method. error when auto creating folders (#65526)

  • The type SP.ListItemEntityCollection does not support HTTP DELETE method. error when importing into folders with special characters (#65533)

• SharePoint Online Batch Importer

  • Importer reaches deadlock on throttle when auto creating/checking folder (#66199)

  • Some errors are not set in processing_message field (#62883)

  • The error message "Object was NOT found in verification step!" is not self explanatory (#62884)

  • SPO Batch Importer does not throw error when importing objects missing required attributes (#63335)

• SharePoint Online Importer + Batch Importer

  • Multiple lines of text attribute should show multivalue attributes on multiple lines (#64597)

• Veeva Importer

  • Missing mandatory attribute still throws error even when inactive for Veeva Objects (#64682)

  • Veeva importer cannot create the root folder (#64411)

  • NPE is thrown when the returned value from attribute map is null (#64432)

• WebClient

  • View Attributes Dialog does not update table (#65656)

  • Import mapping list values from CSV always sets "Exact Match" to 0 in DB (#65878)

  • Mapping list is removed from migset when importing values from CSV (#65884)

  • Run adapter button disables after a run until response is received (#64319)

  • CTRL + Click multi selection does not include the already selected row (#64264)

  • MultiColumnMapValue is not working when using index all for value to be mapped (#65948)

  • Condition parameters in "if" function do not handle "all" and "any" index properly (#64938)

  • Params that do not allow All show All when switching from User Value or Source Attribute to Previous Step in a multivalue rule (#65498)

  • Function parameter index does not take into account Rule Multivalue check (#64156)

  • View Attributes from Scheduler Imported/Error Objects not working (#64978)

Known Issues

• WebClient

  • Global Object Search button is active when no search parameters are set (#65531)

• OTCS Scanner

  • OTCS Scanner throws error when rmWebserviceUrl is empty (#66471) Fixed in MC23.1_hotfix1.

• InfoArchive Importer

  • InfoArchive Importer leaves xml file in Temp when running out of disk space (#66241)

migration-center 22.2

Features & Enhancements

• General

  • Desktop Client has been retired. The new WebClient, introduced in version 22.1, is now the only UI available.

• Database:

  • Add support for AWS installation (#62467)

• Alfresco:

  • Add support Alfresco 7.1 (#60998)

  • Add support Alfresco 7.2 (#63427)

• Cara Importer:

  • Add support for custom attributes in Cara audit trails (#63368)

  • Add support for Cara 5.7 (#63175)

• OnBase Importer:

  • Allows the user to set the document date (#62716)

• OTCS\Scanner:

  • Scan projects specific metadata (#64390)

  • Add support for OpenText CS 21.4 (#61431)

• SharePoint Online Importer (Batch):

  • Add source type to the imported documents (#63881)

• Veeva Importer:

  • Adapt the client ID format for the best practice (#62331)

  • Import VD content as binder attachment (#63367)

  • Veeva importer should allow setting binder permissions (#63364)

  • Veeva importer allows importing major an minor versions of binders (#63365)

  • Veeva importer should allow importing incomplete binders (#63366)

  • Improve performance when importing binders with preserveVersionBinding (#63586)

• Web Client:

  • Upgrade WebClient to Material UI v5 (#63369)

  • Address Security Concerns (#64385)

  • Various changes and improvements of the UI

Fixes

• Database:

  • Removed duplicate attribute country__v in veeva quality document object type (#63361)

• Job Server:

  • Fix vulnerability CVE-2022-42889 (#64144)

• Cara Importer:

  • Cara relation not imported with the message Child object '...' not found (#62754)

  • Cara importer does not check immutable, is_template and status attributes (#62793)

  • Cara performance issue when importing structures (#63044)

• InfoArchive Importer:

  • Invalid zips created when running multiple importers in parallel (#64206)

• OTCS Importer:

  • Import does not work with ACL with empty permissions (#61354)

  • From Date attribute is set to the import date even when null (#63739)

• OTCS Scanner:

  • When having insufficient permissions, an error is thrown and documents are not scanned (#63222)

• SharePoint Online Importer (Batch):

  • SPO- Comparison method violates its general contract (#63185)

  • SharePoint Online Batch Importer does not work via Proxy with Authentication (#62976)

• SharePoint Online Importer (REST):

  • SharePoint Online importer does not work via Proxy with Authentication (#63010)

  • Mandatory managed metadata attributes throw error when importing with SPO Standard importer (#64221)

  • SP appClientSecret is not recognized when ends with = (#63923)

• SharePoint Online Scanner:

  • CAML query not working on SPO Scanner (#59597)

  • SharePoint throws timeout error occasionally when scanning libraries with large number of documents (#52865)

• Veeva Importer:

  • Veeva adapters freeze when an exception is thrown when uploading the content (#62244)

  • Updating documents does not work from 3.15upd1 (#62986)

  • Veeva importer hangs when the connection with Veeva Vault is lost (#63593)

  • Setting document_number__v does not work on binders (#62870)

  • Setting Status does not work on first version of binder (#62875)

  • Veeva attachments are always linked to the last version (#62880)

• Web Client:

  • Object Type attribute change not detected when selected with click + drag outside of section (#64199)

  • Associations are not removed when deleting a rule that was already associated and saved in the DB (#64201)

  • Delete Mapping List Value does not work properly (#63764)

  • TR Step error and warning messages are not displayed (#63920)

  • Deleting new rules that aren't saved but are associated, causes migset error when saving (#64218)

  • Newline character can be entered in the name field of certain objects (#63944)

  • Misleading error on importing CSV with wrong format (#63962)

  • Object Type row can't be deleted after a saving an edit (#63999)

  • Duplicated transformation rules do not appear in associations rule list (#64011)

  • Sorting by date columns has reverse order and does not handle empty values properly (#64020)

  • Some relation columns are hidden (#64086)

  • User can delete previously selected runs from different scanner/importer (#62909)

  • Reset objects from migset has no confirmation dialog (#62982)

  • Copy Pasting system rules with overwrite does not work as expected (#62999)

  • Step stays stuck pointing to previous step that is now no longer valid. (#63075)

  • Double clicking on mapping list values causes the values to disappear or change cell (#61493)

  • Mapping list input field for Value columns gets selected only after several clicks (#61699)

  • Red and Yellow Transformation Rules and Steps have no Highlight color when selected (#62057)

  • Selecting objects in new migset with no name results in "migset with id 0 cannot be found error" (#62288)

  • Importing Configuration in wrong migset type changes system rules (#62518)

  • Pressing the logout button causes the token to be deleted even if the user decides not to log out (#62548)

  • Deleting a freshly created and saved Object Type is not performed (#62576)

  • JDBC connection string does not work in some cases (#62742)

  • IF function not saved properly when using PreviousStep (#62765)

  • Existing exclude filter from migset copy for new set of documents shows duplicates (#62844)

  • "Reset imported items" remains checked sometimes (#62845)

Known Issues

• Alfresco Importer:

  • Aspect/Type with no attributes is not set (#64266)

• Veeva Importer:

  • Misleading error message when importing binder with non existent content location path (#63069)

  • Setting binder permissions with an Auto Managed Group results in warning (#63032)

  • Error message is to generic when setting group to role that supports only users (#63033)

migration-center 22.1.0

This release brings the new migration-center Web Client component to replace the existing Desktop Client. It comes with all the existing features as well as a few new ones:

• MultiColumn mapping lists

• Better handling of the migset configurations

• Copy / paste transformation rules

• Search / filter in most tables and lists

• Split migset feature

• Export mapping lists and object types

• New column with total objects per scanner (all runs)

• Analytics / insights capabilities

The dependency on Oracle Client was removed by providing a new Database installer that connects via JDBC and by using the new WebClient.

The versioning was changed this release from the previous incremental versioning to a calendar versioning system.

Features & Enhancements

• General

  • New migration-center Web Client (#54598)

  • New Database Installer that does not require Oracle Client (#60785)

  • Added support for Oracle 21c. Remove support for Oracle 10g (#60720)

• Documentum Importer

  • Added support for Documentum 21.4 (#60237)

• Documentum Scanner

  • Added ability to filter scanned relations (#58806)

  • Allow scanning a list of ids from a file (#59324)

  • Allow providing dqlString with a length > 4000 characters (#60183)

• D2 Importer

  • Added support for D2 21.4 (#60236)

  • Added mapping of virtual document version binding labels in D2 importer (#52032)

• OpenText Scanner and Importer

  • Added support scanning and importing projects (#61647)

• Veeva Importer

  • Delete the documents with a specific attribute set to true (#60692)

• Alfresco Scanner

  • Allow excluding source attributes (#61956)

Fixes

• Documentum Scanner

  • The values of attribute_list in Audit trails are scanned in reverse order (#61134)

  • Mapping relations in Documentum scanner does not work (#62588)

• D2 Importer

  • D2 validation skipped in some cases: - when property page contains a label that has a value assistance - when property page contains a combo field that are not linked to a property and have "Auto Select Single value list" checked (#60874)

• Database Scanner

  • Database scanner remove some characters from filenames when exporting content (#61073)

  • Database scanner null pointer (#62181)

  • Database scanner null pointer when object with parent is scanned before parent(#62264)

  • Database scanner throws "no versions returned!" errors on valid data (#62627)

  • Make key values in query configuration file case insensitive (#60509)

• OpenText Importer

  • Importing compound docs updates with missing parent, results in nullPointerException (#55316)

  • Import does not work with ACL with empty permissions (#61354)

• OpenText Scanner

  • No objects scanned when rootFolderIds <> "2000" and scanFolderPaths = "/" (#59292)

  • OpenText scanner initializer authenticates too many times (#62301)

• SharePoint Batch Importer

  • Importing documents failed because the local xorHash is not the same with the one computed on SharePoint (#61262)

  • Could not find SPO time zone with description '(UTC-05:00) Eastern Time (US and Canada) (#61267)

• Filesystem Scanner

  • FS scanner error logging not working correctly (#61051)

• Veeva Importer

  • Cannot import objects with a field that refers to itself (#61472)

Known Issues

General issues:

• OpenText Scanner

  • Invalid characters makes OTCS scanner initializer to stop with error (#62332)

• SharePoint Scanner

  • SharePoint OnPrem scanner not working with Java 11 (#61270)

• Veeva Importer

  • Setting value with ',' to a picklist attribute which allows multi-value throws exception (#62501)

  • Map relation names containing spaces does not work as expected (#62657)

• D2 Importer

  • No error is thrown when virtual document version binding label is set to CURRENT and no child has CURRENT label (#60497)

WebClient issues:

• Deleting on freshly created and saved Object Type is not performed (#62576)

• Pressing the logout button causes the token to be deleted even if the user decides not to log out (#62548)

• Migset openSubTab url namings are not accurate for Properties tab (#62545)

• Saving a copy of a migset while being on Transformations tab does not replace the url (#62541)

• Migration Status UI changes when changing tabs (#62472)

• Multi-value type rule for FileSystem scanner results in multi-value target_type system rule after upgrade to 22.1 (#62464)

• Object distribution: scanner definition can be selected without selecting type first (#62354)

• Selecting objects in new migset with no name results in "migset with id 0 cannot be found error" (#62288)

• Length limitations are not imposed in all fields causing ISE when saving (#62254)

• Very long names for Transformation rules cause the whole view to scroll (#62250)

• Red and Yellow Transformation Rules and Steps have no Highlight color when selected (#62057)

• Red Transformation Rules are not updated after Selecting / Deselecting objects (#62046)

• Select Objects has incorrect behavior after selecting objects when filters cause no objects to be selected (#62043)

• Multi Column mapping lists are deleted by the Delphi Client (#62022)

• Mapping list input field for Value columns gets selected only after several clicks (#61699)

• CTRL+A does not work on View Value dialog (#61676)

• Delay when editing the name of a mapping list with many rows loaded (#61614)

• Columns are ignored if CSV has more columns than mapping list (#61520)

• Double clicking on mapping list values causes the values to disappear or change cell (#61493)

• Closing too many notifications takes too long (#60887)

• Moving selection from an object type attribute to the other is considered a change (#60883)

• WebClient Uninstaller does not remove some files and environment variables (#60665)

• Validate objects feature was removed from WebClient and creates confusion (#60568)

• Migset saving has delay which can create unexpected behaviors (#60204)

• There is a small delay between dropdown close and being able to select another field (#60203)

• Adaptors definitions are not refreshed when adding new adapter in Database (#60180)

• Tables are cached when switching MC databases (#60127)

• Resizing columns in Scanner/Migset/Importers behaves strangely (#57265)

migration-center 3.17 Update 4

This release contains the following fixes and updates:

• Updated spring libraries for potential vulnerability CVE-2022-22965 (#61574)

• Fixed error when setting user attributes to "Guest" user using the SharePoint Online Batch Importer (#60948)

Remember to reinstall the CSOM service as well for the SharePoint Online Batch Importer as described here.

migration-center 3.17 Update 3

This release is a collection of cumulative fixes that have been done since version 3.17 Update 2.

Fixes

• Veeva Importer:

  • Importing submission to Veeva RIM with skipUploadContent throws error but import is successful (#60418)

  • Importing submission with skipUploadContent checked does not work (#60306)

  • Uploading/Downloading content to/from FTP Staging Folder does not work with REST calls (#60493)

  • Setting object_type__v attribute throws NullPointerException (#60659)

  • Updating objects throws an error (#60571)

  • The version tree is not correctly scanned when the minor version is greater than 9 (#60957)

  • Submission response is not parsed correctly (#60780)

• Veeva Scanner:

  • Veeva scanner continue working on background after stop (#60805)

• SharePoint Online Scanner:

  • Scanning objects throws an error when parsing the creation date (#60751)

  • An SQL Exception is thrown when the attribute value is greater than the limit (#60208)

  • The build sometimes is compiled for 32 bit platform (#60211)

  • The total number of objects displayed in summary is not correct (#60205)

• D2 Importer:

  • NullPointerException when importing VD relation updates (#60470)

• Dctm Importer (NCC)

  • Updating content on Documnetum NCC with ECS does not work properly (#60795)

migration-center 3.17 Update 2

Features & Enhancements

• Generis Cara Importer:

  • Add support for importing relations (#59664)

  • Add support for setting rendition identifier(#60027)

Known Issues & Limitations

• Generis Cara Importer:

  • When binding relations by version label, no error is thrown when incorrect or missing version label mapping is provided(#60093)

  • Importing a base document and one update (as result of delta scan) results in unpredictable behavior(#60118)

migration-center 3.17 Update 1

Features & Enhancements

• Veeva Importer:

  • Multi-threading for upload content process (#59158)

  • Upload content using File Staging REST API (#59680)

  • Added object type order when importing Veeva Objects (#59085)

  • Updated to use API 21.2 (#59343)

• Veeva Scanner:

  • Multi-threading for download content process (#59158)

  • Retrieving inactive dictionary value from Veeva (#59516)

  • Scan new audit trails in Delta scan (#59641)

  • Download the content from FTP by using REST API (#59160)

  • Updated to use API 21.2 (#59684)

Fixes

• General:

  • Removed SQLJUTL package dependency which caused errors on certain Oracle DBs (#59700)

• SharePoint Online Importer:

  • Removed the need for having minor versions enabled when importing folder updates (#59570)

Known Issues & Limitations

• InfoArchvie Importer:

  • Using Java 8 when generating large PDI files may result in incorrect values in the PDI file (#59214)

• Veeva Importer:

  • objectsOrder feature is ignored if it does not contain all object_name values from the migset (#59981)

  • Setting object_name values that don't exist in Veeva in objectOrder does not throw error (#59980)

migration-center 3.17

Features & Enhancements

• General:

  • Transformation function getDataFromSql can return multiple values (#535420)

• Hyland OnBase Importer

  • Import documents

  • Set custom metadata

  • Import document revisions

  • Delta migration (only for metadata)

• Amazon Comprehend Enrich Scanner

  • Enrich documents metadata based on the content

  • Language detection

  • Extract entities (standard and custom)

  • Support custom classifiers

• Filesystem Scanner:

  • Make versioning case insensitive (#58656)

• Documentum Scanner:

  • Allow more flexible queries for selecting documents to be scanned (#58345)

  • Create counter for already scanned objects in the execution summary (#58907)

  • Export documents with content_location pointing to the path in the storage (#54317)

• Cara Importer:

  • Import audit trails from Documentum as audit trails objects (#58797)

  • Index the imported documents (#59513)

Fixes

• General:

  • Scheduler next run date not calculated correctly (#58845)

• Cara Importer:

  • Fix reporting errors for missing/incorrect system attributes (#58488)

  • Fix nonintuitive error message when required content or rendition attributes are not set (#58608)

• CSV-Excel Scanner:

  • Fix scanning CSV with UTF8 - BOM with first column used as ID (#54010)

• Veeva Importer:

  • Fix max length for system rules (#59046)

  • Attributes mapping does not work properly when the object_type__v is not the same as the object that is imported (#57383)

• Veeva Scanner:

  • Binder relations are scanned even if the child documents are not (#56230)

• SharePoint Online Importer:

  • Temp file is deleted early if HTML error is thrown (#58869)

• OpenText Content Server Importer:

  • Importing compound documents doesn't fail when folder with same name already exists (#52038)

• D2 Importer:

  • Repeating default values are not set correctly (#58692)

Known Issues & Limitations

• Cara Importer:

  • Asynchronous Indexing not setting index on documents (#59574)

• SharePoint Online Scanner:

  • CAML query not working on SPO Scanner (#59597)

migration-center 3.16

Features & Enhancements

• General

  • Add support for Java 11 for all adapters (#53313)

  • Add new transformation function: GetInternalAttributeValue (#57376)

  • Add new transformation function: CalculateNewNumber (#58237)

• Cara Importer (NEW)

  • Add support for checksum verification (#57744)

  • Add support for importing VDs (#57756)

  • Add support for proxy communication (#58057)

  • Add support for uploading content using REST (#58169)

• D2 InPlace Adapter (NEW)

  • D2 Auto-Naming functionality (#57662)

  • D2 Auto-Linking functionality (#57663)

  • D2 Auto-Security functionality (#57664)

  • Validate attributes values based on D2 dictionaries (#57666)

  • Apply D2 rules based on a document’s owner (#57667)

• CSV/Excel Scanner

  • Add support for delta migration on CSV/Excel scanner (#56911)

• D2 Importer

  • Add support for D2 20.4 (#55909)

• Database Scanner

  • Improve performance when scanning data from a single query (#56714)

• Documentum Importer/Scanner

  • Add support for DCTM server 20.4 (#55904)

• Filesystem Scanner

  • Add support for scanning paths provided in a text file (#57073)

  • Specify folders to exclude as relative paths (#57074)

  • Enhance explicit versioning to new versions to existing ones during delta scan(#58563)

• InfoArchive Importer

  • Add support for InfoArchive 20.4 (#55912)

  • Add support for generating huge PDI files (#56912)

• Opentext Content Server Scanner/Importer

  • Add support for OpenText Content Server 20.4 (#55901)

• SharePoint Online Batch Importer

  • Set retention policy labels (#56114)

  • Set sensitivity labels (#57086)

  • Add support for QuickXorHash (needed for files > 15 GB) (#57226)

Fixes

• CSV/Excel Scanner

  • Cells that have nothing but are scanned as null (#57228)

• Documentum Importer

  • Repeating attributes are not rewritten on new versions (#58231)

• Opentext Content Server Importer

  • The job status is not properly set when occurring OutOfMemory error (#57022)

• SharePoint Online Batch Importer

  • MIP Service fails to load DLL (#58038)

• Veeva Scanner

  • The temporary location is not cleared up after the scan run (#57853)

• Veeva Importer

  • Validation errors are not cleared after each validated document (#57206)

  • Submissions cannot be imported when having more than 200 applications (#58062)

Known Issues & Limitations

• Veeva Scanner

  • The binder relations are scanned even if the children documents are not (#56230)

• SharePoint Online Batch Importer

  • When trying to import a broken version tree, the import fails for all documents (even the ones that had a correct version tree) with an error status (#57099)

• Database Scanner

  • The summary is not completely accurate when using a single query (#58228)

• InfoArchive Importer

  • The first version of child doc remains validated when includeChildrenVersions is set to false and includeChildrenOnce is set to true (#57766)

• Veeva Importer

  • Attributes mapping does not work properly when the object_type__v is not the same as the object that is imported (#57383)

• Opentext Content Server Importer

  • NPE when importing documents with no content (#58288)

migration-center 3.15 Update 2

Features & Enhancements

• General

  • Migrate OT shortcuts and URLs to SPO link documents (#55974)

  • New TrackWise Digital importer available (#53977)

  • Improve the performance of the mapping list transformations (#56913)

• SharePoint Online Batch Importer

  • Improve robustness of verification step (#55898)

  • Allow import into multiple sites (#56043)

  • Save imported object URL in object_info1 column (#56113)

• SharePoint Online Scanner

  • App-Only authentication in SPO scanner (#54259)

• Veeva Scanner

  • Automatic resume after daily API limit was exceeded (#56898)

Fixes

• File System Scanner

  • content_location and mc_content_location not updated when using moveFilesToFolder (#56471)

  • Metadata files are not moved when moveFileToFolder is checked (#56488)

• SharePoint Online Classic Importer

  • 'null' added to path when importing to root folder (#56603)

  • Move folder not working in SPO importer (#56703)

• Veeva Importer

  • Document with auto-generated name __v cannot be imported (#56684)

  • Error when importing doc with empty string in attachments and skipUploadToFTP (#56826)

• Veeva Scanner

  • The rendition for already scanned objects is exported to disk in some cases (#56283)

  • Proxy configuration ignored for HTTP requests (#56566)

  • Running scanners in parallel fails with error (#56763)

Known Issues & Limitations

• Veeva Scanner

  • The binder relations are scanned even if the children documents are not (#56230)

• InfoArchive Importer

  • OutOfMemory exception might be thrown by InforArchive importer when generating very large SIP file (#55698)

• SharePoint Online Batch Importer

  • When trying to import a broken version tree, the import fails for all documents (even the ones that had a correct version tree) with an error status (#57099)

• SharePoint On-Prem Importer

  • Moving folders fails with 'File not found' error (#57111)

migration-center 3.15 Update 1

Features & Enhancements

• General

  • Add Veeva Scanner that exports documents and binders from Veeva Vault (#54569)

  • Migrate OpenText shortcuts and URLs to SPO link documents (#55974)

• Documentum Scanner

  • Export all folder paths of all folders where a document is linked (#55486)

• OpenText Scanner

  • Add the URL/path of the original object to the scanned shortcut (#56206)

  • Allow users to configure a list of workspaces/root nodes to be scanned (#55899)

  • Scan URLs as OpenText(object) type so they can be imported to other systems (ex: SharePoint Online) (#56001)

• SharePoint Online Importer

  • Add support for setting sensitivity label for importing documents (#55645)

• Veeva Importer

  • Enable Migration Mode programmatically for the imported objects so Migration Mode is not necessary to be enabled on the vault level (#55493)

Fixes

• Veeva Importer

  • Duplicate values are not supported for object_type__v attribute in RIM Vault (#55664)

Known Issues & Limitations

• Veeva Scanner

  • The renditions for already scanned objects is exported to disk in some cases (#56283)

  • The binder relations are scanned even if the children documents are not (#56230)

• InfoArchive Importer

  • OutOfMemory exception might be thrown by InforArchive importer when generating very large SIP file (#55698)

migration-center 3.15

Features & Enhancements

• CSV - Excel Scanner:

  • Added support for scanning repeating attributes (#54993)

• InfoArchive Importer:

  • Added support for multiple references to the same content (#55529)

• OTCS Scanner:

  • Added support for scanning CAD documents as regular documents (#55900)

• SharePoint Online Batch Importer:

  • Added support for setting approval status on documents (#54990)

  • Added support for setting version numbering (#55505)

  • Added support for setting Lookup field type (#55521)

• Veeva Importer:

  • Added support for delta migration of Veeva objects (#54928)

  • Added support for importing attachments for Veeva Objects (#55535)

• Core Database:

  • Added additional multi-value transformation functions (#55424)

Fixes

• OTCS Importer:

  • Fixed record date not being set in opentext_rm_classification (#55431)

• SharePoint Online Batch Importer:

  • Fixed import failing with invalid XML characters in attributes (#55007)

  • Fixed import failing verification (#55574)

  • Fixed import failing into library with deep path (#55745)

• SharePoint Online Importer:

  • Fixed import failing into site collection URL with spaces (#55571)

  • Fixed not being able to assign AD group (#55796)

  • Fixed error on folder update (#55870)

Known Issues & Limitations

• Alfresco Scanner:

  • Scan doc with versions edited online while autoVersion false, but had autoVersion switched to true afterwards has wrong version content (#55983)

• CSV - Excel Scanner:

  • Content_location is not scanned as multi-value (#55635)

• Veeva Importer:

  • Objects are not rolled back if attachment was set on objects that do not support attachments (#55939)

• Documentum NCC Importer:

  • Delta migration for the multi-page content does not work properly when a new page is added to the primary content (#55739)

migration-center 3.14 Update 1

Features & Enhancements

• Veeva Importer

  • New feature: Import documents using existing content from FTP server (#55303)

  • New feature: Add support for importing relations (#54991)

• SharePoint Online Importer (Batch)

  • New feature: Allow assignment of any valid SP user (#55219)

  • Support for OneDrive (#54262)

• Filesystem Scanner

  • New feature: Perform transformation of source object XML files before processing (#54776)

Fixes

• SharePoint Online Importer (Batch)

  • Update objects not marked as processed/imported (#55058)

• Veeva Importer

  • Import version tree with renditions fails (#55396)

• SharePoint Importer

  • Folder and document get created although a column cannot be set (#55001)

  • SPO importer fails setting lookup column with a NULL value (#55140)

  • CSOM Processor fails with 401 Unauthorized error if a job ran longer than 24 hours (#55323)

• Opentext Scanner

  • Keywords system rule is limited to 255 characters for Physical Objects migset (#55341)

Known Issues & Limitations

• General / logging

  • The installer does not update the location of the Job Server's log files. So if you do not want to use the default location for log files, which is <Job Server Home>/logs, you need to manually update the log file location in the <Job Server Home>/lib/mc-core/logback.xml configuration file (#54732)

migration-center 3.14

Features & Enhancements

• Alfresco Scanner

  • New feature: Scan only last "n" versions (#54289)

  • New feature: Scan multiple sites (#54291)

• D2 Importer

  • Support for D2 20.2

• Documentum Scanner / Importer

  • Support for Documentum Server 20.2

• OpenText Importer

  • Support for OpenText Content Server 20.2

• OpenText Scanner

  • New feature: Scan shortcuts as distinct MC objects (#53710)

  • New feature: Scan any folder subtype objects (#53711)

• SharePoint Online Importer (Classic)

  • New feature: Add user-agent traffic decoration (#52837)

• SharePoint Online Importer (Batch)

  • New feature: Importing role assignments (#54440)

• Tools

  • New tool to export document type definitions from Veeva available (#51539)

Fixes

• OpenText Scanner

  • NPE occurs using excludeFolderPaths (#54326)

  • Wildcards do not work in the root folder (#54329)

  • Set attributes are not scanned if the name is longer than 100 chars (#54589)

• SharePoint Online Importer (Batch)

  • SPO batch importer checks wrong content location (#54568)

  • SPO batch importer throws error when importing large folder hierarchy (#54574)

  • NPE for objects with NULL value in levelInVersionTree in SPO batch importer (#54637)

• SharePoint Importer

  • Wrong max length limit for parentFolder system attribute when importing to SP 2019 (#54592)

Known Issues & Limitations

• General / logging

  • The installer does not update the location of the Job Server's log files. So if you do not want to use the default location for log files, which is <Job Server Home>/logs, you need to manually update the log file location in the <Job Server Home>/lib/mc-core/logback.xml configuration file (#54732)

• D2 Importer

  • Support for importing to D2 4.1, 4.5, and 4.6 was removed

• OpenText Scanner

  • Using binders in the parameters "scanFolderPaths" and "excludeFolderPaths" is not supported (#54963)

migration-center 3.13 Update 2

Features & Enhancements

• PowerShell tools:

  • Support multiple scan run IDs when creating migration sets (#54263)

• SharePoint Online importer:

  • Support for app-only principal authentication with SharePoint permissions (#54277)

• SharePoint Online Bulk importer:

  • Add mc_content_location in migset rules (#54182)

  • Support for app-only principal authentication with SharePoint permissions (#54277)

• SharePoint Online scanner:

  • Add scanLatestVersionOnly feature (#5615)

  • Add includeFolders and excludeFolders parameters (#53706)

Fixes

• OpenText importer: Wrong values for date attribute during physical objects import (#54255)

• OpenText scanner:

  • NPE occurs using excludeFolderPaths (#54326)

  • Wildcards do not work in the root folder (#54329)

• SharePoint (Online) importer: Automatically added content type not added to cache (#54420)

• SharePoint scanner: Permissions & User fields contain ambiguous username instead of login name (#54240)

migration-center 3.13

Features & Enhancements

• New SharePoint Online Batch Importer (#52665)

• Add “removeDuplicate” transformation function (#53528)

• Add support for Oracle 19c (#52930)

• Add support for Oracle JDK 11 & OpenJDK 11 (#53313)

• Add support for Oracle JDK 13 & OpenJDK 13 (#52492)

• Add support IA 16.7 (#52910)

• Added support for Alfresco 6.2.0 for Alfresco scanner and importer (#54108)

• Alfresco scanner and importer now require java 1.8 or later

• Documentum Scanner

  • Scan complete document audit trail and save it as rendition to the current document version (#52846)

• OpenText Importer

  • Assign objects to Physical Object Box with a dedicate system rule (#52748)

• SharePoint importer

  • Support valid filename characters on SharePoint on-prem (#53304)

• Documentum In-Place

  • Implement move content feature in Documentum In-Place adapter (#53518)

Fixes

• Fix typo in transformation function “ConverDateTimezones” (#53136)

• “GetDateFromString” transformation function returns null in some cases (#53164)

• Job server installation on Linux outdated in Installation Guide (#53714)

• OpenText Importer became laggy during impersonation after a certain number of requests (#53180)

• No error or warning when importing two renditions of the same type with OpenText Importer (#53124)

• The underlying connection was closed: An unexpected error occurred on a send in SharePoint Importer (#53099)

• Could not get SharePoint X-RequestDigest error message when space character in site collection name (#53190)

• SharePoint Importer should log error immediately if required fields are missing (#53844)

• HTTP 503 Server Unavailable Error when downloading large content files with SharePoint Online Scanner (#53673)

• Fix “Member ID is not valid” in OpenText scanner (#53482)

• Fix setting empty Vault Object reference in Veeva importer (#53573)

migration-center 3.12

Features and enhancements

• OTCS Scanner

  • Scanning Project objects as OTCS(container) with metadata (#52932)

  • Save version information as source attributes (#52292)

  • Support wildcards in folder paths (#52360)

  • Show number of warnings in job run report summary (#52845)

  • Scan user field with username instead of user id (#52847)

  • Objects scanned from inside projects now contain full parentFolder path (#52960)

  • Revised OpenText Adapter User Manuals (#52550)

• Veeva Importer

  • Re-authentication mechanism in case of session timeout (#52822)

  • Pause and retry mechanism to handle burst and daily API limits (#52823)

  • Support version binding when importing Veeva Vault binders (#52091)

  • Delta Migration of objects in Veeva Importer (#53037)

• Added support for Alfresco 6.1.1 in Alfresco Importer (#53008)

• Added support for annotations in D2 Importer (#53018)

• Documentum scanner now supports dqlExtendedString returning repeating values (#52587)

• Added Support for SP 2019 in SP Importer (#52870)

• Auto-Classification Module

  • Functionality to split dataset into training and test data (#52660)

  • Removing of library under GPL license (#52853)

  • Classification Process Logging (#52855)

Fixes

• Unresolved document file path in ScanRunExtractor (#52876)

• Filesystem importer writes invalid XML characters to metadata XML file (#52909)

• Missing dependency packages in AC module installer (#52935)

• Error validating classification when subtypes not unique (#52945)

Known Issues

• In Veeva Importer setting Binder version labels as major/minor does not work (#53160)

• In Veeva Importer document updates with empty values for attributes that were not empty does not delete existing value (#53229)

• In OTCS Scanner user fields that were deleted from a category are scanned as IDs (#52982)

migration-center 3.11

Features and enhancements

• New SharePoint Online Scanner (#52409)

• Made OTCS scanner more robust to errors (#52361)

• Imptoved OTCS scanner job run log output (#52365)

• FileSystem Importer now applies XSL transformation on whole unified metadata XML file (#52394)

• Veeva Importer now supports importing Documentum documents as renditions of a specific type to a Veeva Vault document (#52090)

Fixes

• Fixed bug in Filesystem Importer where attributes with no value were not being exported in XML metadata file (#52479)

• Fixed OTCS Scanner not scanning documents under folder inside nested projects (#52809)

• Fixed SPOnline importer bug when importing folders with a “%” in the name (#52857)

• Fixed SPOnline importer not refreshing token when all objects of a large import fail (#52775)

Known Issues

• SharePoint Online Scanner might receive timeout error from SharePoint Online when scanning libraries with more than 5000 documents (#52865)

migration-center 3.10

Features and enhancements

• Added support for Oracle database version 18c (#51451)

• Added support for migrating Veeva Vault Objects (#52136)

• Added support for version 16.x for the OpenText scanner (#50340)

• Added support for D2 versions 16.4 and 16.5 (#50972, #51530)

• Added switch for lifecycle error handling in D2 Importer (#50991)

• Updated the IBM Domino Scanner (#49173)

• Improved database security by changing default password (#51112)

• Improved performance of filesystem importer copy operation (#52320)

• Enhanced the RepeatingToSingleValue function to not throw exception when length exceeds 4000 bytes (#51798)

• Added missing file and folder name checks in the SP and SPO importer user guides (#52076)

• Updated linux Jobserver with new YAJSW wrapper (#52347)

• Box.net Importer, added the following features:

  • Import custom metadata (#50312)

  • Import tags (#50314)

  • Import comments (#50315)

  • Import tasks (#50316)

  • Add collaborators to the imported documents (#50602)

Fixes

• Fixed bug in DCTM adapters when calculating multi page content (#50442)

• Fixed bug in SharePoint scanner when scanning SP 2013+ on Windows Server (#51088)

• Fixed error messages bigger than 2000 characters not being saved in the database (#52357)

• SharePoint Importer, fixed the following bugs:

  • import taking a long time when content_location points to folder (#52115)

  • Importer not starting if adfsBaseURL contains trailing slash (#51941)

  • DEBUG messages getting logged despite log level ERROR in log4j (#52082)

  • Added debug log messages for queue building missing in SP importer (#52084)

  • Exception not caught when reverting import action (#52216)

  • Importer hanging when encountering an exception in RefreshDigest method (#52238)

  • Improved Retry handling (#52270)

  • Error when importing into site with %20 in the name (#52272)

  • autoCreateFolders always enabled (#52305)

  • NullPointerException in file upload when SPOnline throttling occurs (#52325)

migration-center 3.9 – update 3

Features and enhancements

• Some new features and enhancements in Domino Scanner

  • New scanner parameter "excludedAttributeTypes"

  • Default for scanner parameter "exportCompositeItems" now "0"

  • Scanner parameter "selectionFormula" set to be editable by default

  • 64bit support (based on IBM Domino); 32bit support remains unchanged (based on IBM Notes)

• InfoArchive Importer: provide a better way for importing email attachments scanned from IBM Domino

Fixes

• Domino Scanner: Extracted floating point numbers truncated/rounded to integer value

• Domino Scanner: Attributes of type "NumberRange" were not exported

• OpenText CS scanner: some logging improvements

• OpenText CS scanner: Fix scanning subprojects

• Veeva Vault Importer: Fix setting status_v for the root version

• Veeva Vault Importer: Fix importing VD relations that have order_no with decimals.

• Veeva Vault Importer: Fix a null pointer exception when logging some results

• CSV/Excel Scanner: Fix setting the internal processing type of the scanner

• Sharepoint Importer: Fix importing documents having # and % in the name

• Sharepoint Importer: Fix importing folder with two consecutive dots (..) in the name

• Sharepoint Importer: Fix token expiration after 24 hours.

Migration-center 3.9 update 2

Features and enhancements

• Add support for importing attachments to Veeva Vault.

Migration-center 3.9 update 1

Features and enhancements

• Added support for scanning nested compound documents in OTCS Scanner

• Added support for scanning the Nickname attribute for folders and documents in OTCS Scanner

• Added Proxy support for ADFS Authentication in SharePoint Importer

• Added support for filtering Scanners and Importers in MC Client

Fixes

• Fixed OTCS Scanner bug not scanning dates properly sometimes

• Fixed OTCS Scanner "Member Type not valid" error message

• Fixed OTCS Scanner nullPointerException when trying to get the owner name in specific cases

• Fixed OTCS Scanner nullPointerException when trying to scan certain Workspaces

• Fixed SharePoint Importer bug autoCreateFolders not working for values with leading slash

• Fixed SharePoint failing authentication with invalid XML chars in use name or password

migration-center 3.9

Features and enhancements

• Replaced Tanuki service wrapper with YAJSW (#51159)

• Added support for Java 64-bit (#51163)

• Added support for OpenJDK 8 (#51156)

• New CSV / Excel Scanner (#50343)

• Added Content Hash Calculation feature to OTCS scanner (#50736)

• Added support for java web service in OTCS Scanner (#51389)

• Added support for importing RIM submissions to Veeva Vault (#51208)

• Added support for importing Documentum Virtual Documents as Binders in Veeva Vault (#51188)

• Added support for setting references to existing master data objects in Veeva Vault (#51151)

• Added support for ADFS authentication in SPO Importer (#51414)

• Added new Transformation function for time-zone conversions (#51480)

Fixes

• Fixed bug when pulling content for updates with the Database scanner (#51142)

• Fixed error message in OTCS log (#51619)

• Fixed SharePoint Online importer too short path length limitation (#51491)

• Fixed SharePoint not resuming properly after pausing job for long time (#51492)

• Changed behavior of setting the file extension for the SharePoint Importer (#51503)

migration-center 3.8

Features and enhancements

• Documentum Scanner: Added option to scan only the latest version of a VD (#51019)

• OTCS Importer: Added support for importing Virtual Documents as Compound Documents (#51008)

• New transformation functions: GetDataFromSQL() and Length() (#50997, #50999)

• Database Scanner: New Delta migration feature (#50477)

• Documentum Importer: Extended waiting time for operations queue to finish (#50995)

Fixes

• Fixed error in D2 Importer when property pages contained tabs with visibility conditions (#50987)

• Removed unneeded jar file from D2 importer folder (#51073)

migration-center 3.7

Features and enhancements

• The Jobserver now requires Java 8. Java 7 is not anymore supported.

• New Veeva Vault importer

• Extended OpenText importer to import physical items (#50282)

• Changed the way of setting RM Classifications in OpenText importer (#50842).

Fixes

• Delta migration issue after upgrading from 3.2.5 or older (#50571)

Known issues

• Importing not allowed items in the physical item container is permitted (#50978)

• RM classifications for physical objects are not removed during delta (#50979)

• Physical objects properties of type date are not updated during delta migration (#50980)

• Veeva importer may fail to start, if DFC is installed on the same machine (#50981)

• No error reported when setting values to Inactive Fields in Veeva Importer (#50880)

• No error reported when setting values to fields that are not in the Type / Subtype / Classification used in Veeva Importer (#50871)

• No error reported when setting permissions not in the selected lifecycle in Veeva Importer (#50939)

migration-center 3.6

Features and enhancements

• New OpenText In-Place Adapter (#49994)

• Updated Tika library to version 1.17 for Filesystem scanner (#49258)

• OTCS scanner is now able to scan Business Workspaces (#49994)

• SharePoint Importer is now able to change the extension of files (#50142)

• D2 Importer validates the Enabled, Visible and Mandatory conditions in a Property Page (#50235)

• D2 Importer marks documents as Partially Imported when failing to apply a lifecycle action (#50274)

Fixes

• Fixed issue with saving migsets when plsql_optimize_level was set to 3 (#49160)

• Fixed issue with exporting BLOB content from a Firebird database (#49197)

• Fixed error in Documentum In-Place adapter with linking into inexistent folderpath (#49217)

• Fixed nullPointerException in SharePoint Importer when using proxy (#49232)

• Fixed bug in Documentum audit trail rollback scripts (#49943)

• Fixed nullPointerException in Alfresco Importer (#50027)

• Fixed error when scanning documents in “Projects” with OTCS Scanner (#50130)

• Fixed individual version creator not being scanned in OTCS scanner (#50273)

• Fixed missing supported versions for Oracle and DFC in the Installation Guide (#50275)

• Fixed DQL Validation for $repeatingvalue placeholder in D2 Importer (#50278)

Known issues

• D2 Importer does not validate values for Editable ComboBox if they are not in the dictionary (#49115)

• D2 Importer does not validate Enabled and Visibility properties if they have no condition attached to them (#50327)

• Running IA Importer with values “16.x” for the InfoArchiveVersion parameter throws error (#50388)

migration-center 3.5

Features and enhancements

• Alfresco scanner now supports Alfresco 5.2 (#49977)

• Database scanner now supports multi-content Blob/Clob (#49260)

• Added support for scanning and importing xCP comments for folders (#49245)

• Added support for Documentum Content Server 16.4 (#49243)

• Added support for InfoArchive 16.3 (#49244)

• OTCS importer now supports folders of type email_folder types in OpenText Content Server (#49257)

• OTCS scanner now supports scanning documents and emails from Email folders (#49995)

• OTCS scanner now supports OTDS authentication (#50134)

• Added checksum verification feature for OpenText Content Server Importer (#49250)

• Added support for Oracle 12c Release 2 (#49259)

Fixes

• Fixed bug in the Alfresco importer rollback scripts (#49251)

• Fixed delta scan issue when only main object metadata changed (#50052)

• Fixed issue with description length in OTCS importer (#50118)

• Fixed error when setting subterm under non available term in SharePoint Online taxonomies (#49978)

• Fixed job getting stuck when connection to SharePoint server is lost during import (#50026)

• Fixed error when importing filename with apostrophe or plus sign in SharePoint (#49087, #49151)

• Fixed error when importing SharePoint lists with certain settings (#49975)

• Fixed rollback not being performed when a importing certain versions fails in SharePoint (#49974)

• Fixed bug where document gets overwritten when old version moved to folder with a different document of the same name in SharePoint (#4661)

migration-center 3.4

Features and enhancements

• Added comprehensive content hashing with different hashing algorithms and encodings for the following Scanners Documentum, SharePoint, Database and Filesystem (#11636)

• Filesystem Importer: XML Metadata file now contains elements for all null and blank attributes (#11606)

• InfoArchive Importer: migrating Documentum AuditTrails is now supported (#11610)

• InfoArchive Importer: migrating Documentum Virtual Documents with children relations is now supported (#11683)

• OpenText Importer: migrating opentext_email objects is now supported (#11670)

• SharePoint Online Importer: added content integrity checking feature for imported Documents (#8296)

• SharePoint Scanner: scanning entire version trees as a single migration-center object is now supported (#11641)

• New system attributes are now available in transformation rules for all adapters (#11941)

Fixes

• Fixed objects not being scanned when reading permissions failed in Filesystem Scanner (#11779)

• Fixed table key lookup query being case sensitive in OpenText Importer (#11772)

• Fixed length limitation for Table Key Lookup attributes in OpenText Importer (#11777)

• Fixed setting attribute values from a different object to a category that has multiple rows when using multiple threads in OpenText Importer (#11797)

• Improved logging for OpenText Importer (#11781)

• Fixed issue where the initializer thread was still running in the background when a job was being stopped manually (#11739)

• Fixed not being able to delete certain Scheduler runs that took more than 2 seconds to delete (#11889)

migration-center 3.3

Features and enhancements

• Sharepoint Scanner:

  • Added support for SharePoint 2016 (#10999)

  • Added support for CAML queries (#11629)

  • Added support for scanning SharePoint internal attributes (#11653)

• Added support for scanning only current version in eRoom scanner (#11649)

• Filesystem Scanner:

  • mc_content_location and original_location are now available in transformation rules when using moveFilesToFolder (#11474)

  • Added parameter for specifying the date format for extracting extended metadata with unusual format (#11673)

  • Added possibility of scanning permissions (#11720)

  • Upgraded to latest version of Tika Libraries (#11693)

• Added support for InfoArchive 4.1 and 4.2 (#10325)

• Added support for migrating SharePoint folders and List Items into InfoArchive (#11639)

• OpenText importer:

  • now support inheriting folder categories when importing folders (#11674)

  • now support inheriting permissions (#11631)

  • now supports setting null values for popup / dropdown attributes (#11550)

Fixes

• Fixed applyD2RulesByOwner error message when using multiple threads in D2 (#11597)

• Fixed some renditions being scanned twice in Documentum scanner (#11740)

• Fixed wrong file path in log for Filesystem importer (#11469)

• Fixed date values not being properly converted to XML format in some cases for InfoArchive importer (#11672)

• Fixed contentless documents failing when ‘nocontent’ is specified in InfoArchive importer (#11656)

• Fixed missing parent_object_id when scanning delta versions in OTCS Scanner (#11750)

• Fixed importing documents that have date table key lookup attribute failing in OTCS Importer (#11576)

• Fixed error when scanning uncommon managed metadata in SharePoint scanner (#11621)

• Fixed only latest content exported for each version of a document in SharePoint scanner (#11657)

• Fixed exportLocation parameter description when using local path in SharePoint scanner (#11568)

• Fixed error when scanning documents with non-mandatory but empty taxonomy field in SharePoint scanner (#11652)

• Fixed lookup attributes not being scanned at all in SharePoint scanner (#11655)

• Improved OTCS scanner documentation (#11667)

• Corrected version labels in Installation Guide (#11622)

• Fixed Linux Jobserver classpath values (#11690)

migration-center 3.2.9

Features and enhancements

• New Documentum In-Place Adapter (#11490)

• Alfresco Importer now supports Alfresco 5.2 (#10772)

• Documentum Importer - added support for CS 7.3 (#9927)

• D2 Importer

  • Added support for D2 version 4.7 (#10777)

  • Changed D2 DQL and Taxonomy validation to be done by the D2 API (#10317)

  • Added information regarding folder migrating options in the D2 Importer User Guide (#10754)

• InfoArchive Importer

  • Added support for multiple content files per AIU (#8877)

  • Added support for multiple Object Types (#8877)

  • Added support for Custom Attributes inside the eas_sip.xml file (#9405)

  • Added support for calculating the PDI file checksum with SHA-256 and base64 encoding (#11418)

• OTCS Scanner is now able to export rendition types (#11419)

• OTCS Importer now supports Extended Attributes Model (#11424)

• SharePoint Importer now does extra check to avoid overwriting existing content with the same List Item ID when trying to move content to different libraries (#11465)

• Added warning regarding using multiple Jobservers with Sharepoint Importer (#11459)

Fixes

• OpenText Importer: fixed java heap space error when importing large size renditions. (#11426)

• OpenText Importer: fixed the authentication cookie refreshment for impersonated user (#11396)

• OpenText Scanner: fixed out of memory error when scanning objects with size larger than 20MB (#11393)

• OpenText Scanner: fixed out of memory error when scanning objects with size larger than 8GB (#11434)

• Sharepoint Importer: fixed updates to intermediate version being applied to the latest version (#11458)

• Sharepoint Importer: fixed a case that caused the importer to not finish (#10338)

• D2 Importer: Fixed validation for certain DQLs containing placeholders (#10318)

• D2 Importer: Fixed validation of certain taxonomies (#11549)

• Fixed a jar conflict between OpenText Importer and Sharepoint Scanner (#11487)

Known issues

• Multi-threaded import using applyD2RulesByOwner fails for some objects in D2 Importer

• Remaining issues from the main release 3.2 to 3.2.8 Update 2 also apply to release 3.2.8 Update 3 unless noted otherwise.

migration-center 3.2.8 Update 3

Features and enhancements

• Add support for migrating to DCM 6.7 (Documentum Compliance Manager).

Known issues

• Remaining issues from the main release 3.2 to 3.2.8 Update 2 also apply to release 3.2.8 Update 3 unless noted otherwise.

migration-center 3.2.8 Update 2

Features and enhancements

• Added support for xCP comments in Documentum Scanner and Documentum Importer (#10886)

• Added support for “dm_note” objects in Documentum Scanner and Documentum Importer (#10887)

• Added support for multi-page content in Documentum Scanner, Documentum Importer and D2 Importer (#11271)

• Added support for extracting content from BLOB / CLOB column types in the Database Scanner (#10899)

Fixes

• Fixed logging the version of the OpenText Importer in the run log (#11322)

• Fixed setting the version description attribute in OpenText Importer (#11270)

Known issues

• Documentum scanner/importer: The scanned/imported “dm_note” objects are not counted in the job run report (#11391)

• DQLs that have enable(row_based) are not processed correctly in the D2 Importer (#11390)

• Remaining issues from the main release 3.2 to 3.2.8 Update 1 also apply to release 3.2.8 Update 2 unless noted otherwise

migration-center 3.2.8 Update 1

Features and enhancements

• New OpenText scanner: supports scanning documents, compound documents and folders from OpenText repositories version 9.7.1, 10.0 and 10.5. Specific OpenText features are supported like scanning categories, classification, permissions and shortcuts.

Fixes

• Several bug fixes regarding validating DQL queries and Taxonomies when using property pages in D2 Importer.

migration-center 3.2.8

Features and enhancements

• Added support for D2 LSS (Life Sciences Solution) version 4.1 (#9990)

• Added multi-threading capabilities to the D2 importer (#10107)

• Added support for Alfresco version 5.1 (#10354)

• Added support for OpenText Content Server version 16.0 (#9937)

• Added support for SharePoint 2016 (#9925)

• Improved SharePoint Online Importer performance when applying internal attributes and taxonomies (#10314)

• Added support for InfoArchive 4.0 (#9926)

• Added support for Documentum ECS (Elastic Cloud Storage) (#9783)

Fixes

• Alfresco Scanner: fixed scanning duplicates on delta scanning a new version for documents created directly in the Alfresco Share interface (#10013)

• InfoArchvie Importer: fixed nullPointer exception when importing objects without content (#10746)

• Filesystem Importer: fixed logging message when setting owner fails (#10326)

• SharePoint Importer: fixed setting author and editor attributes in a multi-domain environment (#10171)

• SharePoint Scanner: fixed job finishing successfully with incorrect credentials (#9939)

• MC Client: fixed description for RepeatingToSingle transformation function (#10291)

Known Issues

• D2 Importer:

  • importing version updates with CURRENT not set to latest version fails (#10784)

  • the CURRENT label is always set to the latest version when applying Lifecycle (#10686)

  • importing branched versions with multiple and no r_version_label associated fails (#10460)

  • D2 importer does not work with D2 4.5 or 4.1 when Jobserver runs on Java version 1.8 (#10384)

migration-center 3.2.7 Update 4

Features and enhancements

• Improved Sharepoint and Sharepoint Online Importers performance when setting Taxonomies and internal attributes. (#10423)

• Improved Sharepoint Importer Error Reporting in certain cases. (#10299)

Known Issues

• Remaining issues from the main release 3.2 to 3.2.7 Update 3 also apply to release 3.2.7 Update 4 unless noted otherwise

migration-center 3.2.7 Update 3

Features and enhancements

• Documentum Importer can attach now documents to a given lifecycle.

Fixes

• FirstDoc importer: Fix a java.lang.ClassCastException error when importing to FDQM module

• FirstDoc importer: Fix importing versions when there is an attribute count difference in the repeating group between create SDL and document definition SDL.

Known Issues

• Remaining issues from the main release 3.2 to 3.2.7 Update 2 also apply to release 3.2.7 Update 3 unless noted otherwise.

migration-center 3.2.7 Update 2

Features and enhancements

• D2 Importer now supports only D2 version 4.6. The older D2 versions are only supported by the previous versions of migration-center

• OpenText Importer now supports creating OpenText Compound Documents

• OpenText Importer now supports importing renditions

• IBM Domino Scanner:

  • Large attribute values can now be split into chunks of maximum 4000 bytes

  • Added custom attributes: "attachmentItemName" - name of item that an attachments was attached to in the original Domino document, "attachmentName" - name of the attachment in the original document and "$dominoNoteID$" - NoteID of the document in the database that it originates from.

Fixes

• Documentum Scanner: Scanning version trees having versions of multiple object types

• OpenText Importer: Error messages concerting a single attribute do not have the attribute name

• OpenText Importer: Categories not being set if no associations are made for it

• Sharepoint Scanner: Documents with paths longer than 260 characters failed to be scanned

Known Issues

• Running a SP scanner with incorrect credentials on a Sharepoint with anonymous authentication enabled, does not show errors.

• Remaining issues from the main release 3.2 to 3.2.7 Update 1 also apply to release 3.2.7 Update 2 unless noted otherwise.