Although most of our Nintex Forms are used solely in the office, we have always defaulted to Responsive Form designer, as it is a more streamlined workflow: limited styling/sizing options, auto-alignment, etc..
As our client’s needs have evolved, we find there are several forms we would like to migrate to the classic designer in order to pick up some form controls that are beneficial (List View, etc.)
I understand there is no conversion tool, but am hoping someone could give us some best practices from a practical experience. The current responsive form is fairly robust (many different columns, controls, rules, etc.), and is actively used.
Some early thoughts we have:
Scenario #1: “The long weekend”
- Export the form to local storage
- Delete the form and rebuild using Classic Designer
- If we run into issues that prevent completion over the weekend, revert to Responsive and import locally stored copy
Scenario #2: “Parallel list”
- Create a list template of current list
- Create clone list from template
- Develop form on cloned list using Classic Designer
- Go to original list
- Export Responsive form to local storage
- Delete existing form and start a form using Classic Designer
- Import form from cloned list
- If we run into issues, revert to Responsive and import locally stored copy
Anyone out there develop a “best practice” for this type of effort? Any script to allow us to convert to Classic by editing the exported XML of the Responsive form?
Thanks!