Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
2500_config_apps:0200_work_bsv:0700_publishing_bsv [2026/08/13 00:55] – removed - external edit (Unknown date) 127.0.0.12500_config_apps:0200_work_bsv:0700_publishing_bsv [2026/08/13 07:20] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +[<10>]
 +====== Publishing Business Space Version ======
 +
 +Once a business space version has been tested and you are happy with how your business rules and processes work, the business space version can be published. Publishing business space version makes it available to the end users. The version is moved into the ''CURRENT'' state – see also [[2500_config_apps:0200_work_bsv:0100_bsv_lifecycle]].  
 +
 +If you already have a version in the ''CURRENT'' state it is recommended that you publish the new version when no one is using the old version in the Operation Mode. //**AwareIM**// will not proceed with publishing of the new version until there is no user activity with the old version, so if the old version is being heavily used //**AwareIM**// will keep waiting until there is a break in the old version usage. Once the new version has been published any current users of the old version will not be able to use the old version any more – they will be advised to log out and log into the new version.
 +
 +**It is also highly recommended that you back up your existing operation data before publishing the version – see **[[2500_config_apps:3400_backup_restore|backing up operation data]]**.**
 +
 +Publishing business space version is a complicated process – in particular, if any new business objects have been defined in the version being published or definitions of the existing business objects have been changed, //**AwareIM**// will build and/or alter the corresponding database tables.
 +
 +<alert type="danger" icon="fa times-circle">
 +**warning**
 +
 + If there is already operational data created by the end users while working with the previous versions, publishing a new version may destroy this data if changes to the business object in the new version are such that it is not possible to preserve the existing data – for example, if a definition of a business object has been deleted, all instances of the business object are lost. Similarly if some attribute of a business object has been deleted, the existing data corresponding to this attribute is lost. //**AwareIM**// does everything it can to preserve the existing data whenever possible (for example, when an attribute type is changed) and the Configuration Tool warns the user immediately if the configurator’s changes lead to any loss of data – see also [[2500_config_apps:0500_add_edit_objects|Adding/Editing Business Objects]].</alert>
 +
 +===== To publish a business space version =====
 +
 +  - Make sure that the version you want to publish is loaded – see [[2500_config_apps:0200_work_bsv:0300_loading_bsv|Loading Business Space Version]].
 +  - Click on the business space version you want to publish in the Elements Tree to select it (the version must be in either the ''UNDER TEST'', ''OBSOLETE'' or ''NEW'' state)
 +  - Select the “Version/Publish” command in the menu or right click to bring up the pop-up menu and select “Publish”. The version will be moved to the ''CURRENT'' state (this may take some time) and displayed in black.
 +
 +<alert type="primary" icon="fa info-circle">
 +**note**
 +
 +before a version is moved to the ''CURRENT'' state the integrity checking of the version is performed. If the version has any integrity problems it will not be published, instead the list of integrity problems will be displayed – see [[2500_config_apps:0200_work_bsv:0500_checking_version_integrity|Checking Version Integrity]].</alert>
 +
 +