Migration
Since a Nintex workflow can become quite complex with lots of information coming from multiple locations it would be great to be able to define all the pieces and parts that are needed for that workflow to run (a report of some sort). Further, once a designer/developer has created a workflow with all it's part and has unit tested the hell out of it, allow them to perform a save that pulls together all of the components into one Migration package / file / folder etc... so that when moving a workflow to a QA server it doesn't take manual fixes to the workflow to re-associate the Content types, or to re-associate InfoPath forms to the actions. Currently, for me to migrate from one environment to the next takes ~ two weeks to practically re-build the associations. In part because my workflow is big and complex and also because I have no way to get a report out or document out from designer all the stuff I've built.
Sunnie
shared this idea
Thanks for the feedback Sunnie.
We’re reviewing this feature request
1 comment
-
Jan Groenendijk
commented
Yes! We currently estimate 4 - 16 hours for migrating from one environment to another as this can be quite painful. I would be nice to have hardcoded links (as part of testing) presented in a report that would help identify issues early. Using a 3rd party product to help with the migration of the list definitions is very expensive.