...
When an artifact exports from MFT the name looks like: so_916dffd7-19fc-406e-9fac-12b46fe79d0f.xml, this makes it hard to determine which files to pick then deploying a transfer and its associated files, so the ExportTransfer operation will automatically rename the files to the name of the source, target, or transfer that it contains. This name will then be the one that is checked into SCM if you add additional steps to the workflow. The name will be converted back to the Source, Target, or Transfer ID at deployment time automatically.
The plugin defaults to exporting Common Attributes like the UI would:
.
You can export with All Attributes using the input "All ConfigPlan Attributes."
Environment/Instance Properties
...
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| Transfers To Export | TRANSFERS_TO_EXPORT | No | Comma separated list of transfers to export. If left empty, all transfers will be exported. |
| All ConfigPlan Attributes | FDMFT_INP_EXPORT_ALL_CONFIG_PLAN | No | If checked, All attributes will be added to the config plan. Otherwise only Common attributes will be added. See the image above for information about where the setting is present in the UI. This input was added in version 5.0.1.8. Prior to that it defaulted to false, exporting only the key (common) options in the config plan. |
Outputs
Output Name | Required | Description |
|---|---|---|
...