For the complete documentation index, see llms.txt. This page is also available as Markdown.

Saving an item together with publishing it

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.

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.

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

Last updated

Was this helpful?