Essentials for Office 365 2.14

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

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

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.

Pause Until

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

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

On-premises Parameter	Comments
Action supported as-is when configured with a date/time value.	Date/time values only.

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

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

Essentials for Office 365 2.14 - User Guide

Loop

Math Operation

Pause For

Pause Until