-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
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
Notification abonnement on catalogus #156
Comments
Refinement: So, Zaken will be filtered in the subscription on the catalog. This is an experimental feature! Estimate: 5 days |
@JanBrek ping |
Asked Peter Arkesteijn if he has a budget for this |
@joeribekker I can hereby approve this ticket. |
Refinement: There's 2 options to implement this:
We go for option 1 (far less spaghetti) and will retrieve the catalog over the network for external zaaktypes. Please mark this everywhere as EXPERIMENTAL. |
…enmerken and support kenmerken for django-loose-fk fields
…enmerken and support kenmerken for django-loose-fk fields
…et_kenmerken and add hook for `_get_field` to support nested attributes in Open Zaak
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
…et_kenmerken and add hook for `_get_field` to support nested attributes in Open Zaak
…et_kenmerken and add hook for `_get_field` to support nested attributes in Open Zaak
…et_kenmerken and add hook for `_get_field` to support nested attributes in Open Zaak
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
because this kenmerk is not part of the standard, it is marked as experimental
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
because this kenmerk is not part of the standard, it is marked as experimental
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
Why is this issue marked as blocked? 🫣 |
@PeterVanBragt I forgot to mention it here (open-zaak/open-zaak#1757 (comment)), this change relies on a library which we need to upgrade, but there is another pull request in progress which must be finished first to make use of that upgrade that library in Open Zaak open-zaak/open-zaak#1753 |
Refinement: Sonny will continue with the library this week. |
…et_kenmerken and add hook for `_get_field` to support nested attributes in Open Zaak
Coming forth from a comment in ticket open-zaak/open-zaak#1661
Allow notification API to be set per catalogus. So set your abbonement to a catalogus instead of using zaaktype as filtering.
One possible solution would be that the zaak kanaal also will include catalogi name/number/whatever in the notification so that it can be used as a filter.
The text was updated successfully, but these errors were encountered: