Import and validate configuration
Import is available from File > Import and may also be invoked for accepted dropped or pasted template files. Use only a trusted .CFG package whose source, checksum, product compatibility and intended target are known.
Import actions
| Displayed action | Effect | Review question |
|---|---|---|
| Add | Saves a new module when the FID is not present. | Are its name, folder, dependencies and environment settings correct? |
| Update | Saves over the existing module with the matching identity. | Which current consumers will see changed behaviour? |
| Add Duplicate | Creates a new identity when a module already exists. | Will references point to the intended original or duplicate? |
| Ignore | Does not save that included module. | Is the existing target object genuinely compatible? |
| Same | Import comparison considers the module unchanged. | Have environment-owned values and runtime behaviour also been checked? |
The importer may initially mark existing folders, Transports and DB Connections as Ignore, other changed existing modules as Update, matching/default modules as Same, and missing modules as Add. Review every row; defaults are not deployment approval.
Procedure
- Back up the target configuration, confirm target context and pause affected processing where required.
- Open the package and confirm the expected root module and dependency count.
- Compare material rows. Assign an explicit action to every non-Same module and preserve the root module.
- Select Import once. Do not repeat an uncertain import without first inspecting the target.
- Confirm each expected module exists under the correct folder, resolves its dependencies and retains intended target-specific values.
- Refresh/restart the relevant runtime and run controlled functional checks through Flow, Transport or API boundaries.
- Record resulting identities, validation results and deviations from the package manifest.
Import saves module families in an internal dependency order and is not an all-or-nothing transaction. If a result is uncertain, stop affected work, preserve logs/comparison artefacts and follow rollback and recovery.