Migration to 7.17.0+

If you run any Nexeed IAS installation on Tenant ID 7311ea8c-5d48-43fe-acf9-980eedf24b6c or any other non-unique Tenant Id do not skip the installation of version 7.17.0 contained in IAS 2025.01.00.

The Tenant ID is conceptually the unique identifier for all data contained in Nexeed IAS in relation to other installations. This will lead to problems if dataflows meet on shared infrastructure (like e.g. RabbitMQ or Solace) or existing systems are to be merged on a shared installation with multiple tenants.

Therefore, the Tenant ID has to be unique - for systems that have been erroneously installed with either Tenant ID 7311ea8c-5d48-43fe-acf9-980eedf24b6c or any other ID shared by another production system, BCI provides limited migration support with documentation and database scripts.

The Migration instructions and scripts available from BCI are specific to that version and cannot be executed on prior or later versions.

Breaking Changes

Device becomes a standard ticket field, not just a domain context attributed restricted to Condition Monitoring domain anymore.
There are breaking API changes in the /BCI_TS/v1/{tenant-id}/tickets/list: and /BCI_TS/v1/{tenant-id}/archived-tickets/list.
- The ticket filtering is now adapted to allow multiple values for each domain attribute. However, due to performance reasons we removed wildcard support for the new values attribute. Please migrate to the new API version /BCI_TS/v2/{tenant-id}/tickets/list and /BCI_TS/v2/{tenant-id}/archived-tickets/list.
- Devices and facility filtering can be specified as filtering criterion for all domains, not restricted to Condition Monitoring domain anymore.
- Sorting by device are now available for all domains.
The manual ticket creation API POST /BCI_TS/v1/{tenant-id}/tickets gets deprecated. A new endpoint POST /BCI_TS/v2/{tenant-id}/tickets is introduced, offering the option to reference a device in a tickets.
The ticket detail APIs GET /BCI_TS/v1/{tenant-id}/tickets/{ticket-id} and GET /BCI_TS/v1/{tenant-id}/archived-tickets/{ticket-id} get deprecated. New endpoint GET /BCI_TS/v2/{tenant-id}/tickets/{ticket-id} and GET /BCI_TS/v2/{tenant-id}/archived-tickets/{ticket-id} are introduced, returning deviceId as standard ticket field.
The ticket change APIs PATCH /BCI_TS/v1/{tenant-id}/tickets/{ticket-id}/actions and PATCH /BCI_TS/v1/{tenant-id}/tickets/{ticket-id} get deprecated. New endpoint PATCH /BCI_TS/v2/{tenant-id}/tickets/{ticket-id}/actions and PATCH /BCI_TS/v1/{tenant-id}/tickets/{ticket-id} are introduced, returning deviceId as standard ticket field.
The Open Telemetry configuration gets injected by Utility-Toolkit into otel-observability-configmap

Changes

New environment variables to configure the maximum number of context attribute values per domain when filtering tickets:
- NEXEED_TM_MAX_NUMBER_OF_CONTEXT_ATTRIBUTE_VALUES_PER_DOMAIN
Fine-grained access control is not restricted to condition monitoring tickets anymore, it now also applies to other domains' tickets with devices.
The client-id for CM's domain is set to the correct value if provided with the environment variable CM_CLIENT_ID to prepare transfer of domain registration to CM.
On ticket creation a user can be assigned to a ticket. For this reason the payload of the ticket creation API (/BCI_TS/v2/{tenant-id}/tickets) has extended. The optional assigneeId field of type string has been added and can contain the user’s id.
It is also possible to assign a user to a ticket which is in state OPEN, now.