Smart Studio - Revision history

NWE at 12:22, 27 July 2023

2023-07-27T12:22:01Z

NWE: /* Merging Worksheets */

2023-07-27T11:21:32Z

‎Merging Worksheets

NWE: /* Project Model Import */

2021-09-29T11:55:24Z

‎Project Model Import

NWE: /* Smart Import */

2021-09-29T11:55:05Z

‎Smart Import

NWE at 11:54, 29 September 2021

2021-09-29T11:54:37Z

NWE: /* Merging Worksheets */

2021-09-13T14:19:00Z

‎Merging Worksheets

NWE at 10:12, 28 September 2020

2020-09-28T10:12:25Z

NWE at 10:11, 28 September 2020

2020-09-28T10:11:23Z

NWE at 15:34, 10 September 2020

2020-09-10T15:34:12Z

NWE: /* Inheritance Graph */

2020-08-14T16:55:41Z

‎Inheritance Graph

@@ Line 1: / Line 1: @@
 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:
+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]]
@@ Line 111: / Line 111: @@
 Further, the user can still do any actions manually, too.
-[[Category:Pages with broken file links|Smart Studio]]
-[[Category:Smart Modelling|Smart Modelling]]
 === Smart Import: Project model import ===
@@ Line 120: / Line 120: @@
 Here's an example for an Excel map that can be imported: [[File:SmartStudio_Excel_Project_Import_Test_Map.zip]]
-[[Category:Pages with broken file links|Smart Studio]]
-[[Category:Smart Modelling|Smart Modelling]]
 == Smart Projects ==
@@ Line 193: / Line 193: @@
 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 ====

@@ Line 179: / Line 179: @@
 ===== ''Merging worksheets with the {{UBIK}} Environment'' =====
-It is possible to merge a worksheet with the Environment ({{UBIK}} database).
+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.
@@ Line 187: / Line 187: @@
 ===== ''Merging worksheets with the SmartStudio project'' =====
-You can also merge a worksheet with the currently active project, without saving it.
+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.
@@ Line 193: / Line 193: @@
 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 ====

@@ Line 114: / Line 114: @@
 [[Category:Smart Modelling|Smart Modelling]]
-=== Project Model Import ===
+=== 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.
@@ Line 120: / Line 120: @@
 Here's an example for an Excel map that can be imported: [[File:SmartStudio_Excel_Project_Import_Test_Map.zip]]
 == Smart Projects ==

@@ Line 100: / Line 100: @@
 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.
-=== Smart Import ===
+=== 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
@@ Line 110: / Line 110: @@
 The user can change the order of steps and switch them on or off.
 Further, the user can still do any actions manually, too.
 === Project Model Import ===

@@ Line 100: / Line 100: @@
 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 Model Import Worksheet ===
+=== Smart 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.
@@ Line 177: / Line 188: @@
 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 ====

@@ Line 158: / Line 158: @@
 Worksheets can originate from an import, from the project or from the environment.
-Wherever it might have came from, you can save the worksheet content to either the project or the environment.
+Wherever it might have come from, you can save the worksheet content to either the project or the environment.
 However, in some cases the worksheet content needs to be combined with what you already have in order to resolve conflicts.
@@ Line 176: / Line 176: @@
 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.
 ==== Cancelling active tasks ====

@@ Line 52: / Line 52: @@
 Create a new proxy by dropping a meta class onto the proxy graph.
 See the respective chapter for the meta proxy graph.
 === Application Graph ===
@@ Line 91: / Line 80: @@
 Queries can be designed using the Bulk Editor. You can use the context menu command "Convert to Query" in order to create a query for the meta class the bulk editor currently shows instances for. Then you can add Query Items by holding the {{key press|shift}} key while dragging column headers onto the query on the top left. The query items appear next to the query and can then be configured.
+{{UBIK}} SmartStudio provides rich code editors supporting IntelliSense and syntax highlighting based on Roslyn. For MetaClass related customizing, you can access such editors using the Behavior inspector tool (on the right hand side if you're using the default layout), when a MetaClass is selected in the Inheritance Graph. The custom code library can be maintained using a dedicated worksheet accessible via the "Behavior" menu.
 === Relation Target Bulk Editor ===

@@ Line 53: / Line 53: @@
 See the respective chapter for the meta proxy graph.
+{{UBIK}} SmartStudio provides rich code editors supporting IntelliSense and syntax highlighting based on Roslyn. For MetaClass related customizing, you can access such editors using the Behavior inspector tool (on the right hand side if you're using the default layout), when a MetaClass is selected in the Inheritance Graph. The custom code library can be maintained using a dedicated worksheet accessible via the "Behavior" menu.
 === Application Graph ===
@@ Line 73: / Line 81: @@
 Further, you can configure how the children should be resolved for a scoped connection - should a relation be used, or a link property on a child pointing to the parent object?
 For query scopes, the outgoing connections are a bit simpler, because they can only target scopes that are compatible with the query filter class, and since the query delivers the children, there isn't much to configure there. For meta query scopes, no outgoing connections are shown because we cannot anticipate what query will be used at design time. However, if you provide a fitting child scope to the context, it will be used for the children of queries.
 === Bulk Editor ===

@@ Line 30: / Line 30: @@
 === Inheritance Graph ===
 There are multiple kinds of modelling worksheets with different responsibilities: The [[Inheritance Graph]] allows the user to create meta models. It's called "Inheritance Graph" because the MetaClasses' inheritance structure is displayed graphically.
 === Application Graph ===