KB Article ID: 12531
Product: | Replicator,SharePoint Migrator |
Product Version: | 6.4.0.0,6.4.0.1,6.4.0.2,6.4.0.3,6.5.0.0,6.5.0.1 |
SharePoint Version: | All |
Details:
DocAve can maintain the state of a running workflow after migrating or replicating it between the source and destination. However, DocAve must write directly to the Content Database in order to do so. Please be aware that Microsoft does not support database writing methods, and using such methods may void your Microsoft Terms of Service. If you choose to use either of the methods below, you do so at your own risk, and AvePoint is not liable for any violation of your Microsoft Terms of Service.
Maintaining the State of Running Workflows with DocAve SharePoint Migrator
If you have a running SharePoint 2010 workflow instance in your SharePoint Server 2010 environment, you can maintain the state of that workflow in the destination SharePoint Server 2013 environment after migrating it using DocAve SharePoint Migrator. To do this, follow the steps below prior to performing your migration. Please be aware that Microsoft does not support database writing methods, and using such methods may void your Microsoft Terms of Service.
*Note: When a SharePoint 2010 workflow is migrated to a SharePoint Server 2013 environment, it will remain a SharePoint 2010 workflow in the destination.
- Log into DocAve.
- Launch the DocAve SharePoint Migrator module.
- Click Profile Settings on the ribbon.
- In the Profile Settings tab, click Download Profile on the ribbon to download the Default Profile to your desktop or another easily accessible location.
- Open the Default Profile.xml file with Notepad.
- Navigate to the keepRunningWorkflowInstance = " " node, set the value to True, and save your changes.
- Rename the Default Profile.xml to RunningWorkflowProfile.xml or another easily identifiable profile name.
- In DocAve, navigate to SharePoint Migrator > Profile Settings and click Upload Profile in the Upload/Download group on the ribbon.
- Select the renamed Default Profile.xml that you edited in the previous step. The file will be uploaded, and your Online Profile will automatically be changed to the profile you created.
- In the Source Component Options section under Workflow, select Include Workflow instance, Include running workflows, and Cancel and restart the running workflows after migration jobs.
- Run the migration job. For more information about running migration jobs, see the SharePoint Migrator User Guide.
Maintaining the State of Running Workflows with DocAve Replicator
If you have a running SharePoint 2010 workflow instance in your SharePoint Server 2010 or SharePoint Server 2013 environment, you can maintain the state of that workflow in the destination after a replication. To do this, follow the steps below prior to performing your replication using DocAve Replicator. Please be aware that Microsoft does not support database writing methods, and using such methods may void your Microsoft Terms of Service.
*Note: DocAve does not support replicating the workflow instance of a checked-out file.
- Log into DocAve.
- Launch the DocAve Replicator module.
- Navigate to Profile Settings > Content > Include running workflow instances, and select Restart workflows from 0% after the replication.
- On all Replicator Agents that will run jobs or plans that you want to maintain the state of SharePoint 2010 running workflows, navigate to …AvePointDocAve6AgentdataSP2010Replicator.
- Find the SP2010Replicator.xml file, right-click it, and select Edit.
- Find the attribute ReplicateRunningWorkflowInstance and modify the value to True.
- Save and close the file, and then run your replication. For more information about running replication jobs, see the Replicator User Guide.