Migrate from Atoti What-If 4.0.4-AS6.1 to 4.1.-AS6.1. Consult the Atoti What-If 4.1.-AS6.1 release notes and changelog for a complete view of changes.Documentation Index
Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt
Use this file to discover all available pages before exploring further.
Recommended migration process
- Back up your project.
- Update the Atoti What-If dependency.
- Upgrade your security manager.
- Update your external database schema (only required if using an external database).
- Confirm successful build and startup.
Update dependencies
pom.xml
Update Atoti Server to 6.1.11
Atoti What-If 4.1.0-AS6.1 is shipped with 6.1.11, but you can use later versions if they are available.
Update Atoti What-If to version 4.1.0-AS6.1
You can upgrade Atoti What-If in your project from 4.0.4-AS6.1 to 4.1.0-AS6.1 by making the following change:- Atoti What-If 4.0.4-AS6.1:
- Atoti What-If 4.1.0-AS6.1:
Upgrade your security manager
Atoti What-If 4.1.0-AS6.1 improves user authorization for simulation and branch management. To achieve this, this release introduces several changes to theIDatabaseSimulationsSecurityManager and its SpringDatabaseSimulationsSecurityManager implementation.
If you are using the provided SpringDatabaseSimulationsSecurityManager implementation, update your configuration from
- Atoti What-If 4.0.4-AS6.1:
- Atoti What-If 4.1.0-AS6.1:
| Method | Previous Parameters | New Parameters | Details |
|---|---|---|---|
canUpdate | Object databaseSimulationId, IDatabaseSimulation updatedDatabaseSimulation | IDatabaseSimulation updatedDatabaseSimulation | The database simulation already includes the ID, making the method logic less error-prone. |
canUpdate | List<Object> databaseSimulationIds, List<IDatabaseSimulation> updatedDatabaseSimulations | List<IDatabaseSimulation> updatedDatabaseSimulations | The database simulations already include the ID, making the method logic less error-prone. |
| Method | Parameter | Details |
|---|---|---|
canCreateBranch | branchName | The security manager has to check permissions to create branches as the Atoti Server branch permissions manager also assigns such permissions. |
Update your external database schema
If you are using an external database for persisting simulation information, update its schema to include the following changes:| Atoti What-If 4.0.4-AS6.1 | Atoti What-If 4.1.0-AS6.1 | Modification | Field | Type | Details |
|---|---|---|---|---|---|
| DATASTORE_SIMULATIONS | DATASTORE_SIMULATIONS | Added field | executedBy | VARCHAR(4000) | The executing user will be persisted alongside all other simulation details. |
4.1.0-AS6.1 to 4.1.1-AS6.1
Migrate from Atoti What-If 4.1.0-AS6.1 to 4.1.1-AS6.1. Consult the Atoti What-If 4.1.1-AS6.1 release notes and changelog for a complete view of changes.No migration needed.
4.1.1-AS6.1 to 4.1.2-AS6.1
Migrate from Atoti What-If 4.1.1-AS6.1 to 4.1.2-AS6.1. Consult the Atoti What-If 4.1.2-AS6.1 release notes and changelog for a complete view of changes.No migration needed.
4.1.2-AS6.1 to 4.1.3-AS6.1
Migrate from Atoti What-If 4.1.2-AS6.1 to 4.1.3-AS6.1. Consult the Atoti What-If 4.1.3-AS6.1 release notes and changelog for a complete view of changes.No migration needed.
4.1.3-AS6.1 to 4.1.4-AS6.1
Migrate from Atoti What-If 4.1.3-AS6.1 to 4.1.4-AS6.1. Consult the Atoti What-If 4.1.4-AS6.1 release notes and changelog for a complete view of changes.No migration needed.
4.1.4-AS6.1 to 4.1.5-AS6.1
Migrate from Atoti What-If 4.1.4-AS6.1 to 4.1.5-AS6.1. Consult the Atoti What-If 4.1.5-AS6.1 release notes and changelog for a complete view of changes.No migration needed.
4.1.5-AS6.1 to 4.1.6-AS6.1
Migrate from Atoti What-If 4.1.5-AS6.1 to 4.1.6-AS6.1. Consult the Atoti What-If 4.1.5-AS6.1 release notes and changelog for a complete view of changes.No migration needed.