We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
latest / a755cd5
No response
If I export a form that has ZGW registration backend and uses the Zaaktype select instead of the legacy URL field:
And I export it, the export has zaaktype="" in the registration options:
zaaktype=""
"registration_backends": [{"key": "backend1", "name": "zgw", "backend": "zgw-create-zaak", "options": {"zaaktype": "", "catalogue": {"rsin": "000000000", "domain": "TEST"}, "objecttype": "http://localhost:8001/api/v2/bla", "zgw_api_group": 1, "objects_api_group": 1, "property_mappings": [], "informatieobjecttype": "http://localhost:8003/catalogi/api/v1/informatieobjecttypen/531f6c1a-97f7-478c-85f0-67d2f23661c7", "case_type_identification": "ZT-001"}}]
If I try to import this form, the import fails because of this empty zaaktype:
The zaaktype field should be properly exported, also if the legacy field is empty
None
The text was updated successfully, but these errors were encountered:
Can no longer reproduce, so this confirms that #4903 fixed it
Sorry, something went wrong.
sergei-maertens
Successfully merging a pull request may close this issue.
Product versie / Product version
latest / a755cd5
Customer reference
No response
Omschrijf het probleem / Describe the bug
If I export a form that has ZGW registration backend and uses the Zaaktype select instead of the legacy URL field:
And I export it, the export has
zaaktype=""
in the registration options:If I try to import this form, the import fails because of this empty zaaktype:
Stappen om te reproduceren / Steps to reproduce
Verwacht gedrag / Expected behavior
The zaaktype field should be properly exported, also if the legacy field is empty
Screen resolution
None
Device
None
OS
None
Browser
No response
The text was updated successfully, but these errors were encountered: