2025.03.00 RC2

Line Control 5.2 is not compatible with Line Control 5.3 database due to new Timer fields (using MS SQL schema)
Because of this known backward compatibility bug it is highly recommended to update to a newer Line Control Version only without running active production on Line Control using MS SQL. (Bug 558111)

Support for MS SQL will be discontinued with the release of Line Control starting 2026.

Provide part 1 of 3 to support Oracle database
This feature enables partial Oracle support for the LineControl system, transitioning from SQL Server (MSSQL) to Oracle. It includes designing a new API V2 framework with a pluggable data access layer, allowing a subset of APIs to work with Oracle as part of an incremental rollout. This ensures long-term maintainability, testability, and performance comparability with the existing MSSQL implementation. (468919)

Provide part 2 of 3 to support Oracle database (vMDT commands)
This feature ensures that all commands from the VMDT AccessModule can be executed with an Oracle database. It guarantees that all functions are executed correctly and efficiently, and that the result of each command is exactly the same as with the former MSSQL implementation, maintaining functional parity, data integrity, execution accuracy, and performance efficiency. (474262)

Provide part 3 of 3 to support Oracle database (Line Control commands)
This feature extends Oracle database support to all remaining APIs and Background Jobs, primarily Line Control API and background jobs. This includes various functionalities like ProcessEnd, ProcessRequest, Counter/Timer operations, data mapping, part routing, and database migration, along with all remaining background jobs and UI elements. (474263)

Check usage of same processNo with different processName within one RouteList
This feature introduces an error message when a user attempts to add a process to a routelist with an existing processNo but a different processName. This prevents a routelist from containing the same processNo with conflicting processName entries. (478323)

Implementation of logic to migrate Macros from MES classic LineControl into IAS Line Control
This feature enhances the API for Macros to facilitate the migration of macro files from MES Classic to IAS Line Control. It enables specifying and uploading individual macros from a file, potentially under a different name, and provides an API to retrieve all existing macro names. This is a crucial precondition for future migration tooling, ensuring macro execution works correctly after migration. (478325)

TypeDataReplication configuration in IAS LineControl Scope configuration
This feature allows system administrators to configure TypeData.Enabled, SetupSpecsScope, ProductionArea, ProductFamilies, and LCApplNameFormatString for each LineControl Scope. It introduces a new logic for Counter/Timer downloads and validation. (478337)

ErrorMessage for adding new process which is existing already
This feature ensures that an error message is displayed when attempting to add a process to the process list that has the same processNo and processName as an existing entry. This prevents duplicate entries in the process list and validates inputs for processNo and processName. (478338)

Extend Counter/Timer configuration within Setup Specs to integrate former Line Control configuration
This feature extends Counter and Timer configurations in SetupSpecs and TypeDataReplication to include former LineControl Configuration Parameters such as Counter.Block.Severity, Timer.Block.Severity, Timer.TriggerTimerCausesPartForStationFalse, Timer.StopTimerOnProcessRequestWhenPartForStationFalse, and Timer.OnProcessRequest.Call.Always.SetNextStation. This ensures consistent behavior of Counters and Timers when configured via SetupControl or SetupSpecs, aligning with previous LineControl Configuration behavior. (478911)

Implementation of logic to migrate Supermarket Data from MES classic LineControl into IAS Line Control
This feature focuses on implementing the logic required for migrating supermarket databases from Nexeed Classic to IAS. It ensures that preconditions for supermarket database migration are met, including tooling for exporting/importing part data (including supermarket name relations) and an API to retrieve existing Supermarket Names for conflict detection. This is a crucial prerequisite for the overall migration process. (545818)

[LC]: Enabler: Horizontal Scalability - Implement async/await pattern for application code
This enabler introduces the async/await pattern throughout the application’s repository methods. This change makes database operations non-blocking, significantly improving the scalability and responsiveness of the application. It ensures that all synchronous calls are replaced with their asynchronous equivalents, and the pattern flows end-to-end through service layers and controllers, preparing the application for horizontal scalability. (417780)

[LC]: Enabler: Horizontal Scalability - Implement proper Memory Cache to read data from DB
This enabler implements a proper memory cache for reading data from the database, a crucial step towards achieving horizontal scalability. This allows multiple instances of the service to run in parallel without interfering with each other, handling increased concurrent requests with improved performance and functionality, nearly linearly scaling with the number of instances. (549317)

ART PEX Enabler [LC] Keep OTEL Tracing - TraceId in rabbitmq-based communication
This enabler ensures that the OTEL TraceId is properly transmitted in asynchronous communication, particularly in RabbitMQ-based interactions. The solution leverages OTEL standard propagation via message broker headers, preventing pollution of the functional payload and ensuring compatibility between communication partners. This allows for comprehensive tracing of operations across services. (548959)

Sets default values for TypeData.BackgroundReplication, TypeData.ReplicationPeriod, GetOnlyNewestRelease, IncludeTypeVariant. (478337)

AdditionalData query is not scoped
The "QueryAdditionalData" call in linecon now correctly scopes AdditionalData queries. Previously, the implementation of "QueryAdditionalData" in DbQueryFactory was not scope-aware, leading to incorrect AdditionalData mappings for parts with the same identifier but different scopes. This fix ensures that parts with identical identifiers but different scopes will now retrieve their distinct AdditionalData correctly. (430793)

Public API (tenantID)/supermarket/parts does not work anymore (linecon API)
The public API /api/legacy-api/v1/{tenantId}/supermarket/parts and /legacy-api/v1/{tenantId}/timers/update now function as expected. Previously, these APIs were not working due to missing scope parameters. This fix ensures that these public APIs continue to operate without errors, maintaining compatibility for existing integrations. (556739)

Removed several obsolete parameters: TypeData.CacheReloadThreshold, TypeData.CallToProviderService.TimeoutInSeconds, TypeData.Cache.UpdateFromSetupControl. (478337)

Removed the "Locations" parameter. (478337)

For some connector packages in ERP Connectivity used by Order Management, the minimum required versions have been updated. Please consult the "Migration of Version 5.12.x to 5.13.x" chapter in the Operations Manual for more details.

Finalize Order Management OPP v1 specification and support (545742)

Calculation of Start and End Date of the Order (549473)

Nexeed IAS Modules offer standarized OpenAPI spec doc (463325)

Finalize SRS related IAS ERP Connectivity integration scenario (548494)

Provision of Public Async API documentation v2 (456781)

Migration to a RabbitMQ 4–Compatible Client Library (551539)

ASM Connector
Failure on GetRecipeHeaders (551737)

Strict-Transport-Security security header on Azure environment missing (551687)

No 0-downtime upgrade from previous versions possible!

Introduces FinalResponseDeliveryStatus to show the overall result of ResponsePath executions in the Message Log, enabling visibility of failed responses to south. Updates the UI with filters and icons that reflect the combined status (562318)

Introduces a dedicated retry mechanism for Response Paths in ConnectorPackages, a WebUI tab for Automatic Retries, and retry configuration (RetryLimit and RetryInterval); retries only failed ResponsePath steps and prevents manual retries while FinalResponseDeliveryStatus is Pending (562319)