LogoLogo
3.14 Update 1
3.14 Update 1
  • Overview
  • Legal Notice
  • Release Notes
    • Previous versions
  • System Requirements
  • Installation Guide
  • Client User Guide
  • Database Administrator’s Guide
  • Sizing Guide
  • Auto Classification Module
  • Documentum security enhancements
  • Glossary
  • Abbreviations
  • Scanners
    • Alfresco Scanner
    • CSV & Excel Scanner
    • Database Scanner
    • Documentum Scanner
    • eRoom Scanner
    • Exchange Scanner
    • Exchange Removal
    • Filesystem scanner
    • Domino Scanner
    • OpenText Scanner
    • Outlook Scanner
    • SharePoint Scanner
    • SharePoint Online Scanner
  • Importers
    • Alfresco Importer
    • Box Importer
    • D2 Importer
    • DCM Importer
    • Documentum Importer
    • Documentum InPlace Adapter
    • Filesystem Importer
    • InfoArchive Importer
    • OpenText Importer
    • OpenText InPlace Adapter
    • SharePoint Importer
    • SharePoint Online Importer
    • SharePoint Online Batch Importer
    • Veeva Importer
Powered by GitBook
On this page
  • migration-center 3.14 Update 1
  • Features & Enhancements
  • Fixes
  • Known Issues & Limitations

Was this helpful?

Export as PDF

Release Notes

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)

Last updated 4 years ago

Was this helpful?