Multiple environments are available to validate setup.
Setup that has been validated on test environment can be easily transferred and deployed on production one thanks to migration feature.
Eligible elements for migration
Some configuration settings and data can be exported and imported.
Ruleset chainings:
This is including all rulesets related to it.Rulesets
This is including timetables, groups and stock requests related to it.Backoffice parameters:
This sections includes all parameters defined in Settings page of the admin websites (like Orders, Stock, Orchestration, Stock locations, Items, Delivery and Languages).Delivery config
This is including routes, areas, metrics, execution times (of delivery config and of store locations related to areas) and delivery restrictions.
Migration is ONLY limited to admin website parameters, site config is NOT eligible for migration.
Translations are NOT eligible for migration.
Export is designed to ease user selection by hiding internal mechanism.
Some elements are including others, it is NOT possible to deny export of included elements.
It is NOT possible to select low level elements.
Export environment config
Connect to admin website of the environment that has to be exported
Go to Configuration → Migration (top right)
Go to Export Environment.
Select the elements to export.
Click on Export button to download locally an export document.
Some delay may occur before download start, due to generation of document.
Duration of download depends on exported data and bandwidth.
Export is based on live version. Draft is NOT included into export.
Import environment config
Environment performing importation MUST be in same version as the one that generated the export file.
Delivery config update requires computation, which requires to use draft for safety reasons.
Importation of delivery config elements forces deletion of existing draft without publishing it. Warning will be displayed to current user performing importation.
Imported elements are on live version.
NO lock is performed on system, so do NOT perform multiple importations at same time.
NO notification is sent to users if importation is performed: data on their screen may NOT be relevant and publication of their draft will be denied.
Connect to admin website of the environment that has to import data.
Go to Configuration/Migration
Go to Import Environment.
Upload export file from local storage
Duration of upload depends on exported data and bandwidth.
List of all elements included in export file is displayed.
Elements that will be added or overwritten are identified.Select elements to import.
Click on Import button to import data into the environment.
System will perform a validity check on data.
Based on content, some warnings may be displayed. Please follow instructions to fix data.If delivery configs are part of imported data, a draft will be created.
Draft can be instantly published or delayed.
If draft publication is NOT performed at end of importation, draft content can be modified and published like any draft (Go to Delivery page and open draft).
If errors occur during importation, warning will be displayed.
There is NO fallback implemented, importation before error raising are not cancelled.
Retry importation will be required except for delivery config: draft will NOT be deleted and can be fixed manually if needed - however, it is STRONGLY advised to retry importation.
Imported delivery configs may involve store locations that are NOT in the environment from which the export has been generated : execution timetable may be missing.
This check is part of the validity check.
List of store locations with missing data will be displayed.
Manual fix is required.
