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.

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.

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:

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.
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).

Last updated
Was this helpful?
