Migration guide 4.1

This guide explains the changes required to migrate to the stated version of the Atoti Adjustments Services API.

Migrate to 4.1.2

No migration needed.

Migrate to 4.1.1

Core configuration class

The AdjustmentServicesCoreConfig class was introduced to centralize the imports of the services and configuration properties that are available in the library. You will need to import this class in one of your @Configuration classes in order to use the library’s services and properties in your application.

Import example:

import com.activeviam.adjustments.cfg.AdjustmentServicesCoreConfig;
...
@Configuration
@Import({
    AdjustmentServicesCoreConfig.class,
    ... // other imports
})
public class MyAppConfig {}

Migrate to 4.1.0

Artifact group ID

The artifact’s group ID has changed. To import this dependency, you now need to use:

<dependency>
    <groupId>com.activeviam.solutions</groupId>
    <artifactId>adjustments-services</artifactId>
    <version>${adjustment-services.version}</version>
</dependency>

Upgrade to Java 21

Java 21 is now required to compile and use the library.

Upgrade to Common Parent POM and Common Dependencies BOM 2.0.1

The library has been upgraded to Common Parent POM and Common Dependencies BOM 2.0.1.

To use the library, please import it as:

<dependency>
    <groupId>com.activeviam.solutions</groupId>
    <artifactId>adjustments-services</artifactId>
    <version>4.1.0</version>
</dependency>

Adjustment filters and input converted to List

The filters and input fields in AdjustmentRequestDTO.java and SupportedAdjustmentDTO.java are now Lists instead of Sets. This change enables the UI to construct dashboards with the order of filters and hierarchies defined by the host server application. This is a breaking change, as any implementation of Atoti Adjustments Services API may need to be updated to use Lists instead of Sets.