Changes
Created page with "Using [[Smart_Studio]], meta data from one {{UBIK}} Environment can be transported into another one. This includes [[MetaClass|Meta Classes]] and their MetaProperty|Meta Pro..."
Using [[Smart_Studio]], meta data from one {{UBIK}} Environment can be transported into another one. This includes [[MetaClass|Meta Classes]] and their [[MetaProperty|Meta Properties]], [[MetaProxy|Meta Proxies]], [[SelectiveList|Selective Lists]] and [[Unit|Units]].
This is useful when a staging strategy is applied in a project, where every feature is quality assured by first being implemented in a Development (DEV) Environment then integrated with other systems in the Integration (INT) Environment and finally, after testing and acceptance, released to the Productive (PROD) Environment.
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/Begin}}<!-- DO NOT REMOVE THIS -->
= Instructions =
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED -->
=== Considerations ===
Before transporting a data model, or meta data, between {{UBIK}} Environments, it is important to consider the following:
* Transporting meta data using SmartStudio is best done in {{UBIK}} 4 and newer, to avoid problems with the Sandbox/Live mode.
* If you don't just transport only once, but continue developing and want to transfer your changes incrementally, you need a development strategy.
* While SmartStudio is capable of merging two different situations, it cannot work out the differences between two situations (at least not in version 4). {{UBIK}} also is no version management system like Git or SVN and does not support several development branches inherently.
=== Development strategy ===
SmartStudio uses [[Smart_Studio#Worksheets|Worksheets]] and [[Smart_Studio#Smart_Projects|Smart Projects]] to store your work. Since, as explained above, you cannot work out the differences between two situations, and {{UBIK}} is no version management system like Git or SVN, you need a good development strategy to avoid serious organizational problems later:
* Develop different features in different Smart Projects. You don't need to have everything in one project.
* Always develop in one direction: From DEV to INT to PROD.
* When transferring a model to another Environment, always perform a [[Smart_Studio#Merging_Worksheets|Merge]].
* Always check the result of a Merge before saving to the Environment.
=== Tools ===
Use the [[Smart_Studio#Inheritance_Graph|Inheritance Graph]] or the [[Smart_Studio#Transport_Container|Transport Container]] to define the models you want to transport. You can use the tools on the left side to [[Smart_Studio#Adding_models_to_a_worksheet|add models to a worksheet]], via Drag & Drop.
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/End}}<!-- DO NOT REMOVE THIS -->
==See also==
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED -->
[[Category:Smart Modelling|Transfer Meta Data between Environments]]
[[Category:Publishing|Transfer Meta Data between Environments]]
[[Category:How-To|Transfer Meta Data between Environments]]
[[Category:FAQ|Transfer Meta Data between Environments]]
This is useful when a staging strategy is applied in a project, where every feature is quality assured by first being implemented in a Development (DEV) Environment then integrated with other systems in the Integration (INT) Environment and finally, after testing and acceptance, released to the Productive (PROD) Environment.
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/Begin}}<!-- DO NOT REMOVE THIS -->
= Instructions =
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED -->
=== Considerations ===
Before transporting a data model, or meta data, between {{UBIK}} Environments, it is important to consider the following:
* Transporting meta data using SmartStudio is best done in {{UBIK}} 4 and newer, to avoid problems with the Sandbox/Live mode.
* If you don't just transport only once, but continue developing and want to transfer your changes incrementally, you need a development strategy.
* While SmartStudio is capable of merging two different situations, it cannot work out the differences between two situations (at least not in version 4). {{UBIK}} also is no version management system like Git or SVN and does not support several development branches inherently.
=== Development strategy ===
SmartStudio uses [[Smart_Studio#Worksheets|Worksheets]] and [[Smart_Studio#Smart_Projects|Smart Projects]] to store your work. Since, as explained above, you cannot work out the differences between two situations, and {{UBIK}} is no version management system like Git or SVN, you need a good development strategy to avoid serious organizational problems later:
* Develop different features in different Smart Projects. You don't need to have everything in one project.
* Always develop in one direction: From DEV to INT to PROD.
* When transferring a model to another Environment, always perform a [[Smart_Studio#Merging_Worksheets|Merge]].
* Always check the result of a Merge before saving to the Environment.
=== Tools ===
Use the [[Smart_Studio#Inheritance_Graph|Inheritance Graph]] or the [[Smart_Studio#Transport_Container|Transport Container]] to define the models you want to transport. You can use the tools on the left side to [[Smart_Studio#Adding_models_to_a_worksheet|add models to a worksheet]], via Drag & Drop.
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/End}}<!-- DO NOT REMOVE THIS -->
==See also==
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED -->
[[Category:Smart Modelling|Transfer Meta Data between Environments]]
[[Category:Publishing|Transfer Meta Data between Environments]]
[[Category:How-To|Transfer Meta Data between Environments]]
[[Category:FAQ|Transfer Meta Data between Environments]]
