The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help
.
. 
Completed Packets MOD009CEQ New from S 39.5.11
Description for versions > DB 39.5.0 and < S 39.5.11
Access path
From DB 39.5.0
- Customizer Migration Migration Packets panel Completed Packets
Up to DB 39.5.0
From S 39.5.17
Information
- This module contains all completed migration packets.
- Completed migration packets have either run successfully or were marked as completed manually.
- Migration packets that were marked as completed manually cannot only be displayed as Completed with a green traffic light, but also as New, Failed, or Not relevant.
Up to S 39.5.17
Information
- This module contains all completed migration packets.
- Completed migration packets have either run successfully or were marked as completed manually.
- The display of a red traffic light can indeed occur in this module if the packet did fail but the customizer has marked this packet manually as completed.
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.
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.
 |
|
