# Save and publish the element

## Saving the currently being created/edited application element <a href="#zapiszpublikacja-zapisaktualnietworzonego-edytowanegoartefaktu" id="zapiszpublikacja-zapisaktualnietworzonego-edytowanegoartefaktu"></a>

After making changes and clicking the **Save**, a popup will appear with the option to save a new version of the business application element.

In the element name and in the description **it is possible** to use the following characters:

* uppercase and lowercase letters (without Polish diacritics),
* numbers,
* hyphens ( - ),
* underscore characters ( \_ ).

It is possible to add a comment and determine whether the current version of the artifact is a new Major version (`*.1`), or a subversion for the current branch (`1.*`). More on versioning in the chapter [Versioning](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/wersjonowanie).

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FQkGLH9NHPfr3QUH0xKuJ%2Fimage.png?alt=media&#x26;token=1388dee9-0a23-4233-884a-5a4490750767" alt=""><figcaption><p align="center"><em><strong>Figure 1.</strong> Standard artifact save popup</em></p></figcaption></figure>

## Dependencies that will be changed <a href="#zapiszpublikacja-artefakty-ktorychzachowaniezmieniasz" id="zapiszpublikacja-artefakty-ktorychzachowaniezmieniasz"></a>

When saving an application element, a list of other elements is displayed, which are affected by the saved version. You should review it and check the checkbox **I have reviewed the list of dependencies**.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FdM2NoQpuLDh4KCyGoKxA%2Fimage.png?alt=media&#x26;token=ac0dcdd7-116e-4d16-93bb-070bc9964a47" alt=""><figcaption><p align="center"><em><strong>Figure 2.</strong> Artifact save popup with a list of dependencies</em></p></figcaption></figure>

## Publishing the selected version of the application element <a href="#zapiszpublikacja-publikacjawybranejwersjiwniosku" id="zapiszpublikacja-publikacjawybranejwersjiwniosku"></a>

Publishing a version of an application element other than the highest one available in the repository is possible in several ways. For example, while in read-only mode in the form editor, you can select the **Versions**, and then after the window is displayed **Version history** select the option from the context menu **Publish**:

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FILAWVwKGuUz56Z7QiCvS%2Fimage.png?alt=media&#x26;token=d35357cd-d093-4afd-a2a2-08f6a75c35b0" alt=""><figcaption><p align="center"><em><strong>Figure 3.</strong> Version history window of the application form and a context menu containing the publish option</em></p></figcaption></figure>

The version history window can also be displayed while in the form editor, where for each template the context menu provides the option **Version history**.

## Currently effective version of the application element <a href="#zapiszpublikacja-aktualnieobowiazujacawersjaartefaktu" id="zapiszpublikacja-aktualnieobowiazujacawersjaartefaktu"></a>

The only information about the currently effective version of the artifact is **checking the date of the last save**.

{% hint style="warning" %}
In the case of forms, it should be remembered that it is not the artifact version that indicates the active one. The illustration below shows that changes were made in version 2.\*, but whether this is the current version of the form depends on whether another version has not been published (see above).
{% endhint %}

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2Fj0lqmjwTIJDmCgeXCSZ3%2Fimage.png?alt=media&#x26;token=58f57c77-1d65-4a3f-904c-e41c0e758036" alt=""><figcaption><p align="center"><em><strong>Figure 4.</strong> Version history window of the form (version 2.* is the version with the latest changes)</em></p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/elementy-aplikacji-artefakty/zarzadzanie-elementami-aplikacji/zapis-wraz-z-publikacja-elementu.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
