I'm in the process of migrating my Nintex Workflows 2013 from Development environment to my QA environment.
What I have:
- I have one Main workflow with ~25 sub-workflows associated to the Main workflow
- I have 2 UDAs (1 is associated to all sub workflows, and the other to just a handful).
- All of my sub-workflows use one Request Data action where the associated Content Type has no site columns (it's empty).
- Since I'm using Nintex Forms 2013 I reference my list colums and workflow variable to capture and store data, the Content type is never referenced.
How I'm migrating
- Using a tool called Sharegate Migration tool, I migrate the following:
- Site Columns (30+)
- Content Types (1 - the empty one described above)
- Users
- Groups
- Permissions
- Lists
- Manually, I'm migrating the following since I have no other tool that works.
- UDA's (importing the .uda files - which should keep the references intact back to the sub-workflows and workflow)
- Sub-workflows
- Main workflow
The problems that are occurring
- One of the UDA's has seemed to keep it's association intact, the other has not
- To resolve this issue shown below I have to open the UDA from within the workflow and save the UDA action, then the warnings go away.
- --------------------------------------------------
Message from webpage
-----------------------------------------------------
The workflow is not valid and cannot be published. The following actions need to be configured:
NUC_UDA_Get_Display_Name - RB Eng
NUC_UDA_Get_Display_Name - RB Eng Bkup
-----------------------------------------------------
The current solution for me on the UDA: after importing the sub-workflow or main workflow I have to open the UDA action in my workflow, hit Save in the ribbon, and then save and publish the workflow.
- The Content type associated to the Request Data Action in each workflow is not being recognized, and I receive the following error:
- ---------------------------
Message from webpage
---------------------------
soap:ServerServer was unable to process request. ---> A content type with title 'NUC_Orl_WF_CT' exists but does not share any fields in common with this request data action. Use a different content type name.
---------------------------
OK
---------------------------
The current solution for me on the content type association, after importing the sub-workflow I have to open the Request Data Action, hit Save in the ribbon, and then save and publish the workflow.
Is there something that I'm doing wrong that would cause these types of issues for Migration.
It would be really great if Nintex would allow you to select all of the information needed to be migrated and build a migration package so that I don't have to do this step by step manual effort and fix these things. This just doesn't seem to work the way other software tools do when migrating from Development to QA and from QA to production.
My fear it that once I have workflows running in QA and/or Production migration of fixes will break running workflows, which I cannot afford.
Help.
One thing that I did do with UDA's on my development server is that from the UDA manager screen, I performed an Analyze on both UDA and re-published the associated workflows. The UDA that has the issue above was analyzed and performed the republish function, and then I did the same for the second UDA which doesn't seem to have the association issue, could this be a reason, could republishing workflows from the UDA screen cause issues where workflows have mutliple UDAs in them?