Migration from previous versions

V1.0 to V1.1

Automated migration from V1.0.0 done by the service. Existing Quick Reactions will not work anymore and have to be recreated after this update since the internal Ticket Management reactor was removed and existing Quick Reactions are not compatible with the new external Ticket Management.

IAS 2023.02 to 2024.01

Nothing to do here.

IAS 2024.02 to 2024.02.01 (Deviation Processor 1.7 to 1.8)

Breaking changes

The Deviation Notification endpoint requires Authorization. Resource "urn:bosch:nexeed:smc:public:deviationnotification" with the privilege "add" is required and will be granted e.g. via the role "Deviation Processor Detector".

IAS 2025.01.00 (Deviation Processor 1.10)

Migration of non-unique Tenant ID

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 1.10.0-rev1 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.

IAS 2025.01.00 to 2025.02.01 (Deviation Processor 1.10 to 1.13)

Database migration

Added two new columns(facilityName, facilityDeletedAt) in Deviation table to track removed facility.