You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It could be critical to the process to ensure that all gerelateerde zaken are added to a zaak, so throwing an error when adding gerelateerde zaken fails, will ensure data consistency by rolling back the whole action (not implemented yet). For other processes gerelateerde zaken could be not so important and it would be preferable to only give a warning when adding gerelateerde zaken fails, so that the process can move on without interruption.
There are also a variety of technical reason why adding a gerelateerde zaak could fail. For example: Adding a closed zaak as gerelateerde zaak without zaken.geforceerd_bijwerken permission scope, or adding a zaak as gerelateerde zaak that is not present in OpenZaak.
Add property to translation profile (example: "relatedCaseFailureBehavior": "warn/error")
Add testcases for both warn and error situations.
Default behavior should be error
The text was updated successfully, but these errors were encountered:
Should also include deletion of gerelateerdeZaken.
Not sure of making warnings/errors configurable is the right way to handle this issue. I'm also leaning towards using errorstores for these mutations. That would not roll back creeerZaak and not break updateZaak. It would be eventually consistent.
The reason for an errorstore would be the retry-ability and clear visibility in the Frank!Console. Almost all the causes for the mutations to fail are technical in nature. A major cause for mutations to fail is the gerelateerde zaak not being present on the ZGW side (yet). This requires the gerelateerde zaak to be added by an external system. After that the mutation should succeed with a retry.
It could be critical to the process to ensure that all gerelateerde zaken are added to a zaak, so throwing an error when adding gerelateerde zaken fails, will ensure data consistency by rolling back the whole action (not implemented yet). For other processes gerelateerde zaken could be not so important and it would be preferable to only give a warning when adding gerelateerde zaken fails, so that the process can move on without interruption.
There are also a variety of technical reason why adding a gerelateerde zaak could fail. For example: Adding a closed zaak as gerelateerde zaak without
zaken.geforceerd_bijwerken
permission scope, or adding a zaak as gerelateerde zaak that is not present in OpenZaak.error
The text was updated successfully, but these errors were encountered: