Overview
Integration actions now support versioning, working the same way versioning already works for form definitions. Every time an integration action is saved, a new version is created. This lets you see how an action has changed over time, review or export older versions without the risk of accidentally editing a version that's already in use.
How Versioning Works
Each integration action has a current version, which is the version used by forms, jobs, and submissions.
Saving changes to an integration action creates a new version rather than overwriting the existing one.
Previous versions are kept and can be viewed at any time, but they cannot be edited.
Testing an integration action always runs against whichever version you currently have selected, not necessarily the current version.
Viewing Version Numbers in the List
The Integration Actions List (Admin tab > Integration Actions) now includes a Version column to the right of the ID column. This shows the current version number for each action at a glance.
The download button on the right panel of the list always downloads the current version of the selected action.
Selecting a Version in the Editor
When you open an integration action, a version selector dropdown appears in the upper right corner of the screen, to the left of the DETAILS / INPUTS / REQUEST / TEST tab bar. Use this dropdown to switch between the current version and any previous version of the action.
Working with previous versions when you select a version other than the current one:
All fields across the Details, Inputs, and Request tabs become read-only.
The Save, Delete, Add, and Clear buttons are disabled wherever they would normally let you make changes.
You can still export a previous version using the download/export option, so you always have a way to retrieve exactly what was in place at that point in time.
This ensures older versions are preserved as an accurate record and can't be modified after the fact.
Testing a Specific Version
The Test tab works the same as before, with one important difference: testing runs against whichever version is currently selected in the version dropdown, not necessarily the current version. This lets you verify the behavior of an older version if needed (for example, when investigating an issue that occurred before the action was last updated).
CAUTION: As with any integration action test, running a test will actually execute the action (for example, adding/updating/deleting Data Table records, or deleting a submission for a Submission Request). This is true regardless of which version you're testing.
What's Changed for Existing Actions
Existing forms, jobs, and submissions that reference an integration action are not affected. They will continue to use the current (latest) version of the action.
The old History tab on the integration action screen has been removed, since version history is now handled through the version selector.
Notes and Limitations
At this time, forms and jobs always use the current version of an integration action. There is no way yet to pin a form or job to a specific older version.
Visibility into which forms and jobs are using a given integration action is planned for a future release and is not part of this initial rollout.