Chat now with support
Chat with Support

Metalogix Essentials for Office 365 2.3 - User Guide

Metalogix Essentials for Office 365 User Guide
Administrator Architect Backup
Interface Overview Common Functions
Connecting to SharePoint and OneDrive for Business Connecting to Cloud Storage Global and SharePoint Administrators Hyper Backup Creating a Full Backup Creating an Update Backup Creating an Exchange Online Mailbox Backup Creating an Office 365 Group Backup Creating a OneDrive for Business Backup Backup Resume Backup Search Restore from Backup Scheduling Backup Jobs Retention Policies Import/Export Backup Archives Moving the Backup Location Backup Project Conversion
Drives
Interface Overview Common Functions
Connecting to Drives Copy Google Drive Copy File Share Copy My Sites to OneDrive for Business Copy Tenant Copy Box Copy Dropbox OneDrive Management Progress Tab Hyper Migration Path Length Overflow
File Manager Informant Migrator
Interface Common Functions
Connect to SharePoint and OneDrive for Business Global and SharePoint Administrators Copy Sites Live Compare Copy Lists and Libraries Copy, Move, and Tag SharePoint Content Copy Alerts Pre-Migration Report Azure Turbo Mode In-Place Tagging of SharePoint Items Incremental Copy Nintex Workflow Migration Orphaned Users Copy Preserving Content Authorship and Approve/Reject Statuses Save Site to XML Using Scripts and Integration With Windows Task Scheduler
Profile and Global Variables Public Folders for SharePoint Reporting and Re-Mapping Users and Templates Security Manager Term Store Manager Scripts Wizards Appendix

Log In History List

During migration to SharePoint Online, the on-premises Nintex Workflow action "Log in History List" will be transformed into the Nintex Online Workflow action "Log to History List".

The following differences related to parameters and configuration should be noted:

On-premises Parameter

Comments

Message was not required.

·Message is now required so if the source was empty, a default value will be added.

·Message does not support rich text.

For additional possible differences, please refer to the General Workflow Objects section.

Loop

During migration to SharePoint Online, the on-premises Nintex Workflow action "Loop" will be transformed into the Nintex Online Workflow action "Loop with Condition".

The following differences related to parameters and configuration should be noted:

On-premises Parameter

Comments

Condition

The following condition variants do not have an equivalent:

·Modified in a specific date span

·Person is a valid SharePoint user

·Created in a specific date span

·The file size in a specific range kilobytes

For additional possible differences, please refer to the General Workflow Objects section.

Math Operation

During migration to SharePoint Online, the on-premises Nintex Workflow action "Math Operation" will be transformed into the Nintex Online Workflow action "Do Calculation".

The following differences related to parameters and configuration should be noted:

On-premises Parameter

Comments

Lookups "User Proflie" and "Workflow Constants" are not available in the Nintex Online "Do Calculation" action.

If either of these lookups are being used, then the workflow will need to be rebuilt post migration.

For additional possible differences, please refer to the General Workflow Objects section.

Pause For

During migration to SharePoint Online, the on-premises Nintex Workflow action "Pause For..." will be transformed into the Nintex Online Workflow action "Pause for Duration".

The following differences related to parameters and configuration should be noted:

On-premises Parameter

Comments

Years

·"Years" has no equivalent and will therefore be converted into days. The conversion assumes 1 year equals 365 days.  For example, if the action contains 2 Years, the conversion will add 730 days to the migrated Days parameter.  This logic requires that both Years and Days are numeric values and not an inserted reference.

·Please note that if you have configured a numeric value in Years and a non-numeric value in Days, then these values cannot be combined.  This is an unsupported configuration and should be manually addressed post migration.

·Please note that if you have configured a non-numeric value in Years then this value will be lost as Years is not included in the Nintex Online action and it cannot be combined with Days (either numeric or non-numeric).

Months

·"Months" has no equivalent and will therefore be converted into days.  The conversion assumes 1 month equals 30 days.  For example, if the action contains 6 Months, the conversion will add 180 days to the migrated Days parameter.  This logic requires that both Months and Days are numeric values and not an inserted reference.

·Please note that if you have configured a numeric value in Months and a non-numeric value in Days, then these values cannot be combined.  This is an unsupported configuration and should be manually addressed post migration.

·Please note that if you have configured a non-numeric value in Months then this value will be lost as Months is not included in the Nintex Online action and it cannot be combined with Days (either numeric or non-numeric).

For additional possible differences, please refer to the General Workflow Objects section.

Related Documents