State of submission form when toggling fields with type-binding

[jlipka]

Describe the bug

In DSpace v8, the state of the submission form is inconsistent when using type-binds (related to the "dc.type" field) in multiple steps. As I understand the problem, it only affects the Dspace-Angular part - the backend state seems to be correct.

To reproduce

Steps to reproduce the behavior:

1. Create a multi-step submission form.
2. Create a type bind on at least two steps with the same type bind value.
3. From the dc.type form field, select the value you defined to bind to.
4. Both related form fields should appear / become visible
5. Enter any values in both related form fields and save the form - everything should be saved correctly
6. Change the "dc.type" option to any value other than the previously defined binding value - the related form fields should disappear now again
7. Save the form.
8. Change the "dc.type" option again to the value (as in step 3) - the related form fields appear again
9. Check the values of the two related form fields that were previously filled. One input will be cleared (empty), the other will still be filled with the previously entered value.

If you change the case and add two type bindings in the first step, you can see that only the form fields of one step (always the first?) are cleared. The fields with type bindings in all other steps remain unaffected and still contain the previously entered value.

Expected behavior

As I understand the submission form, the two fields - which are related to the dc.type value - should be completely cleared in both steps after changing and saving the dc.type input form field. When you reload the submission form after step 7, the related fields are empty in both steps as expected.