-
Notifications
You must be signed in to change notification settings - Fork 30
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2805 from Cumulocity-IoT/feature/MTM-61884/notiti…
…fication2.0_operation_api_update MTM-61884: Change log for tenant context operation api
- Loading branch information
Showing
2 changed files
with
38 additions
and
0 deletions.
There are no files selected for viewing
18 changes: 18 additions & 0 deletions
18
...lytics/cumulocity-undefined-notifications-tenant-context-operations-wildcard.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
--- | ||
date: | ||
title: Changes to Notifications 2.0 tenant context subscriptions with no API filter | ||
change_type: | ||
- value: change-3BQrQ6adS | ||
label: API change | ||
product_area: Platform services | ||
component: | ||
- value: component-JlFdtOPva | ||
label: REST API | ||
build_artifact: | ||
- value: tc-QHwMfWtBk7 | ||
label: cumulocity | ||
ticket: MTM-60734 | ||
version: 2025.30.0 | ||
--- | ||
|
||
As previously [announced](https://cumulocity.com/docs/change-logs/?change-type=.change-type-api-change#cumulocity-undefined-notifications-tenant-context-operations-wildcard-announcement), applications utilizing the wildcard API selector in Notifications 2.0 tenant context subscriptions will now start receiving operations updates in addition to the updates they were already receiving. This change applies to both existing and new tenant context subscriptions. |
20 changes: 20 additions & 0 deletions
20
...services/cumulocity-undefined-notifications-tenant-context-event-type-filter.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
--- | ||
date: | ||
title: Changes to Notifications 2.0 tenant context subscriptions with event API filter | ||
change_type: | ||
- value: change-QHu1GdukP | ||
label: Feature | ||
product_area: Platform services | ||
component: | ||
- value: component-JlFdtOPva | ||
label: REST API | ||
build_artifact: | ||
- value: tc-QHwMfWtBk7 | ||
label: cumulocity | ||
ticket: MTM-60734 | ||
version: 2025.30.0 | ||
--- | ||
|
||
Notifications 2.0 subscriptions may specify the {{< product-c8y-iot >}} APIs to subscribe to, for example `events` or `measurements`. | ||
If the `events` API was specifically included as the only API in a tenant context subscription filter, a type filter was also required to be set in that filter to make the subscription work. | ||
The restriction requiring a type filter when subscribing to the `events` API in the tenant context has been removed. Tenant context subscriptions to the `events` API can now be created without specifying a type filter. |