Version management of flow services
Use version management to track, manage, and restore different versions of flow services.
To view the version history of a flow service, click the More options icon and select Version History from the flow services toolbar panel.
When you save a flow service, a new version is added to the Version History with the default commit message. You can also provide a custom commit message by clicking the drop-down arrow next to the Save option and selecting Save with message. You can click on any version on the Version history panel and view the corresponding flow service version. To restore an earlier version, select the earlier version of the flow service, and click the Restore icon . If you have reverted to an earlier version and there is a scheduled execution for the flow service, the reverted version runs as per the defined schedule.
- If a flow service references any other flow service, then the pipeline mapping of the referenced flow service is also restored to that particular version. But if the pipeline mapping of the referenced flow service has been modified in a later version, the modification might break the mappings and the flow service execution will not be successful.
- If a flow service references any document types, reference data, custom operations, REST connectors, and SOAP connectors, and if those references have been modified, then those references will not be restored.
- If you delete a flow service and then create another flow service with the same name, the version history of the deleted flow service will be available.