Changes

Objects can be shown on the mobile client by configuring a compatible view hierarchy using SmartStudio. This can be achieved using the Application Graph, and connecting a Scope for the object to be shown either as a root object scope to the Application Context(requiring a root object Query delivering the object in question), or as a child to another Scope (requiring a parent objectto be available). In both cases, a Scope modelling the look & feel for objects of that type needs to be provided. In If the latter caseobject should be farther down the hierarchy (not a root object), also a connection between the Scopes for the two types of objects object and its parent object must be provided as well.

Step-by-step, this is how you achieve that starting from scratch: # Make sure there are Configure a {{UBIK}} Environment including a database and functioning web services, as well as a content object you want to show on view hierarchy in the mobile client.# Open a new Application Graph worksheet.# Add a Application by dragging it into the worksheet from a picker (existing Apps) or the toolbox (new App).# Add a Context by dragging it into the worksheet from a picker (existing Contexts) or the toolbox (new Context).# Connect the Context to the Application by dragging a connection between the two.# In order to support the object you want to make appear on the mobile client, add a Scope by dragging a compatible MetaClass into the worksheet from a picker (existing MetaClasses) or the toolbox (new MetaClasses). Such a Scope is a configuration for all instances of the respective MetaClass delivered to the mobile client. # Configure the Scope by adjusting the access rights for its MetaProperties.# Connect the Scope to the Context. This means, instances of the scoped MetaClass will be presentable as root objects (first navigation level on the mobile client).# You can add further Scopes to Save the Application Graph and connect them by dragging a connection between two of them. This means, instances of the right-hand scoped MetaClass will be presentable in the hierarchy level below the left-hand scoped MetaClass' instances.# Configure the connections (i.e., View Items) by choosing the way the instances are actually connected to each other (selecting a relation or link property). This means that for an instance of the left-hand scoped MetaClass, the configured link property or relation will be used to find instances of the right-hand scoped MetaClass to be listed as children of the first instance on the mobile client.# Configure a root Query for the Context by dragging a Query into the worksheet from a picker (existing Queries) or the toolbox (new Queries), and connecting it to the Context, using its root objects input connector. This means, the query finds all instances to show on the root level of the app. The Context must have a compatible scope connected to it in order for the instances to be displayed correctly.# If you want an object to be shown as the child of another on the mobile client, use a relation or link property to connect the two. This relation or link property can then be configured in a connection between two compatible Scopes.# Save the application graph to the desired {{UBIK}} Environment, using the menu bar or context menu.# Release Publish the meta definitions in to the Environment worksheet{{UBIK}} web services.# Restart the {{UBIK}} web services.