Draft version of an element

The draft version mechanism enables secure editing of an application item (such as a form, process, or script) without affecting published versions.

Creating a draft version

Going to edit an item automatically causes:

• disabling editing for other users within the given major version (e.g. 1.*),

• creation of a draft version based on the selected version (e.g. 1.8).

For each major version, there can be only one active draft copy. If one already exists, editing access will be blocked until it is saved or discarded.

---

Working with a draft copy

While editing, changes are saved automatically:

• every 30 seconds,

• and when leaving the editor (e.g. closing the tab, switching to another view).

The editor's top bar displays time since the last save to the server. When the editor is reopened, the draft version is restored from the last saved state.

Figure 1. Draft copy information

Changes are approved by clicking the Save as new versionbutton, which causes:

• saving all changes to the repository,

• creating a new major or minor version,

• releasing the edit lock.

---

Discarding a draft version

The author of a draft version can отказаться? Wait translate to English. The author... can at any time отказаться? Let's do: The author of a draft version can at any time отказаться from the saved changes by selecting the option from the left sidebar menu Discard draft copy.

This operation:

• deletes the current draft version,

• restores editing access to that major version for other users.

Figure 2. Menu with the "Discard draft copy" option

---

Unlocking item editing

If the draft version was created by another user and editing is locked, it is possible to force unlock editing via the option Unlock item editing (also in the menu on the left).

Figure 3. Menu with the "Unlock artifact editing" option

Note: this operation is irreversible – all unsaved changes in the draft version will be permanently deleted.

Figure 4. Popup with artifact unlock confirmation