When approving an agenda, we now always regenerate the decisions of agendaitems that have new document names AND tell the backend to regenerate the "betreft" part so we ensure that the (potentially) new piece names are used.
Note that this does not include BIS documents. For those, the users still need to manually update the decision.
There frontend functionality to generate the betreft part isn't removed, it's now duplicated across the FE and the microservice. In a future we might want to always use the service.
https://kanselarij.atlassian.net/browse/KAS-4713
When approving an agenda, we now always regenerate the decisions of agendaitems that have new document names AND tell the backend to regenerate the "betreft" part so we ensure that the (potentially) new piece names are used.
Note that this does not include BIS documents. For those, the users still need to manually update the decision.
There frontend functionality to generate the betreft part isn't removed, it's now duplicated across the FE and the microservice. In a future we might want to always use the service.
Related PRs: