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
2000_concepts:1000_config_proc:0100_bsv_version_control [2022/08/21 22:47] – ↷ Page moved from docs:2000_concepts:1000_config_proc:0100_bsv_version_control to 2000_concepts:1000_config_proc:0100_bsv_version_control administrator2000_concepts:1000_config_proc:0100_bsv_version_control [2026/08/13 00:57] (current) – ↷ Links adapted because of a move operation localdev
Line 2: Line 2:
 ====== Business Space Versions and Version Control ====== ====== Business Space Versions and Version Control ======
  
-To configure an application is to configure a [[start:2000_concepts:1000_config_proc:helpusingbusinessspace|business space]]. At the end of the day it is the business space that must contain all the configuration elements – business objects, business rules, processes etc. The default business space is created during //**Aware IM**// installation (see the “[[start:1100_installation_guide|Aware IM Installation Guide]]”). This business space is usually the one that represents the application.+To configure an application is to configure a [[2000_concepts:0200_basics:0500_business_space|business space]]. At the end of the day it is the business space that must contain all the configuration elements – business objects, business rules, processes etc. The default business space is created during //**AwareIM**// installation (see the [[:1100_inst_guide|Installation Guide]]). This business space is usually the one that represents the application.
  
 Application configuration is not a trivial process – it involves detailed preparation as the configurator has to collect and analyse requirements of the system and think how these requirements are translated into business objects, business rules etc, and it usually evolves over time as new requirements and new business rules appear or old requirements are changed or become irrelevant. Application configuration is not a trivial process – it involves detailed preparation as the configurator has to collect and analyse requirements of the system and think how these requirements are translated into business objects, business rules etc, and it usually evolves over time as new requirements and new business rules appear or old requirements are changed or become irrelevant.
  
-To help manage changes of a business space //**Aware IM**// includes a built-in version control mechanism. It allows configurators to make and test changes to a business space without affecting the normal operation of the system. When a change to a business space needs to be made a new //[[docs:7000_glossary:business_space_version|business space version]]// must be created and the change must be made in that version. Thus all elements of a configuration are always contained within some business space version. +To help manage changes of a business space //**AwareIM**// includes a built-in version control mechanism. It allows configurators to make and test changes to a business space without affecting the normal operation of the system. When a change to a business space needs to be made a new //[[ref:glossary:business_space_version|business space version]]// must be created and the change must be made in that version. Thus all elements of a configuration are always contained within some business space version. 
  
 With the version control mechanism configurators can also keep track of changes made to the application over time. For example, one can find out which rules and processes were in effect at a particular date and time or what specific information was being registered by the system by inspecting a particular business space version that was current at that time. With the version control mechanism configurators can also keep track of changes made to the application over time. For example, one can find out which rules and processes were in effect at a particular date and time or what specific information was being registered by the system by inspecting a particular business space version that was current at that time.
Line 14: Line 14:
 Most business versions undergo the following lifecycle: Most business versions undergo the following lifecycle:
  
-  - The version is created (either as a blank version or from some base version – see [[start:2000_concepts:1000_config_proc:helpbvversions|Major and Minor Versions]]) in the ''NEW'' state. The configurator makes changes to the version by creating or making modifications to the configuration elements, such as business objects, business rules etc +  - The version is created (either as a blank version or from some base version – see [[2500_config_apps:0200_work_bsv:0400_updating_bsv|Major and Minor Versions]]) in the ''NEW'' state. The configurator makes changes to the version by creating or making modifications to the configuration elements, such as business objects, business rules etc 
-  - Once the configurator is happy with the version she makes it available for testing and the state of the version becomes ''UNDER TEST'' (see [[start:2000_concepts:1000_config_proc:helpbvtesting|Testing Business Space Version]]). At this moment the configurator can test the version in the Operation Mode to verify that the changes work as expected. //**Aware IM**// keeps the version being tested separately from the current operating version, so the testing is not going to disrupt operation activities (see [[#HelpUsingTestingMode|Testing Mode]]). If testing discovers that more changes need to be made to the version the version is moved back to the NEW state and step 2 is repeated. +  - Once the configurator is happy with the version she makes it available for testing and the state of the version becomes ''UNDER TEST'' (see [[2500_config_apps:0200_work_bsv:0600_testing_bsv|Testing Business Space Version]]). At this moment the configurator can test the version in the Operation Mode to verify that the changes work as expected. //**AwareIM**// keeps the version being tested separately from the current operating version, so the testing is not going to disrupt operation activities (see [[2000_concepts:1000_config_proc:0300_testing_mode|Testing Mode]]). If testing discovers that more changes need to be made to the version the version is moved back to the NEW state and step 2 is repeated. 
-  - Once the configurator is satisfied with the version she makes it operational (see [[start:2000_concepts:1000_config_proc:helpbvpublishing|Publishing Business Space Version]]). //**Aware IM**// makes any necessary adjustments and starts using the updated configuration information in the operation mode. The state of the version becomes ''CURRENT''. +  - Once the configurator is satisfied with the version she makes it operational (see [[2500_config_apps:0200_work_bsv:0700_publishing_bsv|Publishing Business Space Version]]). //**AwareIM**// makes any necessary adjustments and starts using the updated configuration information in the operation mode. The state of the version becomes ''CURRENT''. 
   - When some other version is made operational the version becomes ''OBSOLETE''. It can be deleted or kept for historical purposes. It is also possible to return to the obsolete version and make it operational again if for whatever reason the new version has been proven not satisfactory.   - When some other version is made operational the version becomes ''OBSOLETE''. It can be deleted or kept for historical purposes. It is also possible to return to the obsolete version and make it operational again if for whatever reason the new version has been proven not satisfactory.
  
-See also [[start:2000_concepts:1000_config_proc:helpbvlifecycle|Lifecycle of a Business Space Version]]. +See also [[2500_config_apps:0200_work_bsv:0100_bsv_lifecycle|Lifecycle of a Business Space Version]].