The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help

Overview of all Previous Runs MOD009BXV New from S 39.5.0

Access path

Customizer Migration Migration Packets panel Click on the link on the migration packet name in the respective migration packets module

Customizer Migration Migration Packets Click on the link on the migration packet name

Customizer Migration Overview Of The Migration Packets Click on the Show history link

Information

This module is a kind of data sheet of the respective migration packet and provides the following options:
- Results of the migration runs can be checked
- A migration packet can be run (again)
- A migration packet can be marked as completed
- Via the link on the Logfile field, the logfile of a run can be opened

Description

Information

The Description field contains
- a description of the changes that the migration packet carries out.
- (possibly) notes, if the migration packet no longer exists in the specified directory but is still available in the database.

This area contains the following information:

Python path: Path under which the migration packet can be found in the file system
Comment: Optional comments
Upon system start: Setting whether the migration packet is run upon system start.
Completed: Setting whether the migration packet is to be marked as completed. This can be changed manually.

Information

Relevant from DB shows the minimum database version required for carrying out this migration packet.
Up to DB shows the maximum database version required for carrying out this migration packet.
Current DB version shows the database changeset, which is used in the system.
- A migration packet can only be run if the used database changeset is between minimum database version and maximum database version.
- If this is not the case, the migration packet will be classified as not relevant and will be displayed in the Irrelevant Packets module.
- The frame color of the fields indicates whether the dependencies are satisfied (green frame) or not satisfied (red frame).
NEW Database Management System, whether the packet has a dependency with a database management system.
NEW In the Packet dependencies subarea, packets (with the expected status) are listed, on which the opened packet depends.
- If the opened packet has a dependency on a packet which was not imported, there is a message in the status line.

Information

The
- Relevant from DB shows the minimum database version required for carrying out this migration packet.
- Up to DB shows the maximum database version required for carrying out this migration packet.
- Current DB version shows the database changeset, which is used in the system.
A migration packet can only be run if the used database changeset is between minimum database version and maximum database version.
If this is not the case, the migration packet will be classified as not relevant and will be displayed in the Irrelevant Packets module.
The frame color of the fields indicates whether the dependencies are satisfied (green frame) or not satisfied (red frame).