Publish export template changes
How drafts, publishing, and revisions work in the Developer Portal, and how to publish your changes to the Productsup platform.
Changes you make to an export template in the Developer Portal do not go live in the Productsup platform until you publish them. Every change is saved as a draft first, and platform users keep seeing the last published version. This way, you can work on settings, attributes, and analyzer tests without unfinished changes reaching production.
Drafts, revisions, and the active revision
An export template has two parts: the draft you edit and the version the platform uses.
| Term | What it means |
|---|---|
| Draft | Changes you have saved but not published yet. Platform users do not see the draft until you publish it. |
| Revision | A saved copy of the whole export template, created each time you publish. Revisions are numbered, starting with Revision 1, and never change after they are created. |
| Active revision | The revision the platform uses. Publishing creates a new revision from your draft and makes it the active revision. The version history shows the revision that was active before as Previous. |
Publishing covers every part of the export template, including analyzer tests. A change to an analyzer test does not affect the analyzer results in the platform until you publish it.
Check what is live and what is unpublished
The bar at the top of the export template page shows the state of the export template:
- Active revision: the revision number, when it was last published, by whom, and where it was published from, for example the Dev Portal or the API.
- Draft: Unpublished changes when you have saved changes since the last publish, together with the number the next publish gets, for example Will publish as Revision 4. When there is nothing to publish, the bar shows No unpublished changes.
When an export template has unpublished changes, a banner at the top of the page shows how many changes are waiting to be published. An export template that has never been published shows Not yet published.
Publish your changes
Go to Export templates in the Developer Portal and open the export template.
Check that the bar at the top of the page shows Unpublished changes.
Publish is only available when the export template has unpublished changes.
Select Publish.
The Developer Portal creates the next revision and makes it active. While the platform picks up the new revision, the bar shows Publishing revision. This can take up to 6 minutes. Until publishing is complete, platform users keep seeing the previous revision.
You can also publish from the version history of the export template. See View version history.
Work on the same export template with other people
Several people can work on the same export template, in the Developer Portal or through the Export Template Management API. The Developer Portal warns you about changes made by other people, but it does not stop you from saving over them.
- While you edit: If someone else changes the export template after you opened it, the page shows a warning when you return to it. Select Reload to see their changes. Anything you save before reloading can overwrite their changes.
- When you publish: If someone else changed the export template since you loaded the page, the Developer Portal does not publish. Reload the page, check the changes, and select Publish again.
Caution
Reloading replaces what is on screen with the latest saved version. Any edits you have not saved are lost.
Changes made through the API
Changes made through the Export Template Management API go into the same draft as changes made in the Developer Portal. Selecting Publish publishes all unpublished changes to the export template, whichever way they were made.
Publish in the Developer Portal when you review and publish changes yourself. Publish through the API when an integration or a script changes the export template and should publish its own changes. See Publishing changes.
How is this guide?