Migrating to AppStream
Customer modified parameter file and panel files
There is no fixed migration for project modifications. The standard process is to recreate a customer modification.
If the previous modified parameter file is from SWB 16.1.0, you can reuse the previous parameter file. The consequence is that you cannot use the new SWB functionality, which depends on changes in the parameter file, as the information is missing. It is recommended to have assistance when deciding if you can reuse the parameter file modification.
You can reuse the customized panel files for simple panel modifications. It is recommended to have assistance when deciding if you can reuse the panel modification.
Migrating from RDWeb
The RDWeb is setup with five icons that is intended for five different warehouse groups. In this case, you must start each SWB icon and compress the schedule version. Specify the name containing ID of the warehouse group or similar relevant name for the zip file. It is easier to import the zip file into AppStream if the correct zip file is selected.
Follow the steps in migrating SWB in AppStream. You can start SWB in AppStream and upload the relevant zip file to AppStream then SWB imports the zip file. You can now have the same setup in RDWeb for the warehouse group.
Migrating from SWB 15.1.6 or older versions
You can migrate from SWB 15.1.6 or older version by compressing the schedule version to a zip file. The zip file is converted to SWB 16.1.0 format using a tool included in the application.
After conversion, you can import the converted zip file to SWB AppStream.
Migrating customer modified parameter file and panel files from SWB 15.1.6 or older version is not recommended, because of the changes to SWB 16.1.0. You can recreate the customization instead.