The can_access? check will fail if the wizard does not allow multiple submissions. This means that on the second build of the wizard on the final step of a single submission wizard, the wizard instance will have no steps, and an error will be thrown when logic assumes it does.
* Add custom field improvements
This PR does a few things to improve our support of custom fields
1. Adds custom fields added by other plugins to the list in admin/wizards/custom-fields and the custom field list in the mapper selector
2. Adds support for json custom fields in the wizard actions
* Make eslint happy
* Make prettier happy
* Make rubocop happy
* Make ember template lint happy
* Don't assume we have the context in the selector
* Ensure custom fields don't require optional attributes (with tests)
* Re structure builder logic to allow for step conditionality
Concerns
- Performance. Look at whether the additional build in the steps controller can be reduced
- Does not work if applied to the last step.
- Certain conditions will not work with the first step(?)
- How should this be scoped to known functionality?
* Add indexes and conditions to steps and fields
* Complete and add spec
* Complete backend
* Complete step conditionality and field indexing
* Fix failing spec
* Update coverage
* Apply rubocop
* Apply prettier
* Apply prettier to wizard js
* Fix schema issues created in merge
* Remove setting label for force_final
* Improve client wizard cache naming
* Improve steps controller and spec conditionality
* Improve final step attribute naming
* Fix failing spec
* Linting
* Add one more final step test
* Linting
* Fix eslint issues
* Apply prettier
* Linting, syntax, merge and copy cleanups
* Update wizard-admin.scss
* Fix template linting
* Rubocop fixes
