[#2640] Use separate field for storing long case result descriptions #1324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The E-suite occasionally returns case results with descriptions that are longer than allowed by the ZGW spec (20 characters). Updating the E-suite for a single attribute is not an option. The workaround is to store longer descriptions in a dedicated attribute "naam" on
ResultaatType
and use it if it's non-empy, otherwise fall back on default description ("omschrijving").Taiga: https://taiga.maykinmedia.nl/project/open-inwoner/task/2640