> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/elementy-aplikacji-artefakty/zarzadzanie-elementami-aplikacji/zapis-wraz-z-publikacja-elementu.md). # Saving and publishing an item ## Save of the currently being created/edited application element After making changes and clicking the button **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 **you can** use the following characters: * uppercase and lowercase letters (without Polish characters), * numbers, * hyphens ( - ), * underscores ( \_ ). 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 about versioning in chapter [Versioning](/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/wersjonowanie.md).

Figure 1. Standard artifact save popup

## Dependencies that will be changed When saving an application element, a list of other elements affected by the version being saved is displayed. It should be reviewed and the checkbox **I have reviewed the list of dependencies**.

Figure 2. Artifact save popup with dependency list

## Publishing a selected version of an application element 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 button **Versions**, and then after the window appears **Version history** from the context menu select the option **Publish**:

Figure 3. Window with the request version history and a context menu containing the publishing option

The version history window can also be displayed while in the form editor, where for each template the context menu includes the option **Version history**. ## Currently applicable version of the application element The only information about the currently applicable version of the artifact is **checking the date of the last save**. {% hint style="warning" %} In the case of forms, remember that it is not the artifact version that points to the applicable one. The illustration below shows that changes were made in version 2.\*, but whether this is the applicable version of the request depends on whether another version has not been published (see above). {% endhint %}

Figure 4. Window with the request version history (version 2.* is the version with the latest changes)

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` 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=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.