Homepage Configuration Deployment tool (CDT)
Repository > Configuration Deployment Tool
Page purpose¶
The Configuration Deployment tool (CDT) homepage guides the user through the configuration and start-up of the data transfer in a simple and intuitive way.
What it looks like¶
Below are the main elements of the page:
| Letter | Icon | Element | Function |
|---|---|---|---|
| To | Filter Feature | allows the selection of a subset of objects to be transferred between environments source and target. The filter button, associated with the selected object category, opens the list of items of the selected category, allowing the users to filter by code, description or other attributes. | |
| B | Deletion Policy | Indicates the deletion policy. See Policy Update | |
| C | Transfer run button | Starts the transfer procedure | |
| D | Transfer processes | Opens the transfer notification section. See Notification Panel | |
| E | Transfer Logs | Opens the Transfer logs page showing all transfers made to all accessible targets. See Transfer Logs Page | |
| F | Export page | Opens the Export page, which allows you to export data by writing to a file. | |
| G | Import page | Opens the Import page, which allows you to import data by reading from files. |
This page includes two main cards that allow you to select the environments involved in the transfer:
- Source Environment: where the data to be transferred are located.
- Target Environment: the destination to which the data will be transferred.
After selecting the desired environments, the user can start the transfer by clicking the Run button. This action initiates the process and automatically opens the transfer page.
For further details on how to set up and start the transfer, see the procedures section.
Compatibility between different CPM versions¶
From SP35, the CDT supports the transfer of configurations between Tagetik environments with different source and target versions, as long as the difference between the two does not exceed two releases (e.g. from source SP33 to target SP35).
When performing a transfer between non‑aligned versions:
- the tool operates in backward‑compatible mode, using the older version between the source and the target for metadata and configurations
- if the source is on a newer version than the target, some resources may not be transferred, because they are not yet supported by the target.
IMPORTANT: if the difference between source and target exceeds two releases, the transfer can still be started, but may fail. In this case, the system signals the condition with a warning message and the operation may generate errors.