Strict import mode
Imports just everything that is in the exported package so that the configuration in the target environment will be exactly as in the package. Strict import is useful when you want to export the exact set of the configuration from the source to replace in the target environment. In contrast with the Loose import, if a single configuration component is missing, the import will not be carried out.
For instance, if a filter criterion of a TSI step cannot be imported, then in strict mode the entire filter is not imported. As a result, the involved TSI is not imported either. However, other filters/TSIs without problems will be imported though.
For instance, if a filter criterion of a TSI step cannot be imported, then in strict mode the entire filter is not imported. As a result, the involved TSI is not imported either. However, other filters/TSIs without problems will be imported though.
In the Loose mode, the filter is imported without the failing criterion and the TSI is imported as well.
 | A Strict import (entire hierarchical BO) of a Loose export (only userdefined BO (s)) cannot be done as this can corrupt the target configuration inadvertently. In Strict mode, configuration components like UDBOs, pick list items are deleted from the target environment in case they are no longer present in the package. |