Changes

Smart Studio

895 bytes added, 12:22, 27 July 2023
With {{UBIK}} Smart Studio, project engineering is made easier: Smart Modelling means to build meta models, do programmatic customizing and ACM configurations without having to work all the repetitive details. {{UBIK}} Smart Modelling automates as much as it can in order to give the engineer leeway to actually do the project.
On the Augmensys [[https://release.augmensys.com/download/modules/Studio/ release portal]], a test candidate for the beta version of {{UBIK}} Smart Studio is available. Here's the history of recent changes:
[[Smart_Studio_Beta_History]]
MetaProxies, their properties and their inheritance can be modeled and edited in the [[Meta Proxy Graph]]. A picker displaying all MetaProxies in the project and the {{UBIK}} Environment is available for choosing elements to display in the [[Meta Proxy Graph]] worksheet.
=== Project Smart Import: Comos meta data ===The Smart Model Import Worksheet can be used to import meta data XML files exported from Comos. The input is converted to Smart Models and opened in an Inheritance Graph Worksheet for further processing. One can also plan a semi-automatic import procedure, to make sure the import is processed safely and easily. After configuring the relevant steps, you will be guided through them as planned. Such a plan could be:* Show raw import data* Merge with Project data - Project wins in case of conflict (adjustable)* Save to Project* Merge with Environment data - Environment wins in case of conflict (adjustable)* Save to Environment* Finish importThe user can change the order of steps and switch them on or off.Further, the user can still do any actions manually, too.    === Smart Import: Project model import ===
Sometimes it can be handy for a project engineer to let the customer fill in an Excel sheet listing all the MetaClasses and MetaProperties. The engineer then can extend the Excel configuration with details, including MetaProxies and ACM scope configurations. This Excel map can be imported by SmartStudio, using the Excel/OleDB Project Model Import Worksheet. The result of this import can be saved into the active project or the {{UBIK}} Environment, and inspected in various other worksheets if desired.
An important feature of this import worksheet is the configuration of column mappings (assignment of column names or indexes to something meaningful in UBIK, like the name of a MetaClass) and the automatic detection of erroneous column assignments.
Here's an example for an Excel map that can be imported: [[File:SmartStudio_Excel_Project_Import_Test_Map.zip]]
 
 
===== ''Merging worksheets with the {{UBIK}} Environment'' =====
It is possible to merge a worksheet with the Environment ({{UBIK}} database)using the context menu (right-click on the worksheet) or the respective toolbar icon.
The result is a combination between what you have defined in your worksheet and what the environment contains already regarding that situation.
In case of a conflict, normally the environment "wins". E.g., if you have a meta class A deriving from another meta class B in your worksheet, but the environment specifies C as a parent of A, the result of a merge would be A deriving from C. Using the inspector, you can specify whether a worksheet should override the environment on a merge. In that case, the merge result from the example above would be A deriving from B.
===== ''Merging worksheets with the SmartStudio project'' =====
You can also merge a worksheet with the currently active project, without saving it, using the context menu (right-click on the worksheet) or the respective toolbar icon.
The result is a combination between what you have defined in your worksheet and what the project contains already regarding that situation,
In case of a conflict, normally the project "wins". E.g., if you have a meta class A deriving from another meta class B in your worksheet, but the project specifies C as a parent of A, the result of a merge would be A deriving from C. Using the inspector, you can specify whether a worksheet should override the project on a merge. In that case, the merge result from the example above would be A deriving from B.
The result of such a merge is not saved yet; you can edit it and decide what to do with it - e.g., save it to the project, save it to the environment or dismiss it.
[[Category:Pages with broken file links|Smart Studio]][[Category:Smart Modelling|Smart Modelling]]
==== Cancelling active tasks ====
1,733
edits

Help improve this page!