Versioning

In a component, you can select the version you want to edit.

By clicking on the first menu item (Version 1…N), a dialog will show you the versions currently defined for the component.
By default, only Version 1 is available.

The table displays the available versions, and for each one, the status and last update date.
The status can be one of:

• Published: the version is visible in at least one environment as specified in the Availability section.

• Not Published: the version is not visible in any environment.

You can click on a specific version to edit, and the page will switch to that version.
When entering the component editing page, the latest version is always opened, so be careful when starting to edit.

Create a new Version

By clicking on the Add Version button, the entire component is cloned to a new version with the state set to Not Published.
The new version is marked as Draft, and within it, you can start editing the new version of the component.

When done, you can click on the Draft version to start editing it.
In the Availability section, you can select one environment to test changes. Each time you edit something and press the Save button, the DRAFT component is immediately installed and updated in the selected environment.
In this way, you can directly test changes without affecting other environments using the same component.

To help you debug your code, the JS resource is NOT MINIMIZED, so you can navigate the DPS and add breakpoints to your source code.
When you have completed your development, in the Version table, by clicking on the 3-dot icon of the Draft version, you can select whether to promote changes to a new version (e.g., Version 2) or merge changes to the current one (e.g., Version 1).

In case you select a new version (e.g., Version 2), you should also edit the Availability to make the component version visible in your environments.