Jump to: navigation, search

Difference between revisions of "HowTo:Make an Object appear on the Mobile Client"


 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Publishing an object's data, including its children, properties and documents, requires to build up an [[Application Context Management]].
+
Publishing an object's data via the {{UBIK}} web services, potentially including its children, properties and documents, requires to configure the [[Application Context Management]] (ACM).
  
[[Create a new Application]]
+
=== {{UBIK}} Studio ===
[[Create a new Context]]
+
[[Create a new MetaClassScope]]
+
  
[[Category:How-To]]
+
# Set up web services
 +
# [[HowTo:Create a new Application]]
 +
# [[HowTo:Create a new Context]]
 +
# [[HowTo:Create a new MetaClassScope]] or [[HowTo:Create a new QueryScope]]
 +
# [[HowTo:Create a new View]]
 +
# [[HowTo:Create a new ViewItem]]
 +
# Release the meta definitions
 +
# Restart the {{UBIK}} Content web service
 +
 
 +
 
 +
 
 +
=== {{UBIK}} SmartStudio ===
 +
 
 +
Objects can be shown on the mobile client by configuring a compatible view hierarchy using SmartStudio.
 +
This can be achieved using the Application Graph, connecting a Scope for the object to be shown either as a root 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 object to be available). In both cases, a Scope modelling the look & feel for objects of that type needs to be provided. If the object should be farther down the hierarchy (not a root object), also a connection between the Scopes for the object and its parent object must be provided as well.
 +
 
 +
# Set up web services.
 +
# Configure a view hierarchy in the Application Graph.
 +
## Drop an application and context on the graph.
 +
## Drop scopes on the graph describing the look & feel of the objects on the mobile client.
 +
## Connect the scopes to the context or each other using drag & drop to establish a navigation hierarchy.
 +
# Save the Application Graph to the {{UBIK}} Environment.
 +
# Publish the meta definitions to the {{UBIK}} web services.
 +
# Restart the {{UBIK}} Content web service.
 +
 
 +
 
 +
=== Troubleshooting ===
 +
 
 +
# Check whether the meta definitions were published.
 +
# Check whether the web service was restarted.
 +
# Check whether there is a scope for the object in question.
 +
# Check the visibility of the properties in case they are missing.
 +
# Check whether the object is either a root object, delivered by query or connected to its parent object correctly (scope connection in ACM and reference or relation on content).
 +
# Check for errors displayed on the client.
 +
# Check for errors logged by the web service.
 +
 
 +
=== See also ===
 +
* [[HowTo:Configure_the_ACM]]
 +
 
 +
[[Category:Client|Make an Object appear on the Mobile Client]]
 +
[[Category:How-To|Make an Object appear on the Mobile Client]]
 +
[[Category:Publishing|Make an Object appear on the Mobile Client]]

Latest revision as of 15:40, 20 November 2019

Publishing an object's data via the UBIK® web services, potentially including its children, properties and documents, requires to configure the Application Context Management (ACM).

UBIK® Studio

  1. Set up web services
  2. Create a new Application
  3. Create a new Context
  4. Create a new MetaClassScope or Create a new QueryScope
  5. Create a new View
  6. Create a new ViewItem
  7. Release the meta definitions
  8. Restart the UBIK® Content web service


UBIK® SmartStudio

Objects can be shown on the mobile client by configuring a compatible view hierarchy using SmartStudio. This can be achieved using the Application Graph, connecting a Scope for the object to be shown either as a root 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 object to be available). In both cases, a Scope modelling the look & feel for objects of that type needs to be provided. If the object should be farther down the hierarchy (not a root object), also a connection between the Scopes for the object and its parent object must be provided as well.

  1. Set up web services.
  2. Configure a view hierarchy in the Application Graph.
    1. Drop an application and context on the graph.
    2. Drop scopes on the graph describing the look & feel of the objects on the mobile client.
    3. Connect the scopes to the context or each other using drag & drop to establish a navigation hierarchy.
  3. Save the Application Graph to the UBIK® Environment.
  4. Publish the meta definitions to the UBIK® web services.
  5. Restart the UBIK® Content web service.


Troubleshooting

  1. Check whether the meta definitions were published.
  2. Check whether the web service was restarted.
  3. Check whether there is a scope for the object in question.
  4. Check the visibility of the properties in case they are missing.
  5. Check whether the object is either a root object, delivered by query or connected to its parent object correctly (scope connection in ACM and reference or relation on content).
  6. Check for errors displayed on the client.
  7. Check for errors logged by the web service.

See also