The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help
.
. 
Invalid Packets MOD009CEV New from S 39.5.11
From DB 39.5.0
- Customizer Migration Migration packets panel Invalid Packets
Up to DB 39.5.0
- This module contains all invalid migration packets.
- Invalid migration packets are packets that are saved in the database but can no longer be found under the saved path. The path must either be corrected or the packets must be deleted.
From S 39.5.17
Legend
-
indicates that the migration packet has not been executed yet.
-
indicates that the migration packet has run successfully.
-
indicates that the migration packet has failed. The failure of a migration packet may have several reasons: - Before they are run, many migration packets check whether the customizing on which the fix is based, has changed.
- If this is the case, the packet will not be changed. The packet is considered failed.
- In this case, the customizing has to be checked in order to find out whether the modification in question can be carried out.
- If the modification has been carried out or the modification is not necessary, the packet can be set to completed manually by activating the Completed checkbox.
- As a result, it is moved from the Failed/open packets area to the Completed Packets module.
- If this is the case, the packet will not be changed. The packet is considered failed.
- Many help packets check the customizing for problems.
- If they fail, this means that the customizer must become active.
- As a result, the positions listed in the logfile have to be checked and modified.
- If the cause for the failure has been eliminated, the migration packet can be run again by clicking on the Run packet button in the Overview of all Previous Runs module.
- Before they are run, many migration packets check whether the customizing on which the fix is based, has changed.
-
NEW signalizes that this migration packet is still open and waits for another migrationpacket to reach a particular status before it can be run.
-
NEW signalizes that this migration packet is not relevant for the current update type due to version dependencies.
-
means that this migration packet has been skipped. This status is not used at the moment.
Up to S 39.5.17
Legend
-
signalizes that the migration packet has not been executed yet.
- means that this migration packet has been skipped.
-
signalizes that the migration packet has failed. The failure of a migration packet may have several reasons: - Before they are run, many migration packets check whether the customizing on which the fix is based, has changed.
- If this is the case, the packet will not be changed. The packet is considered failed.
- In this case, the customizing has to be checked in order to find out whether the modification in question can be carried out.
- If the modification has been carried out or the modification is not necessary, the packet can be set to completed manually by activating the Completed checkbox.
- As a result, it is moved from the Failed packets area to the Completed Packets module.
- If this is the case, the packet will not be changed. The packet is considered failed.
- Many help packets check the customizing for problems.
- If they fail, this means that the customizer must become active.
- As a result, the positions listed in the logfile have to be checked and modified.
- If the cause for the failure has been fixed, the migration packet can be run again by clicking on the Run packet button in the Overview of all Previous Runs module.
- Before they are run, many migration packets check whether the customizing on which the fix is based, has changed.
-
means that a migration packet has run successfully.
 |
|
