...

This operation is intended to be used in a utility workflow that commits the exported files to your SCM. This allows us to set up a utility project that runs on a schedule. Then, we can configure a separate Build/Deploy project for each integration that use uses a 'Poll SCM' trigger watching the SCM path that the utility project commits changes to. This allows for Continuous Integration even though the project is not normally stored in SCM.

...

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

Special Considerations

Integrations will be exported based on their last updated date time. When an update is detected, the integration will be exported to an .iar file inside of a folder with it's integration id in the FD_TEMP_DIR. For example, the integration "HELLO_WORLD" version 1.001.0000 would be exported to the following location: FD_TEMP_DIR/HELLO_WORLD.1.001.0000/HELLO_WORLD.1.001.0000.iar.

If FDOIC_INP_EXTRACT_INTEGRATIONS is INTEGRATIONS is true, the .iar file will be expanded at the same level as the original file. (e.g. FD FD_TEMP_DIR/HELLO_WORLD.1.001.0000/...)