Save with publication of an element
Saving the application item currently being created/edited
After making changes and clicking the Savebutton, we get a popup allowing us to save a new version of the business application item.
In the item name and in the description you can use the following characters:
uppercase and lowercase letters (without Polish diacritics),
numbers,
hyphens ( - ),
underscore characters ( _ ).
It is possible to add a comment and specify 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 the chapter Versioning.
Dependencies that will be changed
When saving an application item, a list of other items affected by the saved version is displayed. You should review it and check the checkbox I have reviewed the list of dependencies.
Publishing the selected version of the application item
Publishing a version of an application item other than the highest available in the repository is possible in several ways. For example, while in read-only mode in the form editor, you can choose the Versionsbutton, and then after the window appears Version history select the option from the context menu Publish:
The version history window can also be displayed while in the form editor, where for each template the context menu contains the option Version history.
Currently active version of the application item
The only information about the currently active 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 indicates the active one. The illustration below shows that changes were made in version 2.*, while whether this is the active application version depends on whether another version was published (see above).
Last updated
Was this helpful?