The purpose of this operation is to simplify getting MFT artifacts into an SCM, and typically this operation will be used in a utility workflow specifically built to populate SCM, rather than in the build workflow.
Exports a list of transfers and the associated source and target artifacts , including and the config plan , from the MFT Design time to the export folder in the plugin execution's temp folder FD_TEMP_DIR/export . You can copy these files from the ../temp/export/ folder to wherever your mft source is checked out from the SCM using the file plugin.
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 file 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 purpose of this operation is to simplify getting MFT artifacts into an SCM, and typically this operation will be used in a workflow specifically built to populate SCM, rather than in the build workflowThe name will be converted back to the Source, Target, or Transfer ID at deployment time automatically.
Environment/Instance Properties
...
Property Name | Property Code | Required | Description |
|---|---|---|---|
Rename After Export | FDMFT_RENAME_AFTER_EXPORT | No | The artifacts wil If checked, the artifacts will be renamed to the name of the artifact after exportexporting. See the paragraphs above for more information on how and when the artifacts are renamed. |
Inputs
| 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. |
...