Flow Revisions
Each time a flow is saved a separate revision of that flow is stored. An optional Comment field is available at the bottom of the flow workspace for information about changes to the flow. The Comment, date, and user name of the user who saved the flow are stored with each revision.
Using the Revisions dialog you can view a list of revisions for a flow along with the associated Comment, date, and user name of the user who saved the flow. Revisions are listed in descending order from most recent to oldest. From the menu 
for a revision you can revert the working copy of a flow to that revision or export the entire revision. Exported revisions can be imported just like any exported flow.
Considerations
- A reverted flow is incomplete until it is opened, validated, and saved.
- A flow locked by another user cannot be reverted to a prior version.
- When a flow is duplicated, the most recent revision of the original flow is used.
- The Net Change feature for a reverted flow uses the Most Recent Record Processed date stored for the last execution of any revision of the flow not the date that was part of the stored revision.
To access the Revisions dialog:
- Open the app containing the flow with the revisions you want to view.
- From the menu for that flow select Revisions.
Flow Revisions
The Revisions dialog includes the following information:
| Field | Definition |
|---|---|
|
Columns |
|
|
Revision |
Number of the revision. The current working copy of the flow is the revision with the highest number. If you revert the current working copy to a prior revision, the flow is saved and the revision number is incremented. |
|
Comment |
Comment associated with the revision. Comments can be entered in the Comment field at the bottom of the flow workspace or generated by TIBCO Cloud™ Integration - Connect based on the action taken. Comments are not required. Comments generated automatically by TIBCO Cloud™ Integration - Connect, include: Duplicated — Flow has been copied from another flow. Flow autosaved due to an inactivity logout — The user interface was idle long enough to exceed the inactivity timer. The flow was automatically saved and the user was logged out. If the changes should not have been saved, you can go back one revision andaccess the prior version of the flow. Imported — Flow has been imported. Initial Revision — Flow is created. Reassigned connection from 'ConnectionName' to 'NewConnectionName' — A Connection in the flowp has been reassigned. Reassigned connection to 'NewConnectionName' — The original Connection in the flowp could not be found and a new one has been reassigned. This could happen if the flow was imported and the Connection in the import file does not exist in the Organization. Reverted to revision 'xxx' — Flow has been updated to the revision number shown in the comment. |
|
Date |
Date and time the revision was saved. |
|
Created by |
User name of the user who created the revision. |
|
Menu |
|
|
Revert |
Reverts the current working copy of the flow to the selected revision and makes that a new revision at the top of the list. This option is not available for the highest revision since that is the current working copy of the flow. |
|
Export |
Exports the selected revision of the flow in a JSON format. The exported flow can be imported. |