Changes
/* Inheritance Graph and Application Graph */
Sometimes, you don't want to design a data model but instead take it from one {{UBIK}} Environment to another, or to control in detail what you want to save to a target {{UBIK}} Environment. This is what the [[Transport Container]] is for. This worksheet (like the project view) features a [[Situation Editor]] giving you a detailed overview about the models it contains as well as the possibility to add or remove models, and to select a subset of the contained models and do something with it (e.g., retain only the selected models).
=== Inheritance Graph and Application 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 ===The [[Application Graph]] can be used to define what the user can see on the mobile device. It's called "Application Graph" because the browsing hierarchy for the mobile application is displayed graphically. One can define specific mobile versions of MetaClasses (namely Scopes) as well as their properties and children with it. ==== App and Context ====You can create or reuse app and context objects to identify the view providing data to your satellites. Below a context, you can model the view hierarchy graphically using scopes and connections between them.The context can be configured with input queries for the root and infrastructure objects. Just drag a query onto the graph and connect it to the context's respective input connector. ==== Scopes ====A scope specifies what properties for instances of a meta class will be delivered to the satellite. E.g., for pumps we might have many properties in the data base, but on the client, we require only two of them - this can be specified using meta class scopes. You can specify whether it should be possible to create or delete instances on the scope.However, you can also use query scopes to provide an interface to a query object on the client. In order to create a query scope, hold {{key press|Shift}}) while dragging a query onto the graph. Drop meta properties on a scoped query in order to provide access to the query's properties and query items.Meta query scopes are supported as well; dropping a query meta class on the graph will result in a respective scope. ==== Connections ====In the app graph, scopes can be connected hierarchically, in order to specify: "As children for scope-A-objects, I want to see scope-B-objects".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. [[Category:Pages with broken file links|Smart Studio]][[Category:Smart Modelling|Smart Modelling]]
=== Bulk Editor ===
