Transform finance operations with AI-driven automation at the Financial Leadership Summit
(Sun, May 18, 10:00 PM)
NUP Self-Service Program
With options for self-service migration, dedicated professional services and certified partner migration offerings, you can vastly accelerate time to value, reduce project costs, and protect your workflow-related intellectual capital.
Below are frequently asked questions related to Nintex Workflow, Nintex for SharePoint and Upgrade. Click each title to expand and view.
What will happen to deactivated legacy workflows with tasks that are in flight?
Tasks that are in flight prior to the workflow deactivation will continue to be in flight until the task completes or fails.
What happens when a new list item is being created shortly after the legacy workflow has been deactivated?
New tasks will now be created in Nintex Automation Cloud if the workflow is already published to production in Nintex Automation Cloud.
What happens if a component workflow that is required by an inflight task is being deactivated in the legacy environment?
As the inflight task is required to start the component workflow which has been deactivated, the task will fail to complete as the component workflow is deemed unavailable.
Should component workflows be deactivated at the same time from the legacy environment? Component workflows should only be deactivated IF there are no more tasks in flight that requires the use of the component workflows. IF there are still tasks running that calls the component workflows, the component workflows should be left activated in SharePoint Online/SharePoint On-Prem.
When can component workflows be deactivated from the legacy environment?
Component workflows can be deactivated in the following scenarios:
- There are no more inflight tasks that require to start the component workflow(s).
- Tasks that are still inflight have already completed the execution of the component workflow(s).
Who can I contact for help?
Contact the Modernization Team.
Should component workflows be deactivated at the same time from the legacy environment? Component workflows should only be deactivated IF there are no more tasks in flight that requires the use of the component workflows. IF there are still tasks running that calls the component workflows, the component workflows should be left activated in SharePoint Online/SharePoint On-Prem.
When can component workflows be deactivated from the legacy environment?
Component workflows can be deactivated in the following scenarios:
- There are no more inflight tasks that require to start the component workflow(s).
- Tasks that are still inflight have already completed the execution of the component workflow(s).
Who can I contact for help?
Contact the Modernization Team.
About the NUP Program
Find step-by-step instructions to help you seamlessly transition to Nintex Workflow and optimize your workflows.
The Nintex Modernization team has launched an exciting new four-part webinar series, aiming to support and guide our customers through the process of Migrating to Nintex Workflow (formally known as Nintex Automation Cloud).
Whether you are managing the migration independently, leveraging a partner, or utilizing our Upgrade Center for support, these webinars will provide valuable insights on where to begin and how to navigate each phase of the process.
