Changes

HowTo:Configure the ACM

2,446 bytes added, 15:00, 20 November 2019
# Create a new project or open an existing one.
# If necessary, design new Meta Classes (for objects to provide to the client) using the Inheritance Graph or connect to a {{UBIK}} environment (database) and use the Meta Classes defined there.
# Make sure there are a {{UBIK}} Environment including a database and functioning web services, as well as a content object you want to show on the mobile client.
# Open a new Application Graph worksheet.
# Create Add a Application and by dragging it into the worksheet from a picker (existing Apps) or the toolbox (new App), available to the left of the worksheet area.# Add a Context objects and connect themby dragging it into the worksheet from a picker (existing Contexts) or the toolbox (new Context), available to the left of the worksheet area.# Use drag & drop Connect the Context to define Scopes for previously created Meta Classes 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), available in pickers on to the left sideof the worksheet area. 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 the Application Graph in the same manner.# Connect the Scopes in order to define the hierarchy. Also Instances of the right-hand scoped MetaClass will be presentable in the hierarchy level below the left-hand scoped MetaClass' instances.## Scope connections can be established by dragging connections between the output connector of the parent Scope and the input connector of the child Scope.## Configure the connections by choosing the way the instances are actually connected to each other (selecting a relation or link property). 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.## 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.# Connect at least one Scope to the Context as a child. Instances of the scoped MetaClass will be presentable as root objects (first navigation level on the mobile client).# If necessary, define queries Configure a root objects Query for the root Context by dragging a Query into the worksheet from a picker (existing Queries) or the toolbox (new Queries), available to the left of the worksheet area, and infrastructure objects and connect them connecting it to the Context as , using its root objects input elementsconnector. 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.# Make sure the target {{UBIK}} environment Environment is connected.# Save the new Application Graph application graph to the desired {{UBIK}} environment (database) Environment, using the context menu bar or the context menu bar above the worksheet area.
# Open the {{UBIK}} environment page and select the ACM management sub-section.
# Publish Select the relevant Application and Context, and assemble and publish the Meta Definitions.
# Restart the {{UBIK}} web services.
# Test the results using any {{UBIK}} satellite.
 
 
 
 
 
=== {{UBIK}} Studio ===
# Restart the {{UBIK}} web services.
# Test the results using any {{UBIK}} satellite.
 
 
 
 
1,606
edits