Every release and update of an app is versioned, following standard development protocols. To facilitate this, Gravity has a workflow built in for developers and end-users to allow for concurrency of versions and the ability to roll out updates properly.
For every app, there is a currently published version and a draft version that contains unpublished changes.
Publishing an App
When modifying an app, you can manage the status and versioning on the top right of the screen, as you can see here:
.png "image(23).png")
You can see:
The draft status (including the number of changes that have not yet been published)
The date it was last published
A button to publish
When publishing, you will see the following:
.png "image(24).png")
Here it is important to write proper documentation regarding the update, and to set the update type properly.
Once published, the new app version will apply to all new workflow steps created using the app.
Any existing workflow steps will not be changed to use the new version, to avoid any breaking changes. Workflow steps can be updated to the current app version in the workflow builder.
Existing workflow steps using an older version of an app will be indicated as follows:
.png "image(25).png")
Testing a Draft
When you have an app with unpublished changes, you will likely want to test workflows using those changes without needing to publish.
This is accomplished by turning on App Developer Mode on the bottom-right of the workflow builder:
.png "image(26).png")
If this is enabled, all new workflow steps created will use the latest draft of that app. You will see them differently, with the border dotted instead of solid:
.png "image(27).png")
App Developer Mode is at the level of user preferences, meaning all workflow steps created will be affected until you turn it off.
Once you have validated that the updated version of the app is functional, publish it and turn off App Developer Mode to build production workflows.